chore: delete unconsumed in-repo prompt copies (operator decision: guard interaction) #489

New issue

Open

opened 2026-08-09 07:02:09 +00:00 by igor · 0 comments

igor commented

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

Collaborator

Split from #487: delete the seven now-unconsumed in-repo prompt copies (the prompt body of AGENTS.md, and bin/lib/{review-directive,voice,feedback-directive,site-work-directive,sports-digest-directive,now-directive}.md) plus add the negative wiring assertion (grep -rn 'bin/lib/.*\.md' bin/ lib/ finds no consuming reads).

Why this needs an operator decision: the deletion is ~1,100 non-test lines and structurally CANNOT pass the 1000-line runaway guard, so the loop cannot ship it -- the guard blocked #487's first attempt exactly as designed. Options:

You make the deletion commit yourself (attended; it's git rm + a small check-sync stub decision -- whether AGENTS.md remains as a sentinel-only stub, see #487's retarget).
Teach the guard that deletions aren't runaway: count only ADDED lines (numstat column 1) toward the guard. Principled -- the guard exists to bound unreviewable generated volume, and pure deletions are trivially reviewable -- but it's a guard change, so it's your call, not mine. If chosen, that's a small Agent ticket first, then this one re-queues.
Leave the copies in place indefinitely -- they're unread museum pieces; the only real cost is confusion for future readers. (Not recommended: drift + misleading docs.)

No urgency: nothing reads these files (verified in #486), and check-sync mis-guarding is fixed by #487 independently.

Split from #487: delete the seven now-unconsumed in-repo prompt copies (the prompt body of `AGENTS.md`, and `bin/lib/{review-directive,voice,feedback-directive,site-work-directive,sports-digest-directive,now-directive}.md`) plus add the negative wiring assertion (`grep -rn 'bin/lib/.*\.md' bin/ lib/` finds no consuming reads). **Why this needs an operator decision:** the deletion is ~1,100 non-test lines and structurally CANNOT pass the 1000-line runaway guard, so the loop cannot ship it -- the guard blocked #487's first attempt exactly as designed. Options: 1. **You make the deletion commit yourself** (attended; it's `git rm` + a small check-sync stub decision -- whether AGENTS.md remains as a sentinel-only stub, see #487's retarget). 2. **Teach the guard that deletions aren't runaway:** count only ADDED lines (numstat column 1) toward the guard. Principled -- the guard exists to bound unreviewable generated volume, and pure deletions are trivially reviewable -- but it's a guard change, so it's your call, not mine. If chosen, that's a small Agent ticket first, then this one re-queues. 3. **Leave the copies in place indefinitely** -- they're unread museum pieces; the only real cost is confusion for future readers. (Not recommended: drift + misleading docs.) No urgency: nothing reads these files (verified in #486), and check-sync mis-guarding is fixed by #487 independently.