Land the Gate A acceptance matrix and its two missing tickets

[MongLong0214]

ADR-0020/0021/0022 and PRD-F9 cite a "CTO acceptance matrix" (P0-1..P0-8, P1-5) as authority. It never existed as a file. docs/GATE-A-ACCEPTANCE.md reconstructs each row from its actual citation site — not from a recovered original — and states that distinction explicitly, including the one grep (git log -p --all) that would disprove it. I ran that grep before committing; nothing was missed.

Two rows had no closing ticket:

• P0-4 — the P0-3 capture architecture proven end-to-end. Every existing ticket's AC is unit-level; nothing runs the real CLI/MCP/Git chain together. T-1023 adds it.
• P0-7 — no prior citation anywhere. Named from an operational gap: PRD-F9's 14 requirements never mention removing a pending file, and prepare writes one on every attempt including empty verifications. Nothing deletes it. T-1019 adds recovery/GC. The T-1018→T-1020 and P0-6→P0-8 numbering gaps are noted as circumstantial, explicitly not claimed as evidence.

Also: T-1007/T-1008/T-1009/T-1020 all edit src/mcp/server.ts and had no complete ordering between them (T-1009 depended on two of the three; T-1020 depended on neither). Each now states the merge order.

Not touched: ADR-0020/0021/0022, PRD-F9/F10, or the #193-213 issue bodies. They already meet the source review's own bar (exact ownership, forbidden scope, RED/GREEN, AC-to-test, four-tier verification) — rewriting them would be churn, not correction.

npx tsc -p tsconfig.json --noEmit exits 0.

[github-actions]

CommitLore — record lint

Trailers: clean — 1 commit in origin/dev..45a8f2b9eb1c6b4720744e0b5b61078df71632c7
Active constraints: 3 limits · 8 ruled-out · 4 warnings — from 6 records over 4 changed paths

Active constraints for the paths this PR touches

Limits (3)

• r-gateaacc 45a8f2b — nothing enforces the src/mcp/server.ts merge-sequencing rule automatically — it is a process constraint the next PR author has to read and follow
• r-c0f4e2 3d249cd — npm gitlore is held by an active same-domain CLI, so the owner's first-choice name was not available
• r-a8f3c1 ef48843 — Rename must land before any code exists -- after 27 tickets it would touch spec, fixtures, index, hooks and every doc

Ruled out (8)

• r-gateaacc 45a8f2b — rewriting ADR-0020/0021/0022 or the existing T-1001 · Pending transaction store #193-213 issue bodies | they already meet or exceed the source review's own requirements (exact ownership, forbidden scope, RED/GREEN, AC-to-test, four-tier verification, evidence invalidation, stop conditions); rewriting working documents to match a stale review would be pure churn
• r-gateaacc 45a8f2b — inventing content for a hypothetical P0-7 original definition | none exists in history (verified); asserting one would be the exact failure this document exists to prevent
• r-3b57e2 30f2d5f — converting the three translated READMEs for consistency | they are the product, not the record, and two checks exist specifically to keep them
• r-c0f4e2 3d249cd — GitLore published as git-lore | the binary and search results still collide with the existing gitlore tool
• r-c0f4e2 3d249cd — keep Annals | the sound problem does not decay, and with code near zero this is the cheapest moment the project will ever have
• r-c0f4e2 3d249cd — rename code and spec first, documents later | the drift window makes every artifact written in it wrong
• r-a8f3c1 ef48843 — keep name, change vocabulary only | vocabulary is the protocol, so half the change leaves the substance untouched
• r-a8f3c1 ef48843 — drop Certainty as a dead field | a real route exists -- stale sweep prioritizes guess-level records for review

Warnings (4)

• r-3b57e2 30f2d5f (claim) — bench/PREREGISTRATION.md is append-only and was translated in place. Its section numbering and order are unchanged, but a translation is still an edit to a file whose whole discipline is that it is not edited. Recorded here rather than left to be noticed
• r-c0f4e2 3d249cd (claim) — ADR-0008 and ADR-0009 keep the literal string Annals on purpose -- mechanical substitution there destroys the decision trail
• r-c0f4e2 3d249cd (claim) — the residual grep for lore_query reports a false positive because commitlore_query contains it as a substring, so check the prefix
• r-a8f3c1 ef48843 (claim) — docs/adr/ADR-0008 is the canonical vocabulary -- do not reintroduce old terms from memory

git log --follow accepts exactly one pathspec, so renames are not followed for 4 paths; query one path at a time to follow its rename chain

_{Trailer violations fail this check. Active constraints are informational — they are what the repository already decided, not a verdict on this PR.}