- Shipped
- 4 Septemba 2026, 18:49 UTC
- Author
- Kamo
- Commit
- e9fe869
Reported: "my user has god enabled, yet I still don't see the new publish field." The gate was isGodModeActive(), which is getIsGod() AND an open break-glass window — and getIsGod()'s own comment in useUserInfo calls it "can see the god mode toggle". Being allowed to elevate and having elevated are different facts, and the form asked for the second while the report described the first. It is now getIsGod(). A report an operator cannot see is a report they cannot release, and making them burn a 30-minute non-sliding window to read a private bug list put the flag out of reach of the people it exists for. The server made the same move in the same breath; the comment on mayPublish says so, because a form that draws a control the endpoint then 403s is worse than one that draws nothing. The regression is pinned rather than described: in SystemBugReportWindowPublish the window flag is hard-wired FALSE for every case in the file, so a test there cannot pass by way of an open window even accidentally, and `does not require an open god-mode window` fails the moment somebody reaches for isGodModeActive() again. The SEND TO AI test's useUserInfo mock is updated in step and its god-eligibility kept false deliberately — that file finds the SEND TO AI switch as "the form's only checkbox", which stops being true the moment Publish is drawn beside it.