[Task] Track the production editor-camera roadmap

[JeanPhilippeKernel]

Type

• Bug
• Feature
• Refactor / cleanup
• Task / chore

Overview

Track the remaining work needed to take the editor camera from its current navigation foundation to a production-grade editor workflow. This is a planning and dependency tracker; implementation stays in the linked, independently reviewable issues.

Context

The current camera work supplies fly/orbit/pan navigation, scene bounds and selection framing, perspective/orthographic projection, axis views, temporary numeric bookmarks, semantic commands, platform-aware shortcuts, and focused input ownership. The current slice is validated by FlyCamera, controller, scene-ray-query, ZUI input-capture, and InputManager tests.

Do not fold the separate engine-native transform gizmo work into camera PRs; it is tracked by #788. Preserve allocation-free hot paths and semantic input routing as the roadmap grows.

What needs to be done

Foundation and correctness

• [Bug] Synchronize FlyCamera projection with docked viewport extent #780 — make projection state match the docked viewport extent.
• [Feature] Replace placeholder FlyCamera raycast with a scene query #781 — use real scene ray queries for camera interaction.
• [Bug] Harden FlyCamera input ownership, focus, and cursor capture #782 — maintain explicit FlyCamera input ownership, focus, and cursor capture.
• [Task] Add deterministic FlyCamera and controller coverage #783 — retain deterministic FlyCamera/controller test coverage.

Navigation and scene-scale behavior

• [Feature] Deliver standard editor navigation commands and preferences #784 — finish commands, preferences, profiles, persistent settings, and named bookmarks.
• [Feature] Support large-world and scene-aware navigation modes #785 — define large-world precision, clipping, navigation modes, collision, and scene-aware pivots.
• feat(editor): multi-actor selection in Outliner #672 — add Outliner multi-selection to enable multi-object framing.
• [Feature] Add an editor viewport orientation widget #789 — add a viewport orientation widget over the existing axis-view commands.

Authoring and rendering integration

• [Feature] Support editor and scene-camera piloting workflows #790 — support editor/scene-camera piloting, alignment, and game-camera preview.
• [Feature] Integrate editor camera cuts with temporal rendering #791 — reset temporal rendering history on editor camera cuts and preserve unjittered interaction math.
• [Feature] Editor transform gizmo delivered in incremental PRs #788 — deliver the native transform gizmo through separate incremental PRs.

Optional professional-device and review workflows

• [Feature] Add gamepad and 3D-mouse editor navigation #792 — add gamepad and 3D-mouse navigation.
• [Feature] Add editor camera paths and reviewable shot playback #793 — add editor camera paths and shot playback.

Resources

• ZEngine/docs/future-plan/fly-camera-redesign.md
• ZEngine/ZEngine/Rendering/Cameras/FlyCamera.*
• ZEngine/ZEngine/Controllers/FlyCameraController.*
• Tetragrama/Controllers/EditorCameraController.cpp
• [Feature] Deliver standard editor navigation commands and preferences #784, [Feature] Support large-world and scene-aware navigation modes #785, [Feature] Editor transform gizmo delivered in incremental PRs #788 — related scope and delivery constraints

Testing

• Each implementation issue must add focused CPU/input tests and manual editor validation.
• Validate keyboard/mouse, projection, framing, and focus behavior on macOS, Windows, and Linux.
• Build Debug and Release on each supported platform before closing a roadmap item.

Acceptance criteria

• Every remaining production-camera capability has a non-duplicated implementation issue or an explicitly linked existing issue.
• Dependencies and intended delivery boundaries are clear before implementation starts.
• The tracker stays current as linked issues are completed or superseded.
• Builds without warnings in Debug and Release.
• All relevant unit tests pass.
• No regression in existing functionality.

Estimated effort

Multi-PR roadmap; approximately 4–8 weeks excluding optional device backend work.