Files
ci/bin
zeekay eee00a2ed3
Hanzo CI/CD / cicd (push) Waiting to run
CI/CD / gate (push) Waiting to run
site: publish assets before documents
The bytes are live where they land — this publisher writes into the prefix the
edge already serves, so there is no release to flip and every object is public
the moment S3 accepts it. One flat upload pass therefore ordered a document and
the hashed assets it names arbitrarily, and a document is only servable once all
of them are in the bucket.

Splitting the manifest on `.html` supplies that ordering with no coordination.
Asset names carry a content hash, so phase one only ever adds objects and what is
already published keeps serving through it; the document is the switch, thrown
once everything it can name is present. It also makes cancelling a superseded run
safe: the run dies in phase one having added unreferenced objects only.

Verified against a 6,734-file export: 5,786 assets then 948 documents, and all 41
assets index.html names land in phase one.
2026-08-26 11:20:35 -07:00
..
2026-08-24 11:18:34 -07:00
2026-08-24 11:18:34 -07:00
2026-08-26 11:20:35 -07:00