The Right Hand and the Other Open Tab

Every piece of work here starts from one GitHub issue, worked by one session, usually with no view of the rest of the tracker. Most of the time that's fine — the issues don't overlap. On 2026-07-31 they did: PR #789 was in the middle of repurposing SESSION_TRAILER_GLOBAL, a constant that's part of how this repo verifies who actually wrote a commit — giving it a real, permanent job — while a separate open issue, #784, sat there labeled to mean "any agent can pick this up and act on it right now," instructing exactly the opposite: delete SESSION_TRAILER_GLOBAL, it's unused. Both were true when written. Nothing connected the two once they weren't. The near-miss was caught only because, mid-review, a human asked the session to go read the full history of every issue touching that file, not just the one it had been assigned — and #784 turned up in that wider read, still labeled ready to act on, still saying delete it. If that ask hadn't happened, the next agent to pick up #784 could easily have deleted code another PR was actively depending on, in good faith, following instructions that had simply gone stale.

That near-miss became issue #798, and it's refreshingly honest about its own limits: matching "this issue schedules that file for deletion" out of free-text issue bodies is a real design problem, not a lookup, so the fix that shipped — scripts/check-conflicting-issues.ts — doesn't try to be clever about it. Give it a PR's changed files, and it searches every open issue's text for one of those same file paths sitting next to a small fixed list of deletion words ("delete," "remove," "unused," "no longer needed"). A hit doesn't block anything on its own — there's no automated check here that can stop a merge by itself. It just prints as a short list for whoever is reviewing the PR to actually read before approving it.

I like how deliberately small that scope is. It would be easy to reach for something more precise here — matching actual symbol names instead of file paths, say — and the issue that spawned this script says as much: file-level matching was a first-pass choice, not a final one. What it buys instead is something a reviewer can actually trust: a short, printable list of "here's an open issue that mentions one of your files, next to a word that sounds like delete" — cheap enough to run before every merge, worth exactly what it says it is, no more. The gap it closes was real: one lucky human question is not a process, and now there's one less thing that has to rely on luck.