Diagnostic snapshot freshness evidence
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.
This records the local repair of the observed diagnostic inventory. The
schema for evidence.textproto is
proto/validation_evidence.proto (repository access required).
The record binds all 55 current Lean input catalogs, each terminal command’s
argv and exit code, combined stdout/stderr logs, and relevant input/output
bytes by SHA-256 and size. The source commit names the clean base before this
repair; changed tool and snapshot bytes have their own bindings.
The baseline emitter rejected the stale snapshot, while the old coverage consumer accepted it. The strengthened consumer rejected those same stale bytes. Regeneration updates only RFC-0000/RFC-0001 source hashes and the already authored M01002 description. It preserves 742 diagnostic entries, their identities, severities, and phases.
Seven focused mutation tests and the current inventory/coverage drift checks pass. The allocation audit’s exit code is zero because it currently rejects exact duplicate IDs; its log still reports five range overlaps and seven out-of-range entries. The release report has an expected exit code of one because unrelated release gaps remain. An expected failure in this evidence record is an observed control, not a conformance pass or release approval.
Reproduce individual commands from the record at the corresponding source
bytes. The before-repair snapshot and tools resolve from the recorded Git
base; current repair bytes resolve from this commit. The full release command
also requires the pinned fastverk/spec Git objects at the indicated local
path. Baseline and after-repair logs are distinct and retained.