docs(remediation): bank D-44 — the anti-inert-gate registry was inert-able four distinct ways

rev-974 NO-GO at 83d2ecb2. A4/A5/A6 confirmed and three further blockers found, two of them outside my
registered set. Each is a silent-defeat path of the registry itself: the activation seam inerts the
history audit (seam=HEAD gives 0 prospective commits and no failures — and HEAD's parent and the
introduction commit also pass, so forbidding equality with HEAD does not close it); a misspelled
outputPattern silently reduces an assertion to exit-code-only because the closed schema is not
recursive; two provider records sharing pipeline number 7 certify two different commits; and the D-38
and D-40 criteria are absent, with blocker 4 a live instance of the very D-38 clause that is missing.

The headline: all four passed CI, passed the canonical gate:verify, and passed 38/38 focused tests.
Greens discharged nothing. My own AC set was incomplete too — A3 corrects the prospective range to
eight commits, not the seven I wrote; I omitted the seam commit itself.

Mos ruled ALL FOUR in this PR, no trim, and sizing does not help: a registry that ships with a known
way to be silently defeated IS the inert gate it exists to detect. There is no core registry that is
integrity-complete without these — they are not hardening on top of the deliverable, they are the
deliverable. Theme: the registry's own checks must not be silently defeatable. Each fix carries a
red-first must-fail control proving the specific defeat is now caught, and that control set IS the
D-38/D-40 coverage work rather than being additive to it.

Blocker 1's fix keeps the value and replaces the mechanism: derive the seam from non-author-controlled
history (parent of the first first-parent commit introducing gates/gates.manifest.json) rather than
asserting it in an author-editable field, plus must-fail controls for HEAD, HEAD's parent, and the
introduction commit. If the work balloons past reviewability the only acceptable split is by
integrity-complete stage, never by deferring a blocker.

Method note banked as a positive: I could not reproduce "full verifier exit 0", traced my first attempt
to my own instrumentation artifact (json.dump reformatting the manifest), and stated the divergence
rather than wielding non-reproduction as a refutation. The vacuity itself reproduced and blocker 3 was
confirmed by construction. Non-reproduction is not refutation. Open thread: why my gate:verify exits 1
on checkout-preflight with outcome 42.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>

docs/remediation/TASKS.md

@@ -558,6 +558,56 @@ claims from the provider**, not merely confirming the file parses or that a succ
 > orchestrator does so before dispatch; **the coordinator does so before acting on or relaying a board
 > claim that gates a decision** — Mos noted he had relayed board-derived state to Jason all session.
 
+### D-44 — the anti-inert-gate registry was inert-able FOUR distinct ways, and every green missed all four
+
+`rev-974` @ `83d2ecb2`, **NO GO**. Each finding is a **silent-defeat path of the registry itself**:
+
+| #   | defeat path                                                                                                                                                                                                         | status                                         |
+| --- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
+| 1   | **The activation seam inerts the history audit.** `seam=HEAD` ⇒ 0 prospective commits, `failures: []`, verifier exit 0. **HEAD's parent** also exits 0 covering only HEAD; the **introduction commit** omits itself | A4/A5/A6 **CONFIRMED**                         |
+| 2   | **D-38 and D-40 criteria absent** from the manifest ⇒ whole failure modes uncovered, no bound must-fail cases                                                                                                       | ruled in-scope, missing                        |
+| 3   | **The "closed schema" is not recursive.** `outputPattern` → `outputPatern` ⇒ structure check AND full verifier both exit 0, assertion silently reduced to exit-code-only                                            | orchestrator confirmed by construction         |
+| 4   | **Provider evidence is not subject-bound.** Two records sharing pipeline number `7` certified **two different commits** — uniqueness is checked only AFTER filtering by commit                                      | a **live instance of the missing D-38 clause** |
+
+**★ THE HEADLINE: every one of these passed CI, passed the canonical `pnpm gate:verify`, and passed
+38/38 focused tests. Greens discharged NOTHING.** All four were found by mutating things nobody had
+registered a check for — **two of them outside the orchestrator's registered set**, which is D-17 again
+(a set is a floor, never a ceiling). The reviewer-beyond-the-set is the current backstop; the
+registry's own coverage clause is what will eventually mechanise it.
+
+**The orchestrator's AC set was also incomplete:** A3 corrected the prospective range to **eight**
+commits, not seven — `83d2ecb2` (the seam commit itself) was omitted.
+
+> **★ SCOPE RULED — ALL FOUR IN THIS PR, NO TRIM (Mos, 2026-08-01), and sizing does not help:**
+> **a registry that ships with a known way to be silently defeated IS the inert gate it exists to
+> detect.** There is no "core registry" that is integrity-complete without these — **they are not
+> hardening on top of the deliverable, they ARE the deliverable.** This is the one place in the mission
+> where _"it works except for these known holes"_ is **disqualifying by definition**, because detecting
+> exactly those holes is the product.
+>
+> Theme: **"the registry's own checks must not be silently defeatable."** Each fix carries a RED-FIRST
+> must-fail control proving the specific defeat is now **caught**. That control set **IS** the
+> D-38/D-40/coverage clause work — **not additive to the ruled scope; it is that scope made real.**
+>
+> **Blocker 1's cheap fix is dead:** forbidding `seam == HEAD` does not close it, because HEAD's parent
+> and the introduction commit also pass. The value must be **DERIVED from non-author-controlled
+> history** (parent of the first first-parent commit introducing `gates/gates.manifest.json`) —
+> computed, not asserted in an editable field. **Keep the value (A1 confirmed it right); fix the
+> mechanism.**
+>
+> **If it balloons past reviewability, the ONLY acceptable split is by INTEGRITY-COMPLETE STAGE — never
+> by deferring a blocker.** A stage that ships a known silent-defeat path is not a stage.
+
+**This NO-GO is the keystone being forged, not failing.** It lands hardened against its own failure
+modes, which is the only thing that makes it a registry rather than a manifest.
+
+**Method note banked as a positive (Mos):** the orchestrator could **not** reproduce "full verifier exit
+0", traced its first attempt to its **own instrumentation artifact** (`json.dump` reformatting the
+manifest), and **stated the divergence rather than wielding non-reproduction as a refutation** — the
+vacuity itself reproduced, and blocker 3 was confirmed by construction, which needs no environment.
+**Non-reproduction is not refutation.** Open method thread, not a blocker: why the orchestrator's
+`gate:verify` exits 1 on `checkout-preflight` with outcome 42 (bubblewrap class).
+
 ### PRE-POSITIONED DISPOSITION — RM-02's activation-seam question (A4/A5/A6), ruled BEFORE the verdict
 
 > **Status: OPEN — the verdict belongs to `rev-974`'s independent A4/A5/A6, not to anyone's guess.**