Skip to content

Cortex 4.14.0 — schema-migration entry point + wiki.pages↔FS parity

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Jul 16:20
v4.14.0
da3f210

Added

  • Standalone schema-migration entry point — python -m mcp_server.migrate. Brings a PostgreSQL store's schema current by reusing PgMemoryStore's existing hash-gated, advisory-lock-serialized DDL apply path (no duplicated DDL, no MCP server boot). Frozen contract, consumed by the cortex-viz plugin: DATABASE_URL=<url> python -m mcp_server.migrate → exit 0 (schema up to date | applied N statements) / exit 1 (one-line stderr reason). cortex-viz 2.6.1's open_visualization preflight invokes it to migrate an outdated store before building the graph — replacing the previous silently-empty-graph failure on an old schema with either an automatic migration or an actionable support message.
  • wiki_migrate MCP tool + wiki.pages↔filesystem reconciliation — backfill, ghost purge, and a parity guard keep the wiki.pages table and the on-disk wiki in sync. Standalone tool count 49 → 50 (53 with upstream integrations).

Fixed

  • wiki.pages pages_status_check widened to the full system-emitted status union.

Verified (pre-tag guard, exact release tree)

  • LongMemEval-S: MRR 0.9166 / R@10 0.982 (reranker active) — exact match to the 4.13.3 reference.
  • LoCoMo (3-run mean): MRR 0.8005 / R@10 0.9131 — matches the 4.13.3 baseline (0.8017 / 0.9152) on identical, retrieval-orthogonal code; both gated floors PASS.
  • BEAM-100K: 0.5471. Raw results committed under benchmarks/results/repro/20260713-v4.14.0-pretag/.

Pairs with cortex-viz 2.6.1.

Assets 2
Loading