docs/test-harness.md documents a goose harness deleted in June 2026 #1117

New issue

Open

opened 2026-08-17 19:08:53 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-17 19:08:53 +00:00

Member

Split out of the ward exec retirement (coilysiren/inbox#366) rather than fixed inside it, because the honest repair is a deletion decision rather than a spelling change.

What is stale

docs/test-harness.md documents goose-ask as a live verb, with a four-line usage block:

ward exec goose-ask -- "a single question"
ward exec goose-ask -- -f scripts/goose-probe.txt        # capability battery
ward exec goose-ask -- -m qwen3:30b-a3b "compare models" # override GOOSE_MODEL
ward exec goose-ask -- -s "Answer in one word." "ping"   # extra system text

None of that exists. Commit 03d15257 ("aos execed agent commands are last era", 2026-06-26) deleted scripts/goose-ask.sh and scripts/goose-probe.txt along with the rest of the backlog-loop and goose-triage surface, and removed 18 lines from .ward/ward.yaml in the same commit. The doc was not touched.

The doc also states the mechanism as if it ships: "goose-ask.sh wraps that with banner stripping, timing, transcript capture, and -f batch / -s system / -m model-override flags." There is no such file.

Why the migration left it alone

The four usage lines are the only ward exec references in this repository that were not rewritten. Rewriting them to just goose-ask would have replaced a stale command with a stale command that also does not resolve, which reads as current rather than dead. Leaving the retired spelling at least signals its age.

The decision

Whether the doc goes or the harness comes back. Reading the deleting commit, goose-ask went out with the rest of an era rather than being singled out, which points at deleting the doc. Against that: docs/test-harness.md established the test-harness-<agent> doc family (aba617df), so check whether anything still points at it before removing the family's founding page.

If it goes, that is also one doc off the count in #1097.

Filed by Angie (engineer seat) while sweeping ward exec out of the fleet.

Split out of the `ward exec` retirement (coilysiren/inbox#366) rather than fixed inside it, because the honest repair is a deletion decision rather than a spelling change. ## What is stale `docs/test-harness.md` documents `goose-ask` as a live verb, with a four-line usage block: ``` ward exec goose-ask -- "a single question" ward exec goose-ask -- -f scripts/goose-probe.txt # capability battery ward exec goose-ask -- -m qwen3:30b-a3b "compare models" # override GOOSE_MODEL ward exec goose-ask -- -s "Answer in one word." "ping" # extra system text ``` None of that exists. Commit `03d15257` ("aos execed agent commands are last era", 2026-06-26) deleted `scripts/goose-ask.sh` and `scripts/goose-probe.txt` along with the rest of the backlog-loop and goose-triage surface, and removed 18 lines from `.ward/ward.yaml` in the same commit. The doc was not touched. The doc also states the mechanism as if it ships: *"`goose-ask.sh` wraps that with banner stripping, timing, transcript capture, and `-f` batch / `-s` system / `-m` model-override flags."* There is no such file. ## Why the migration left it alone The four usage lines are the only `ward exec` references in this repository that were not rewritten. Rewriting them to `just goose-ask` would have replaced a stale command with a stale command that also does not resolve, which reads as current rather than dead. Leaving the retired spelling at least signals its age. ## The decision Whether the doc goes or the harness comes back. Reading the deleting commit, `goose-ask` went out with the rest of an era rather than being singled out, which points at deleting the doc. Against that: `docs/test-harness.md` established the `test-harness-<agent>` doc family (`aba617df`), so check whether anything still points at it before removing the family's founding page. If it goes, that is also one doc off the count in #1097. Filed by Angie (engineer seat) while sweeping `ward exec` out of the fleet.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/agentic-os#1117

No description provided.

Rows
Columns