- Shipped
- August 14, 2026 at 5:32 PM UTC
- Author
- kamo
- Commit
- dde2d1a
Three things. Pinned notes reach the home launchpad. Every note pinned on /notes gets a chip there in its own sticky colour, with a short preview; clicking one picks it up onto the overlay, and a corner control opens it in the full editor instead for the things a sticky cannot do. A note that is CURRENTLY FLOATING is left out — it is already on the member's screen, and listing it would offer the same note twice, the same rule that makes its /notes card go inert. Closing the sticky puts the chip back. The band renders only when the notes option survived the nav's own gate, so it decides nothing about access on its own, and it prefers the overlay's cached copy of a note so a chip never shows a title or colour from before it was picked up. New notes rotate through the palette. Each one opens on the colour after the member's most recently CREATED note, wrapping at the end, so a wall of stickies is never a block of identical yellow. Keyed off the notes themselves rather than a stored counter, so it stays right across devices and sessions with nothing extra to persist; an unset or unrecognised previous colour restarts the rotation instead of guessing. Closing a note now crumples it. A beat of anticipation, then it scrunches, spins and drops away, leaving a puff of paper scraps in its own colour over the space it left. The scraps are rendered by the layer, not the note: a child inherits the note's exit transform and would shrink away with it instead of bursting outward, so the note hands over its last rectangle and colour on the way out. A maximized note bursts across the whole viewport rather than the size it would restore down to; a minimized one bursts not at all, having no space on screen to burst over; and prefers-reduced-motion gets a plain fade with no scraps. The scatter is a deterministic hash, not Math.random, which would re-roll every render and jitter the scraps mid-flight.