Clean up leftover engine/vector residue after vector boundary moves

BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP

Author: DavidQ

docs/dev/CODEX_COMMANDS.md

@@ -2,27 +2,31 @@ MODEL: GPT-5.4
 REASONING: high
 
 COMMAND:
-Create `BUILD_PR_LEVEL_01_SCENE_SCENES_BOUNDARY_NORMALIZATION`.
+Create `BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP`.
 
-Implement one clear scene boundary decision:
+Implement a surgical cleanup of the leftover `engine/vector/` residue.
 
-1. Do NOT keep both `scene` and `scenes` as competing top-level engine concepts when they overlap.
-2. Prefer `src/engine/scene/` as the single engine domain boundary.
-3. Treat plural "scenes" as content collections/instances owned by games or samples where appropriate, not as a competing engine boundary.
-4. Normalize imports/exports to that one truth.
-5. Keep ownership clear:
-   - engine owns reusable scene runtime logic only
-   - game/sample-specific scene content stays in its owning layer unless truly reusable
-6. Keep the changes surgical.
-7. Update roadmap/status only if needed and only by status markers or additive truth-safe structure clarification.
-8. Validate:
+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 duplicate scene/scenes top-level ambiguity remains
-   - engine scene ownership is clearer
-   - section 1 residue is reduced or closed truthfully
+   - 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.
 
 Final packaging step is REQUIRED:
-`<project folder>/tmp/BUILD_PR_LEVEL_01_SCENE_SCENES_BOUNDARY_NORMALIZATION.zip`
+`<project folder>/tmp/BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP.zip`
 
 Hard rules:
 - implementation by Codex

docs/dev/COMMIT_COMMENT.txt

@@ -1,2 +1,2 @@
-Normalize scene vs scenes into one engine boundary
-BUILD_PR_LEVEL_01_SCENE_SCENES_BOUNDARY_NORMALIZATION
+Clean up leftover engine/vector residue after vector boundary moves
+BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP

docs/dev/reports/change_summary.txt

@@ -1,3 +1,3 @@
-- Added PR to collapse scene/scenes ambiguity into one engine boundary
-- Recommends keeping scene as the engine domain and moving content-owned scenes to their owning layer
-- Keeps section-1 normalization surgical and truth-based
+- 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

docs/dev/reports/validation_checklist.txt

@@ -1,7 +1,7 @@
-- only one top-level engine scene boundary remains
-- scene no longer competes with scenes as a parallel engine concept
-- imports/exports normalized and valid
-- game/sample scene content ownership is clearer
+- 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_SCENE_SCENES_BOUNDARY_NORMALIZATION.zip
+  <project folder>/tmp/BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP.zip

docs/pr/BUILD_PR_LEVEL_01_ENGINE_VECTOR_RESIDUE_CLEANUP.md

@@ -0,0 +1,63 @@
+# 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
+
+## 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

games/Asteroids/entities/Asteroid.js

@@ -5,7 +5,7 @@ David Quesenberry
 Asteroid.js
 */
 import { TAU, randomRange, wrap } from '../utils/math.js';
-import { transformPoints } from '/src/engine/vector/index.js';
+import { transformPoints } from '/src/engine/rendering/index.js';
 
 const BASE_VECTOR_MAP = [
   { x: 10, y: 40 },

games/Asteroids/entities/Ship.js

@@ -5,7 +5,7 @@ David Quesenberry
 Ship.js
 */
 import { wrap } from '../utils/math.js';
-import { transformPoints } from '/src/engine/vector/index.js';
+import { transformPoints } from '/src/engine/rendering/index.js';
 
 const SMALL_VECTOR_MAP = [
   { x: 14, y: 0 },

games/Asteroids/entities/Ufo.js

@@ -6,7 +6,7 @@ Ufo.js
 */
 import Bullet from './Bullet.js';
 import { distance } from '/src/engine/utils/index.js';
-import { transformPoints } from '/src/engine/vector/index.js';
+import { transformPoints } from '/src/engine/rendering/index.js';
 import { randomRange } from '../utils/math.js';
 
 const UFO_PROFILES = {

samples/metadata/samples.index.metadata.json

@@ -3862,8 +3862,8 @@
         "engine/scene/index/Scene",
         "engine/theme/index/Theme",
         "engine/theme/index/ThemeTokens",
-        "engine/vector/index/drawVectorShape",
-        "engine/vector/index/transformPoints"
+        "engine/rendering/index/drawVectorShape",
+        "engine/rendering/index/transformPoints"
       ],
       "thumbnail": "/samples/phase-09/0901/assets/images/preview.svg",
       "preview": "/samples/phase-09/0901/assets/images/preview.svg"
@@ -3890,8 +3890,8 @@
         "engine/scene/index/Scene",
         "engine/theme/index/Theme",
         "engine/theme/index/ThemeTokens",
-        "engine/vector/index/drawVectorShape",
-        "engine/vector/index/transformPoints"
+        "engine/rendering/index/drawVectorShape",
+        "engine/rendering/index/transformPoints"
       ],
       "thumbnail": "/samples/phase-09/0902/assets/images/preview.svg",
       "preview": "/samples/phase-09/0902/assets/images/preview.svg"
@@ -3917,7 +3917,7 @@
         "engine/scene/index/Scene",
         "engine/theme/index/Theme",
         "engine/theme/index/ThemeTokens",
-        "engine/vector/index/drawVectorShape"
+        "engine/rendering/index/drawVectorShape"
       ],
       "thumbnail": "/samples/phase-09/0903/assets/images/preview.svg",
       "preview": "/samples/phase-09/0903/assets/images/preview.svg"
@@ -4008,8 +4008,8 @@
         "engine/scene/index/Scene",
         "engine/theme/index/Theme",
         "engine/theme/index/ThemeTokens",
-        "engine/vector/index/drawVectorShape",
-        "engine/vector/index/transformPoints"
+        "engine/rendering/index/drawVectorShape",
+        "engine/rendering/index/transformPoints"
       ],
       "thumbnail": "/samples/phase-09/0906/assets/images/preview.svg",
       "preview": "/samples/phase-09/0906/assets/images/preview.svg"

samples/metadata/samples.shared.boundaries.report.json

@@ -521,7 +521,7 @@
         "boundaryStatus": "allowed-public"
       },
       {
-        "specifier": "/src/engine/vector/index.js",
+        "specifier": "/src/engine/rendering/index.js",
         "importCount": 4,
         "importerExamples": [
           "phase-09/0901/VectorRenderingSystemScene.js",