FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Verifying publication through the running version
Directly comparing the current version with metadata returned by the Custom Domain
Purpose
Web delivery completion needed direct evidence of the version actually serving production traffic rather than a listing API subject to propagation delay.
Implementation
A runtime version-metadata binding was added, and the health response now exposes the running version. The delivery procedure compares the newly created version with health metadata through the Custom Domain every five seconds for up to ninety seconds, then checks major public routes on the same data plane.
The health route now reads version metadata from the running Worker and returns it in a non-cacheable response header. The public verification script can compare that value with the version expected for the deployment.
Rendering diagram…
What was confirmed
Verification results
Linting, delivery-contract checks, Web type checks and 30 tests, the Worker build, dry-run, and specification auditing passed.
At the cutoff, exact version matching on production traffic had not been verified.
Basis for completion
The work was complete when bounded verification directly comparing the version serving production traffic was implemented and tested.