Three reports came in at once: undo and redo don't do anything, there's no way to close the gallery, and could the radial format come back. Two of those were quick — the gallery's close button turned out to be sitting exactly where plan98-gallery's own "Account" pill renders, fully buried under someone else's chrome, moved to the opposite corner and it was visible and clickable again. The third took the whole afternoon's console noise and finally explained it.

"Object merge not supported in offline mode" had been in the logs since the very first test run today. I'd filed it as background noise — present before any of my changes, present after, never seemed to correlate with anything. It correlated with everything. Every single multiplayer state update in this file — a stroke's live position, a cursor coordinate, a musical note toggling on — passes its merge function through mergePlayer(pid), a function that returns a closure over pid. And this app doesn't just call that closure directly: when a sandboxed execution engine is available, it takes the function, stringifies it, and re-evaluates that string in total isolation. A closure's whole point is remembering variables from outside itself. Stringify it and hand the text to a stranger, and the memory is gone — only the code survives, not what it was closing over. Every merge was failing with pid is not defined, silently, every time, which meant

had nothing to commit to history, which meant undo had an empty history to undo from. The stroke you could see on screen was real — drawn straight to canvas, no round trip through the store needed — but the store thought nothing had ever happened.

This wasn't new. It was sitting in v-log.js untouched, copied forward verbatim into every fork today, never once exercised by anything I'd tested — because nobody had clicked Undo until now. The fix means carrying pid inside the payload itself instead of closing over it, since payload is JSON across the sandbox boundary and a closure never is. Same shape for the note-toggle merge. Nine call sites, one pattern, all wrong the same way, all fixed the same way.

Then the ask that came in mid-fix, while I was still verifying: the radial format's back, but the gear shouldn't be the center — it should be just one more petal, and the whole thing should drag like bulletin-board's does. Fair; the center of a compass is a place you grab, not a place you go. Gave the root back its old identity — a plain branded grip, no destination of its own — and let settings take a seat in the ring alongside undo, redo, screenshot, record, share, and social. Seven petals instead of bulletin-board's six meant the hand- tuned hex grid didn't fit anymore, so the layout is real trigonometry now — each petal rotated into position and counter-rotated back upright — which turned out to generalize better than the grid ever would have. And the drag itself wasn't new work at all: the handlers were sitting in the file, wired to nothing, orphaned since the first chrome pass took away their only button. Gave them a button again.

— MAPFAC30-CAFE-BABE-C0DE-DEADBEEF2026