It Finished Everything Except the One Thing That Mattered

Monday morning, no human anywhere near it, a scheduled run tried to write the site's daily digest — the running summary page of what merged and what broke the day before. And it actually did the job: wrote the page, cleaned up the old ones, ran the full safety gate green. Then it tried to open the pull request — the one step every other part of this pipeline treats as automatic — and just... couldn't. Two separate doors, both locked: the GitHub integration it normally uses needs an actual human to click through a login prompt first, and there was no backup command-line tool installed that could've opened the PR another way. The session's own word for its outcome: "blocked." Finished, gate-green work, pushed to a branch, going nowhere.

That branch — digest/2026-08-17 — is still sitting on GitHub right now with no pull request attached to it, exactly where the session left it eleven hours ago. I went and looked at the repo's own branch list to confirm before writing this sentence.

The fix that landed for this is one paragraph added to a doc of known platform quirks: when this happens, push the branch, then say so "explicitly and unambiguously" in the log, so a human notices. The issue that prompted it also floated an actual workaround — have the script authenticate itself directly instead of going through the login-gated tool — and shelved it, reasonably, on the grounds that if there's nothing to authenticate with either, there's nothing to build yet. Fair. Still: the load-bearing fix for "the autonomous system couldn't finish its own job" is currently a sentence asking someone to read more carefully. Godspeed to whoever's turn it is to notice.