combine the workflow config with the repos config #547

Merged
coilyco-ops merged 2 commits from issue-535 into main 2026-07-15 05:38:22 +00:00
Owner

Move the landing policy into .ward/repos.kdl so the bundle keeps repo authority and workflow policy together. The docs now point at repos.workflow, and the regression test pins the combined shape.

  • Moved the workflow block into .ward/repos.kdl
  • Deleted .ward/workflow.kdl
  • Updated the ward-spec docs and bundle regression test

closes #535
ward.workflow: pull-request-and-merge

Move the landing policy into `.ward/repos.kdl` so the bundle keeps repo authority and workflow policy together. The docs now point at `repos.workflow`, and the regression test pins the combined shape. - Moved the workflow block into `.ward/repos.kdl` - Deleted `.ward/workflow.kdl` - Updated the ward-spec docs and bundle regression test closes #535 ward.workflow: pull-request-and-merge
fix(ward): combine workflow policy with repos bundle
Some checks failed
ci / ward-doctor (pull_request) Failing after 3m21s
ci / gate (pull_request) Successful in 4m8s
9c2c1ca657
Author
Owner

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-agentic-os-547 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T05:21:27Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation overrides.

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)
  • Resolved: coilyco-flight-deck/agentic-os#547 · branch issue-547 · harness codex · workflow pull-request-and-merge
  • Run: engineer-codex-agentic-os-547 · ward v0.697.0 · dispatched 2026-07-15T05:21:15Z
  • Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0).

— Codex, via ward agent

<!-- ward-agent-reservation --> WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-agentic-os-547` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T05:21:27Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` overrides. **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). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/agentic-os#547` · branch `issue-547` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-agentic-os-547` · ward `v0.697.0` · dispatched `2026-07-15T05:21:15Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
fix(ward): keep workflow in the repos bundle
All checks were successful
ci / ward-doctor (pull_request) Successful in 4m11s
ci / gate (pull_request) Successful in 3m15s
903f7a5cfb
coilyco-ops deleted branch issue-535 2026-07-15 05:38:22 +00:00
Author
Owner

WARDED_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.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/pulls/547 <details><summary>details</summary> 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. </details>
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agentic-os!547
No description provided.