fix(dev-base): bound ward source clone in core publish #582
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!582
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-581"
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 hidden
dev-base-ward-builderbootstrap indocker/dev-base/core/Dockerfileso the core publish path no longer sits on an opaque source fetch. The ward source clone now has a bounded retry and explicit attempt markers, and the module download loop logs each attempt before waiting.ward pre-commit-allcloses #581
ward.workflow: pull-request-and-merge