Correct coilyco workflow defaults: only ward uses pull-requests-and-merge

coilyco-ops commented

2026-07-09 00:44:44 +00:00

Owner

Problem

The coilyco ward workflow default config was applied in the wrong direction: instead of only the ward repo using pull requests, all repos started producing PRs. That breaks the intended dispatch posture.

Kai also corrected the workflow vocabulary: the config option should use spelled-out workflow names, not pr.

Desired config

Once ward supports the corrected workflow values, the aos-authored coilyco bundle should resolve as:

fleet default: direct-main
coilyco-flight-deck/ward: pull-requests-and-merge

Do not set a global pull-request default for all coilyco repos.

Use spelled-out names in config. pull-requests means open a PR and stop. pull-requests-and-merge means open a PR, wait for checks/review, then merge.

Do

Update the aos ward bundle config from the stale pr framing to the corrected values.
Ensure only coilyco-flight-deck/ward is overridden away from direct-main.
Use pull-requests-and-merge for ward, not pull-requests.
Update docs that mention the coilyco override.
Add or update validation so a future bundle change cannot accidentally flip every repo into pull-request workflow.

Acceptance

The coilyco bundle resolves non-ward repos to direct-main.
coilyco-flight-deck/ward resolves to pull-requests-and-merge.
The config uses spelled-out workflow names, not pr.
Validation passes.

Related: ward workflow vocabulary correction issue to split pull-requests from pull-requests-and-merge.

## Problem The coilyco ward workflow default config was applied in the wrong direction: instead of only the ward repo using pull requests, all repos started producing PRs. That breaks the intended dispatch posture. Kai also corrected the workflow vocabulary: the config option should use spelled-out workflow names, not `pr`. ## Desired config Once ward supports the corrected workflow values, the aos-authored coilyco bundle should resolve as: * fleet default: `direct-main` * `coilyco-flight-deck/ward`: `pull-requests-and-merge` Do **not** set a global pull-request default for all coilyco repos. Use spelled-out names in config. `pull-requests` means open a PR and stop. `pull-requests-and-merge` means open a PR, wait for checks/review, then merge. ## Do * Update the aos ward bundle config from the stale `pr` framing to the corrected values. * Ensure only `coilyco-flight-deck/ward` is overridden away from `direct-main`. * Use `pull-requests-and-merge` for ward, not `pull-requests`. * Update docs that mention the coilyco override. * Add or update validation so a future bundle change cannot accidentally flip every repo into pull-request workflow. ## Acceptance * The coilyco bundle resolves non-ward repos to `direct-main`. * `coilyco-flight-deck/ward` resolves to `pull-requests-and-merge`. * The config uses spelled-out workflow names, not `pr`. * Validation passes. Related: ward workflow vocabulary correction issue to split `pull-requests` from `pull-requests-and-merge`.

coilyco-ops added the

labels

2026-07-09 00:44:55 +00:00

coilyco-ops commented

2026-07-09 00:45:25 +00:00

Author

Owner

🔒 Reserved by ward agent --harness codex — container engineer-codex-agentic-os-351 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T00:45:23Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force 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#351 · branch issue-351 · harness codex · workflow pr
Run: engineer-codex-agentic-os-351 · ward v0.470.0 · dispatched 2026-07-09T00:45:23Z
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.470.0).

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-agentic-os-351` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T00:45:23Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL); `--force` 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#351` · branch `issue-351` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-agentic-os-351` · ward `v0.470.0` · dispatched `2026-07-09T00:45:23Z` - **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.470.0). </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 00:52:33 +00:00

Correct coilyco workflow defaults #352

coilyco-ops commented

2026-07-09 00:53:15 +00:00

Author

Owner

WARD-OUTCOME: blocked - review summary: blocked: codex: exit status 1

Review panel verdicts:

codex: ERROR: codex: exit status 1 (conf 0.00)
claude: ERROR: claude: exit status 1 (conf 0.00)
goose: ERROR: goose: exit status 1 (conf 0.00)

— Codex, via ward agent

WARD-OUTCOME: blocked - review summary: blocked: codex: exit status 1 Review panel verdicts: - codex: ERROR: codex: exit status 1 (conf 0.00) - claude: ERROR: claude: exit status 1 (conf 0.00) - goose: ERROR: goose: exit status 1 (conf 0.00)  — Codex, via `ward agent`

coilyco-ops commented

2026-07-09 00:54:05 +00:00

Author

Owner

WARD-OUTCOME: blocked - ward review gate could not authenticate, so the PR was closed instead of being landed.
Review summary: blocked: codex: exit status 1
The bundle change itself was straightforward. The review tool fought back on auth, so confidence in the diff is high from tests but not from the required review path.

WARD-OUTCOME: blocked - ward review gate could not authenticate, so the PR was closed instead of being landed. Review summary: blocked: codex: exit status 1 The bundle change itself was straightforward. The review tool fought back on auth, so confidence in the diff is high from tests but not from the required review path.

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 00:54:16 +00:00

ward salvage: ward-salvage/agentic-os-69907181 #353

coilyco-ops commented

2026-07-09 00:54:16 +00:00

Author

Owner

⚠️ Reopened: this run's work did not land on `main`

An ephemeral ward container (codex mode) dispatched for this issue finished but its work was not merged to main, so the reaper preserved it on a branch before teardown and reopened the issue (a closing reference for #351 never reached main). Recover from the salvage branch below.

Repo: coilyco-flight-deck/agentic-os
Salvage branch: ward-salvage/agentic-os-69907181
Pull request: not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input
Reason: run workflow does not land on main (--workflow pr/patch-only)
Container uptime at reap: 8m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token)

Reap diagnostics

--- reap diagnostics ---
ward version:      v0.470.0
version source:    pinned via WARD_VERSION/--ward-version (v0.470.0)
HEAD:              aa3ab933498c
origin/main:       ae3677c83d75
ancestry:          HEAD is NOT yet on origin/main - residual work remains to land
decision gate:     workflow does not land on main (--workflow pr/patch-only)
reason:            run workflow does not land on main (--workflow pr/patch-only)
provenance:        not read (workflow hold)
run-owned landed:  no
working tree:      clean
container uptime:  8m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os.git ward-salvage/agentic-os-69907181
git checkout -b ward-salvage/agentic-os-69907181 FETCH_HEAD

— Codex, via ward agent

## ⚠️ Reopened: this run's work did not land on `main` An ephemeral `ward container` (codex mode) dispatched for this issue finished but its work was **not merged to `main`**, so the reaper preserved it on a branch before teardown and reopened the issue (a closing reference for #351 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/agentic-os` - **Salvage branch:** `ward-salvage/agentic-os-69907181` - **Pull request:** not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input - **Reason:** run workflow does not land on main (--workflow pr/patch-only) - **Container uptime at reap:** 8m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token) ## Reap diagnostics ``` --- reap diagnostics --- ward version: v0.470.0 version source: pinned via WARD_VERSION/--ward-version (v0.470.0) HEAD: aa3ab933498c origin/main: ae3677c83d75 ancestry: HEAD is NOT yet on origin/main - residual work remains to land decision gate: workflow does not land on main (--workflow pr/patch-only) reason: run workflow does not land on main (--workflow pr/patch-only) provenance: not read (workflow hold) run-owned landed: no working tree: clean container uptime: 8m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os.git ward-salvage/agentic-os-69907181 git checkout -b ward-salvage/agentic-os-69907181 FETCH_HEAD ```  — Codex, via `ward agent`

coilyco-ops commented

2026-07-09 04:51:59 +00:00

Author

Owner

🔒 Reserved by ward agent --harness codex — container engineer-codex-agentic-os-351 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T04:51:57Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force 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#351 · branch issue-351 · harness codex · workflow pr
Run: engineer-codex-agentic-os-351 · ward v0.470.0 · dispatched 2026-07-09T04:51:57Z
Comment thread: 3 included in the pre-flight read, 1 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-09T00:53:15Z), @coilyco-ops (2026-07-09T00:54:05Z), @coilyco-ops (2026-07-09T00:54:16Z)
- stripped: @coilyco-ops (2026-07-09T00:45:25Z)

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

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-agentic-os-351` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T04:51:57Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL); `--force` 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#351` · branch `issue-351` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-agentic-os-351` · ward `v0.470.0` · dispatched `2026-07-09T04:51:57Z` - **Comment thread:** 3 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T00:53:15Z), @coilyco-ops (2026-07-09T00:54:05Z), @coilyco-ops (2026-07-09T00:54:16Z) - stripped: @coilyco-ops (2026-07-09T00:45:25Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.470.0). </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-09 05:06:33 +00:00

Author

Owner

WARD-OUTCOME: blocked - review summary: blocked: codex: exit status 1

Review panel verdicts:

codex: ERROR: codex: exit status 1 (conf 0.00)
claude: ERROR: claude: exit status 1 (conf 0.00)
goose: ERROR: goose: exit status 1 (conf 0.00)

— Codex, via ward agent

WARD-OUTCOME: blocked - review summary: blocked: codex: exit status 1 Review panel verdicts: - codex: ERROR: codex: exit status 1 (conf 0.00) - claude: ERROR: claude: exit status 1 (conf 0.00) - goose: ERROR: goose: exit status 1 (conf 0.00)  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 05:07:23 +00:00

ward salvage: ward-salvage/agentic-os-4fd26694 #365

coilyco-ops commented

2026-07-09 05:07:24 +00:00

Author

Owner

⚠️ Reopened: this run's work did not land on `main`

An ephemeral ward container (codex mode) dispatched for this issue finished but its work was not merged to main, so the reaper preserved it on a branch before teardown and reopened the issue (a closing reference for #351 never reached main). Recover from the salvage branch below.

Repo: coilyco-flight-deck/agentic-os
Salvage branch: ward-salvage/agentic-os-4fd26694
Pull request: not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input
Reason: run workflow does not land on main (--workflow pr/patch-only)
Container uptime at reap: 14m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token)

Reap diagnostics

--- reap diagnostics ---
ward version:      v0.470.0
version source:    pinned via WARD_VERSION/--ward-version (v0.470.0)
HEAD:              8437c91539a0
origin/main:       fe2b9bdf8b46
ancestry:          HEAD is NOT yet on origin/main - residual work remains to land
decision gate:     workflow does not land on main (--workflow pr/patch-only)
reason:            run workflow does not land on main (--workflow pr/patch-only)
provenance:        not read (workflow hold)
run-owned landed:  no
working tree:      clean
container uptime:  14m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os.git ward-salvage/agentic-os-4fd26694
git checkout -b ward-salvage/agentic-os-4fd26694 FETCH_HEAD

— Codex, via ward agent

## ⚠️ Reopened: this run's work did not land on `main` An ephemeral `ward container` (codex mode) dispatched for this issue finished but its work was **not merged to `main`**, so the reaper preserved it on a branch before teardown and reopened the issue (a closing reference for #351 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/agentic-os` - **Salvage branch:** `ward-salvage/agentic-os-4fd26694` - **Pull request:** not opened - PR creation failed: forgejo: parse created pull request: unexpected end of JSON input - **Reason:** run workflow does not land on main (--workflow pr/patch-only) - **Container uptime at reap:** 14m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token) ## Reap diagnostics ``` --- reap diagnostics --- ward version: v0.470.0 version source: pinned via WARD_VERSION/--ward-version (v0.470.0) HEAD: 8437c91539a0 origin/main: fe2b9bdf8b46 ancestry: HEAD is NOT yet on origin/main - residual work remains to land decision gate: workflow does not land on main (--workflow pr/patch-only) reason: run workflow does not land on main (--workflow pr/patch-only) provenance: not read (workflow hold) run-owned landed: no working tree: clean container uptime: 14m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os.git ward-salvage/agentic-os-4fd26694 git checkout -b ward-salvage/agentic-os-4fd26694 FETCH_HEAD ```  — Codex, via `ward agent`

coilyco-ops commented

2026-07-09 06:22:18 +00:00

Author

Owner

Director recovery note, 2026-07-09T06:22Z:

The salvage PR #365 has the right shape for this issue, but it is stale after the temporary prose merge/revert on main. A local merge test of pull/365/head onto current agentic-os main (ce0599bbe73f7aa2d21653a7d7f794a7e1ed5419) conflicts only in:

docs/FEATURES.md

The fresh run should reapply the #365 behavior on top of current main:

add .ward/ward-kdl.defaults.kdl with fleet default direct-main and only coilyco-flight-deck/ward overridden to pull-requests-and-merge.
package ward-kdl.defaults.kdl in the release bundle.
keep the new pre-commit/catalog validation for the coilyco ward-specs bundle.
preserve current main docs, including the revert of the earlier workflow-prose change.

Use --skip-review for this incident recovery lane.

Director recovery note, 2026-07-09T06:22Z: The salvage PR #365 has the right shape for this issue, but it is stale after the temporary prose merge/revert on main. A local merge test of `pull/365/head` onto current agentic-os main (`ce0599bbe73f7aa2d21653a7d7f794a7e1ed5419`) conflicts only in: * `docs/FEATURES.md` The fresh run should reapply the #365 behavior on top of current main: * add `.ward/ward-kdl.defaults.kdl` with fleet default `direct-main` and only `coilyco-flight-deck/ward` overridden to `pull-requests-and-merge`. * package `ward-kdl.defaults.kdl` in the release bundle. * keep the new pre-commit/catalog validation for the coilyco ward-specs bundle. * preserve current main docs, including the revert of the earlier workflow-prose change. Use `--skip-review` for this incident recovery lane.

coilyco-ops commented

2026-07-09 06:22:27 +00:00

Author

Owner

🔒 Reserved by ward agent --harness codex — container engineer-codex-agentic-os-351 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T06:22:26Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force 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#351 · branch issue-351 · harness codex · workflow pr
Run: engineer-codex-agentic-os-351 · ward v0.474.0 · dispatched 2026-07-09T06:22:26Z
Comment thread: 6 included in the pre-flight read, 2 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-09T00:53:15Z), @coilyco-ops (2026-07-09T00:54:05Z), @coilyco-ops (2026-07-09T00:54:16Z), @coilyco-ops (2026-07-09T05:06:33Z), @coilyco-ops (2026-07-09T05:07:24Z), @coilyco-ops (2026-07-09T06:22:18Z)
- stripped: @coilyco-ops (2026-07-09T00:45:25Z), @coilyco-ops (2026-07-09T04:51:59Z)

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

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-agentic-os-351` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T06:22:26Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL); `--force` 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#351` · branch `issue-351` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-agentic-os-351` · ward `v0.474.0` · dispatched `2026-07-09T06:22:26Z` - **Comment thread:** 6 included in the pre-flight read, 2 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T00:53:15Z), @coilyco-ops (2026-07-09T00:54:05Z), @coilyco-ops (2026-07-09T00:54:16Z), @coilyco-ops (2026-07-09T05:06:33Z), @coilyco-ops (2026-07-09T05:07:24Z), @coilyco-ops (2026-07-09T06:22:18Z) - stripped: @coilyco-ops (2026-07-09T00:45:25Z), @coilyco-ops (2026-07-09T04:51:59Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.474.0). </details>  — Codex, via `ward agent`

~~coilyco-ops referenced this issue 2026-07-09 06:33:38 +00:00~~

Fix root-owned ~/.ward in dev-base director surfaces so warded can audit #368

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 06:34:02 +00:00

Correct coilyco workflow defaults: only ward uses pull-requests-and-merge #369

coilyco-ops commented

2026-07-09 06:34:28 +00:00

Author

Owner

WARD-OUTCOME: done - opened PR 369 with the corrected ward workflow defaults
workflow: pull-requests-and-merge; review summary: skipped by --skip-review / --no-review-gate

The bundle update went cleanly once the branch history was reconciled. The only surprise was the preexisting salvage branch noise, so this landed as a rebase plus PR refresh instead of a straight push. Confidence is high, and the remaining rough edge is just the older branch history around the issue, not the bundle itself.

WARD-OUTCOME: done - opened PR 369 with the corrected ward workflow defaults workflow: pull-requests-and-merge; review summary: skipped by --skip-review / --no-review-gate The bundle update went cleanly once the branch history was reconciled. The only surprise was the preexisting salvage branch noise, so this landed as a rebase plus PR refresh instead of a straight push. Confidence is high, and the remaining rough edge is just the older branch history around the issue, not the bundle itself.

coilyco-ops commented

2026-07-09 06:37:42 +00:00

Author

Owner

Director triage, 2026-07-09T06:41Z:

Fresh PR #369 was closed as unsafe because its branch was based on the old salvage branch, not current main. A correct recovery should start from current main after PR #368, then reapply only the #351 change set:

keep .ward/ward-kdl.defaults.kdl with fleet default direct-main; only coilyco-flight-deck/ward uses pull-requests-and-merge.
keep the ward-spec bundle packaging and validation tests.
do not touch release action wrappers, release shell libraries, or old #365 salvage-only files.
preserve the current docs state from main.

Director triage, 2026-07-09T06:41Z: Fresh PR #369 was closed as unsafe because its branch was based on the old salvage branch, not current main. A correct recovery should start from current `main` after PR #368, then reapply only the #351 change set: * keep `.ward/ward-kdl.defaults.kdl` with fleet default `direct-main`; only `coilyco-flight-deck/ward` uses `pull-requests-and-merge`. * keep the ward-spec bundle packaging and validation tests. * do not touch release action wrappers, release shell libraries, or old #365 salvage-only files. * preserve the current docs state from main.

coilyco-ops commented

2026-07-09 06:37:55 +00:00

Author

Owner

🔒 Reserved by ward agent --harness codex — container engineer-codex-agentic-os-351 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T06:37:53Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL); --force 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#351 · branch issue-351 · harness codex · workflow pr
Run: engineer-codex-agentic-os-351 · ward v0.474.0 · dispatched 2026-07-09T06:37:53Z
Comment thread: 8 included in the pre-flight read, 3 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-09T00:53:15Z), @coilyco-ops (2026-07-09T00:54:05Z), @coilyco-ops (2026-07-09T00:54:16Z), @coilyco-ops (2026-07-09T05:06:33Z), @coilyco-ops (2026-07-09T05:07:24Z), @coilyco-ops (2026-07-09T06:22:18Z), @coilyco-ops (2026-07-09T06:34:28Z), @coilyco-ops (2026-07-09T06:37:42Z)
- stripped: @coilyco-ops (2026-07-09T00:45:25Z), @coilyco-ops (2026-07-09T04:51:59Z), @coilyco-ops (2026-07-09T06:22:27Z)

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

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-agentic-os-351` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T06:37:53Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL); `--force` 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#351` · branch `issue-351` · harness `codex` · workflow `pr` - **Run:** `engineer-codex-agentic-os-351` · ward `v0.474.0` · dispatched `2026-07-09T06:37:53Z` - **Comment thread:** 8 included in the pre-flight read, 3 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T00:53:15Z), @coilyco-ops (2026-07-09T00:54:05Z), @coilyco-ops (2026-07-09T00:54:16Z), @coilyco-ops (2026-07-09T05:06:33Z), @coilyco-ops (2026-07-09T05:07:24Z), @coilyco-ops (2026-07-09T06:22:18Z), @coilyco-ops (2026-07-09T06:34:28Z), @coilyco-ops (2026-07-09T06:37:42Z) - stripped: @coilyco-ops (2026-07-09T00:45:25Z), @coilyco-ops (2026-07-09T04:51:59Z), @coilyco-ops (2026-07-09T06:22:27Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.474.0). </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

2026-07-09 06:40:30 +00:00

ward salvage: ward-salvage/agentic-os-4fd26694 #365

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-09 06:47:45 +00:00

Fix coilyco workflow defaults #370

coilyco-ops commented

2026-07-09 06:48:00 +00:00

Author

Owner

WARD-OUTCOME: done - corrected coilyco ward defaults and added bundle validation
workflow: pr; review summary: skipped because review gate skipped by --skip-review / --no-review-gate
The bundle change itself was straightforward. The only friction was the stale remote issue branch and the docs cap, both resolved cleanly. Confidence is high, and the remaining rough edge is just human review/merge.

WARD-OUTCOME: done - corrected coilyco ward defaults and added bundle validation workflow: pr; review summary: skipped because review gate skipped by --skip-review / --no-review-gate The bundle change itself was straightforward. The only friction was the stale remote issue branch and the docs cap, both resolved cleanly. Confidence is high, and the remaining rough edge is just human review/merge.

coilyco-ops closed this issue

2026-07-09 06:52:24 +00:00

Rows
Columns

Correct coilyco workflow defaults: only ward uses pull-requests-and-merge #351

Problem

Desired config

Do

Acceptance

⚠️ Reopened: this run's work did not land on main

Reap diagnostics

Recover

⚠️ Reopened: this run's work did not land on main

Reap diagnostics

Recover

⚠️ Reopened: this run's work did not land on `main`

⚠️ Reopened: this run's work did not land on `main`