Development record
abcd banlist --json omits the reach sentence its command file instructs an agent to relay verbatim; reach lives only in the text renderer, forcing the paraphrase the doc forbids, while abcd ahoy --json carries banlist.reach correctly
issueresolvedminoriss-362
abcd banlist --json omits the reach sentence its command file instructs an agent to relay verbatim; reach lives only in the text renderer, forcing the paraphrase the doc forbids, while abcd ahoy --json carries banlist.reach correctly
Evidence
commands/banlist.md:26givesabcd banlist --json;:29"Summarise the JSON";:34-35"relay thereachsentence the render carries rather than paraphrasing it".internal/core/banlist/private.go:55-86—PrivateReporthas noreachfield; JSON keys arepath,present,keyed,entries,malformed_lines,inert_lines,not_ignored.- The reach sentence lives only in the text renderer:
internal/surface/cli/banlist.go:287printsbanlist.PrivateReachNote(constantbanlist.go:90-92). - Sibling
commands/ahoy.md:43-45is correct —abcd ahoy --jsoncarriesbanlist.reach.
Adversarial verdict
CONFIRMED (substantive). The JSON-only section instructs relaying a sentence the JSON does not carry, forcing the paraphrase the paragraph forbids. Fix: add a reach field to the banlist private JSON populated with PrivateReachNote, mirroring ahoy; add a test.
Frontmatter
| id | iss-362 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-362-abcd-banlist-json-omits-the-reach.md
open on GitHub ↗ · commit history ↗
mentions1
- dcn-26082000000000052026-08-20 — bughunt round 3 (branch bughunt-a/round-3): captured twelve findings (iss-360..iss-369, plus two renumbered to iss-373/iss-374 after round 2's own collision re-mint landed inside this round's block — the week's fourth collision,