- Ya
- 4 Septemba 2026, 18:48 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 300865f
The Publish flag shipped gated on godModeActive — GD plus a deliberately opened 30-minute break-glass window. Every god-eligible operator then found the switch missing, because holding GD and having activated it are different facts and only the second starts a countdown. A report an operator cannot see is a report they cannot release, so requiring a window put the flag out of reach of exactly the people it is for. So SessionPlatformFacts gains godEligible alongside godModeActive rather than anyone reading the session a second time — that record exists because two readers of these flags is how one of them ends up subtly wrong, and the same argument applies to a caller wanting only half of what it already computes. The two components are strictly ordered: godEligible is a WIDER set than godModeActive, so reading one where the other was meant is the exact failure this record was written to prevent. That is why they are two named accessors rather than one flag plus a boolean argument, why the javadoc on godEligible says never to pass it to PlatformRightsResolver — doing so would grant every platform right to every god-eligible operator, permanently — and why SessionPlatformFactsTest now pins both halves independently in both directions. The query parameter is renamed :godMode -> :godEligible across all five predicates for the same reason. A parameter named godMode that deliberately ignores the window is how somebody later "fixes" it back.