WIP: build: add reproducible artifact contract #9
Loading…
Reference in a new issue
No description provided.
Delete branch "audit/reproducible-artifact-contract"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
This PR remains Draft/WIP and must not be merged. It integrates the approved audit heads in serial order over
mainand preserves the reviewed final source and Git LFS artifact tree.Clean history rewrite
The branch was force-rewritten at exact head
4747aadd4b453989c071e91d4dbe942d1d698790to remove accidental operational backup paths from published PR history.a150e4db256fbdddcbe656f36674e434fadf7ee113a46f9461ca86d23051bdb5fc553501f93dd3f0b647dcaa46f20c37b753e62d1cbd6e137b454e55.ops-backup-*and operational temp/backup paths; none remain.8b5d5f9b3b63b8c48a625dee9566c8eccba860eftree. The only removed historical content was the accidental operational backup directory.Corrected R2 preview evidence
Direct inspection of exact approved R2 commit
13a46f9461ca86d23051bdb5fc553501f93dd3f0provesbuild/audio/memory-symphony-preview.mp3is an LFS pointer to:sha256:ca16da1a2e43a393a01fd29fc464416e48b621e05344a6abcb5d8cf8444466bfwith size
32871644bytes. The earlierca16da1a2e43c152...claim is incorrect and is not a replacement object.Artifact contract and verification
build/artifact-contract.jsonlocks Git LFS object/content digests and semantic structure for all 35 deliverables (29 PDFs, 4 MIDI, 2 MP3). CI validates LFS integrity/contract behavior, generated source, strict vocabulary, project policy, and pinned LilyPond rendering without modifying tracked artifacts.Completed locally on the rewritten exact head:
make testpython3 tools/verify_artifacts.py --require-hifi-inputgit lfs fsck --objectsgit fsck --strict,git diff --check, exact-ancestor and final-tree-equivalence checksForgejo CI on this rewritten exact head must reach terminal success before fresh independent review. No release asset was created or changed.
e1073750958575432cdabuild: add reproducible artifact contractto WIP: build: add reproducible artifact contractff9a6949674d98fe2774Fresh R4 review requested for exact head
4d98fe2774d55c67474bbd5299a63166433ccc44against base12525be54d84c177128426a20d5c4f883c3402c7; no prior approval is being carried forward. Fresh-clone evidence: exact approved R1/R2/R3 heads were preserved in serial order, all 35 LFS objects fetched and passedgit lfs fsck,make testand strict high-fidelity verification passed, and pinned LilyPond 2.26.0 rebuilt all 29 entrypoints with semantic comparison passing (1,102 s). All 12 branch-only commits verify signed, the scoped added-line secret scan found zero candidates, the tree is clean, and no release was created. Forgejo Score run 19 remains queued asWaiting to run; approval/integration must wait for terminal-green CI on this exact head. The supported title-prefix Draft state remains intact.8b5d5f9b3b4747aadd4bHistory-remediation verification is complete for rewritten exact head
4747aadd4b453989c071e91d4dbe942d1d698790. Forgejo pull-request CI run 21 (https://code.mehalter.com/clawlter/memory-symphony/actions/runs/21) reached terminalsuccess. The branch retains exact approved R1a150e4db256fbdddcbe656f36674e434fadf7ee1, R213a46f9461ca86d23051bdb5fc553501f93dd3f0, and R3b647dcaa46f20c37b753e62d1cbd6e137b454e55as serialized ancestors; all newly authored commits are signed; every PR commit tree was scanned clean of operational backup/temp paths; and the final tree matches the prior reviewed head exactly. Correct R2 preview evidence issha256:ca16da1a2e43a393a01fd29fc464416e48b621e05344a6abcb5d8cf8444466bf, size32871644; do not use the earlierca16da1a2e43c152...claim. Fresh independent review is now required; do not merge.Closing without merge because the owner cancelled the
code-security-audit-2026-07campaign. This does not revert previously merged work.Pull request closed