Directors don't need to start inside a git repo anymore #1112

New issue

Closed

opened 2026-07-11 15:40:04 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-11 15:40:04 +00:00

Owner

The problem

Proposed change

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 // ### 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 added the

headless

labels

2026-07-14 06:50:10 +00:00

coilyco-ops commented

2026-07-14 09:18:53 +00:00

Member

WARDED_WORKFLOW: reservation-held

reservation details

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

Accepted by ward agent --harness codex (reserved 2026-07-14T09:18:52Z). 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#1112 · branch issue-1112 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1112 · ward v0.672.0 · dispatched 2026-07-14T09:18:48Z
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.672.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1112` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-14T09:18:52Z). 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#1112` · branch `issue-1112` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1112` · ward `v0.672.0` · dispatched `2026-07-14T09:18:48Z` - **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.672.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-14 09:33:49 +00:00

fix: let directors start outside a git repo #1259

coilyco-ops closed this issue

2026-07-14 09:39:36 +00:00

coilyco-ops commented

2026-07-14 09:40:16 +00:00

Member

WARDED_WORKFLOW: #1259

details

workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default

The change felt narrow once the shared director scope resolver was isolated. Confidence is high on the scope logic and medium on the overall landing because the container ran out of disk during local Go and pre-commit bootstrap. Surprise: the first regression test used an org token and would have exercised a live expansion path, so I tightened it to repo slugs only.

Follow-ups: none.

WARDED_WORKFLOW: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/1259 <details><summary>details</summary> workflow: pull-request-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default The change felt narrow once the shared director scope resolver was isolated. Confidence is high on the scope logic and medium on the overall landing because the container ran out of disk during local Go and pre-commit bootstrap. Surprise: the first regression test used an org token and would have exercised a live expansion path, so I tightened it to repo slugs only. Follow-ups: none. </details>