Add bounded retries for dev-base publish probes #599
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!599
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-596"
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?
Add bounded retries around the narrow dev-base publish registry checks and source-image waits. The build step itself still fails immediately on deterministic Docker errors, so this only masks transient registry noise and makes the retry behavior visible in logs and step summaries.
closes #596
ward.workflow: pull-request-and-merge