Diagnose fast publish-core failure after bounded clone fix #583
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
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#583
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
The targeted publish-core repair from PR #582 landed and fixed main CI, but the next dev-base publication still failed before producing
agentic-os-full:latest.Evidence:
81cdc64dc05283f4b2d55e65b33093c0edf3df28.ci.ymlrun 8459 / #1420 succeeded.dev-base-publish.ymlrun 8463 / #1423 failed on the same exact SHA after about 2m16s.agentic-os-full:latestremains absent (manifest unknown).publish-core.Diagnose the exact fast
publish-corefailure after PR #582, repair it if repository-owned, and preserve the bounded clone plus retry/resume behavior. If an external registry/storage condition is the wall, make the workflow emit the precise actionable condition without broad diagnostic churn.Acceptance:
dev-base-publish.ymlrun passespublish-core, or the exact external blocker and required operator action are recorded.agentic-os-full:latestbecomes available, or the issue remains open with the precise external blocker.WARDED_WORKFLOW: reservation-held
reservation details
Holder: launch intent for container
engineer-codex-agentic-os-583on host74a70515a491.Accepted by
ward agent --harness codex(reserved 2026-07-15T10:36:13Z). Concurrentward agentruns are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL).--override-reservationoverrides.Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).
run seed context — what this run is carrying (ward#609)
coilyco-flight-deck/agentic-os#583· branchissue-583· harnesscodex· workflowpull-request-and-mergeengineer-codex-agentic-os-583· wardv0.710.0· dispatched2026-07-15T10:36:10ZStatic container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.710.0).
— Codex, via
ward agentWARDED_WORKFLOW: dispatch-deferred
launch failure details
The repair run never started.
warded engineer coilyco-flight-deck/agentic-os#583 --harness codex --workflow pull-request-and-mergefailed before container creation becauseforgejo.coilysiren.me/coilyco-flight-deck/agentic-os-full:latestwas unavailable remotely and no local image existed. Docker has noengineer-codex-agentic-os-583container. No implementation work was performed.The reservation is released for redispatch from a fresh director. Issue #583 remains the concrete repair for failed publish run 8463 on SHA
81cdc64dc05283f4b2d55e65b33093c0edf3df28.ward agentWARDED_WORKFLOW: reservation-held
reservation details
Holder: launch intent for container
engineer-codex-agentic-os-583on host74a70515a491.Accepted by
ward agent --harness codex(reserved 2026-07-15T11:36:15Z). Concurrentward agentruns are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL).--override-reservationoverrides.Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).
run seed context — what this run is carrying (ward#609)
coilyco-flight-deck/agentic-os#583· branchissue-583· harnesscodex· workflowpull-request-and-mergeengineer-codex-agentic-os-583· wardv0.710.0· dispatched2026-07-15T11:36:11ZStatic container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.710.0).
— Codex, via
ward agentWARDED_WORKFLOW: dispatch-deferred
launch failure details
A fresh repair run was attempted after dev-base-publish run 8500 failed and the image remained unavailable. The stale 10:36 reservation was safely reclaimed because dispatch-health showed zero running/held Agentic engineers and no container. The new launch then failed before start while Ward v0.710 seeded the release image: docker cp to /opt/agentic-os/ward-shell-entrypoint.sh returned not a directory. The created container engineer-codex-agentic-os-583 was stopped; no engineer code ran and no branch or PR was created.
This surface cannot use its brokered stop endpoint, so the reservation is released by this explicit failed-prelaunch record for redispatch from a compatible director. Issue #583 remains the direct repair for failed dev-base-publish run 8500 / #1429 and the absent agentic-os-full:latest manifest.