Recovery verification canary for ward 0.483 PR workflow #780

New issue

Closed

opened 2026-07-09 07:57:57 +00:00 by coilyco-ops · 4 comments

coilyco-ops commented

2026-07-09 07:57:57 +00:00

Member

Goal

Canary for ward#779 recovery verification. Make a tiny documentation-only clarification in the ward workflow docs, then carry it through a PR-shaped workflow.

Constraints

Keep the change documentation-only and low risk.
Mention WARD-RECOVERY-VERIFY-0483 in the PR body or issue comment so the reservation and worker context are easy to find.
Do not modify runtime code.

Codex, via ward agent

## Goal Canary for ward#779 recovery verification. Make a tiny documentation-only clarification in the ward workflow docs, then carry it through a PR-shaped workflow. ## Constraints * Keep the change documentation-only and low risk. * Mention `WARD-RECOVERY-VERIFY-0483` in the PR body or issue comment so the reservation and worker context are easy to find. * Do not modify runtime code.  Codex, via `ward agent`

coilyco-ops commented

2026-07-09 07:58:09 +00:00

Author

Member

🔒 Reserved by ward agent --harness codex — container engineer-codex-ward-780 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-09T07:58:07Z). 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/ward#780 · branch issue-780 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-780 · ward v0.483.0 · dispatched 2026-07-09T07:58:07Z
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.483.0).

— Codex, via ward agent

🔒 Reserved by `ward agent --harness codex` — container `engineer-codex-ward-780` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-09T07:58:07Z). 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/ward#780` · branch `issue-780` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-780` · ward `v0.483.0` · dispatched `2026-07-09T07:58:07Z` - **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.483.0). </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

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

Verify ward 0.483 director recovery behavior #779

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

2026-07-09 08:02:53 +00:00

docs: clarify salvage PR recovery path #783

coilyco-ops commented

2026-07-09 08:05:37 +00:00

Author

Member

WARD-OUTCOME: blocked - review summary: blocked: docs/agent-workflow.md:96-99 is internally inconsistent with the workflow matrix. It says a pr/patch-only run gets a...

Review panel verdicts:

codex: docs/agent-workflow.md:96-99 is internally inconsistent with the workflow matrix. It says a pr/patch-only run gets a separate recovery PR, but patch-only never opens a worker PR, and the same do... (conf 0.79)
claude: ERROR: claude: exit status 1: {"type":"system","subtype":"hook_started","hook_id":"cbd241af-f9b5-414e-a323-207c87ee9b51","hook_name":"SessionStart:startup","hook_event":"SessionStart","uuid":"06b7085b... (conf 0.00)
goose: ERROR: goose: exit status 1: error: No provider configured. Run 'goose configure' first. (conf 0.00)

— Codex, via ward agent

WARD-OUTCOME: blocked - review summary: blocked: docs/agent-workflow.md:96-99 is internally inconsistent with the workflow matrix. It says a `pr`/`patch-only` run gets a... Review panel verdicts: - codex: docs/agent-workflow.md:96-99 is internally inconsistent with the workflow matrix. It says a `pr`/`patch-only` run gets a separate recovery PR, but `patch-only` never opens a worker PR, and the same do... (conf 0.79) - claude: ERROR: claude: exit status 1: {"type":"system","subtype":"hook_started","hook_id":"cbd241af-f9b5-414e-a323-207c87ee9b51","hook_name":"SessionStart:startup","hook_event":"SessionStart","uuid":"06b7085b... (conf 0.00) - goose: ERROR: goose: exit status 1: error: No provider configured. Run 'goose configure' first. (conf 0.00)  — Codex, via `ward agent`

coilyco-ops commented

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

Author

Member

WARD-OUTCOME: done - review summary: passed: I tried to refute the doc change against the live workflow docs, the reaper implementation, and the issue thread, and th...

Review panel verdicts:

codex: I tried to refute the doc change against the live workflow docs, the reaper implementation, and the issue thread, and the new wording still matches the existing salvage-PR behavior. The issue contract... (conf 0.78)

— Codex, via ward agent

WARD-OUTCOME: done - review summary: passed: I tried to refute the doc change against the live workflow docs, the reaper implementation, and the issue thread, and th... Review panel verdicts: - codex: I tried to refute the doc change against the live workflow docs, the reaper implementation, and the issue thread, and the new wording still matches the existing salvage-PR behavior. The issue contract... (conf 0.78)  — Codex, via `ward agent`

coilyco-ops commented

2026-07-09 08:09:14 +00:00

Author

Member

This was straightforward after the first wording mismatch was caught. The only thing that fought back was the salvage-PR/patch-only boundary, which needed one more pass to match the implementation exactly. Confidence is high; no runtime code changed.

WARD-OUTCOME: done - clarified salvage PR recovery wording in docs/agent-workflow.md and carried it through PR 783 workflow: pull-requests-and-merge; review summary: passed: I tried to refute the doc change against the live workflow docs, the reaper implementation, and the issue thread, and th... This was straightforward after the first wording mismatch was caught. The only thing that fought back was the salvage-PR/patch-only boundary, which needed one more pass to match the implementation exactly. Confidence is high; no runtime code changed.