Dig report
The Thirty-Day Exception
A whole Tenant — the only one that ever read at runtime — declared as an exception, lived thirty days, and was lifted out on a typecheck failure that turned out not to be real.
Everything else in this trench is a part of something: a component, a dependency, a page, a rule. This site holds a whole — the only one that asked the repository a question while a visitor was watching, rather than serving what the build had already decided. It broke the platform's founding rule, that nothing is created at runtime, on purpose and in writing, and lived thirty days.
the Wire Cut · 13 Aug 2026 – 4 Sep 2026
the Commits Tenant
commit b008ec1 · commitsclosed by ownerassessed 25 Aug 2026
Seven files and one live wire. Alone among the Tenants it read at runtime — a git call behind a server route, handing the repo's newest commit to a page that displayed it. The break from build-time baking was not smuggled in: it was declared in the Tenant's own context file, under a heading that named the ADR it was breaking, and again in the platform's ground rules as one of two scoped relaxations. It lived thirty days. On the last of them a typecheck failure was read as rot — and by the time the removal was proposed that diagnosis had already been retracted, in the same pull request, under a heading flagging it to the reviewer. It merged seventeen minutes later regardless, on a human's say-so. The gain recorded for its removal was that a paragraph got shorter.
“Explicit return type instead of relying on Nitro's typed-route inference to derive it from the function body — that inference intermittently fails after a clean install, surfacing as TS2339 in LatestCommit.vue (issue #940).”layers/commits/server/api/latest-commit.get.ts, the comment above its return type
remainsthe live wire, and its own warning about the error that killed itthe exception, declared under its own heading