Two pages went live answering 500 today and the gate reported PASSED. Not a gap in what it checks - the list it checks had quietly collapsed.
Page names are derived from the table in Entrypoint.swift, where an entry spans two lines:
(
"about", "About. Flamenet Messenger",
The pattern matched eight spaces and an opening paren - the line with no name on it. It extracted nothing, every time, for as long as the table has been formatted that way. The fallback hand-list then became the entire gate: 5 pages, plus donate and releases named separately. That is the "7 public pages" it has been reporting.
25 pages exist. Two were new today, neither was in the list of five, and both 500'd in production while the gate passed the deploy.
Fixed the pattern, and added a floor. Falling back is fail-safe only if somebody finds out; degrading from 25 to 5 and printing PASSED is fail-quiet, which is worse than no gate because it reads like coverage. If the count collapses, the derivation broke - say so and stop.
Verified against production: derivation picks 25, renders 27 with donate and releases, all 200.
Two pages went live answering **500** today and the gate reported `PASSED`. Not a gap in what it checks - the list it checks had quietly collapsed.
Page names are derived from the table in `Entrypoint.swift`, where an entry spans two lines:
```
(
"about", "About. Flamenet Messenger",
```
The pattern matched **eight spaces and an opening paren** - the line with no name on it. It extracted nothing, every time, for as long as the table has been formatted that way. The fallback hand-list then became the entire gate: 5 pages, plus `donate` and `releases` named separately. That is the "7 public pages" it has been reporting.
**25 pages exist.** Two were new today, neither was in the list of five, and both 500'd in production while the gate passed the deploy.
Fixed the pattern, and added a floor. Falling back is fail-safe only if somebody finds out; degrading from 25 to 5 and printing PASSED is fail-*quiet*, which is worse than no gate because it reads like coverage. If the count collapses, the derivation broke - say so and stop.
Verified against production: derivation picks 25, renders 27 with donate and releases, all 200.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
paulhitt
(Migrated from gitlab.com)
merged commit 847034651e into main2026-09-11 14:23:09 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two pages went live answering 500 today and the gate reported
PASSED. Not a gap in what it checks - the list it checks had quietly collapsed.Page names are derived from the table in
Entrypoint.swift, where an entry spans two lines:The pattern matched eight spaces and an opening paren - the line with no name on it. It extracted nothing, every time, for as long as the table has been formatted that way. The fallback hand-list then became the entire gate: 5 pages, plus
donateandreleasesnamed separately. That is the "7 public pages" it has been reporting.25 pages exist. Two were new today, neither was in the list of five, and both 500'd in production while the gate passed the deploy.
Fixed the pattern, and added a floor. Falling back is fail-safe only if somebody finds out; degrading from 25 to 5 and printing PASSED is fail-quiet, which is worse than no gate because it reads like coverage. If the count collapses, the derivation broke - say so and stop.
Verified against production: derivation picks 25, renders 27 with donate and releases, all 200.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
mentioned in commit
847034651e