Promote roadmap rules out of checklist

Author: DavidQ

docs/dev/CODEX_COMMANDS.md

@@ -2,34 +2,23 @@ MODEL: GPT-5.4
 REASONING: high
 
 COMMAND:
-Create `BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP`.
+Create BUILD_PR_ROADMAP_RULES_PROMOTION_AND_NORMALIZATION
 
-Implement a surgical cleanup of the leftover `engine/vector/` residue.
+1. Locate the two items:
+- repo structure work is now constrained to exact move-map BUILDs only
+- remaining structure normalization should avoid broad folder churn until active shared extraction and promotion-gate work stabilize
 
-Required work:
-1. Audit the remaining contents of `engine/vector/`.
-2. For each remaining item, classify it as:
-   - stale residue to remove
-   - real content to move to the correct modern home
-   - temporary compatibility surface that must remain
-3. Preferred outcome:
-   - if the folder is only stale residue, remove it cleanly
-   - if it contains real content, move that content first, then remove the stale shell if possible
-4. Respect current boundary decisions:
-   - rendering-owned vector drawing stays with rendering
-   - shared math/utility-owned vector math stays in shared math/utility
-5. Normalize lingering imports pointing at `engine/vector/`.
-6. Validate:
-   - imports remain green
-   - no misleading old vector boundary remains unless a temporary compatibility reason is explicitly documented
-   - section-1 truth is improved
-7. Update roadmap status markers only if truthfully supported.
+2. Convert them:
+- remove checkbox markers
+- move to top of roadmap under rules section
 
-Final packaging step is REQUIRED:
-`<project folder>/tmp/BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP.zip`
+3. Do NOT:
+- change wording
+- delete content
 
-Hard rules:
-- implementation by Codex
-- surgical changes only
-- no unrelated repo changes
-- no missing ZIP
+4. Ensure:
+- checklist contains only tasks
+- rules are clearly separated
+
+OUTPUT:
+<project folder>/tmp/BUILD_PR_ROADMAP_RULES_PROMOTION_AND_NORMALIZATION.zip

docs/dev/COMMIT_COMMENT.txt

@@ -1,2 +1 @@
-Clean up leftover engine/vector residue after vector boundary moves
-BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP
+Promote roadmap rules out of checklist

docs/dev/NEXT_COMMAND.txt

@@ -1 +1 @@
-BUILD_PR_LEVEL_01_SECTION_1_CLOSEOUT_RECHECK
+NEXT_PR_TBD

docs/dev/reports/change_summary.txt

@@ -1,3 +1 @@
-- Added residue-cleanup PR for the leftover engine/vector folder
-- Requires audit, move-or-remove classification, and import normalization
-- Aims to eliminate misleading legacy vector ownership during section-1 closeout
+Moved rules from checklist to top

docs/dev/reports/validation_checklist.txt

@@ -1,7 +1 @@
-- remaining engine/vector contents were audited
-- stale residue removed or real content moved
-- lingering imports normalized
-- old vector boundary no longer misleads structure truth
-- roadmap/status handling remains truth-safe
-- output ZIP created at:
-  <project folder>/tmp/BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP.zip
+Rules no longer use [ ]

docs/dev/roadmaps/MASTER_ROADMAP_HIGH_LEVEL.md

@@ -5,6 +5,10 @@
 - [.] in progress
 - [ ] planned
 
+## Rules
+- repo structure work is now constrained to exact move-map BUILDs only
+- remaining structure normalization should avoid broad folder churn until active shared extraction and promotion-gate work stabilize
+
 ## Conservative Rebaseline (2026-04-12)
 - status updates in this revision are conservative and execution-backed
 - recent tool-host, asset-pipeline, debug-inspector, and launch-smoke lanes are reflected without broad scope expansion
@@ -130,8 +134,6 @@
 - [x] broad import-path correction from `engine/` to `src/engine/` applied across remaining games/samples
 - [x] partial retro smoke pass completed after path correction
 - [x] additional post-move validation complete
-- [.] repo structure work is now constrained to exact move-map BUILDs only
-- [ ] remaining structure normalization should avoid broad folder churn until active shared extraction and promotion-gate work stabilize
 
 ---
 

docs/pr/BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP.md

@@ -1,63 +1,71 @@
 # BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP
 
 ## Purpose
-Clean up the leftover `engine/vector/` residue now that the vector classes/content have already been moved elsewhere.
-
-## Problem
-The old `engine/vector/` folder and remaining content still exist even though the intended classes were already moved.
-That creates:
-- stale ownership ambiguity
-- legacy import risk
-- false structure signals during section-1 closeout
-
-## Scope
-
-### A. Residue audit
-Codex must inspect the remaining `engine/vector/` folder and classify each remaining item as one of:
-- stale residue that should be removed
-- still-owned content that must be moved to its correct current home
-- compatibility surface that must remain temporarily but should be marked clearly
-
-### B. Cleanup rule
-Preferred outcome:
-- if the folder is only stale residue, remove it cleanly
-- if it still contains real content, move that content to the correct modern home first
-- do not leave `engine/vector/` as an ambiguous half-alive legacy boundary
-
-### C. Boundary truth
-Use current boundary decisions already established or in-flight:
-- rendering-owned vector drawing stays with rendering
-- shared math/utility-owned vector math stays in shared math/utility
-- engine should not keep a misleading old vector home if the real ownership moved
-
-### D. Import safety
-- normalize any lingering imports that still point at `engine/vector/`
-- keep validation green
-- avoid broad churn outside this residue cleanup
-
-### E. Roadmap handling
-- update roadmap status markers only if truthfully supported
-- no roadmap text rewrite
-
-## Desired outcome
-After this PR:
-- `engine/vector/` is no longer a misleading leftover boundary
-- any real remaining content is in the correct modern home
-- legacy import risk is reduced
-- section-1 residue is reduced further
-
-## Validation requirements
-Codex must report:
-- what remained inside `engine/vector/`
-- what was removed vs moved
-- any imports updated
-- whether the old folder still exists after cleanup and why
-- whether this helps close section 1 truthfully
+Remove the leftover `src/engine/vector/` boundary residue now that vector ownership is already normalized to:
+- rendering-owned vector drawing in `src/engine/rendering/`
+- shared math-owned vector math in `src/shared/math/`
+
+## Residue Audit
+Remaining items found in `src/engine/vector/` before cleanup:
+1. `src/engine/vector/index.js`
+- Classification: temporary compatibility surface (re-export only)
+- Reason: re-exported `transformPoints` and `drawVectorShape` from rendering and `vectorFromAngle` from shared math
+
+2. `src/engine/vector/VectorDrawing.js`
+- Classification: stale residue (re-export only)
+- Reason: no owned logic, only re-export to rendering
+
+3. `src/engine/vector/VectorMath.js`
+- Classification: stale residue (re-export only)
+- Reason: no owned logic, only re-export to shared math
+
+## Implementation
+1. Removed stale boundary folder:
+- deleted `src/engine/vector/index.js`
+- deleted `src/engine/vector/VectorDrawing.js`
+- deleted `src/engine/vector/VectorMath.js`
+- removed `src/engine/vector/`
+
+2. Normalized runtime/sample imports away from `engine/vector`:
+- `games/Asteroids/entities/Asteroid.js`
+- `games/Asteroids/entities/Ship.js`
+- `games/Asteroids/entities/Ufo.js`
+- `samples/phase-09/0901/VectorRenderingSystemScene.js`
+- `samples/phase-09/0902/PolygonCollisionScene.js`
+- `samples/phase-09/0903/PointInPolygonScene.js`
+- `samples/phase-09/0906/HybridCollisionScene.js`
+
+All moved from:
+- `'/src/engine/vector/index.js'`
+
+To:
+- `'/src/engine/rendering/index.js'`
+
+3. Normalized metadata/contract references to modern boundary:
+- updated `samples/metadata/samples.shared.boundaries.report.json`
+- updated `samples/metadata/samples.index.metadata.json`
+- updated `tools/shared/renderPipelineContract.js` (`vector-asset-studio` engine targets no longer include `engine/vector`)
+
+## Validation
+Executed focused validation for this PR:
+1. Boundary residue check
+- `src/engine/vector/` no longer exists
+
+2. Import/path ambiguity check
+- no remaining `engine/vector` references in `src`, `games`, `samples`, `tests`, `tools` JS/MJS/JSON surfaces
+
+3. Syntax checks (`node --check`)
+- touched JS/MJS files parse cleanly
+
+4. Focused runtime regression checks
+- `node tests/scenes/SceneManager.test.mjs`
+- `node tests/scenes/TransitionScene.test.mjs`
+- `node tests/scenes/AttractModeController.test.mjs`
+- `node tests/core/EngineSceneLifecycle.test.mjs`
+- `node tests/final/PlatformUxSystems.test.mjs`
+
+## Roadmap
+No roadmap status marker changes were required for this surgical residue cleanup.
 
 ## Packaging
 `<project folder>/tmp/BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP.zip`
-
-## Scope guard
-- docs-first PR bundle
-- Codex writes implementation
-- no unrelated repo changes

docs/pr/BUILD_PR_ROADMAP_RULES_PROMOTION_AND_NORMALIZATION.md

@@ -0,0 +1,29 @@
+# BUILD_PR_ROADMAP_RULES_PROMOTION_AND_NORMALIZATION
+
+## Purpose
+Promote roadmap operational rules out of checklist items and normalize them as top-level guidance.
+
+## Decision
+These are NOT tasks. They are rules:
+
+- repo structure work is now constrained to exact move-map BUILDs only
+- remaining structure normalization should avoid broad folder churn until active shared extraction and promotion-gate work stabilize
+
+## Required change
+
+### A. Convert to rules
+- remove checkbox format
+- move to top of roadmap under a rules/guidelines section
+
+### B. Preserve content
+- no wording changes
+- no deletions
+- only move + format change
+
+### C. Roadmap cleanup
+- ensure no rules remain as `[ ]` or `[.]` items
+- checklist should contain only actionable tasks
+
+## Outcome
+- roadmap becomes cleaner
+- rules vs tasks clearly separated