- Shipped
- August 22, 2026 at 8:51 AM UTC
- Author
- kamo
- Commit
- b8b0801
"My Master Note" and "Our Master Note" are panes in the same sortable grid as everything else — dragged, resized and ordered like any other pane — and neither can be removed. The organisation's carries a turning conic-gradient ring painted from --color-primary, the only moving edge on the page, so the one pane that did not come from the member reads as such from across the room. Stilled to a static ring under prefers-reduced-motion. Both are pinned, so they arrive in the pinned list too; selectPinnedPanes drops them there, or each would be painted twice and the duplicate would be the copy without the badge and the edge. Fetched from /api/notes/master, which is NOT gated on the Notes app: the pinned note panes are the Notes app spilling onto the home page, and these are furniture of the home page itself. Every control the server would refuse is taken away rather than disabled: no unpin, no delete and no rename on either master note, and no colour, no toolbar and no typing surface on the organisation's for a member without the right. A read-only member gets a reader — the same rendering the pane uses — instead of an editor whose saves would be rejected after they had done the work. notesApi.saveNote routes by scope, so the sticky, the editor, the wall and the launchpad's colour picker stop needing to know that the organisation's note has no member and so cannot be reached by the per-id endpoint.