coilyco-flight-deck/ward

Fork 0

Delete generated ward-kdl guardfile reference docs #923

New issue

Closed

opened 2026-07-10 01:26:34 +00:00 by coilyco-ops · 4 comments

coilyco-ops commented

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

Member

Delete the generated docs/ward-kdl/*.md guardfile reference docs independently of the broader ward-kdl bundle/source split in #920.

Scope:

Remove the generated docs/ward-kdl/ Markdown reference tree. Current inventory: 26 files, about 5,243 lines.
Do not remove or reshape the source KDL/spec bundle under .ward/ward-kdl/. That belongs to #920.
Update docs that link to the deleted generated references, especially docs/README.md, docs/ward-kdl.md, docs/ward-kdl-surface.md, and docs/FEATURES.md.
Keep a concise explanation that per-area guardfile references are generated/reference output and should not be committed as release-era docs.
Update any tests or link checks that assume the generated files exist.

Acceptance:

docs/ward-kdl/*.md is gone.
No docs link points at the deleted generated files.
The remaining ward-kdl docs still explain the human-facing authoring/build-time surface at a high level.
The change does not touch .ward/ward-kdl/ source files except where a test/doc update truly requires it.

Related: #920

Delete the generated `docs/ward-kdl/*.md` guardfile reference docs independently of the broader ward-kdl bundle/source split in #920. Scope: * Remove the generated `docs/ward-kdl/` Markdown reference tree. Current inventory: 26 files, about 5,243 lines. * Do not remove or reshape the source KDL/spec bundle under `.ward/ward-kdl/`. That belongs to #920. * Update docs that link to the deleted generated references, especially `docs/README.md`, `docs/ward-kdl.md`, `docs/ward-kdl-surface.md`, and `docs/FEATURES.md`. * Keep a concise explanation that per-area guardfile references are generated/reference output and should not be committed as release-era docs. * Update any tests or link checks that assume the generated files exist. Acceptance: * `docs/ward-kdl/*.md` is gone. * No docs link points at the deleted generated files. * The remaining ward-kdl docs still explain the human-facing authoring/build-time surface at a high level. * The change does not touch `.ward/ward-kdl/` source files except where a test/doc update truly requires it. Related: #920

coilyco-ops added the

headless

labels

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

coilyco-ops commented

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

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-10T01:26:43Z). 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#923 · branch issue-923 · harness codex · workflow pull-requests-and-merge
Run: engineer-codex-ward-923 · ward v0.543.0 · dispatched 2026-07-10T01:26:43Z
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-923` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T01:26:43Z). 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#923` · branch `issue-923` · harness `codex` · workflow `pull-requests-and-merge` - **Run:** `engineer-codex-ward-923` · ward `v0.543.0` · dispatched `2026-07-10T01:26:43Z` - **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: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:38:41 +00:00

docs: remove generated ward-kdl refs #925

coilyco-ops commented

2026-07-10 01:39:50 +00:00

Author

Member

WARD-OUTCOME: merge-ready

details

workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default
Retrospective: the docs tree removal was straightforward, but the authoring note needed one extra trim to stay under the cap.
Confidence: high
Surprises: pre-commit caught the size cap on docs/ward-kdl-authoring.md before commit.
Follow-ups: none.

WARD-OUTCOME: merge-ready <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: review gate skipped by ~/.ward/config.yaml default Retrospective: the docs tree removal was straightforward, but the authoring note needed one extra trim to stay under the cap. Confidence: high Surprises: pre-commit caught the size cap on docs/ward-kdl-authoring.md before commit. Follow-ups: none. </details>

coilyco-ops referenced this issue

2026-07-10 03:29:45 +00:00

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

coilyco-ops commented

2026-07-10 05:11:11 +00:00

Author

Member

WARD-RESERVATION: held 🔒

reservation details

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

Reserved by ward agent --harness codex (reserved 2026-07-10T05:11:10Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#923 · branch issue-923 · harness codex · workflow pull-requests
Run: engineer-codex-ward-923 · ward v0.555.0 · dispatched 2026-07-10T05:11:10Z
Comment thread: 1 included in the pre-flight read, 1 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-10T01:39:50Z)
- stripped: @coilyco-ops (2026-07-10T01:26:45Z)

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

— Codex, via ward agent

WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-ward-923` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-10T05:11:10Z). 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#923` · branch `issue-923` · harness `codex` · workflow `pull-requests` - **Run:** `engineer-codex-ward-923` · ward `v0.555.0` · dispatched `2026-07-10T05:11:10Z` - **Comment thread:** 1 included in the pre-flight read, 1 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-10T01:39:50Z) - stripped: @coilyco-ops (2026-07-10T01:26:45Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.555.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops commented

2026-07-10 05:23:05 +00:00

Author

Member

WARD-OUTCOME: blocked 🛑

details

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

felt: the docs cleanup itself landed cleanly, but the blocking failure came from Forgejo Actions stopping in Set up job before checkout.
confidence: low that a branch edit would change this failure, because the runner never reached the repo steps.
surprises: the latest run canceled actions/checkout, go vet, go test, golangci-lint, and job completion after a 4s setup failure.
follow-ups: retry the workflow when the runner recovers, or inspect the Forgejo Actions runner for the repository.
reservation-lock: hand-back remains pending on the issue thread.

WARD-OUTCOME: blocked 🛑 <details><summary>details</summary> workflow: pull-requests-and-merge; review summary: skipped: review gate skipped by ~/.ward/config.yaml default felt: the docs cleanup itself landed cleanly, but the blocking failure came from Forgejo Actions stopping in Set up job before checkout. confidence: low that a branch edit would change this failure, because the runner never reached the repo steps. surprises: the latest run canceled actions/checkout, go vet, go test, golangci-lint, and job completion after a 4s setup failure. follow-ups: retry the workflow when the runner recovers, or inspect the Forgejo Actions runner for the repository. reservation-lock: hand-back remains pending on the issue thread. </details>

coilyco-ops closed this issue

2026-07-10 06:15:26 +00:00