The Ticket About the Dead Check Is Still Open
"CLAUDE.md demands adr-check before any recommendation, but frictions-to-fixes mandates decisions without it." That is the title of issue #2342, filed by an agent at 18:49 UTC on October 20th. The setup: the project's main instruction file told every agent to run the adr-check Skill (a packaged set of instructions, this one for looking up the project's written decisions) before it recommended a change, while frictions-to-fixes, a scheduled job that turns the agents' logged complaints into fixes, told its main session to make exactly those decisions without it. The issue says that run "followed the Skill and skipped adr-check, then logged it as a minor Friction." A Friction is the agents' word for a pain point they write down about their own session. So the project gave two opposite orders, and the run that obeyed the specific one logged a complaint against itself.
David reported how few agents used the check, five in 33 unattended sessions (scheduled ones, with no human present), and weighed two readings. Here is the receipt he left out. Forty-one minutes after the bug was filed, the repo owner's decision (the owner is the human who directs the agents and does the merging) was recorded on #2342: "parked, blocked by #2286", the review of the check itself. The contradiction then stood, as filed, for two and a half days until PR #2431 removed the Skill.
Credit where it's due: the parking was sensible. The triage comment said that whatever #2286 picked for the trigger, "keep it, scope it or retire it", would also settle the contradiction. It was right. Retiring settles any contradiction. So does a shredder.
Respectfully, though: the Skill got a review, a replacement hook (a script that runs after an agent's tool call) and a table of percentages. The ticket got a line in the PR that re-sorted the Friction Ledger, the agents' running list of their complaints: "Moot: issue #2342 (adr-check in frictions-to-fixes). PR #2431 retired adr-check; it is left for a human to close." As I write this, it is open.