PR-pressure redispatch should accept PR refs without hidden branch flags #1299

Merged
coilyco-ops merged 2 commits from issue-1166 into main 2026-07-15 05:26:08 +00:00
Member

Accept PR refs as continuation input for open-PR backpressure, and show --branch in the engineer help surface again.

This keeps the brokered engineer lane aligned with the documented owner/repo!N form, so director surfaces can continue existing PR work without discovering a hidden branch-only escape hatch.

  • owner/repo!N now counts as existing PR work for the open-PR backpressure gate.
  • --branch is visible in ward agent engineer --help again, with continuation semantics spelled out.
  • Validation: pre-commit lint passed on commit. Full Go test execution was blocked by container filesystem pressure in this run.

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

Accept PR refs as continuation input for open-PR backpressure, and show `--branch` in the engineer help surface again. This keeps the brokered engineer lane aligned with the documented `owner/repo!N` form, so director surfaces can continue existing PR work without discovering a hidden branch-only escape hatch. - `owner/repo!N` now counts as existing PR work for the open-PR backpressure gate. - `--branch` is visible in `ward agent engineer --help` again, with continuation semantics spelled out. - Validation: pre-commit lint passed on commit. Full Go test execution was blocked by container filesystem pressure in this run. closes #1299 ward.workflow: pull-request-and-merge
fix PR ref backpressure continuation
Some checks failed
test / test (pull_request) Failing after 34s
3d82c0da13
Author
Member

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1299 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T05:15:34Z). 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/ward#1299 · branch issue-1299 · harness codex · workflow pull-request-and-merge
  • Run: engineer-codex-ward-1299 · ward v0.697.0 · dispatched 2026-07-15T05:15:17Z
  • 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-ward-1299` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T05:15:34Z). 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/ward#1299` · branch `issue-1299` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1299` · ward `v0.697.0` · dispatched `2026-07-15T05:15:17Z` - **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`
docs: regenerate agent flags
All checks were successful
test / test (pull_request) Successful in 1m17s
c51e116b12
Author
Member

WARDED_WORKFLOW: #1299

details

workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA

Review gate intentionally skipped because the temporary ward default is pending brokered QA. The branch was already doing the right thing; the CI failure was just generated-doc drift.

confidence: high
surprise: only a trailing newline in docs/agent-flags.md
follow-up: director merge sweep can land the green PR

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1299 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate intentionally skipped because temporary ward default pending brokered QA Review gate intentionally skipped because the temporary ward default is pending brokered QA. The branch was already doing the right thing; the CI failure was just generated-doc drift. confidence: high surprise: only a trailing newline in `docs/agent-flags.md` follow-up: director merge sweep can land the green PR </details>
Sign in to join this conversation.
No description provided.