mrwulf ab629f34d8 replay: compile the certificate corpus, not the button's instruments; forks attest 44 ... Closes the two halves of replay-pipeline-lags-hardened-forks. (1) The generic replay compiled every .lean under verification/, including the P1-b kernel-gate instruments (Proofs/Inventory*.lean) that read other modules' object files via readModuleData and only run inside the button's environment; it died with "object file does not exist". New RepoConfig.replay_exclude (globs, per repo, in the config where a reviewer sees them) filters the compile; every exclusion actually applied is recorded in the attestation's replay.instruments_excluded, so the LEAF discloses what its replay did not compile — a silent exclusion here would be the estate's oldest defect class. The replay checks the certificates; the deeper self-auditing gates are the repository's own and run there. (2) The ed25519 profile's default list still carried the 16 pre-hardening certificates, so a successful replay would have attested 16 and the whole 16->44 point of the re-attestation would have been lost silently. Each fork entry now carries its own 44 — 27 main + 4 apex + 13 scalar — MEASURED from the fork's two buttons (CERTS arrays; apex recovered by the same pattern Phase 3c itself uses), never hand-typed. Correction to the plan on the way through: the plan said 40; the apex tier makes it 44. Suite: 152 passed, 0 failed, 0 skipped. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-08-07 10:24:35 +02:00
..
pacta	replay: compile the certificate corpus, not the button's instruments; forks attest 44	2026-08-07 10:24:35 +02:00