← Results index

Enforce shared artifact drift check before push/deploy

2026-08-18T20:32:54Z Bug fix completed Quantmodel now fails closed on deterministic shared-artifact drift: pipeline verification and the scheduled worker check the offline shared bundle before shipping, Pages runs for artifact-source and catalog-canary changes, and regenerated shared/pipeline artifacts plus regressions keep the deploy bundle current.

Objective

Prevent deterministic shared-artifact drift from reaching main or leaving the Cloudflare Pages deployment red. Pipeline verification and the scheduled Beads worker must detect drift before push or PR creation, relevant source-only changes must trigger Pages validation, and the required offline rebuild command must be documented.

Approach

Added the canonical shared-artifact check to the offline pipeline verifier and made the verification prompt require a revisit rather than a pass when drift exists. Added the same fail-closed command to the worker's awaiting_shipping boundary before staging, pushing, or opening a PR. Expanded the Pages workflow paths to cover artifact sources and catalog-canary inputs, documented the rebuild command, and regenerated every task-owned public artifact through its producer.

Files changed

Validation

Results

Shared-artifact drift can no longer silently pass the pipeline or the scheduled worker's shipping boundary. Source-only changes under the artifact and catalog-canary trees now start the Pages workflow, stale output errors name the canonical offline rebuild command, and the checked-in shared bundle and pipeline visualization are current. No credentials, private data, or database mutations were involved.

Source artifact: research/results/qm-6awh.md