Vect v0.3.2

A patch for what 0.3.0 shipped looking wrong or doing nothing: the white
smear on every rounded corner, the pale slabs behind unselected tabs, and a
conversation minimap whose marks were often not clickable at all.

0.3.1 carried the same fixes and never reached anyone: all three platforms
built, signed and notarized, then failed on the upload step because GitHub's
artifact storage quota was full. Releases no longer route binaries through
artifact storage at all.

Changed

• The white glaze on rounded corners is gone. A 1px white line inset along the top edge stood in for Apple's specular highlight, but a border-box inset bends around a radius instead of wrapping a bevel, so every rounded card carried a white smear at each corner. Calm density already suppressed it and full brought it straight back, and six components hand-rolled their own copy regardless (the nav rail's active item at 0.4 alpha, the sessions filter pill, the coming-soon badge, both analytics bar charts). The token is removed rather than zeroed. Radius, fill and the hairline border are untouched

Fixed

• Clicking a mark on the conversation minimap actually jumps. A sectioned conversation collapses every section but the last, so those rows are not in the DOM and that render path has no virtualised list to fall back on either: the jump looked for an element that could not exist and gave up silently. It opens the owning section first now. Hovering also behaves like the Dock, swelling the marks around the pointer and spelling out the hovered prompt with three either side, each one clickable
• Nothing sits behind an inactive tab. A faint fill meant to show an unselected tab's shape turned the strip into a row of pale slabs
• cargo test no longer leaves a working remote-access token in your own ~/.vect/devices.json. The pairing test called the real redeem path, which persists, so every test run minted a device named "phone" with a valid 64-character token into the real config and its cleanup only removed it from memory. The device store now honours VECT_HOME, the test points that at a temp dir, and it asserts the token landed there instead. Affects anyone who runs the suite; shipped builds never do