Replace baked ward-kdl bundle with toy/example-safe defaults #920

New issue

Closed

opened 2026-07-10 01:07:38 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-10 01:07:38 +00:00

Member

PR #914 showed the wrong final shape: it neutralized the current .ward/ward-kdl payload in place, but ward should stop carrying the legacy custom specgen/KDL bundle as product source.

Scope:

Remove the huge legacy specgen payload from ward's tracked default bundle, especially .ward/ward-kdl/forgejo.swagger.v1.json and any custom coilyco-oriented generated/spec inputs that are only there for Kai's deployment.
Keep ward's shipped default bundle tiny and example-safe, anchored on the existing examples/toy/ and examples/ward-specs/ shapes.
Move deployment-specific KDL/specgen assets out of ward into the aos-owned bundle/config source path. Ward should select or overlay that source, not own it as tracked product config.
Preserve ward's loader/parser/generator logic and tests with minimal neutral fixtures.
Update docs and docs/FEATURES.md so release readers understand the split between ward's example-safe defaults and external deployment bundles.

Acceptance:

A fresh ward checkout no longer tracks the giant legacy Forgejo swagger/specgen payload under .ward/ward-kdl.
Building/testing ward still exercises ward-kdl embedding with neutral fixtures.
The custom coilyco/aos bundle location and selection path are documented.
PR #914 remains superseded rather than revived.

Related: #893, #914

PR #914 showed the wrong final shape: it neutralized the current `.ward/ward-kdl` payload in place, but ward should stop carrying the legacy custom specgen/KDL bundle as product source. Scope: * Remove the huge legacy specgen payload from ward's tracked default bundle, especially `.ward/ward-kdl/forgejo.swagger.v1.json` and any custom coilyco-oriented generated/spec inputs that are only there for Kai's deployment. * Keep ward's shipped default bundle tiny and example-safe, anchored on the existing `examples/toy/` and `examples/ward-specs/` shapes. * Move deployment-specific KDL/specgen assets out of ward into the aos-owned bundle/config source path. Ward should select or overlay that source, not own it as tracked product config. * Preserve ward's loader/parser/generator logic and tests with minimal neutral fixtures. * Update docs and `docs/FEATURES.md` so release readers understand the split between ward's example-safe defaults and external deployment bundles. Acceptance: * A fresh ward checkout no longer tracks the giant legacy Forgejo swagger/specgen payload under `.ward/ward-kdl`. * Building/testing ward still exercises ward-kdl embedding with neutral fixtures. * The custom coilyco/aos bundle location and selection path are documented. * PR #914 remains superseded rather than revived. Related: #893, #914

coilyco-ops added the

headless

labels

2026-07-10 01:07:47 +00:00

coilyco-ops commented

2026-07-10 01:08:00 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-10T01:07:57Z). 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#920 · branch issue-920 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-920 · ward v0.543.0 · dispatched 2026-07-10T01:07:57Z
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.543.0).

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-920` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T01:07:57Z). 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#920` · branch `issue-920` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-920` · ward `v0.543.0` · dispatched `2026-07-10T01:07:57Z` - **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.543.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue

2026-07-10 01:26:34 +00:00

Delete generated ward-kdl guardfile reference docs #923

coilyco-ops referenced this issue

2026-07-10 01:36:46 +00:00

Shrink ward docs to release-era surface #924

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

2026-07-10 01:41:22 +00:00

Replace baked ward-kdl bundle with toy/example-safe defaults #926

coilyco-ops closed this issue

2026-07-10 01:49:31 +00:00

coilyco-ops commented

2026-07-10 01:49:49 +00:00

Author

Member

WARD-OUTCOME: merge-ready

details

workflow: pull-requests-and-merge; review summary: skipped because ~/.ward/config.yaml default skipped it review gate: skipped by ~/.ward/config.yaml default retrospective: the change felt like fixture cleanup after the real bundle swap confidence: high surprises: the suite only needed a couple of stale trust-gate expectations updated follow-ups: none

WARD-OUTCOME: merge-ready <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: skipped because ~/.ward/config.yaml default skipped it review gate: skipped by ~/.ward/config.yaml default retrospective: the change felt like fixture cleanup after the real bundle swap confidence: high surprises: the suite only needed a couple of stale trust-gate expectations updated follow-ups: none </details>

coilyco-ops referenced this issue

2026-07-10 02:17:24 +00:00

Remove runtime KDL/specgen dependency from ward core paths #929