coilyco-flight-deck/ward

Archived

Watch

Only allow 3 engineers to be working in a repo at a time #1124

Closed

opened 2026-07-12 05:22:17 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-12 05:22:17 +00:00

Owner

The problem

Proposed change

composes with the total PR limit

Alternatives considered

No response

Before filing

I searched existing issues and this is not a duplicate.
This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb.

### The problem // ### Proposed change composes with the total PR limit ### Alternatives considered _No response_ ### Before filing - [x] I searched existing issues and this is not a duplicate. - [x] This stays within ward's scope (the dev-verb gate / agent driver), not a personal-infra or downstream-repo verb.

coilyco-ops commented

2026-07-13 03:41:32 +00:00

Owner

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-1124 on host KAI-DESKTOP-TOWER.

Reserved by ward agent --harness codex (reserved 2026-07-13T03:41:29Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (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#1124 · branch issue-1124 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1124 · ward v0.633.0 · dispatched 2026-07-13T03:41:29Z
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.633.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-1124` on host `KAI-DESKTOP-TOWER`. Reserved by `ward agent --harness codex` (reserved 2026-07-13T03:41:29Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (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#1124` · branch `issue-1124` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1124` · ward `v0.633.0` · dispatched `2026-07-13T03:41:29Z` - **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.633.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-13 04:01:27 +00:00

feat: cap repo engineer launches

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

2026-07-13 04:01:59 +00:00

Only allow 3 engineers to be working in a repo at a time #1165

coilyco-ops commented

2026-07-13 04:03:23 +00:00

Owner

WARD-OUTCOME: submitted

details

workflow: pull-request-and-merge; review summary: skipped (temporary ward default pending brokered QA)
retrospective: the repo gate fit beside the existing PR cap, but it needed a repo-scoped launch lock to stay race-safe.
confidence: high
surprises: the old global-cap test had to be made repo-aware so it would not trip the new cap first.
follow-ups: none

WARD-OUTCOME: submitted <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped (temporary ward default pending brokered QA) retrospective: the repo gate fit beside the existing PR cap, but it needed a repo-scoped launch lock to stay race-safe. confidence: high surprises: the old global-cap test had to be made repo-aware so it would not trip the new cap first. follow-ups: none </details>

coilysiren closed this issue

2026-07-13 07:30:06 +00:00

coilysiren referenced this issue from a commit

2026-07-13 07:30:06 +00:00

Merge ward PR #1165: Only allow 3 engineers working in a repo at a time

Commenting is not possible because the repository is archived.

No milestone

No project

No assignees

2 participants

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/ward#1124

No description provided.

Rows
Columns