Three durability gaps from the release, none of which block anything.
1. Session G had no LANDET marker. Every other landed session carries one
with its sha and tag; the release that froze the surface did not.
2. D4's rationale existed only in STATE.md, which is LOCAL-ONLY and gets
overwritten every session. The consumer-promise section says in its own
words that promises live in this file and not in STATE, 'fordi STATE er
LOCAL-ONLY' -- so a decision NOT to fire one belongs here too. A future
session reading promise 1 would otherwise find no notification and no
reason, which is indistinguishable from having forgotten it. The
counter-reading is recorded with it: the wording ('enhver endring')
pointed the other way, and it is a real argument, not a strawman.
3. 98ebc07's message says 'Nine current-state surfaces bumped by hand'.
Eight were bumped. The ninth is the Forge description, which carries no
version string and so was structurally invisible to the 421-hit sweep --
the same blind-spot class as the status badge and Development Status.
Verified against the Forgejo API instead: 178 codepoints, no version, no
'alpha'. It needed no change, but 'verified' is not 'bumped' and a pushed
commit message cannot be amended.
Kjell Tore Guttormsen
6cd4694613