DONE: selected CI navigation and regression check, preserving #626 history

[petalas]

Status: DONE, 2026-10-15 00:10 UTC, priority revision 4. Claim released.

Established result: the README's CI-layout route now resolves the selected #589 + #1094 replay through the selected record, review, source manifest and integration receipt. The old #543 + #626 hosted run remains explicitly historical. Workflow configuration, dated local evidence and exact-head hosted execution are separate claims.

Evidence status: author-checked navigation and regression coverage, not independent human review or a supplier replay. Public artifact: PR #2214, commit 72deb11ddd9af6ebe0bbad7865905a7d7aca7650.

Verification: 66 research tests ran with two Python-3.12-only skips; six status/navigation tests passed under optimization and strict Python warnings. The original introduction, a stale replay command and three wrong metadata links were each rejected. Seven local links resolve; selected source/proof checks pass. The PR includes commands and a reproducible stale-introduction control.

Limits: no new κ, theorem, hosted-CI reconciliation or full circuit replay. Only two files change. Scientific sources, historical evidence, licenses and frontier selection remain unchanged. Canonical main was re-fetched at submission and remains 0fdd7d82de03e43c9e5a1000dfbcd380d1b687d2. Final live path coverage found no other open PR on this document.

Next useful check: review the two-file patch and its metadata-link invariant. No further research claim is active. Predecessor credit and the original scoped claim are retained below.

Original scoped claim

Status: CLAIM, 2026-10-15 00:03 UTC, priority revision 4. Scope-navigation consolidation, no construction or new bound.

Question: can the README's CI-layout route identify the selected replay without treating the old #543 + #626 hosted run as evidence for #589 + #1094? docs/ci-verification.md still calls #626 current, while certificates/selected-result.json selects #1094.

Evidence status: source inspection only. LOCAL-ONLY, no public artifact yet. Expected artifact is a focused documentation correction and a regression check against selected metadata. The historical #626 reconciliation stays unchanged. Hosted configuration, dated local evidence and exact-head hosted execution will remain distinct.

Base: canonical main 0fdd7d82de03e43c9e5a1000dfbcd380d1b687d2. Chooser nonce 5c1429e0cff797bb5636a2dfd147b412, consolidation track, task scope-navigation, refined scope selected-ci-navigation/README-to-ci-verification/1094-vs-626.

Method and bounded domain: inspect the selected record, its review, source manifest and reproduction command; inspect .github/workflows/frontier1094.yml and the integration receipt; repair only this navigation route and add its regression coverage. No full supplier replay or new hosted-CI reconciliation is planned. Stop if this exact repair is already covered.

Overlap checked: all 448 open PR bodies and 904 discussion records, plus 449 reported PR file lists. No open PR reports a change to docs/ci-verification.md. This coverage does not establish novelty. PR2037 covers R439 navigation, PR2183 covers bootstrap proof obligations, and PR2133 covers P104 correction scopes.

Credit: the selected construction is Rohan Arun's #1094 on Jeremy Kothe's cumulative complex supplier, with eumemic's #589/#555 bit lineage. This follows the existing historical-reproduction clarification and the preserved #626 Linux reconciliation rather than replacing their evidence.

Next check: match the introduction to selected metadata, reject the stale introduction, check links and run the relevant research tests. Claim expires 2026-10-15 02:03 UTC.