Purpose
This mode is a workspace-driven tactile desktop. It starts from a structured `haptic_workspace`, then moves the user through a 3D launcher,
paginated content galleries, file-system navigation, and opened scenes for models, audio, and text.
Current Interaction
- Select the active workspace from the left panel, then load it into the scene engine.
- Move the pointer emulator with `W`, `A`, `S`, `D`, `Q`, and `E` and activate focused objects with `Space` or `Enter`.
- Entering a gallery or the file browser should land first on a tactile `Gallery` or `Browser` hub so the user starts from the paginated scene context instead of from a single content item.
- Use distinct tactile object shapes in the file browser: folders, models, texts, audio files, and unsupported files are intentionally not represented by the same 3D form.
- Supported files opened from the file browser now enter their corresponding runtime scene directly: models to the 3D model scene, texts to the Braille reading scene, and audio files to the audio transport scene.
- Use `Gallery` or `Browser` to return to the exact gallery page or file-browser location that launched the current scene, and use `Launcher` to return to the workspace start scene.
- Use `Start` or `Root` to return to the first page of a gallery or the root of the file browser, not just to the current origin page.
- Read the Navigation Trail panel as the compact visual explanation of how the current scene was reached: launcher, gallery or browser context, page or path, and opened detail or content scene.
- Orbit, pan, and zoom changes now persist while you stay on this page, so moving through desktop scenes does not force you to reframe the view after each activation.
- Use tactile scene controls for launcher return, gallery or browser return, gallery start or file-browser root, paging, opening content, and browsing the workspace file root.
- Returning to the launcher should land on the neutral launcher hub first, not on a specific gallery tile.
- Use spoken cues as a support channel while keeping the object shapes and scene changes as the primary interaction contract.
Current Limits
- The workspace-driven desktop is still a modern rebuild, not a recovered legacy implementation.
- The initial content-opening paths are designed to prove the interaction model before a native haptic backend is attached.
- User workspaces are rooted in external folders on disk so large assets do not need to live inside the application repository.