[feat] controls and bottom-dock rework: ride-above dock, unified toggles, explorer tab, play mode menu, roster pill, rebindable shortcuts

[AlexZ005]

The Controls / bottom-dock rework: five design phases, then two rounds of fixes from the user's on-device passes. Designed against DCC standards (VS Code's bottom panel, Unity's Shortcut Manager, Blender/Unity's editor-area layout, the mobile-FPS touch convention).

Round 1 — the rework

1. 0854c3b Controls above the dock — pill + play FAB anchor on --bottom-inset; the <=500px --dock-inset padding hack deleted.
2. cb3c059 one decision tree for the panel buttons — $lib/panelToggles shared by the buttons AND the O/N keys (open in last mode → raise a buried window → hide only when on top); windowFocus.isTopVisibleWindow fixes the stale-top-of-stack misfire.
3. 739f9df the Explorer is a dock tab — DOCK_FAMILY/dockTabs, the force-close exclusivity deleted, one shared dock height, one shared "+" builder.
4. ee786fc play mode menu — right-click the play button for Play / VR / AR, pick-and-enter in one gesture; $lib/playMode owns the probes and requestPlay(); both hidden XR buttons mount permanently (kills the remount race and the threlte label sniff).
5. 55f8b5c the pill is a persisted, customizable roster.
6. 74398be rebindable shortcuts — stable ids + overrides, Alt-aware comboOf, click-to-rebind with conflict Swap, Ctrl+Enter = play.

Round 2 — first on-device pass

7. eed6221 ContextMenu keepOpen + rowActions (the Customize checklist survives clicks); Move left/right acts on the VISUAL row, one slot per press; collapsed = the well alone with Expand in the menu; viewport Tools ▸ Node editor. Also root-caused the standing reset-windows red (the suite clicked the wrong accordion).
8. c5d23d8 floating toolbar made opt-in; dock minimize + close-tab chrome.
9. 65212eb instant play re-entry (the flat 2s wall replaced by a pointer-lock retry where the refusal actually lives) + XR-permission-deny recovery (isVRMode had one writer and no failure reset; the wedge was Scene's viewport-menu guard, the ONE writer of both context menus).
10. b8e9a84 right-pinned dock chrome, filtered "+" menu, per-tab Undock/Close via a generalized arm seam, and G = grab in viewport / UV / timeline (a new external registry kind: listed and rebindable in Settings, executed by the owning editor).
11. 87ca571 mobile play mode — left half walks, right half looks, a still tap interacts, X overlay and Android Back both exit. Found two real bugs: play mode left the canvas scrollable (Chromium pointercanceled every drag after one frame) and a redundant 250ms tap threshold ate tap-to-interact.

Round 3 — second on-device pass (this round)

12. 54a1e64 ONE root cause behind two reports: the round-2 lucide icon buttons dropped text-xs, so their 24px line-height flex-stretched the tab band 22px → 34px — which both fattened the tabs and pushed the band's bottom edge 10px inside the panel, burying the resize cue. Tabs restored to 97.89 x 22px exactly; the cue raised above the strip in all seven panels, including ShaderEditor which never had one (so the shared dock height was frozen whenever it was showing). Dock X removed; the Explorer's close button turned out to exist but sit outside its own window at narrow widths; minimize glyph → PanelBottom, picked by rendering ten candidates at 14px.
13. 253c497 the dock resizes the viewport instead of covering it (default on, revertible in Settings ▸ Interface ▸ Viewport). Rendering was free — threlte sizes from a ResizeObserver on the canvas's parent — so the work was the eight client→NDC sites that read window.innerHeight and were right only by accident (Explorer drop, api.pointerRay, the mesh knife, vertex-handle sizing, pong, the framing guide, the PiP, mobile add), all now unconditional through one canvasRect.js leaf. The same latent bug was in the test harness. Measured: a hand-paced resize drag with AO at dpr 2 = 61 buffer reallocations, zero frames over 20ms, so the drag stays live.
14. f0514cd the toolbar floats by default with the slide removed; always-on-top split from the floating geometry (the combination worth knowing: floating off + on-top on = the bar stays on the floor and the dock passes behind it); the bar drags horizontally with a clamp measured against whichever HUD buttons share its row. Found a real modalGrab bug: its capture guard blocks a fresh gesture but not the browser's following click, so committing a move over a cell opened the dock and shifted the placement 21px.
15. 0cd8238 the Customize "mess" was three defects, including that chevron-left/chevron-right were in no icon map — Icon.svelte falls back to MAP[name] ?? Box, so both reorder controls had been drawing the same square since they shipped. The list is now the bar itself (top-to-bottom = left-to-right, the play well as its own row); the five other dock views are optional roster buttons (defaults byte-identical); "Swap with" shares one data source with the "+" list; togglePanel went 3 panels → 8.
16. 18f188e dock tabs reorder by drag or menu with a persisted order, drag out to undock, drag a floating window in to dock; precedence header-merge > bottom band > left/right edges. Two bugs caught by its own tests: a header-merge was being docked on top of and dissolved, and the new band stole the object list's edge drop.
17. 44cece7 / 642fd44 the two lanes merged and verified as a composition, not just as a text merge — one real defect found (the default-on floating toolbar covering the header a dock-drag test parked at screen centre under a 560px dock, measured at z45 over 43) and fixed in that suite, since both behaviours are correct.

Gates

• svelte-check 384 errors / 47 warnings on the merged head. Pristine base was 385/62; every delta is accounted (warnings −15 from the roster {#each} consolidation; errors −1 net from the applyLook fold plus exitPlay). release.yml's hardcoded gate must move to 384/47 with this branch.
• npm run build green at every commit and on the merge.
• 21 suites green on the merged tree, including a purpose-written cross-lane probe. New this branch: play-mode-menu, controls-roster (102), shortcut-rebind, dock-tabs-coexist, panel-toggle-keys, dock-chrome (64), viewport-tools-menu, play-reentry, grab-key, touch-play, toolbar-position (57), dock-tab-drag (52), viewport-scale (34). Every guard proven by breaking the code; every red A/B-proven pre-existing against BOTH merge parents.

Owed on-device (headless cannot judge)

• Whether the Customize list's up/down arrows read naturally for a horizontal bar (the tooltips say it; the feel is a judgement call).
• The toolbar drag on a real trackpad; the Android long-press cell menu (the whole drag discrimination exists to protect it); the new Settings rows and dock chrome in non-dark themes.
• Real-headset VR/AR entry from the play menu; Cardboard on a real Android; mobile stick/look feel and hardware Back under gesture-nav.
• The viewport-scaling default against a real workflow — and whether the corner HUD buttons should also lift with the dock (they deliberately stay window-anchored today).

🤖 Generated with Claude Code

Round 4 — third on-device pass

18. a87529f floating show/hide fixed for every panel, and click-to-front fixed app-wide. Two root causes: four windows (Flow Code, Animation, UV, HUD) registered use:focusStack with no key, so raiseWindow/isTopVisibleWindow could not address them and their roster buttons silently no-opped; and windowFocus.apply() ranked the z band from the bottom (40 + min(index,4)), tying every window past the fifth at 44 — measured five windows at z=44 at once, so a click changed no number and DOM order decided who painted. Ranking from the top makes the raised window uniquely 44. "Add a view" also left the Controls cell menu (the strip's ＋ keeps it).
19. 0a5563f a shortcut for every toolbar tool, and the Shader editor's floating window. Bare T = dock show/hide; Alt+E/F/A/U/S/H = Explorer / Flow Code / Animation / UV / Shader / HUD; O/N unchanged; every binding names the TOOL, not a toolbar slot, and all stay rebindable. conflictOf reported clear for all seven before they were added. Only E, F and S are bare mesh-session keys, but all six take Alt+ anyway — a scheme with memorised exceptions is worse than one that is always true (proven by A/B on a live mesh session: bare S is swallowed, Alt+S opens). The Shader editor gained #shader-window mirrored from the UV editor, and both exceptions coded around its absence are gone (dockOnly in the toggle tree, the guard withholding "Undock" from its tab menu).
20. 3ce32cf merge verification. No behavioural composition defect, but three things worth naming. The shader-editor suite's red was ours, not pre-existing — an earlier A/B compared against this branch's own HEAD, which already contained the change; origin/release/next passes with the same selector. Three suites were rotted by the ＋-to-lucide change, not one. And the flowCode/flowcode key mismatch was worse than reported: three callers address windowTabs by the dock key, so besides the tab-group branch it broke headerTargetAt's self-exclusion — during a header drag the pointer is always on FlowCode's own header, so Flow Code could never be dragged into the dock at all. Renamed with a windowTabGroups migration (dragWindow deliberately keeps its key — it names a persisted rect). Also corrected a z assertion that only held for five windows, a coverage gap blind to the eighth window, and a uv-editor check that was vacuous (it matched the strip's own tab, so it read green with the click doing nothing).

New suites this round: floating-window-focus (52), panel-shortcuts (126), shader-window (40). Gates still 384 errors / 47 warnings, build green.