PLAN_PR_INTERACTIVE_DEV_CONSOLE_UI

- Planned interactive on-canvas dev console UI
- Reused existing runtime and combo-key architecture
- Scoped implementation to tools/dev plus one sample

Author: DavidQ

docs/dev/CODEX_COMMANDS.md

@@ -7,23 +7,16 @@ MODEL: GPT-5.4-codex
 REASONING: high
 
 COMMAND:
-Apply the canvas debug HUD renderer implementation.
+Create BUILD_PR_INTERACTIVE_DEV_CONSOLE_UI as a docs-only, repo-structured delta.
 
 Requirements:
-- Keep changes isolated to:
-  - tools/dev/canvasDebugHudRenderer.js
-  - tools/dev/devConsoleIntegration.js
-  - one sample entry file only
-- Do not modify engine core
-- Draw HUD last on canvas
-- Preserve combo-key bindings exactly
-- Use canvas save()/restore()
-- Run node --check on touched JS files
-- Package result to:
-  <project folder>/tmp/APPLY_PR_CANVAS_DEBUG_OVERLAY_RENDERER_delta.zip
-
-Report back:
-- exact files changed
-- selected sample file
-- how HUD draw is invoked
-- validation results
+- Follow PLAN_PR -> BUILD_PR -> APPLY_PR
+- Docs-first only
+- No implementation code in this bundle
+- Plan a canvas-rendered interactive console UI
+- Reuse existing runtime and combo-key controls
+- Scope implementation to tools/dev and one sample entry only
+- Define input behavior, output history, validation steps, and rollback notes
+- Keep commit_comment.txt header-free
+- Package output to:
+  <project folder>/tmp/BUILD_PR_INTERACTIVE_DEV_CONSOLE_UI_delta.zip

docs/dev/COMMIT_COMMENT.txt

@@ -1,5 +1,5 @@
-APPLY_PR_CANVAS_DEBUG_OVERLAY_RENDERER
+PLAN_PR_INTERACTIVE_DEV_CONSOLE_UI
 
-- Added on-canvas debug HUD renderer
-- Wired HUD draw into sample-level debug integration
-- Preserved combo-key controls and HUD-last draw order
+- Planned interactive on-canvas dev console UI
+- Reused existing runtime and combo-key architecture
+- Scoped implementation to tools/dev plus one sample

docs/dev/NEXT_COMMAND.txt

@@ -1 +1 @@
-PLAN_PR_SAMPLE_GAME_USING_FULL_PIPELINE
+BUILD_PR_INTERACTIVE_DEV_CONSOLE_UI

docs/dev/change_summary.txt

@@ -4,6 +4,6 @@ David Quesenberry
 change_summary.txt
 
 Summary
-- Applied canvas HUD implementation path
-- Locked draw-order, combo keys, and sample-only integration
-- Preserved no-header rule for docs/dev/commit_comment.txt
+- Added PLAN PR for interactive dev console UI
+- Preserved sample-safe integration boundaries
+- Preserved docs-first workflow and commit_comment no-header exception

docs/dev/file_tree.txt

@@ -3,7 +3,7 @@ David Quesenberry
 04/05/2026
 file_tree.txt
 
-docs/pr/APPLY_PR_CANVAS_DEBUG_OVERLAY_RENDERER.md
+docs/pr/PLAN_PR_INTERACTIVE_DEV_CONSOLE_UI.md
 docs/dev/codex_commands.md
 docs/dev/commit_comment.txt
 docs/dev/change_summary.txt

docs/dev/validation_checklist.txt

@@ -6,25 +6,18 @@ validation_checklist.txt
 VALIDATION CHECKLIST
 
 Workflow
-- APPLY_PR created
+- PLAN_PR created
 - One PR per purpose
-- commit_comment.txt has no header
+- No implementation code in bundle
 
-Files
-- tools/dev/canvasDebugHudRenderer.js present
-- tools/dev/devConsoleIntegration.js updated
-- one sample entry updated
+Header Rules
+- Header present in all new files except docs/dev/commit_comment.txt
+- commit_comment.txt contains no Toolbox Aid header
 
-Functional
-- Ctrl + Shift + ` toggles HUD visibility
-- HUD draws on canvas
-- HUD draws after gameplay content
-- Panel navigation works
-- Missing diagnostics do not crash draw path
-- Reload combo remains browser-safe
-
-Safety
-- No engine core files modified
-- No F-key bindings remain
-- Canvas save/restore used
-- No duplicate listeners/runtime instances
+Plan Quality
+- Interactive console UI scope defined
+- Input behavior defined
+- Output history behavior defined
+- Sample-only integration boundary defined
+- Acceptance criteria defined
+- Validation steps defined

docs/pr/PLAN_PR_INTERACTIVE_DEV_CONSOLE_UI.md

@@ -0,0 +1,108 @@
+Toolbox Aid
+David Quesenberry
+04/05/2026
+PLAN_PR_INTERACTIVE_DEV_CONSOLE_UI.md
+
+# PLAN PR
+Interactive Dev Console UI
+
+## Objective
+Plan a sample-safe interactive on-screen developer console UI that builds on the existing dev console runtime,
+combo-key system, and canvas debug HUD so commands can be typed and executed directly inside the running sample.
+
+## Scope
+- Add an interactive console UI layer above the existing runtime
+- Support text input, command submission, output history, and simple focus behavior
+- Reuse the current command execution pipeline
+- Keep implementation isolated to tools/dev and one sample integration target
+- Preserve engine core boundaries and current debug controls
+
+## Non-Goals
+- No engine core rewrite
+- No DOM-only console dependency
+- No full editor framework
+- No autocomplete requirement in this PR
+- No multi-sample rollout
+
+## Existing Foundation
+Already in place:
+- dev console runtime
+- combo-key debug controls
+- canvas HUD renderer
+- sample-level integration path
+
+## Planned Behavior
+- Shift + ` toggles console UI visibility
+- Ctrl + Shift + ` toggles HUD visibility
+- Console accepts typed input while open
+- Enter submits a command
+- Escape closes the console UI
+- Up/Down browse recent command history
+- Output is rendered in a visible console region on-canvas
+- Existing runtime commands are reused, not reimplemented
+
+## Candidate Files
+Expected future implementation focus:
+- tools/dev/interactiveDevConsoleRenderer.js
+- tools/dev/devConsoleIntegration.js
+- one sample entry file only
+- optional test file for input/history behavior
+
+## UI Requirements
+- On-canvas console surface
+- Fixed anchor, default bottom-left or top-left
+- Separate input line from output history
+- Readable font and padding
+- Transparent/dim background
+- Safe clipping for long output
+- Max visible history window
+- Distinct prompt marker
+- Non-destructive when closed
+
+## Input Requirements
+- Capture character input only while console is open
+- Do not interfere with sample controls while closed
+- Backspace edits current line
+- Enter executes command
+- Escape closes console
+- Up/Down cycle command history
+- Tab reserved for future autocomplete; no required behavior now
+
+## Integration Rules
+- Reuse existing runtime executeConsoleInput()
+- Reuse current combo-key bindings already implemented
+- Do not spread input handling into engine core
+- Do not duplicate command registry
+- Keep console rendering after world render
+- Keep HUD and console rendering coordinated but separate
+
+## Acceptance Criteria
+- Console opens and closes reliably
+- Typed characters appear on screen
+- Enter executes commands
+- Output history is visible
+- Up/Down history navigation works
+- Escape closes without crashing
+- Sample still runs normally
+- No F-key bindings reintroduced
+- No engine core file changes
+
+## Validation
+- node --check on touched JS files
+- manual browser run
+- verify console typing
+- verify command execution for:
+  - help
+  - status
+  - scene.info
+- verify invalid command output is shown safely
+- verify console input does not remain captured after close
+
+## Risks
+- key handling collisions with gameplay input
+- text rendering overflow
+- duplicate listener setup
+- runtime/UI state drift
+
+## Deliverable
+Create BUILD_PR_INTERACTIVE_DEV_CONSOLE_UI as a docs-only, repo-structured delta.