Development record
The charter, manifest.go and the brief surfaces index describe the manifest as timestamp-free and identical across two assemblies of one repository state, but it carries run_id, a minted timestamp plus entropy, so two dry-run assemblies of one HEAD produce different manifest hashes; state what holds — items and exclusions identical, the bundle byte-identical, the manifest differing only in run_id. Also the AssembleResult.OutDir comment claims a verbatim echo of an operator-supplied path while the front door now absolutises every relative --out against the working directory.
The charter, manifest.go and the brief surfaces index describe the manifest as timestamp-free and identical across two assemblies of one repository state, but it carries run_id, a minted timestamp plus entropy, so two dry-run assemblies of one HEAD produce different manifest hashes; state what holds — items and exclusions identical, the bundle byte-identical, the manifest differing only in run_id. Also the AssembleResult.OutDir comment claims a verbatim echo of an operator-supplied path while the front door now absolutises every relative --out against the working directory.
Frontmatter
| id | iss-2608300335037531 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2608300335037531-manifest-determinism-and-outdir-contract.md
open on GitHub ↗ · commit history ↗