Authenticate accepted source updates in historical reconciliation checks

[antunishdPursuit]

The aggregate historical reconciliation check rejected legitimate source updates, while the frozen clone and split-skip checks ran against optimized live helpers. This follow-up to #2026 replays those historical checks with their exact original inputs and recognizes only explicitly authenticated successor bytes.

• Preserve frontier890's original spectrum receipt by authenticating the exact one-digest refresh from Sagar Thakrar's 02c46c7e. Bind the current helper hash and require every other byte, including all 41 mathematical cases.
• Authenticate batch932's exact assertion-safe runner/test successors (2b7dc6cf) and the scoped historical clone runner extension (c58c1778). Removing assertion protection, disabling the adapter, changing other bytes or forging predecessor pins still rejects.
• Reuse the authenticated isolated reconciliation92 replay from the aggregate checker. The original verifier and pre-PR154 Makefile pin remain unchanged.
• Restore PR53's exclusion-circuit helper from Wentao Li's retained baseline when replaying the original clone acceptance suite. Restore all three split-skip helpers named by its unchanged manifest: fused-block, exclusion-circuit and shared-point-circuit. Retain the live optimizations unchanged and reject any unrecognized live successor or corrupt baseline.
• Authenticate every replacement before copying and again before execution; keep all other tracked working bytes and the existing post-replay hash/diff gates. Reject duplicate paths and untracked dependencies. The default runner still executes every test module in its own interpreter; the historical clone module receives its authenticated original helper.
• Extend the existing scoped workflow's path filters and adapter controls, and run the same scoped job on contributor branches so fork CI can verify the repair.

Started from current main e112d71c. Current head 92276c22f6f419bbefd870bf2bb373bc41b0c643. No historical coverage receipt, frozen archive, mathematical payload, selected-result record or contributor disposition is edited. No checks are disabled and no mathematical frontier is changed.

Validation on Windows / Python 3.11 with PYTHONUTF8=1:

• Complete scripts/verify_pr_reconciliation.py: PASS, 1,685 attributed PR records and all its full-tree inventories / evidence checks.
• Reconciliation regression suite: 38 tests pass normally and under -O.
• Historical replay adapter: 13 tests pass normally and under -O, including multiple dependency overlays, corrupt second inputs, duplicate/untracked dependencies, unchanged live sources and output mutation rejection.
• Isolated runner: 5 tests pass, including real child assertion failures under inherited optimization and same-named synthetic clone failures.
• Earlier spectrum replay: all 41 literal cases and package corruption controls pass; those source bytes are unchanged by the follow-up repairs.
• Exact baseline and successor hashes checked against the original manifests / Git objects; git diff --check origin/main passes.

Hosted Ubuntu checks on this exact head (92276c22) passed: 64/64 jobs across all eight fork workflows, including all 52 full research matrix jobs (Python 3.11/3.13/3.14), the previously failing clone/test groups, historical Lean checks, R420 native checks, and the complete scoped source audit. Full matrix: https://github.com/antunishdPursuit/integer-mult-bounds/actions/runs/38627449009 ; scoped audit: https://github.com/antunishdPursuit/integer-mult-bounds/actions/runs/38627448547 . The registered-package selector against the actual PR base e112d71c emits an empty replay matrix.

Remaining upstream queue: all 65 CrocSwap-side PR checks still report QUEUED, with no runner assigned to the sampled scoped job. For example: https://github.com/CrocSwap/integer-mult-bounds/actions/runs/38627464190 . Earlier superseded-head checks also never started. The contributor account has read-only upstream repository permissions, so a maintainer needs to inspect/unblock that queue; no queued check is reported as passed, cancelled or bypassed. Requesting maintainer help with the queue, while the existing monitor continues following these runs.

Freshness checkpoint: canonical main fetched at 0fdd7d82, priority revision 4, on 2026-10-14. Its new priority/discussion guidance was read; only guidance/catalogue files changed since this PR's pinned base and the selected record is unchanged. Continue the donor-assigned CI repair, without rerolling research or altering priority choices. This remains a CI/source integrity repair, not a new multiplication bound, selected cold replay or full theorem verification.

Credit ljste's spectrum audit; Sagar Thakrar's source-pin repair; woklerx's assertion-safety repair; Chafik Boukhalfa, RaD/hipotures and Rohan Garg's clone / split-skip lineage; Wentao Li's retained support-mask and shared-point digest baselines; and the historical reconciliation authors. Prepared by Dennis (antunishdPursuit) with substantial OpenAI Codex assistance; Apache-2.0. Coordination: #1166 (comment)