Harden dev-base publish cache visibility and determinism #597
No reviewers
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agentic-os!597
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-594"
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?
This tightens the dev-base publish path so each tier reports the cache ref it reads and writes, plus a cheap provenance check before build. The core publish job now uses the same helper as the tier composite, so the cache breadcrumbing stays consistent across the whole family.
ward exec test -- tests/test_dev_base_image.py tests/test_dev_base_publish_workflows.py;ward exec pre-commit-all.closes #594
ward.workflow: pull-request-and-merge