coilyco-flight-deck/ward

Fork 0

container bootstrap: bash opencode path still gates on WARD_MODE=qwen (canonical is opencode) #498

New issue

Closed

opened 2026-07-02 02:45:33 +00:00 by coilysiren · 4 comments

coilysiren commented

2026-07-02 02:45:33 +00:00

Owner

Found

During ward#487 (retro, ward#492 burndown session): entrypoint.sh's compose_opencode_config and its launch case still test WARD_MODE = qwen, while the canonical mode name is now opencode. The #487 run gated around it defensively but left the mismatch in place as out of scope.

Deliverable

Align the bash bootstrap on opencode, deciding explicitly whether qwen stays as an accepted legacy alias or drops per the alias policy (see ward#448 for the README side of the naming).
Cover the path with the same feature-test treatment the #487 gate got, so the mismatch class cannot silently return.

Cross-refs

ward#487 - where the mismatch was found and gated around.
ward#448 - README names qwen as a harness, same naming cleanup family.

Filed by Claude Code (Fable) during the ward#492 burndown session.

## Found During ward#487 (retro, ward#492 burndown session): `entrypoint.sh`'s `compose_opencode_config` and its launch case still test `WARD_MODE = qwen`, while the canonical mode name is now `opencode`. The #487 run gated around it defensively but left the mismatch in place as out of scope. ## Deliverable * Align the bash bootstrap on `opencode`, deciding explicitly whether `qwen` stays as an accepted legacy alias or drops per the alias policy (see ward#448 for the README side of the naming). * Cover the path with the same feature-test treatment the #487 gate got, so the mismatch class cannot silently return. ## Cross-refs * ward#487 - where the mismatch was found and gated around. * ward#448 - README names qwen as a harness, same naming cleanup family. Filed by Claude Code (Fable) during the ward#492 burndown session.

coilyco-ops added the

consult

labels

2026-07-02 07:04:07 +00:00

coilyco-ops added

headless

and removed

consult

labels

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

coilyco-ops commented

2026-07-09 18:27:55 +00:00

Member

Consult interrogation: promoted to headless. The issue has a concrete bootstrap mismatch ( vs ) and a testable deliverable; no remaining design decision is needed before implementation.

coilyco-ops commented

2026-07-09 18:28:05 +00:00

Member

Correction to the promotion note: the concrete bootstrap mismatch is the qwen legacy mode check versus canonical opencode. The issue remains promoted to headless.

Correction to the promotion note: the concrete bootstrap mismatch is the `qwen` legacy mode check versus canonical `opencode`. The issue remains promoted to headless.

coilyco-ops commented

2026-07-09 21:53:31 +00:00

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-ward-498 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T21:53:29Z). 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#498 · branch issue-498 · harness codex · workflow direct-to-main
Run: engineer-codex-ward-498 · ward v0.522.0 · dispatched 2026-07-09T21:53:29Z
Comment thread: 2 included in the pre-flight read, 0 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-09T18:27:55Z), @coilyco-ops (2026-07-09T18:28:05Z)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.522.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-498` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T21:53:29Z). 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#498` · branch `issue-498` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-ward-498` · ward `v0.522.0` · dispatched `2026-07-09T21:53:29Z` - **Comment thread:** 2 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-09T18:27:55Z), @coilyco-ops (2026-07-09T18:28:05Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.522.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-09 22:08:16 +00:00

fix: canonicalize opencode bootstrap naming

coilyco-ops closed this issue

2026-07-09 22:08:16 +00:00

coilyco-ops commented

2026-07-09 22:08:49 +00:00

Member

WARD-OUTCOME: done

details

workflow: direct-main; review summary: review gate skipped by ~/.ward/config.yaml default felt: straightforward bootstrap renaming and test pin cleanup confidence: high surprises: the container hit cache-space limits during full `ward exec` runs, so I verified the change with targeted reasoning and the repo hooks on commit follow-ups: none

WARD-OUTCOME: done <details><summary>details</summary> workflow: direct-main; review summary: review gate skipped by ~/.ward/config.yaml default felt: straightforward bootstrap renaming and test pin cleanup confidence: high surprises: the container hit cache-space limits during full `ward exec` runs, so I verified the change with targeted reasoning and the repo hooks on commit follow-ups: none </details>

coilysiren referenced this issue

2026-07-14 15:27:09 +00:00

director should emit colorized, space buffered, visually distinct messages about the categories of actions its performing on startup #1283