Docs advisory: the wiki was pinning an old engine version (0.6.0) — please re-check your install

[idapixl]

A docs audit today found that our GitHub wiki had drifted from the shipped engine. The README was correct, but the wiki was not — and the wiki had never been audited before. Apologies.

If you set up cortex from the wiki, check your version

The wiki's .mcp.json examples pinned the unscoped package at an old version:

"args": ["-y", "cortex-engine@0.6.0"]

Unscoped cortex-engine is now only a deprecation stub — but 0.6.0 still resolves, so this silently installed engine 0.6.0 instead of 1.3.0. That predates the v1.0.0 tool absorption and the SQLite-by-default change, so a lot of documented behaviour simply wouldn't match.

Check what you actually have:

npm ls @fozikio/cortex-engine cortex-engine

The correct config is the scoped package:

"args": ["-y", "@fozikio/cortex-engine@1.3.0"]

Or just let npx fozikio init generate it — it's version-pinned and platform-aware.

Also corrected

• Tool count. Three pages disagreed (25, 57, 25). The real number is 59, verified against createTools() in a clean build.
• The @fozikio/tools-* packages are deprecated. They were absorbed into core at v1.0.0 and are frozen on npm. Several wiki pages still told you to npm install them — that adds nothing. All 59 tools ship inside the engine; 12 are active by default and the rest are enabled per-namespace:

npx fozikio tools     # list every tool by category
npx fozikio config    # choose which are active

• Tool Reference listed every tool twice (once as core, again under plugin headings). Rewritten against the engine's own category taxonomy.
• CLI reference was missing migrate, tools, and nli.

Third-party plugin authoring is unaffected and still supported.

The Quick Start, Installation, MCP Integration, Tool Reference, FAQ, and Deployment pages are all updated.

If something still looks wrong, please reply here.