Continuous Verification Pipeline Repaired, Registry v2.10

Every push to the SpeyBooks repository runs a set of static verification gates, mirroring checks that already run on every deploy. One of those repository-side gates was misconfigured from the day it was introduced: its scan was so broad that it flagged correct code, which meant the pipeline reported failure on every run and the gates behind it never executed.

• Repository verification now runs end to end The misconfigured gate was rebuilt with a precisely scoped rule set and validated against planted test cases in both directions — it catches the violations it exists to catch, including a variant the original scan missed, and stays silent on correct code. The gates behind it now execute on every push, and the pipeline is being made a required check so a failure can never again go unnoticed.

• One genuine issue class found and fixed The rebuilt gate surfaced five instances of a single internal pattern: queries supporting the migration wizard selected a record using creation timestamps rather than the ledger’s canonical ordering — including one variant the original scan could never have seen. In practice every instance always selected the same record, and no stored data is affected; all five now use the canonical axis, removing the theoretical ambiguity.

The deploy-side verification that guards every production release was never affected and has passed throughout — this work brings the repository-side mirror up to the same standard.

Versioning

Kernel axiom registry → v2.10. No API surface changed and no application behaviour changed for any request.