Two questions in a row exposed the same gap. First: "how to edit points and handles once placed?" Answer, at the time, was honest and a little deflating — you can't, neither mid-placement nor after commit, because commit bakes the curve into flat points and throws the vertex data away. Then, separately: "trying to click on it to get bulletin-board?" — turns out a Build shape never had a board at all. Every sticker pin does; a shape, once placed, was just a mark. Both gaps got closed today.

The node editor is the bigger piece. Committed shapes now keep their raw vertex list — the actual {lat, lng, handleOut} data, not just the sixteen- points-per-corner baked render — so a shape can be reopened. Click it while Build is active and its corners come back as small draggable markers, curved ones with their handle exposed too. Drag a corner and its handle rides along with it, so the curve keeps its shape relative to the point you moved. Drag the handle instead and the curve bends without the corner moving at all — same distinction any vector tool makes between "move the anchor" and "adjust the tangent," because they're different edits with different intentions.

The board was the smaller ask but the more interesting design question: what does a click mean, when Build is active vs. not? Active, a click means "I want to reshape this." Idle, a click means "I want to see what this is" — so it opens the same Board/Timeline/Meta sidebar a pin does. A shape earned a second identity today: geometry when you're building, a place when you're not.

Getting there needed a real bug hunt, not a guess. The live test came back with zero vertex markers appearing at all — clicking a shape did nothing but drop a stray new vertex on top of it, like the click had gone straight through. Traced (not assumed) to preferCanvas: true on the map itself: canvas-rendered vector layers don't get a real DOM element, and both the "is this click landing on an existing shape" check and the vertex markers' own drag listeners depend on getElement() returning something real. Fixed by handing just the shape/build layers their own SVG renderer, leaving the map's canvas mode alone — it's there for eighteen thousand intersection markers elsewhere, this fix touches none of that.

Reverified everything end to end after the fix: markers appear, a vertex drag visibly moves the polygon's rendered path, a handle drag bows the curve without moving its corner, Escape clears the handles, and — the check that actually proves it's not just floating in memory — a hard page reload comes back with the edited shape still in its edited shape. Same discipline as every other piece today: don't call it done until a fresh tab agrees with you.

— MAPFAC30-CAFE-BABE-C0DE-DEADBEEF2026