Title: Fix read-only director surfaces missing WARD_CONFIG_REF for ward… #455

New issue

Closed

opened 2026-07-10 21:51:05 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-10 21:51:05 +00:00

Member

Title: Fix read-only director surfaces missing WARD_CONFIG_REF for ward ops

Director surface repro from /workspace/agentic-os on 2026-07-10:

The environment has no WARD_CONFIG_REF.
Running ward ops forgejo describe fails before any tracker access:

ward: ward ops forgejo: guardfile runtime failed to mount: read bundle ops manifest ward.bundle.kdl: open ward.bundle.kdl: no such file or directory

Expected behavior: read-only director sessions can use ward ops forgejo without manual environment repair.

Context:

docs/dev-base-image.md says the platform seed sets AOS_REPO_ROOT plus WARD_CONFIG_REF before the read-only director shell starts.
docs/ward-specs.md says ward consumes the coilyco bundle through WARD_CONFIG_REF.
The current surface proves that guarantee is not true in at least one director session.

Task:

Fix the container/surface bootstrap or ward fallback so read-only director sessions get a valid WARD_CONFIG_REF, or so ward resolves the cwd .ward bundle correctly when the documented seed is absent.
Add a regression check that exercises the director/read-only bootstrap path or equivalent config-resolution path.
Verify ward ops forgejo describe succeeds in the fixed environment.
Run the repo's ward validation before landing.

Keep public-safe wording.

Filed by ward agent engineer --harness codex.

— Codex, via ward agent

Title: Fix read-only director surfaces missing WARD_CONFIG_REF for ward ops Director surface repro from `/workspace/agentic-os` on 2026-07-10: 1. The environment has no `WARD_CONFIG_REF`. 2. Running `ward ops forgejo describe` fails before any tracker access: ```text ward: ward ops forgejo: guardfile runtime failed to mount: read bundle ops manifest ward.bundle.kdl: open ward.bundle.kdl: no such file or directory ``` Expected behavior: read-only director sessions can use `ward ops forgejo` without manual environment repair. Context: - `docs/dev-base-image.md` says the platform seed sets `AOS_REPO_ROOT` plus `WARD_CONFIG_REF` before the read-only director shell starts. - `docs/ward-specs.md` says ward consumes the coilyco bundle through `WARD_CONFIG_REF`. - The current surface proves that guarantee is not true in at least one director session. Task: - Fix the container/surface bootstrap or ward fallback so read-only director sessions get a valid `WARD_CONFIG_REF`, or so ward resolves the cwd `.ward` bundle correctly when the documented seed is absent. - Add a regression check that exercises the director/read-only bootstrap path or equivalent config-resolution path. - Verify `ward ops forgejo describe` succeeds in the fixed environment. - Run the repo's ward validation before landing. Keep public-safe wording. --- Filed by `ward agent engineer --harness codex`.  — Codex, via `ward agent`

coilyco-ops commented

2026-07-10 21:51:13 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-agentic-os-455 on host KAI-DESKTOP-TOWER.

Reserved by ward agent --harness codex (reserved 2026-07-10T21:51:14Z). 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/agentic-os#455 · branch issue-455 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-agentic-os-455 · ward v0.605.0 · dispatched 2026-07-10T21:51:14Z
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.605.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-agentic-os-455` on host `KAI-DESKTOP-TOWER`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T21:51:14Z). 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/agentic-os#455` · branch `issue-455` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-agentic-os-455` · ward `v0.605.0` · dispatched `2026-07-10T21:51:14Z` - **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.605.0). </details> </details>  — Codex, via `ward agent`

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

2026-07-10 22:12:47 +00:00

Fix read-only director surfaces missing WARD_CONFIG_REF for ward ops #458

coilyco-ops closed this issue

2026-07-10 22:25:22 +00:00

coilyco-ops commented

2026-07-10 22:25:50 +00:00

Author

Member

WARD-OUTCOME: submitted

details

workflow: pull-request-and-merge; review summary: skipped
The review gate was intentionally skipped because the temporary ward default pending brokered QA.
The implementation felt straightforward after separating the bundle manifest from the bootstrap seam.
Confidence: high.
Surprises: the CI image did not guarantee ward, so the regression moved to the shell bootstrap path.
Follow-ups: none.

WARD-OUTCOME: submitted <details><summary>details</summary> workflow: pull-request-and-merge; review summary: skipped The review gate was intentionally skipped because the temporary ward default pending brokered QA. The implementation felt straightforward after separating the bundle manifest from the bootstrap seam. Confidence: high. Surprises: the CI image did not guarantee `ward`, so the regression moved to the shell bootstrap path. Follow-ups: none. </details>