[33-editor-ui] toolbar order, Interact cell, edit-in-game moves stay, FPS + draw calls

[AlexZ005]

Roadmap 33, lane 33-editor-ui — items E1 E2 E3 E4 Q1 of cloud plans/core/lanes/33/user-feedback-2026-10-01b.md.

What changed

• E1 toolbar order — the default bar is Move, Rotate, Scale, Interact, Play, Object list, Node editor, Explorer, Animation. A stored toolbar that is still a shipped default migrates (keeps where the bar is parked and whether it is collapsed); a customized bar wins as saved and does not gain Animation (Controls.svelte: LEGACY_DEFAULT_ROWS, PROMOTED_DEFAULTS).
• E2 red border — the Interact <button> took focus on click and wore classActive's focus:ring-4; its ring is now keyboard-only (focus-visible), so a click looks like every other cell.
• E3 corners by Play — the well's hover halves listened to p:hover; the Interact toggle is a <button>, so they never painted beside it. Now *:hover.
• E4 Edit in a running game — measured: with a game running then Edit, Towers 10/44, Stars Room 26/49 and the football could not be put anywhere (the gizmo release handed a dynamic body back to the still-running sim with a throw). In Edit, in a game scene, a release now parks the body (physics.js, hold 'edit'); leaving Edit releases every parked body at rest. A plain physics playground keeps the editor throw. VR: scenery (>= 4 m, or around your head) was never grip-holdable; a selected wall/floor is now held in Edit (vrGrip.pickGripTarget), unselected scenery still moves the world, and a one-time headset banner says so.
• Q1 FPS + draw calls — Settings ▸ Interface ▸ Viewport (and the VR settings panel): fps, frame ms, draw calls, triangles, in any mode. Desktop: the one FpsCounter (the game shell's); VR: vrPerfStrip.js, a head-locked strip. Draw calls amber > 120, red > 150 (fpsMeter.callsTier). XR frames now drive the draw-call sampler (sceneBudget.noteExternalFrame), which froze in a headset because the window rAF stops.

Proof

• svelte-check 333/47 (baseline held); vitest 385/385 (new fpsMeter, extended vrGrip).
• e2e, green on this branch: editor-ui-33 (new, 3/3 consecutive runs), edit-move-games (new — the seven Games-tab games, every object moved fresh and with the game running; 38 bodies parked), controls-roster, editor-modes, game-shell, vr-game-panel, vr-grips-by-mode, throw-velocity.
• Counterfactuals: p:hover restored -> E3.1/E3.2 red; classActive back on the toggle -> E2.1/E2.2 red (a 4 px ring over the neighbour); the pre-park game-running probe is the E4 "before". Logs: /home/deck/.code/lanes-30/after-33/33-editor-ui/.

Not done / owed

• Waves' walking enemies are positioned by the module as a pure function of time during a wave, so they still snap back in Edit mid-wave — module side, filed for 33-modules (QUESTIONS F5).
• A non-initiator peer's drag of a dynamic body reaches the initiator as a move (external hold, then physics) — not parked; would need an additive wire field (F4).
• On a Quest (owed): the perf strip's placement/readability, the select-then-grip feel on walls/floors, the hint banner.

🤖 Generated with Claude Code