/spec is generated, so the §15 correction is not live until this ships.
The guard earned its keep immediately
#7 landed a check that hashes each page-s source into its banner. It caught this
drift on its first real use, not in a test:
spec.leaf from flamenet-e2e/docs/SPEC.md (41002a1e… != 50c7c8d5…)
exit=1
That is the exact failure it was built for — a source corrected and the page left
stale, silently, still being served. Regenerated; the checker is clean:
9 generated pages match their sources
Pages ship inside the relay image, so this needs a deploy to be live.
Follows paulhitt/flamenet-e2e!3.
`/spec` is generated, so the §15 correction is not live until this ships.
### The guard earned its keep immediately
#7 landed a check that hashes each page-s source into its banner. It caught this
drift on its **first real use**, not in a test:
```
spec.leaf from flamenet-e2e/docs/SPEC.md (41002a1e… != 50c7c8d5…)
exit=1
```
That is the exact failure it was built for — a source corrected and the page left
stale, silently, still being served. Regenerated; the checker is clean:
```
9 generated pages match their sources
```
Pages ship inside the relay image, so this needs a deploy to be live.
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.
Follows paulhitt/flamenet-e2e!3.
/specis generated, so the §15 correction is not live until this ships.The guard earned its keep immediately
#7 landed a check that hashes each page-s source into its banner. It caught this
drift on its first real use, not in a test:
That is the exact failure it was built for — a source corrected and the page left
stale, silently, still being served. Regenerated; the checker is clean:
Pages ship inside the relay image, so this needs a deploy to be live.
mentioned in commit
0daa4225e4mentioned in merge request !9