{
  "summary": "Exhaustive read-only sweep: 50 assigned entries (IR-1–49 plus IR-54), including headingless IR-31. Strong stale-status findings: IR-1/4 landed and exercised; IR-26 build-side identity is present but claim-side remedy remains missing; IR-29 first face landed but later faces remain; IR-33 sized-stack implementation exists; IR-46 ruled floor tokens are implemented but acceptance receipts remain distinct. No tests, measurements, edits, or board mutations performed.",
  "files": [
    {
      "path": "docs/INFRA-REGISTER.md:180-2725",
      "description": "All assigned bodies read; 49 numbered entries plus IR-54, with IR-31 beginning at the second Status paragraph inside IR-30."
    },
    {
      "path": ".github/workflows/golden.yml",
      "description": "Verified current link probes, toolchain print, START/END/DOCS disk assertions, and traceable-reqs pin still 0.2.0."
    },
    {
      "path": "crates/xtask/src/main.rs",
      "description": "Verified load-bearing patch check, unguarded help-output generation, current pool-claim tree-match guard and unconditional incumbent overwrite."
    },
    {
      "path": "crates/spt-poolguard/src/lib.rs:367-443",
      "description": "Verified anchored lane identity and ancestry-only settled predicate; no patch-id fallback."
    },
    {
      "path": "crates/spt/src/main.rs:72-205",
      "description": "Verified CLI runs on 16 MiB owned thread stack; existing cli_stack_smoke integration evidence source identified."
    },
    {
      "path": "crates/spt-store/src/info.rs:872-876",
      "description": "IR-44 preservation-overclaim remains verbatim."
    },
    {
      "path": ".github/ci/ci-notify.sh:129-130,182-200",
      "description": "IR-40 bare CI verdict wording and IR-47 quiet absent-coauthor branch remain."
    }
  ],
  "architecture": "The register mixes original status headers, later corrections, and independent residual mechanisms. Treat implementation, exercised acceptance, historical specimens, and current release receipts as separate evidence objects. Pool enforcement executes in the arriving tree; claim writes remain a separate path. Disk tokens are instantaneous observations, not sustained headroom.",
  "report": "## Scope and decision vocabulary\nExactly 50 rows: IR-1 through IR-49, plus IR-54. IR-50 begins at line 2726 and is excluded. IR-31 is the headingless second Status paragraph after IR-30's Linux-face resolution, through line 2068. Trigger means the entry's stated ripeness event, including a historically documented firing; UNKNOWN never means disproved. CLOSE for already-built/retired entries means preserve their established disposition, not a new claim based on v0.69.0 green. Source reads below were not executions.\n\n| IR | Current entry status | Trigger | Recommended disposition and evidence |\n|---|---|---|---|\n| 1 | Open / lane unlanded | FIRED | CLOSE stale header: reconciliation at 2878–2906 explicitly identifies landed commits; register 169–171 records first golden exercise; current golden.yml 1096/1264 invokes both link probes. Original 4–7 ms negative is not a universal network acquittal. |\n| 2 | RETIRED; incremental remains ON | UNKNOWN for reopen threshold | CARRY retired decision, flag returned disk pressure. New 14.3 vs 32 GiB red weakens historical ample-disk rationale but does not by itself establish the required recurring floor-red threshold or causal ON/OFF timing. No automatic flip or new causal claim. |\n| 3 | Open | UNKNOWN | CARRY: release facts do not demonstrate endpoint-churn wakeup instrumentation or the specific lifecycle trigger. No retirement from battery/build success. |\n| 4 | Open / lane unlanded | FIRED | CLOSE stale header: same landed reconciliation as IR-1; xtask main.rs 47–49 executes patch-pin check; 1047+ implementation; GOLDEN-CI 99–109 carries targeted update/block+edge/toolchain procedure; golden 276/304 prints toolchain. Register first-exercise receipt covers golden steps. |\n| 5 | Open / conditional | UNKNOWN now; NOT FIRED on original rider | COMPOSE next count-consuming rig task. Foot reconciliation 2920–2928 explicitly says original condition NOT MET, contradicting header's unreported condition. 121/3167 counts are receipts, not proof a summary parser was needed or built. |\n| 6 | Open / conditional | FIRED historically; latest extent UNKNOWN | COMPOSE gate-output work; original rider condition NOT MET, with only its new LINK rows voluntarily compliant. Current count receipts do not prove estate-wide membership enumeration. |\n| 7 | Open / hertz fixup linked | FIRED (queued lane) | CARRY linked daemon-leak lane; hertz offline/unacknowledged brief is not a landing. No source/acceptance proof of in-job launch replacement in supplied release facts. |\n| 8 | BUILT | FIRED / satisfied | CLOSE unchanged: established two-platform unreadable-path UNPROVEN verdict and Linux kill-failure evidence stand. |\n| 9 | Pin landed / BUILT | FIRED / satisfied | CLOSE unchanged: 35968156 pin plus documented runner-account/version-print and tested-cut evidence stand. |\n| 10 | Open | FIRED historically | COMPOSE runbook/checklist follow-through. Runbook work demonstrably occurred (IR-54/28); no verified consumer-population checklist fulfilment here. |\n| 11 | Open | UNKNOWN for implementation wave | COMPOSE next rig-tooling rider; cleanup is a use of holder discipline, not evidence --headless became a column. |\n| 12 | BUILT narrowed blind arm; kin note retired | FIRED / satisfied | CLOSE: preserve existing missing-assets fix plus 2026-09-06 stale-binary mutation result. Original rig cause remains unproven; prebuild rule survives independently. |\n| 13 | BUILT | FIRED / satisfied | CLOSE unchanged on documented mutation-specific fulfilment, not latest green. |\n| 14 | Open; 08-30 audit/rule completed | FIRED (operator cleanup) | CARRY structural residue, annotate new cleanup. 38 clean merged trees removed without removing dirty/unmerged/retained evidence; separate checkout/orphan hygiene from target-byte reclaim. Old count tables are dated specimens, not current inventory. |\n| 15 | BUILT | FIRED / satisfied | CLOSE unchanged: authenticated death oracle and both repins documented. Original specimen remains cause-unidentified; green rerun did not identify it. |\n| 16 | BUILT | FIRED / satisfied | CLOSE unchanged on checked returns/named loss/loud refusal fulfilment; keep already-exited Windows exception and dropped rename reasoning. |\n| 17 | Open; Windows population remains | FIRED historically; new matching sighting UNKNOWN | CARRY linked hardening/instrumented family. Known sync-cell red and unavailable earlier PR logs are not identified resident-service/grandchild sightings. Preserve Linux member's separately named closure and remaining Windows uncertainty. |\n| 18 | BUILT; deferred (b) work embedded | FIRED / satisfied for named lane | CLOSE existing authenticated-teardown disposition only; do not silently erase deferred shared breadcrumb-read/cleanliness-consolidation work. Record explicitly whether parent retains/re-homes those residuals; original specimen's killer remains unidentified. |\n| 19 | RETIRED intentional main-push policy | FIRED / satisfied | CLOSE unchanged. Full main-push unit execution is expected; 3167-pass receipt does not revive classifier defect. |\n| 20 | Open / hertz fixup linked | FIRED (hardening lane queued) | CARRY: stop stderr discrimination and load-bearing perch-pid caution remain; scoped greens do not prove explicit stop did anything. |\n| 21 | BUILT | FIRED / satisfied | CLOSE unchanged: explicit cross-package prebuilds, binedge check and shared missing-fixture precondition documented. Keep same-package/cross-package distinction. |\n| 22 | Open | FIRED historically (hygiene wave) | COMPOSE diagnostic-set remedy with test hygiene; no all-markers diagnostic proof supplied. Generic env scrubbing does not satisfy the diagnostic half. |\n| 23 | BUILT | FIRED / satisfied | CLOSE unchanged: TempDir staging plus declared parallel bare-cargo exercise recorded. |\n| 24 | BUILT | FIRED / satisfied | CLOSE unchanged on named TerminateJobObject loss and ordinary-exited TerminateProcess discrimination. Historical wrong path already corrected in status. |\n| 25 | Open | FIRED historically (CI/rig waves) | CARRY fragility; compose rig rule/hardening. Sanctioned nextest avoids in-process interference but does not retire marginal tests. Do not attribute latest unknown PR red to this family. |\n| 26 | Open / built but uncommitted (stale) | FIRED; cleanup shrank old-reader population | CARRY with status replacement. Body already says committed 8ce40d9/98cfafe; current poolguard has anchored git identity and precedence. However xtask 3134 writes owner directly after constructing claim: no incumbent lane adjudication or displaced record. Latest 38-tree removal mitigates old enforcers, not current claim-path loss. |\n| 27 | Open | FIRED (cleanup/audit slot) | CARRY post-teardown trigger gap. Existing pool-sweep detection was already shipped; new reclaim does not prove automatic post-removal sweep or link+pool lifecycle coupling. Distinguish real target dirs from junction pairs; no blanket claim latest cleanup exercised both shapes. |\n| 28 | BUILT | FIRED / satisfied | CLOSE unchanged: mechanical commit-range/changelog accounting required by PR #176. Latest release success alone is not the evidence. |\n| 29 | Open / first fix authored-unlanded (stale) | FIRED (many twohost windows) | CARRY residual faces with corrected status. IR-30 explicitly records 17bbbd8 landed v0.54.0. Later terminal-cadence seal face and emitted-token requirement must not disappear under first-face closure. Six-draw margin series remains closed/unrecoverable. |\n| 30 | Open for family sightings only | UNKNOWN whether latest red matches family | CARRY. Instruments already landed; classify known sync red only from its own frame. Earlier PR red lacks logs and remains unclassified. 121 battery / 3167 units / release build cannot close intermittent family. |\n| 31 | Open; headingless | FIRED (disk-floor recurrence/rig work) | COMPOSE aggregate lane-disk accounting with existing floor work; CARRY structural capacity debt. Root target 62.32 GiB + CI debug 59.70 GiB reclamation addresses bytes; later net 4.22 GiB cleanup is separate. No observation proves aggregate-aware admission/reservation or finished-lane disposal automation. |\n| 32 | Open | FIRED (docs/xtask wave) | COMPOSE generator refusal; source confirms still open: help_for 100–108 ignores child exit and accepts empty stdout; cli_reference inserts it; gen_one writes unconditionally. Stack mitigation does not repair producer self-agreement. |\n| 33 | Open; old 3-arg ceiling | FIRED historically | CARRY only acceptance/status reconciliation, not stale remedy proposal: main.rs 72–205 implements 16 MiB CLI thread; cli_stack_smoke.rs has real binary help/version/nonzero-return contracts. Source presence establishes changed mechanism, not current named debug execution receipt or measured new margin. Mark implementation present; require existing lane/acceptance receipt before declaring full closure. |\n| 34 | Open / hertz fixup linked | FIRED (nextest-config waves) | CARRY linked fixture/config disposition. A single non-leaky run carries no closure information; no delivered lane proof. |\n| 35 | Open rate home | FIRED historically; remeasure-after-landing UNKNOWN | CARRY. Need operator rate ruling plus landed package and correctly deduped new rate. 3167 unit passes is one population, not replacement for historical execution series; no new ratio derived. |\n| 36 | BUILT | FIRED / satisfied | CLOSE unchanged on existing owning/tree-killing helper and diagnostic/death proof. Preserve documented clone-count distinction rather than recounting. |\n| 37 | Upstream released; consume outstanding | FIRED (upstream release) | COMPOSE consume lane, do not close: current golden.yml 1413 pins WANT=0.2.0, not required 0.4.0. Upstream release is not downstream adoption; placement config/acceptance still owed. |\n| 38 | BUILT | FIRED / satisfied | CLOSE existing test-leak fix; cleanup corroborates importance of independent CWD-holder population, not a new all-holders closure. |\n| 39 | BUILT | FIRED / satisfied | CLOSE unchanged on shared missing-fixture refusal and package-correct recipe evidence. |\n| 40 | Open, resume recency + notify scope | FIRED for workflow window; arm-A implementation UNKNOWN | CARRY / COMPOSE scope-wording rider. ci-notify.sh 130 still prints bare CI $verdict. Latest 3167 passes followed by 14.3 GiB floor red is decisive receipt-scope example: workload success != job/run success. SHIP at known-red a9e786b2 is authorization, not green; release build success is another object. Brief delivered to offline hertz != acknowledged/accepted. |\n| 41 | Open; documentation corrected | FIRED (CI/runbook work) | CARRY policy decision; docs acceptance already complete, concurrency-key change is not required without ruling. No supplied evidence latest missing PR logs resulted from queued supersession; do not manufacture that explanation. |\n| 42 | BUILT documentation correction | FIRED / satisfied historically | CLOSE existing incumbent-enforcement clarification but flag wording drift: current pool_claim can refuse wrong-tree/unreadable-tree claims (main.rs 3075–3110). 'Never refuses' is now too broad; it still does not adjudicate incumbent lane ownership, so preserve that precise distinction. |\n| 43 | Open observation; mechanism unmeasured | UNKNOWN | CARRY transport-bound question. Latest sync red not identified as NoReply 60/30-second specimen; no attribution by timing overlap. |\n| 44 | Open | UNKNOWN for specific info.rs touch | COMPOSE next info.rs touch; exact false-preservation sentence still at 873–875. Serialization is not preservation; no proof remedy landed. |\n| 45 | RETIRED | FIRED / satisfied | CLOSE unchanged: temp-root path chain answered disk hermeticity only; third-node runtime ingress is not exonerated by it. |\n| 46 | Open; ruled/composed WEBSERVE rider | FIRED | CARRY acceptance reconciliation, mark source implementation present. golden START/END/DOCS raw-byte tokens exist; END always() before teardown, sample=INSTANT, 32 GiB unchanged. Latest unit-pass then disk-floor-red is honest workload-versus-resource separation, not product failure. Need per-job actual START/END and relevant golden/DOCS receipts before full ruled-remedy close; neither cleanup nor release-build green substitutes. |\n| 47 | Open; patch stashed | FIRED (golden/workflow rider window) | COMPOSE notification warning: ci-notify.sh 197–200 still merges absent/unparseable and doyle-only into quiet info. Source is enough to reject closure; no need to recover stash just to carry. |\n| 48 | Open preventive control | UNKNOWN for exact parity-cell touch | CARRY / COMPOSE next parity change. main.rs 3012 uses checked-in config; inspected parity test region supplies no LF/CRLF fixture-pair control. Current CRLF tolerance is not its own regression proof. |\n| 49 | Open ancestry-only takeover defect | FIRED (shared cleanup audit slot); takeover request UNKNOWN | CARRY; current git_lane_state 424–438 remains ancestry-only, no patch-id fallback. Removing clean merged worktrees/pools may remove affected claims/readers but does not fix future cherry-picked member takeover. Manual cleanup classification is not guard semantics. |\n| 54 | BUILT | FIRED / satisfied | CLOSE unchanged on PR #176's intake/never-executed-cells/lock-property changes. Release counter105/tag16df0e41 and known-red candidate remain explicit distinct receipts; do not flatten into tested==released green. |\n\n## Load-bearing deltas for parent edits\n1. Correct stale state, not merely append another contradictory note: IR-1/4 unlanded headers contradicted by their own landed reconciliation and first-exercise record; IR-5/6 original conditional answer is explicitly NO, not unknown. IR-26 is no longer uncommitted, IR-29's original fix no longer unlanded, IR-33's old stack mechanism has shipped source, and IR-46's ruled source exists.\n2. Operator cleanup: IR-14/26/27/49 should receive one consistently scoped event, not four closures. Removing 38 clean merged worktrees shrinks the stale-arriving-enforcer population and reconciles checkout residue. It does not establish a durable teardown trigger, incumbent guard at claim time, patch-id settled predicate, or future pool safety. No dirty/unmerged/retained evidence was removed. 62.32 GiB root target and 59.70 GiB CI debug reclamation are cache-byte mitigations; net 4.22 GiB later cleanup is a distinct event/meter. Do not add unlike values into a claimed single net-free reading.\n3. IR-40/46: preserve receipt types. 121 scoped battery pass; push-CI Windows 3167 unit pass followed by 14.3/32 GiB resource red; earlier PR unit-red logs unavailable/unclassified; golden known sync cell red under explicit SHIP; release build succeeded; v0.69.0 counter105 published at16df0e41. None logically substitutes for another. Cleanup does not establish cause of the earlier PR red, and passing workload before end-floor RED is not proof disk caused that workload or the prior red.\n4. IR-37 has a concrete unfulfilled downstream obligation: current golden installer still requests traceable-reqs 0.2.0. Upstream closed-through-release wording must not become spt-core closed.\n5. IR-32 remains a source-demonstrable hole despite stack and recursive-doc improvements. IR-42's old universal 'claim never refuses' sentence is now false because a different, tree-match refusal was added; incumbent ownership enforcement is still absent. Keep these distinctions visible.\n6. No new family membership, rate, cause, or acceptance execution was inferred from source presence, temporal overlap, unavailable logs, or green receipts. Existing built/retired verdicts above stand on their recorded evidence; no validation suite was run."
}