fix(designer): share one panel reconciler across sessions

[KingDoxik]

Why

Editing properties in the designer right panel silently did nothing — background colour on a screen node, border radius on a view, the absolute-positioning toggle. The only symptom in the browser was a React warning:

Detected multiple renderers concurrently rendering the same context provider. This is currently unsupported.

Root cause

createPanelReconciler called createReconciler() once per panel session, with isPrimaryRenderer: true. Every call mints a distinct React renderer, and React stores a context's live value in exactly two slots — _currentValue for the primary renderer, _currentValue2 for the secondary.

With a screen selected there are four built-in panels (Variables, States, Layout, Fill), so five renderers — react-dom plus four panel reconcilers — all claiming primary and all pushing/popping PaywallStoreContext, PanelHostServicesProvider, and DefinitionSelectionProvider on the same slot. Each renderer pops from its own stack into a shared slot, so a definition can read another session's — or a popped, default — context value.

Fix

One process-wide reconciler with isPrimaryRenderer: false:

• Per-session state (instance registry, id counter, commit hook) moved from the closure onto PanelContainer, so the host config can be shared. createPanelReconciler() keeps its signature and just mints a fresh container.
• detachDeletedInstance only receives the instance, so instances carry a Symbol-keyed back-reference to their owning container to evict from the right registry.
• isPrimaryRenderer: false puts panels on _currentValue2 and leaves _currentValue to react-dom. Safe because wrap already re-provides everything inside the reconciler root — every definition reads only PaywallStoreContext, host services, and the selection store.

Also in this PR

• Designer panel chrome aligned with the shared design-system colours.
• Panel wire vocabulary extended: button hint/width, toggle group width, menu icon/label/variant/size, select field icon, popover content title/onClose, align icons.
• popoverTrigger fixed — Radix asChild clones a single element child, but renderChildren returned an array of Fragment-wrapped nodes, so the trigger rendered nothing.
• host-renderer.test.tsx un-quarantined (+251 lines of coverage); designer suites get a 20s test timeout.
• Carries the earlier fix: separate community analytics surfaces commit, which was stranded on an orphan root commit in this worktree and has been re-parented onto main.

Verification

• libraries/paywalls: 185/185 tests pass.
• Designer suite: 628/628 across 66 files.
• Build and typecheck clean.
• Repro (five BuiltinPanelHosts under one react-dom store provider) emitted the warning five times before, none after.

⚠️ The renderer collision is a definite defect and was the only anomaly present, but it could not be made to reproduce the no-op edit in jsdom — the repros committed correctly despite the warning. Worth confirming in the running app; @voidhash/paywalls is pre-bundled by Vite, so restart the dev server with --force.

🤖 Generated with Claude Code

[greptile-apps]

Too many files changed for review (133 files, 100 file limit).

Bypass the limit by tagging @greptile-apps to review.

[github-actions]

Thank you for following the naming conventions for pull request titles! 🙏

[github-actions]

Install the packages built from e56c891:

@voidhash/paywalls

pnpm add @voidhash/paywalls@https://pkg.voidha.sh/paywalls/e56c891

@voidhash/node

pnpm add @voidhash/node@https://pkg.voidha.sh/node/e56c891

@voidhash/web

pnpm add @voidhash/web@https://pkg.voidha.sh/web/e56c891

voidhash-cli

pnpm add voidhash-cli@https://pkg.voidha.sh/cli/e56c891

@voidhash/react-native

pnpm add @voidhash/react-native@https://pkg.voidha.sh/react-native/e56c891

Internal workspace deps (lib, generated-clients, shared, studio) are published at the same sha and resolved automatically.

Replace the sha with pr-127 or the branch name to always get the latest build of this PR.