Plan Phase 16 3D execution (all items structured into layers)

Author: DavidQ

docs/dev/CODEX_COMMANDS.md

@@ -1,3 +1,19 @@
-MODEL: GPT-5.3-codex
-REASONING: high
-COMMAND: Implement BUILD_PR_LEVEL_12_3_REPLICATION_CLIENT_APPLICATION.
+
+MODEL: GPT-5.4
+REASONING: medium
+
+COMMAND:
+Prepare for Phase 16 execution using PLAN_PR_3D_PHASE16_MASTER_EXECUTION
+
+Do NOT implement yet.
+
+Tasks:
+- understand layer ordering
+- prepare for Layer 1 start
+- ensure no conflicts with existing engine
+- confirm separation from 2D systems
+
+Rules:
+- no code generation in this step
+- no repo modification
+- planning only

docs/dev/COMMIT_COMMENT.txt

@@ -1 +1 @@
-implement client replication and application layer — BUILD_PR_LEVEL_12_3_REPLICATION_CLIENT_APPLICATION
+Plan Phase 16 3D execution (all items structured into layers)

docs/dev/NEXT_COMMAND.txt

@@ -1 +1 @@
-PLAN_PR_REAL_NETWORK_CAPABILITY_ENTRY
+PLAN_PR_3D_LAYER_1_FOUNDATION

docs/dev/reports/change_summary.txt

@@ -1,3 +1 @@
-- Added roadmap-update bundle to make full real-network capability a prerequisite before 3D
-- Includes live transport, authoritative server runtime, replication, playable validation, and Docker-hosted server items
-- Preserves existing completed network/debug/container work
+Structured all 3D roadmap items into dependency-ordered execution layers

docs/dev/reports/validation_checklist.txt

@@ -1,3 +1 @@
-- replication intake
-- client apply
-- no regressions
+plan-only; no code; no repo changes; layered execution defined

docs/dev/roadmaps/MASTER_ROADMAP_HIGH_LEVEL.md

@@ -670,3 +670,4 @@
 [ ] simulated code (like some of the netword samples) should be coverted to use real networks) understanding, tests may need some moch
 [ ] single class per file
 [ ] organize/rebuild samples/games so the are as if new construction with proper classes/data/etc in proper folder
+[ ] flatten css layer, there should only be a few, use as much as possible to top layer a button is a button, should be a single class to operate, I know exceptions can exist

docs/pr/PLAN_PR_3D_PHASE16_MASTER_EXECUTION.md

@@ -0,0 +1,180 @@
+
+# PLAN_PR_3D_PHASE16_MASTER_EXECUTION
+
+## Purpose
+Define a clean, dependency-ordered execution plan for all Phase 16 (3D) items (~41 items) based on the current roadmap state.
+
+This is a PLAN-ONLY bundle. No implementation.
+
+---
+
+## Ground Truth
+Non-3D system is complete and stable.
+3D work begins as an isolated capability lane.
+
+Reference:
+- 3D Engine Foundation
+- 3D Samples
+- 3D Debug Support
+- 3D Tooling
+- 3D Capability Requirements
+
+---
+
+## Execution Strategy
+
+### RULES (Carry Forward)
+- no broad repo cleanup
+- exact-cluster extraction only
+- validate-first before promotion
+- samples prove capability before engine abstraction
+
+---
+
+## PHASE 16 EXECUTION STACK
+
+### LAYER 1 — Minimal 3D Runtime Spine (FOUNDATION)
+Goal: Get something rendering and moving.
+
+1. 3D scene boot
+2. 3D render foundation
+3. basic transform model (position/rotation/scale)
+4. camera controls (orbit + free)
+5. minimal render loop integration
+
+Exit Criteria:
+- cube renders
+- camera moves
+- no tools required
+
+---
+
+### LAYER 2 — Core Interaction (MOVEMENT + COLLISION)
+Goal: Make 3D interactive.
+
+6. 3D movement base
+7. basic collision (AABB or simple bounds)
+8. input mapping for 3D
+9. update loop integration with state
+
+Exit Criteria:
+- player can move
+- collision prevents pass-through
+
+---
+
+### LAYER 3 — SAMPLE PROOF (PREREQUISITES)
+Goal: Lock learning path before expansion.
+
+10. Scene Boot Sample
+11. Camera Orbit Sample
+12. 3D Movement Sample
+13. Basic Collision Sample
+
+Exit Criteria:
+- all 4 prerequisite samples exist and run independently
+
+---
+
+### LAYER 4 — CORE SAMPLE TRACK (1601–1608)
+Goal: Expand capability through samples.
+
+14–21:
+- Cube Explorer
+- Maze Runner
+- First Person Walkthrough
+- Platformer
+- Driving Sandbox
+- Physics Playground
+- Space Shooter
+- Dungeon Crawler
+
+Rule:
+- each sample introduces ONE concept cleanly
+
+---
+
+### LAYER 5 — ADVANCED CAPABILITY
+22–24:
+- Lighting Demo
+- AI Navigation Demo
+- Large World Streaming
+
+---
+
+### LAYER 6 — DEBUG SUPPORT (3D)
+25–30:
+- transform inspector
+- camera debug panel
+- render pipeline stages
+- collision overlays
+- scene graph inspector
+
+Rule:
+- debug surfaces follow sample needs (not ahead)
+
+---
+
+### LAYER 7 — TOOLING (3D)
+31–36:
+- 3DMapEditor stabilization
+- 3DAssetViewer validation
+- camera path editor alignment
+- physics sandbox integration
+- asset pipeline validation for 3D
+- model converter alignment
+
+Rule:
+- tools follow asset + sample pressure
+
+---
+
+### LAYER 8 — CAPABILITY COMPLETION
+37–41:
+- rendering completeness
+- camera completeness
+- movement completeness
+- physics completeness
+- debug completeness
+
+Exit Criteria:
+- 3D matches 2D capability maturity (parity mindset)
+
+---
+
+## DELIVERY MODEL
+
+Each layer executes as:
+PLAN → BUILD → APPLY
+
+Small PRs only:
+- 1 concept per PR
+- 1 sample per PR
+- no cross-layer mixing
+
+---
+
+## ORDER OF EXECUTION (STRICT)
+
+1. Layer 1 (foundation)
+2. Layer 2 (interaction)
+3. Layer 3 (prereq samples)
+4. Layer 4 (core samples)
+5. Layer 6 (debug as needed)
+6. Layer 7 (tools as needed)
+7. Layer 5 (advanced)
+8. Layer 8 (finalization)
+
+---
+
+## VALIDATION STRATEGY
+
+For every PR:
+- visual validation required
+- sample runs independently
+- no regression to 2D
+
+---
+
+## OUTPUT
+<project folder>/tmp/PLAN_PR_3D_PHASE16_MASTER_EXECUTION.zip