PR-pressure redispatch should accept PR refs without hidden branch flags #1299
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
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
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/ward!1299
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-1166"
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?
Accept PR refs as continuation input for open-PR backpressure, and show
--branchin the engineer help surface again.This keeps the brokered engineer lane aligned with the documented
owner/repo!Nform, so director surfaces can continue existing PR work without discovering a hidden branch-only escape hatch.owner/repo!Nnow counts as existing PR work for the open-PR backpressure gate.--branchis visible inward agent engineer --helpagain, with continuation semantics spelled out.closes #1299
ward.workflow: pull-request-and-merge
WARDED_WORKFLOW: reservation-held
reservation details
Holder: launch intent for container
engineer-codex-ward-1299on hostkais-macbook-pro-2.local.Accepted by
ward agent --harness codex(reserved 2026-07-15T05:15:34Z). 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/ward#1299· branchissue-1299· harnesscodex· workflowpull-request-and-mergeengineer-codex-ward-1299· wardv0.697.0· dispatched2026-07-15T05:15:17ZStatic container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.697.0).
— Codex, via
ward agentWARDED_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.mdfollow-up: director merge sweep can land the green PR