Upgrades

Upgrading the binary, the storage format and cached compilation output.

1. Read the newest devlogs and RFC status for changes that affect your workspace.
2. Build the new binary; keep the old one until you have verified.
3. Run ekos doctor and ekos config validate — unknown config sections are rejected.
4. Run the pipeline. The build fingerprint includes the pipeline's logic version, so changed analyzers reprocess automatically; no manual .ekos wipe is needed.
5. If a read-only client (MCP server) reports "search index schema is stale", run ekos ledger repair once.

Storage format migration

An existing SQLite workspace is never migrated automatically. Migrate a copy first and compare ekos status before and after.

Cached output

A CompilerPass skipped as cached uses its version and inputs. If an upgrade changes a pass without bumping its version, clear with ekos clean and rebuild.