combine the workflow config with the repos config #547
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!547
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-535"
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?
Move the landing policy into
.ward/repos.kdlso the bundle keeps repo authority and workflow policy together. The docs now point atrepos.workflow, and the regression test pins the combined shape..ward/repos.kdl.ward/workflow.kdlcloses #535
ward.workflow: pull-request-and-merge
WARDED_WORKFLOW: reservation-held
reservation details
Holder: launch intent for container
engineer-codex-agentic-os-547on hostkais-macbook-pro-2.local.Accepted by
ward agent --harness codex(reserved 2026-07-15T05:21:27Z). 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#547· branchissue-547· harnesscodex· workflowpull-request-and-mergeengineer-codex-agentic-os-547· wardv0.697.0· dispatched2026-07-15T05:21:15ZStatic container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0).
— Codex, via
ward agentWARDED_WORKFLOW: #547
details
workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA.
Retrospective: The fix was a parser shape mismatch, not a bundle content bug.
Confidence: high.
Surprise: ward main still required the workflow block to stay top-level in
.ward/repos.kdl.Follow-ups: none.