- Ya
- 4 Septemba 2026, 05:22 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 445f4f0
An operator with an open god-mode window filing a bug or enhancement now gets a Publish switch. It is off when the window opens and does not remember its last position: the flag decides whether the organization a report is filed against can see it, and a control that remembered would eventually publish something nobody meant to publish — or, worse, quietly withhold one. The drawer gets a matching toggle so a report already filed can be released later, and both card and drawer mark an unpublished report so an operator can see at a glance which reports the tenant is not watching. Gated on god mode, NOT on MANAGE_SYSTEM_BUGS — the SEND TO AI switch sitting beside it in the same form is gated on the standing platform right, and this one deliberately is not. A platform administrator triages every report whether or not they have broken glass; deciding who can SEE one takes the open window. The form reads the browser's own god-mode state, which fails CLOSED: the worst case is an operator not being offered the control and filing a published report, which is what happened before this existed. It decides only whether the switch is DRAWN — the server ignores `publish` from anyone without an open window, so nothing here grants anything. The drawer uses the server's canPublish instead, because it has a detail DTO to read it from. `publish` is omitted from the payload entirely when the switch was not drawn, rather than sent as true: the server reads an absent value as "the client did not ask", which for an ordinary member is the same as every other answer. That is what keeps a member who never sees the control from filing their own report invisible. Filing only. An edit window never shows the switch, because update does not carry the flag and a switch that silently did nothing would be worse than no switch.