coilyco-flight-deck/ward

Fork 0

Correct PR 802: move default substrate ownership to aos #805

New issue

Closed

opened 2026-07-09 15:52:09 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

2026-07-09 15:52:09 +00:00

Member

PR #802 closed #801 by removing coilyco-flight-deck/ward from ward's embedded default substrate manifest:

cmd/ward/containerassets/preclone-repos.txt dropped coilyco-flight-deck/ward.
cmd/ward/container_substrate_test.go began failing if ward appears in the embedded manifest.
cmd/ward/containerassets/AGENTS.container.md, docs/container-substrate.md, and docs/FEATURES.md now document that ward is excluded from default substrate.

Correction from Kai: the default repo substrate was supposed to move into aos, not become a ward-side deletion. Aos owns the dev-base image and seed content, so the default/image-tier substrate list should be canonical in coilyco-flight-deck/agentic-os. Ward should not encode the product decision by removing itself from its own manifest.

Do:

Revert or reshape the ward-side #802 changes so ward no longer asserts that coilyco-flight-deck/ward must be absent from the embedded substrate manifest.
Keep ward-targeted /workspace/ward vs /substrate/ward doctrine correct: /workspace remains authoritative for work, /substrate remains read-only reference when present.
Point docs/comments at aos ownership for the default substrate list, not ward ownership.
In the paired aos repo work, close coilyco-flight-deck/agentic-os#373 by making aos canonical for docker/dev-base/substrate-image-repos.txt and its docs/comments.
If a generated-copy flow is needed, implement the smallest durable path. Do not leave two files both claiming to be canonical.

Acceptance:

Ward tests no longer enforce "ward absent from default substrate".
Ward docs no longer say the default substrate slice intentionally omits ward itself.
Aos docs/comments say aos owns the image-tier substrate set because aos owns the dev-base image/seed.
coilyco-flight-deck/ward#802 is effectively corrected, and coilyco-flight-deck/agentic-os#373 is closed by the aos-side landing.
Run relevant ward and aos validation through ward / pre-commit.

Related: #802

PR #802 closed #801 by removing `coilyco-flight-deck/ward` from ward's embedded default substrate manifest: * `cmd/ward/containerassets/preclone-repos.txt` dropped `coilyco-flight-deck/ward`. * `cmd/ward/container_substrate_test.go` began failing if ward appears in the embedded manifest. * `cmd/ward/containerassets/AGENTS.container.md`, `docs/container-substrate.md`, and `docs/FEATURES.md` now document that ward is excluded from default substrate. Correction from Kai: the default repo substrate was supposed to move into aos, not become a ward-side deletion. Aos owns the dev-base image and seed content, so the default/image-tier substrate list should be canonical in `coilyco-flight-deck/agentic-os`. Ward should not encode the product decision by removing itself from its own manifest. Do: * Revert or reshape the ward-side `#802` changes so ward no longer asserts that `coilyco-flight-deck/ward` must be absent from the embedded substrate manifest. * Keep ward-targeted `/workspace/ward` vs `/substrate/ward` doctrine correct: `/workspace` remains authoritative for work, `/substrate` remains read-only reference when present. * Point docs/comments at aos ownership for the default substrate list, not ward ownership. * In the paired aos repo work, close `coilyco-flight-deck/agentic-os#373` by making aos canonical for `docker/dev-base/substrate-image-repos.txt` and its docs/comments. * If a generated-copy flow is needed, implement the smallest durable path. Do not leave two files both claiming to be canonical. Acceptance: * Ward tests no longer enforce "ward absent from default substrate". * Ward docs no longer say the default substrate slice intentionally omits ward itself. * Aos docs/comments say aos owns the image-tier substrate set because aos owns the dev-base image/seed. * `coilyco-flight-deck/ward#802` is effectively corrected, and `coilyco-flight-deck/agentic-os#373` is closed by the aos-side landing. * Run relevant ward and aos validation through `ward` / pre-commit. Related: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/802

coilyco-ops commented

2026-07-09 15:52:22 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-09T15:52:20Z). 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#805 · branch issue-805 · harness codex · workflow pull-request
Run: engineer-codex-ward-805 · ward v0.493.0 · dispatched 2026-07-09T15:52:20Z
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.493.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-805` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T15:52:20Z). 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#805` · branch `issue-805` · harness `codex` · workflow `pull-request` - **Run:** `engineer-codex-ward-805` · ward `v0.493.0` · dispatched `2026-07-09T15:52:20Z` - **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.493.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a commit

2026-07-09 15:59:25 +00:00

fix: restore shared substrate ownership boundary

~~coilyco-ops referenced this issue 2026-07-09 16:01:17 +00:00~~

fix: restore shared substrate ownership boundary #807

coilyco-ops commented

2026-07-09 16:06:54 +00:00

Author

Member

WARD-OUTCOME: done ✅

details

workflow: pull-request; review summary: review gate skipped by ~/.ward/config.yaml default
retrospective: the split was straightforward once the image-tier seed ownership moved to aos and ward stopped encoding an exclusion rule.
confidence: high.
surprises: ward’s PR test surfaced quickly; aos had no PR task within the wait window.
follow-ups: merge PR #807 and PR #374 when policy allows.

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: pull-request; review summary: review gate skipped by ~/.ward/config.yaml default retrospective: the split was straightforward once the image-tier seed ownership moved to aos and ward stopped encoding an exclusion rule. confidence: high. surprises: ward’s PR test surfaced quickly; aos had no PR task within the wait window. follow-ups: merge PR #807 and PR #374 when policy allows. </details>

coilyco-ops commented

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

Author

Member

WARD-REAP: reopened 🛑

grant details

This run held --repo grants and closed against coilyco-flight-deck/ward, but cleanup could not confirm every granted repo's work reached its main. A secondary push can be silently rejected (a non-fast-forward on a busy main, a dead/rotated PAT) while the primary push succeeds, so the issue is reopened rather than left reading "done" with the cross-repo half lost.

`coilyco-flight-deck/agentic-os`

Verdict: 1 local commit(s) never reached origin/main.
Preserved on: ward-salvage/agentic-os-b6dc7c37

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os.git ward-salvage/agentic-os-b6dc7c37
git checkout -b ward-salvage/agentic-os-b6dc7c37 FETCH_HEAD

Re-run the cross-repo half, or - per ward#291 - file it as a native issue in the granted repo so it becomes a single-repo run that sidesteps this failure mode.

— Codex, via ward agent

WARD-REAP: reopened 🛑 <details><summary>grant details</summary> This run held `--repo` grants and closed against `coilyco-flight-deck/ward`, but cleanup could not confirm every granted repo's work reached its `main`. A secondary push can be silently rejected (a non-fast-forward on a busy `main`, a dead/rotated PAT) while the primary push succeeds, so the issue is **reopened** rather than left reading "done" with the cross-repo half lost. ### `coilyco-flight-deck/agentic-os` - **Verdict:** 1 local commit(s) never reached `origin/main`. - **Preserved on:** `ward-salvage/agentic-os-b6dc7c37` ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os.git ward-salvage/agentic-os-b6dc7c37 git checkout -b ward-salvage/agentic-os-b6dc7c37 FETCH_HEAD ``` Re-run the cross-repo half, or - per ward#291 - file it as a native issue in the granted repo so it becomes a single-repo run that sidesteps this failure mode. </details>  — Codex, via `ward agent`

coilyco-ops closed this issue

2026-07-09 16:11:56 +00:00