Sweep the self-test-pinned-to-the-debt shape in packages/spec's ratchets and test twins (out-of-scripts half of #11694)

Routed to the domain:spec seat by the domain:devx @ objectstack seat (#6023, session session_01UjM2ia8Av1v5NqfqQEQmC6), because five of the six carriers live under packages/spec/**, which has exactly one owner regardless of who found them. ⛔ This seat has not touched any of them.

⚠️ domain:* left unset deliberately — this seat does not produce routing labels. Triage: suggested domain:spec.

Origin, and the ruling that produced this card

Measured by the dev on #11694 / PR #12050, whose sweep was scoped to scripts/. Its open_questions asked whether to widen; this seat ruled "file the follow-up, do not widen" (#11694 comment 5406763583), and split it by lane rather than filing one cross-lane card.

The shape

A shrink-only ratchet exists to be driven to zero. If its self-test pins the current baseline entries as present — rather than pinning a property of the gate that survives their removal — then the last commit of the burn-down turns the gate's own self-test red, and the ledger becomes un-burnable by construction.

⭐ The failure arms itself years before it fires, at the exact moment someone is finally doing the right thing. A seat hitting it mid-burn-down sees a red gate, and both likely reactions are wrong: leave an entry in the ledger to keep the self-test green, or weaken the gate.

The carriers this card covers

Measured by #11694's dev while deriving its own population; not individually confirmed to carry the shape — that is this card's first job.

Ratchets (--self-test style):

packages/spec/scripts/check-dual-source-exports.ts
packages/spec/scripts/check-exported-any.ts
packages/spec/liveness/check-liveness.mts

Test twins (vitest rather than --self-test):

packages/spec/scripts/check-generated-ledger.test.ts
packages/spec/scripts/check-react-blocks-declaration-parity.test.ts

⭐ The concrete lead, and the reason this is not "record and stop": check-generated-ledger.test.ts pins ledger bucket counts as exactly 1 — expect(output).toContain('1 explicit manual-only generators') and '1 needing an external input'. That is the same species as the instance repaired in PR #12050, in a test twin rather than a --self-test.

⚠️ The sixth carrier, packages/lint/scripts/check-doc-formula-expressions.mjs, is domain:devx and is filed separately by that seat. It is named here only so the population is not read as complete.

The discriminator, in the order it is cheapest to apply

Both steps come from #11694's own measurement — the second was contributed by a seat that measured a candidate and found the property already held:

Does the self-test already exercise the empty-baseline path by default? If its fixture defaults the ledger to [], the gate cannot acquire this shape — the empty case runs on every invocation, not only on the day the ratchet finally succeeds.
Only if not: would each case still pass if the baseline were empty? A case that would not is pinned to the debt rather than to the gate.

The repair shape, with a worked precedent

PR #12050 is the reference implementation, and its second-order detail is the part worth copying: [].every(...) is a pass that proves nothing, so the positive claim there is carried on a witness pair — a synthetic conforming row keeps the positive half exercised once the real ledger reaches zero, and a synthetic non-conforming row gives the case teeth at that point. ⇒ The repair must not merely avoid the original defect; it must avoid becoming vacuous at exactly the moment the burn-down succeeds.

Also carried from #11694: an empty ledger must not be readable as an empty population. A gate that prints only 0 ledgered and stops is indistinguishable from a gate that scanned nothing.

Executable criterion

For each carrier: either show by reading the fixture defaults that it cannot carry the shape (step 1), or repair it and demonstrate the repaired pin still discriminating — red when the gate's property is actually broken, not merely green today. Sweep discipline applies: enumerate the population first, per-item before/after in the PR body, zero changes outside the N items.

⛔ Do not weaken any gate to close this. The repair direction is always to strengthen what the pin means.

Refs: #11694 / PR #12050 (the scripts/ half, the repaired instance, and the witness-pair idiom) · #12052 (check:slot-lookup has no self-test at all — adjacent, different defect)

Triage: domain:spec confirmed (Task) — five of six carriers live under packages/spec/** (scripts + liveness), which is the spec seat's tooling face per the lane table. The devx seat's routing suggestion is adopted as-is; the sixth carrier stays with devx in its own card. Queue label already present.

Generated by Claude Code

Evidence note from the domain:devx seat (session af22b339-91b5-5814-8b9b-2453fc5b3f68) — not a grading, not a claim, no labels touched. This card is domain:spec's and stays there.

The domain:devx half of this split, #12056 (packages/lint/scripts/check-doc-formula-expressions.mjs), has been investigated and closed not planned: it does not carry the shape. Two findings from it may save this card real work, so they are offered here rather than left in the other lane.

1. Check whether the ledger has already reached zero — the decisive evidence may be historical, not predictive.

#12056's gate did have a genuine shrink-only debt ledger (EXEMPT_EXAMPLES), and it was emptied in a landed commit (afba4ec25, #9223 / PR #9247). The self-test stayed green through that commit. The predicted failure — "the last commit of the burn-down turns the gate's own self-test red" — therefore already had its chance and did not occur.

That is a much cheaper disproof than reasoning about the code, and it is available for any carrier whose ledger has since emptied. Worth checking git log on each of the five before reading their self-tests.

2. The witness-pair idiom may already be native, not owed.

PR #12050 had to retrofit the witness pair onto check-driver-memory-census.mjs. In #12056's gate it was already there — applyExemptions is exercised through cases passing their own synthetic judged/exemptions arrays, and 0 of 50 self-test cases read the real ledger at all. So "carrier of the shape" and "member of the habitat" came apart on that one, exactly as this card's sibling warned they might.

3. A step-0 discriminator worth running before step 1. Distinguish a debt ledger (exists to be driven to zero; finite, enumerated, shrink-only) from an exemption (permanent principled carve-out, never expected to empty). Only the first has a moment of success for a self-test to break at. #12056's 49 exempt mentions turned out to be two mechanisms, only one a ledger — and a third construct in the same file, SPEC_EXAMPLE_SLOTS, is a registry that must grow, which is the exact inverse of debt and would have been miscounted by a vocabulary scan.

⚠️ On that last point, a caution about my own method: I opened #12056's dispatch with a word census (exempt: 49, ledger: 0, ratchet: 0, against a control of 32 on a real ratchet). It usefully sharpened the question and it did not settle it — a census enumerates spellings, not mechanisms. Useful as a starting point, not as a verdict.

Full evidence, including a both-directions ablation with a positive control, is on #12056. ⛔ Nothing under packages/spec/** was read or touched by that work.

Generated by Claude Code

Claim: PM loop round R7, wave 4
Session: session_01E5LFCYBJ3q2s6yW6oMLxwy
Branch: claude/issue-12055-selftest-debt-pins
Worktree: objectstack-issue-12055
Domain: domain:spec
File surface: the five named carriers — packages/spec/scripts/check-dual-source-exports.ts, packages/spec/scripts/check-exported-any.ts, packages/spec/scripts/liveness/check-liveness.mts (path re-measured at fire: the card's packages/spec/liveness/… spelling is stale, the script lives under scripts/liveness/), packages/spec/scripts/check-generated-ledger.test.ts (concrete lead re-verified at :84/:95), packages/spec/scripts/check-react-blocks-declaration-parity.test.ts — plus whatever fixture files their repairs need; sweep discipline: zero changes outside the enumerated population (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus — gate-pin semantics judgment; not a contract accept/reject change, and the surface is outside packages/spec/src/** (no clause-② path limb)
Clause-②: no
Serial constraints cleared: packages/spec/scripts/** is free — #12418 (which added check-entry-nameability.ts and touched check-generated.ts) is MERGED; no carrier intersects it or any in-flight claim; wave-4 sibling #12344 (src/ui/component.zod.ts + packages/mcp) disjoint. H17: no hit.

Generated by Claude Code

Dev claim (os-dev seat, dispatched by the domain:spec PM seat, PM loop R7 wave 4).

Session: session_01E5LFCYBJ3q2s6yW6oMLxwy
Branch: claude/issue-12055-selftest-debt-pins (pushed empty at start as the write-route probe; push succeeded)
Worktree: ../objectstack-issue-12055 from origin/main @ 68c5dba

Population I am sweeping (enumerated; zero changes outside it):

packages/spec/scripts/check-dual-source-exports.ts
packages/spec/scripts/check-exported-any.ts
packages/spec/scripts/liveness/check-liveness.mts — the card's packages/spec/liveness/… path is stale; re-measured location on origin/main
packages/spec/scripts/check-generated-ledger.test.ts (the concrete lead)
packages/spec/scripts/check-react-blocks-declaration-parity.test.ts
plus fixture files a genuine repair needs. The sixth carrier (packages/lint) is the devx seat's and is already closed not-planned — not touched.

Method, per carrier and in this order: step 0 (debt ledger vs. permanent exemption / growing registry) → historical disproof (git log: did the ledger already empty in a landed commit with the self-test staying green?) → step 1 (does the self-test already default to the empty baseline?) → step 2 (would each case still pass at zero?). Repairs follow the PR #12050 witness-pair idiom; no gate gets weakened.

Generated by Claude Code

os-dev-report

Outcome: all five carriers DISPROVEN. Zero-diff — no PR. The card's own first job ("not individually confirmed to carry the shape — that is this card's first job") is done, and the answer is that none of the five carry it. The card's concrete lead is specifically falsified, by measurement.

Branch claude/issue-12055-selftest-debt-pins was pushed at start as the write-route probe and carries 0 commits (tip == origin/main @ 68c5dba) — it is not in-flight work.

Per-carrier verdicts (disproven is not skipped)

#	carrier	step 0: debt ledger?	disproving step	verdict
1	`scripts/check-dual-source-exports.ts`	yes — `dual-source-exports.baseline.json`, shrink-only	already at ZERO today, green; and `selfTest()` never reads the baseline	disproven
2	`scripts/check-exported-any.ts`	yes — `KNOWN_ANY`, "every entry is debt with a name on it"	already at ZERO today, green; self-test passes `{}` as the exemption map — step 1 in its purest form	disproven
3	`scripts/liveness/check-liveness.mts`	no — the walked ledgers are a GROWING inventory	twin reads neither of the lane's two debt baselines; its floors rise with burn-down	disproven
4	`scripts/check-generated-ledger.test.ts`	no — the buckets are a PARTITION of package.json	ablation A: an empty bucket is not a reachable green state	disproven (the card's lead, falsified)
5	`scripts/check-react-blocks-declaration-parity.test.ts`	yes — 3 accepted `registryOnly` divergences	ablation B: burning the debt to zero leaves the twin 18/18 green	disproven

1 — `check-dual-source-exports.ts`

Two independent disproofs. Present-tense (the devx seat's shortcut, observed directly rather than reconstructed): dual-source-exports.baseline.json already reads "entries": [] on origin/main. The predicted failure has had its chance and did not occur:

--self-test  exit 0   ✅  self-test: flags same-name different-declaration exports, and nothing else.
full audit   exit 0   ✅  no new dual-source exports: 4982 names across 17 entry points —
                          193 re-exported (single declaration), 0 accepted dual-source (baseline).

Step 1: selfTest() builds its own temp-dir program and calls scan(program, entries) — the baseline is never read on that path, so emptying it cannot move the self-test. The success line above also already satisfies the card's other carried rule: the population (4982 names, 193 re-exported) prints beside the zero, so an empty ledger is not readable as an empty population.

2 — `check-exported-any.ts`

KNOWN_ANY is {} on origin/main — at zero, green. And the self-test is the card's step 1 in its purest form: it calls scan(program, { './fixture': fixture }, {}), passing an explicitly empty exemption map, so the empty-baseline path is not merely reachable, it is the only path that ever runs.

--self-test  exit 0   ✅  self-test: detects `any` types and `any`-output schemas, and nothing else.
full audit   exit 0   ✅  no exported type resolves to `any`: 2431 types + 1516 schemas across 17 entry points.

3 — `scripts/liveness/check-liveness.mts`

Path note confirmed: the card's packages/spec/liveness/… is the ledger data directory; the script lives at packages/spec/scripts/liveness/, twin check-liveness.test.ts.

Step 0 disproof. The ledgers this gate walks (packages/spec/liveness/*.json) are a growing inventory of every governed property — they gain rows as types are governed. That is the exact inverse of debt, and precisely the SPEC_EXAMPLE_SLOTS shape the devx seat's note warned a vocabulary scan would miscount. The liveness lane's real debt ledgers are key-mention.baseline.json and undrilled-containers.baseline.json, and the twin reads neither (grepped: the only occurrence of the string in the file is prose in a comment at :147).

Its numeric assertions are exit codes plus two > 100 floors on live-entry evidence pointers — a population that grows as the ledger burns down, i.e. an anti-vacuity floor, which is the correct idiom rather than the defect. State counts are matched \d+, never a literal. This carrier is in fact a positive exemplar of the repair shape the card asks for: every failure case mutates a copy via --ledger-root against a verbatim-copy green control — a witness pair already.

4 — `check-generated-ledger.test.ts` — the card's concrete lead, falsified

The card reads '1 explicit manual-only generators' and '1 needing an external input' as pinning a debt ledger's entries as present. Step 0 says otherwise, and an ablation settles it: EXPLICIT_GENERATORS and EXTERNAL_INPUT_REQUIRED are not a debt list but a partition of package.json's own check:/gen: scripts. Every script must land in exactly one bucket, so a bucket cannot reach zero while its script exists.

Measured — each bucket emptied in turn, mutation proved on disk, --reconcile-only run, file restored and proved byte-identical to its HEAD blob:

empty EXPLICIT_GENERATORS      -> exit 1
  `gen:authorable-surface-base` exists in package.json but no GATED entry names it
  and it is not in UNGATED_GENERATORS.

empty EXTERNAL_INPUT_REQUIRED  -> exit 1
  `check:react-declaration-parity` exists in package.json but is in neither GATED
  nor NO_GENERATOR (nor EXTERNAL_INPUT_REQUIRED).

Both reds are the reconciliation's own complaint, not the count pin's. So there is no moment of success for the self-test to break at: an empty bucket is unreachable as a green state. It empties only when the script is deleted — which is exactly the change the case exists to route back through this file, as its own comment says ("Named here so a later change that drops either script also has to come back through this file"). Retiring a gate is not a burn-down.

Both buckets are permanent by ruling besides: check:react-declaration-parity's manifest source is settled (maintainer ruling 2026-08-07, "not from CI"), and gen:authorable-surface-base is a deliberate manual-only act (#5358).

Secondary observation, examined and deliberately NOT acted on. The two 1 literals are exact counts, while the sibling case at :70 deliberately derives its counts from package.json. A second legitimate external-input gate or manual-only generator would therefore red this test for a non-defect. That is churn-sensitivity, a different species from this card's shape, and "repairing" it would blunt a deliberate deletion-detector — so it is named here rather than changed. Not filed as an issue: it is a design tension the file's own comments already reason about, not a defect.

5 — `check-react-blocks-declaration-parity.test.ts`

This is the one carrier with a genuine debt ledger and a self-test case that reads it, so step 2 was answered by measurement rather than by reading.

react-declaration-parity.baseline.json holds 9 blocks, of which 3 real registryOnly divergences (all on ObjectForm), each with a reason in _acceptedReasons — one explicitly parked pending a family ruling with the revisit tracked on #9392. Real shrink-only debt.

16 of the 18 cases write their own synthetic baseline to a temp dir (step 1). The one case that reads the committed baseline (:181) derives block names from it to build a manifest — it never asserts an entry is present. Two ablations, each with the mutation proved structurally on disk and the file restored to its HEAD blob:

B1  blocks.ObjectForm.registryOnly 3 -> 0   (the actual burn-down moment)
      vitest exit 0 — Test Files 1 passed, Tests 18 passed
B2  blocks map 9 -> 0                        (the whole ledger emptied)
      vitest exit 0 — Test Files 1 passed, Tests 18 passed

Green through the moment of success, both times. Does not carry the shape.

Verification

All measurements at 68c5dba, the branch tip, which is origin/main — the tree was never modified except inside the ablations, each restored and proved byte-identical to its HEAD blob before the next reading.

pnpm --filter @objectstack/spec build                                    exit 0
pnpm exec tsx scripts/check-dual-source-exports.ts --self-test           exit 0
pnpm exec tsx scripts/check-dual-source-exports.ts                       exit 0
pnpm exec tsx scripts/check-exported-any.ts --self-test                  exit 0
pnpm exec tsx scripts/check-exported-any.ts                              exit 0
vitest run check-generated-ledger.test.ts
       check-react-blocks-declaration-parity.test.ts
       liveness/check-liveness.test.ts                                   exit 0
                                        Test Files 3 passed (3) · Tests 49 passed (49)
node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack
  "this branch changes nothing against 'origin/main' (merge base 68c5dbaab)
   — nothing to derive."     => no gate family is owed; the diff is empty.

Heavy runs went through scripts/pm/os-verify-lock.sh; verdicts read from the printed VERDICT lines, exit codes captured before any pipe.

One ablation ran empty and is reported as such. The first attempt at ablation A landed a malformed edit (my regex kept = ];), and the on-disk check caught it — injected count=0 — so the run was aborted and the reading discarded rather than reported. The anchor was fixed and both legs re-run; the numbers above are from the corrected run only.

Method caveat, stated rather than papered over. This checkout is shallow (git rev-parse --is-shallow-repository = true), so windowed git log archaeology is not trustworthy here. I therefore did not reconstruct the devx seat's historical disproof from history — for carriers 1 and 2 I observed the stronger present-tense fact directly: the ledger is at zero today and the gate is green today.

Out-of-scope finding

#12462 — key-mention.test.ts:168 asserts doc.exemptions.length is greater than 0 against the shipped key-mention.baseline.json, which declares itself a SHRINK-ONLY RATCHET (#11457). That clears step 0, and both halves of the shape are present: the pin reds on the commit that empties the ledger, and the loop on the next line goes vacuous at zero. Filed unassigned, not repaired — it is outside this card's enumerated population, and widening is what #11694's ruling declined.

To keep that from reading as a lone sighting, the surrounding lane was enumerated: of the eight *.test.ts under scripts/liveness/, it is the only one that both reads a real shipped ledger and asserts it non-empty. The three other toBeGreaterThan(0) sites were checked and are not this shape (empty-state.test.ts:273, proof-registry.test.ts:92, readme-table.test.ts:49,101).

Deviations

REST is 403 from this seat (probed: REST_STATUS=403), as the dispatch stated, so the duplicate search before filing key-mention.test.ts pins the shipped shrink-only ledger as NON-EMPTY — the #11694 shape, in the one liveness twin the #12055 sweep could not touch #12462 went through MCP search_issues rather than the REST list endpoints my contract prefers. Two hits, both closed ([finding] a shrink-only ratchet whose self-test asserts its own entries are PRESENT can never reach zero — one instance found and fixed, the class unswept #11694, tests(attachments): pin the unpinned authorization clauses of the attachments chain — coverage gaps from QA run #9401 #9483), no duplicate.
No changeset and no skip-changeset label, because there is no PR. Nothing is published and nothing landed.

{
  "issue": 12055,
  "status": "done",
  "branch": "claude/issue-12055-selftest-debt-pins",
  "pr": null,
  "premise_still_valid": false,
  "summary": "Swept all five enumerated carriers; none carries the self-test-pinned-to-the-debt shape, so the outcome is zero-diff and there is no PR. Carriers 1 and 2 are disproven twice over: their ledgers (dual-source-exports.baseline.json entries, KNOWN_ANY) are ALREADY at zero on origin/main with both gates green, and neither self-test reads the real ledger at all (check-exported-any's passes an explicitly empty exemption map, the purest form of step 1). Carrier 3 fails step 0 - the liveness ledgers are a growing inventory, not debt, and its twin reads neither of the lane's two real debt baselines; it is in fact a positive exemplar of the witness-pair idiom. Carrier 4, the card's concrete lead, is FALSIFIED by ablation: EXPLICIT_GENERATORS and EXTERNAL_INPUT_REQUIRED are a partition of package.json's scripts rather than a debt list, and emptying either makes the reconciliation itself exit 1 for its own reason, so an empty bucket is not a reachable green state and there is no moment of success for the pin to break at. Carrier 5 is the only one with real debt plus a case reading it, and an ablation burning that debt to zero left the twin 18/18 green.",
  "tests": "All at 68c5dba (branch tip == origin/main; zero commits, zero diff - `git status --porcelain` and `git diff HEAD --stat` both empty). GREEN BASELINE: pnpm --filter @objectstack/spec build exit 0; check-dual-source-exports.ts --self-test exit 0 ('flags same-name different-declaration exports, and nothing else'); full audit exit 0 ('4982 names across 17 entry points - 193 re-exported, 0 accepted dual-source (baseline)'); check-exported-any.ts --self-test exit 0; full audit exit 0 ('2431 types + 1516 schemas across 17 entry points'); vitest run over check-generated-ledger.test.ts + check-react-blocks-declaration-parity.test.ts + liveness/check-liveness.test.ts exit 0, 'Test Files 3 passed (3) / Tests 49 passed (49)'. ABLATION A (carrier 4), no rebuild needed - these are tsx source-run scripts with no dist in the resolution path: emptied EXPLICIT_GENERATORS, mutation proved on disk by anchored grep counts (deleted text \"gen: 'gen:authorable-surface-base'\" 1->0, injected '= [];' lines 2->3), --reconcile-only exit 1 'exists in package.json but no GATED entry names it and it is not in UNGATED_GENERATORS'; restored and proved byte-identical to HEAD blob 6651ad40. Same for EXTERNAL_INPUT_REQUIRED (marker 1->0, '= [];' 2->3), exit 1 'is in neither GATED nor NO_GENERATOR (nor EXTERNAL_INPUT_REQUIRED)'; restored, hash proved. Predicted direction RED and observed RED, but for the RECONCILIATION's reason, not the count pin's - which is the discriminating observation. ABLATION B (carrier 5): B1 blocks.ObjectForm.registryOnly 3->0 (structural proof via json parse; the raw grep only drops 2->1 because _acceptedReasons keeps its own copy of the name, so the count was anchored structurally), vitest exit 0 18/18 passed; B2 blocks map 9->0, vitest exit 0 18/18 passed. Both restored and proved byte-identical to HEAD blob 636a4c74; final `git diff HEAD --stat` empty. Predicted direction GREEN and observed GREEN, which is the disproof. FIRST ATTEMPT AT ABLATION A RAN EMPTY and is reported rather than silently re-run: a malformed regex wrote '= ];' and the on-disk check reported injected count=0, so the run was aborted and its reading discarded; anchor fixed, both legs re-run, only corrected numbers reported. Ablation script carried trap '<restore>' EXIT INT TERM with absolute paths seeded from git rev-parse --show-toplevel, and every restore was proved by comparing git hash-object against the path's HEAD blob with empty hash treated as failure. Heavy runs via scripts/pm/os-verify-lock.sh; verdicts read from its VERDICT lines, exit codes captured before any pipe. GATES OWED: none - `node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack` reports 'this branch changes nothing against origin/main (merge base 68c5dbaab) - nothing to derive.' CAVEAT: checkout is shallow, so no git-log archaeology was relied on; carriers 1 and 2 were disproven by the stronger present-tense observation (ledger at zero today, gate green today).",
  "open_questions": [],
  "out_of_scope_findings": [
    "filed as #12462: key-mention.test.ts:168 asserts doc.exemptions.length > 0 against the shipped key-mention.baseline.json, which declares itself a SHRINK-ONLY RATCHET (#11457) - a genuine instance of this card's shape, plus the vacuity half (the loop on the next line asserts nothing at zero). Outside the enumerated population, so measured and left untouched; the surrounding lane was enumerated to confirm it is the only such site among the eight liveness test twins."
  ]
}

Generated by Claude Code

ACCEPT — premise falsified, zero-diff, card complete — reviewer of record: spec seat R7, session_01E5LFCYBJ3q2s6yW6oMLxwy. Not clause-② (no packages/spec/src/** surface; no diff at all). A premise_still_valid: false + pr: null run is a first-class deliverable, and this one is exemplary:

The card's own first job is done: all five carriers individually adjudicated, each with the step that disproves it named — two by the present-tense zero-ledger observation (stronger than the historical shortcut on a shallow checkout, and the report says why), one by the step-0 debt-vs-inventory discriminator (the exact SPEC_EXAMPLE_SLOTS inverse the devx note predicted), and two by ablation with proven mutation AND proven restore.
The concrete lead is falsified by the discriminating observation: carrier 4's buckets are a PARTITION of package.json, and emptying one reds the reconciliation for its OWN reason — an empty bucket is not a reachable green state, so there is no burn-down moment for the pin to break at. The secondary churn-sensitivity observation was examined and deliberately not "repaired" (it is a deletion-detector) — correct restraint.
A bad instrument run was aborted and reported, not silently retried to success (the malformed-regex ablation caught by its own on-disk check). Same instrument discipline the lane has now shown twice this shift.
The one true positive found sits OUTSIDE the population and was filed, not fixed: key-mention.test.ts pins the shipped shrink-only ledger as NON-EMPTY — the #11694 shape, in the one liveness twin the #12055 sweep could not touch #12462 (verified — well-formed, unassigned, with the lane enumerated so it is not a lone sighting) — exactly the "file the follow-up, do not widen" ruling this card was itself born from.

Closing this card as COMPLETED: the executable criterion ("for each carrier: either show it cannot carry the shape, or repair it") is satisfied in the first arm for all five, and the sweep record above is the deliverable. #12462 carries the residual work and awaits triage. The 0-commit probe branch is deleted as part of this close-out.

Generated by Claude Code

Navigation Menu

Repository navigation

Sweep the self-test-pinned-to-the-debt shape in packages/spec's ratchets and test twins (out-of-scripts half of #11694) #12055

Origin, and the ruling that produced this card

The shape

The carriers this card covers

The discriminator, in the order it is cheapest to apply

The repair shape, with a worked precedent

Executable criterion

Per-carrier verdicts (disproven is not skipped)

1 — `check-dual-source-exports.ts`

2 — `check-exported-any.ts`

3 — `scripts/liveness/check-liveness.mts`

4 — `check-generated-ledger.test.ts` — the card's concrete lead, falsified

5 — `check-react-blocks-declaration-parity.test.ts`

Verification

Out-of-scope finding

Deviations

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Sweep the self-test-pinned-to-the-debt shape in packages/spec's ratchets and test twins (out-of-scripts half of #11694) #12055

Description

Origin, and the ruling that produced this card

The shape

The carriers this card covers

The discriminator, in the order it is cheapest to apply

The repair shape, with a worked precedent

Executable criterion

Activity

yinlianghui-tw commented on Aug 25, 2026

yinlianghui commented on Aug 25, 2026

huangyiirene commented on Aug 26, 2026

huangyiirene commented on Aug 26, 2026

huangyiirene commented on Aug 26, 2026

Per-carrier verdicts (disproven is not skipped)

1 — check-dual-source-exports.ts

2 — check-exported-any.ts

3 — scripts/liveness/check-liveness.mts

4 — check-generated-ledger.test.ts — the card's concrete lead, falsified

5 — check-react-blocks-declaration-parity.test.ts

Verification

Out-of-scope finding

Deviations

huangyiirene commented on Aug 26, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

1 — `check-dual-source-exports.ts`

2 — `check-exported-any.ts`

3 — `scripts/liveness/check-liveness.mts`

4 — `check-generated-ledger.test.ts` — the card's concrete lead, falsified

5 — `check-react-blocks-declaration-parity.test.ts`