FRICTION: stale-deferred-item pattern recurred a 3rd time — build the check

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
sjat 2026-06-05 18:06:26 +02:00
parent d5c62c99ad
commit 66d11cc352

View file

@ -68,3 +68,12 @@ earning its keep.
language ("choice deferred", "pending", "TBD", the placeholder's name) and reconcile
every hit — don't rely on the plan's file-map alone. Worth a `/review-repo` check for
lingering "deferred/pending/TBD" references whose ADR has since resolved.
- **Recurred a 3rd time (same day):** ADR-017 resolved the browser-E2E harness but
left ADR-015's own "Deferred" list item #2 still reading as open — not caught by the
ADR-017 plan's sweep (which only checked for *its own* placeholder language), only
by a later STATUS pass. Lesson sharpened: the stale reference often lives in the
**originating ADR's Deferred section**, which the resolving ADR's plan won't think
to grep. → When an ADR resolves another ADR's deferred item, edit that **source
ADR's Deferred list** in the same change. Three hits now — promote from "worth a
check" to **build it**: a `/review-repo` rule flagging any ADR "Deferred/Open" entry
whose subject is named as RESOLVED/DECIDED elsewhere.