Gergo Magyar ceca5c9614 fix(storage): renumber schema versions to 38/34 after an exact collision on main (#2766) ... `main` landed Spring AOP (#2416) with SCHEMA_BUMP 37 and INCREMENTAL_SCHEMA_VERSION 33 — exactly the numbers this branch already used. Every prior instance in this series was a near-miss, where main took a number below or beside this branch's. This one is an exact clash: two incompatible schemas both claiming 37/33, so an index built by either would satisfy the other's freshness check while carrying content it cannot read. Renumbered to 38/34 and merged both changelog notes rather than replacing main's. Extended the reuse-gate test so v33 is asserted to FAIL the gate — a v33 index carries receiver chains in wire format v1, which the v2 decoder refuses by design, and an incremental top-up would silently fall back to the text cascade for every chain-carrying site. Re-verified after the rebase, not before: 4424 tests and all eight CI benches green against the new base. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>		2026-08-01 16:43:09 +00:00
..
fixtures	test(golden): reconcile the python capture golden after rebase (#2766)	2026-08-01 16:28:36 +00:00
helpers	fix(test): harden findInstalledFtsExtension for cross-OS filesystem quirks	2026-07-21 06:14:58 +00:00
integration	fix(go): drop the phantom read site on a member call's callee (#2766)	2026-08-01 16:28:34 +00:00
unit	fix(storage): renumber schema versions to 38/34 after an exact collision on main (#2766)	2026-08-01 16:43:09 +00:00
utils	fix(hook): emit MCP query hint when server owns DB lock (#2396) (#2397)	2026-07-08 18:34:05 +01:00