docs: replace APIs that never existed, unpin the install, resync to 1.4.1
The wiki had drifted past staleness into fiction. Verified every claim against
the 1.4.1 source and the published package rather than the previous revision.
Plugin Authoring documented an API with no referent: `CortexPlugin`,
`CortexInstance` and `CortexEngine` appear nowhere in the engine, and the
registration example constructed a class that does not exist. The real contract
is a default-exported `{ name, tools }`, with handlers taking `(args, ctx)`.
Rewrote both examples against `ToolPlugin` / `ToolDefinition` / `ToolContext`,
including the required `category` and `whenToUse` fields the old sample omitted.
The result typechecks against @fozikio/cortex-engine@1.4.1 from npm.
Deployment told operators to hand-roll a Hono wrapper around that same
non-existent class. The engine has shipped its own REST server since 1.3.0
(`serve --rest`, or the exported `startRestServer`), so the wrapper was both
broken and unnecessary. It also imported the unscoped `cortex-engine` — the
same wrong-package trap fixed elsewhere in July, still live here.
MCP Integration pinned `@fozikio/cortex-engine@1.3.0` in all three client
configs. That pin is why new installs silently landed on an old engine; it was
last corrected in July and had gone stale again by 1.4.1. Removed it entirely
rather than bumping, so it cannot rot a third time.
Tool count was 59 everywhere; the engine registers 60. `evolution_resolve`
arrived in 1.4.0 and was never documented — added, and the journal section
count corrected to match.
CLI Commands still described the pre-1.4.0 flat layout, omitting `up`, `down`,
`status`, `doctor`, `dashboard`, `update` and the whole `service` subtree.
Rewrote it around the noun-verb tree, noting the flat forms survive as aliases.
docs: correct stale install commands, tool counts, and deprecated plugin guidance
The wiki had drifted badly from the shipped engine (v1.3.0):
- Install commands used the UNSCOPED 'cortex-engine' package, which is now
only a deprecation stub on npm. The .mcp.json examples pinned
'cortex-engine@0.6.0' — a version that genuinely still resolves, so anyone
following the wiki got engine 0.6.0 instead of 1.3.0. Now scoped
@fozikio/cortex-engine, pinned to 1.3.0 in the MCP examples.
- Tool counts were wrong in three places: Quick-Start said 25, Tool-Reference
said 57, MCP-Integration said 25. Verified against createTools() in the
built engine: 59.
- Tool-Reference listed the same tools twice — once under 'Core' and again
under '@fozikio/tools-*' plugin headings — and told users to install those
packages. They were absorbed into core at v1.0.0 and are frozen/unmaintained
on npm. Rewritten against the engine's own 13-category taxonomy.
- FAQ/MCP-Integration/Quick-Start told users to npm install the deprecated
tools-* packages; replaced with the real mechanism (per-namespace config).
- MCP-Integration's 'core tools' table now matches CORE_TOOLS exactly (12).
- CLI list was missing migrate, tools, and nli.
Counts and command lists verified against a clean clone + build of master,
not from the old docs.
docs: update wiki for SQLite defaults, reflex CLI, npx fozikio init
- Installation: SQLite + built-in embeddings as defaults, no cloud needed
- Quick Start: npx fozikio init flow, CLI commands, reflex validation
- MCP Integration: simplified config, plugin auto-discovery, agent scoping
- Configuration: agent.yaml reference, storage/embed comparison tables
- FAQ: updated for local-first defaults, reflex rules, plugin list
- Architecture: SQLite alongside Firestore, reflex in diagram
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
docs: initialize wiki with 10 pages
Home, Installation, Quick Start, Architecture, Plugin Authoring,
MCP Integration, Deployment, Tool Reference, Configuration, FAQ
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>