coilyco-flight-deck/ward

Fork 0

Remove ward ci watch (and the ci-watching surface) from ward #491

New issue

Closed

opened 2026-07-01 23:56:37 +00:00 by coilyco-ops · 2 comments

coilyco-ops commented

2026-07-01 23:56:37 +00:00

Member

Why

Kai (2026-07-01 triage): "we need to just remove the ci watching stuff - it's very anomalous when held next to everything else." Removal also dissolves half of #462 (AGENTS.md instructs verifying CI with retiring coily ops while ward ci watch exists).

Deliverable

Remove the ward ci watch surface from the binary, docs/ci-watch.md, and FEATURES.md rows.
Rewrite the AGENTS.md release-verification instruction for the post-removal reality (#462 - same pass or explicitly sequenced).

Done condition

No ci-watch surface in binary or docs; AGENTS.md release section gives a working verification instruction that references neither coily nor ci watch.

Recorded by Claude Code (Fable) during the 2026-07-01 ward launch triage session with Kai.

## Why Kai (2026-07-01 triage): "we need to just remove the ci watching stuff - it's very anomalous when held next to everything else." Removal also dissolves half of #462 (AGENTS.md instructs verifying CI with retiring `coily ops` while `ward ci watch` exists). ## Deliverable - Remove the `ward ci` watch surface from the binary, docs/ci-watch.md, and FEATURES.md rows. - Rewrite the AGENTS.md release-verification instruction for the post-removal reality (#462 - same pass or explicitly sequenced). ## Done condition No ci-watch surface in binary or docs; AGENTS.md release section gives a working verification instruction that references neither coily nor ci watch. --- Recorded by Claude Code (Fable) during the 2026-07-01 ward launch triage session with Kai.

coilyco-ops added this to the ward launch milestone

2026-07-01 23:56:37 +00:00

coilyco-ops added the

headless

labels

2026-07-01 23:56:37 +00:00

coilyco-ops referenced this issue

2026-07-01 23:57:00 +00:00

add github equivalents for all forgejo integrations / functionality #414

coilyco-ops referenced this issue

2026-07-01 23:59:29 +00:00

AGENTS.md instructs verifying CI with coily ops, a tool the same doc says is retiring in favor of ward ci watch #462

coilyco-ops referenced this issue

2026-07-02 00:01:42 +00:00

meta: jul 1st evening sprint - launch burndown session 1 #492

coilyco-ops referenced this issue

2026-07-02 00:20:39 +00:00

Feature prune #216

coilyco-ops commented

2026-07-02 02:22:36 +00:00

Author

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-ward-491 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-02T02:22:34Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-ward-491` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-02T02:22:34Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-07-02 02:32:09 +00:00

refactor(ci): remove the ward ci watch surface and ci-watch complex action (closes #491)

coilysiren closed this issue

2026-07-02 02:32:09 +00:00

coilysiren commented

2026-07-02 02:32:50 +00:00

Owner

WARD-OUTCOME: done - removed the ward ci watch verb + the ci-watch complex action, deleted docs/ci-watch.md and its links, and rewrote the AGENTS.md release-verify step; landed on main as 37bc074.

Mostly a clean subtraction. The native ward ci verb and its test were self-contained, so main.go and the subsystem-pointer table were the only wiring to unpick.

The one real judgement call: the deliverable bullets named only the native verb, but the title ("...and the ci-watching surface") and the done-condition ("no ci-watch surface in binary or docs") also cover the generated ward ops forgejo action ci-watch complex action - a second CI-watcher embedded through the forgejo guardfile. I removed that too (keeping the read-only tasks list leaf it polled), since leaving it would contradict the done-condition and Kai's "remove the ci watching stuff" wholesale. Flagging it here in case the intended scope was narrower.

Only friction: my first AGENTS.md rewrite tipped the file past the 4000-char doc-size cap (4302); trimmed it back to 3995. Reasonably confident in the result - build/vet/full go test and the whole pre-commit suite are green, and dead-cross-links stayed clean after deleting ci-watch.md.

Two rough edges worth a note: I hand-edited the generated guardfile doc (docs/ward-kdl/ward-kdl.forgejo.guardfile.md) rather than regenerating via make build-ward-kdl, which needs the ward-kdl tool + upstream spec fetch - a future full regen should reproduce the same bytes. And this only dissolves half of #462; any remaining coily references elsewhere are still open.

WARD-OUTCOME: done - removed the `ward ci watch` verb + the `ci-watch` complex action, deleted docs/ci-watch.md and its links, and rewrote the AGENTS.md release-verify step; landed on main as 37bc074. Mostly a clean subtraction. The native `ward ci` verb and its test were self-contained, so `main.go` and the subsystem-pointer table were the only wiring to unpick. The one real judgement call: the deliverable bullets named only the native verb, but the title ("...and the ci-watching surface") and the done-condition ("no ci-watch surface in binary **or** docs") also cover the generated `ward ops forgejo action ci-watch` complex action - a second CI-watcher embedded through the forgejo guardfile. I removed that too (keeping the read-only `tasks list` leaf it polled), since leaving it would contradict the done-condition and Kai's "remove the ci watching stuff" wholesale. Flagging it here in case the intended scope was narrower. Only friction: my first AGENTS.md rewrite tipped the file past the 4000-char doc-size cap (4302); trimmed it back to 3995. Reasonably confident in the result - build/vet/full `go test` and the whole pre-commit suite are green, and dead-cross-links stayed clean after deleting ci-watch.md. Two rough edges worth a note: I hand-edited the generated guardfile doc (`docs/ward-kdl/ward-kdl.forgejo.guardfile.md`) rather than regenerating via `make build-ward-kdl`, which needs the ward-kdl tool + upstream spec fetch - a future full regen should reproduce the same bytes. And this only dissolves half of #462; any remaining `coily` references elsewhere are still open.

coilysiren referenced this issue

2026-07-02 02:38:18 +00:00

AGENTS.md instructs verifying CI with coily ops, a tool the same doc says is retiring in favor of ward ci watch #462

coilysiren referenced this issue

2026-07-02 02:38:32 +00:00

release: lift the README length cap so the README can grow into the launch-grade front page #427

coilysiren referenced this issue

2026-07-02 08:08:20 +00:00

AGENTS.md instructs verifying CI with coily ops, a tool the same doc says is retiring in favor of ward ci watch #462

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