build(level-16): execute ci, debug, hot reload, and distribution expansion suite

Author: ToolboxAid

.github/workflows/platform-validation.yml

@@ -0,0 +1,23 @@
+name: Platform Validation
+
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+      - master
+
+jobs:
+  platform-validation:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+
+      - name: Run Platform Validation Suite
+        run: node ./scripts/run-platform-validation-suite.mjs

docs/dev/CODEX_COMMANDS.md

@@ -2,26 +2,20 @@ MODEL: GPT-5.4
 REASONING: high
 
 COMMAND:
-Execute this atomic Level 15 package in order.
+Execute this Level 16 expansion suite in order, treating each PLAN as the governing architecture contract for its corresponding BUILD/APPLY.
 
-Step 1:
-Treat docs/pr/PLAN_PR_PLATFORM_VALIDATION_SUITE.md as the governing architecture contract.
+Order:
+1. PLAN/BUILD/APPLY_PR_CI_VALIDATION_PIPELINE
+2. PLAN/BUILD/APPLY_PR_DEBUG_VISUALIZATION_LAYER
+3. PLAN/BUILD/APPLY_PR_HOT_RELOAD_SYSTEM
+4. PLAN/BUILD/APPLY_PR_MULTI_TARGET_EXPORT
 
-Step 2:
-Create BUILD_PR_PLATFORM_VALIDATION_SUITE.
-
-BUILD requirements:
-- Implement a repeatable platform validation suite for accepted system flows
-- Cover golden-path, failure-path, remediation, packaging, runtime, streaming, plugin, and versioning scenarios
-- Produce stable, readable validation reports
-- Preserve accepted platform boundaries
+Global requirements:
+- Preserve the accepted Level 15 self-validating platform baseline
 - Do not modify engine core APIs
+- Maintain deterministic behavior and readable reporting wherever applicable
+- Keep validation, packaging, and runtime boundaries authoritative
+- Package each completed slice to the repo tmp directory using the established naming conventions
 
-Step 3:
-Validate BUILD against docs/pr/BUILD_PR_PLATFORM_VALIDATION_SUITE.md.
-
-Step 4:
-Treat docs/pr/APPLY_PR_PLATFORM_VALIDATION_SUITE.md as the acceptance boundary and package results.
-
-Package:
-HTML-JavaScript-Gaming/tmp/LEVEL_15_PLATFORM_VALIDATION_SUITE_delta.zip
+Master package:
+HTML-JavaScript-Gaming/tmp/LEVEL_16_EXPANSION_SUITE_ATOMIC_PACKAGE_delta.zip

docs/dev/COMMIT_COMMENT.txt

@@ -1 +1 @@
-build(validation-suite): add platform validation suite for full pipeline coverage
+build(level-16): execute ci, debug, hot reload, and distribution expansion suite

docs/dev/change_summary.txt

@@ -1,3 +1 @@
-Single atomic Level 15 package containing PLAN, BUILD, and APPLY documentation for a
-platform validation suite. This bundle is docs-first and Codex-ready, with implementation
-ownership delegated to Codex.
+Combined Level 16 suite containing PLAN/BUILD/APPLY docs for CI, debug visualization, hot reload, and multi-target export.

docs/dev/file_tree.txt

@@ -1,6 +1,15 @@
-docs/pr/PLAN_PR_PLATFORM_VALIDATION_SUITE.md
-docs/pr/BUILD_PR_PLATFORM_VALIDATION_SUITE.md
-docs/pr/APPLY_PR_PLATFORM_VALIDATION_SUITE.md
+docs/pr/PLAN_PR_CI_VALIDATION_PIPELINE.md
+docs/pr/BUILD_PR_CI_VALIDATION_PIPELINE.md
+docs/pr/APPLY_PR_CI_VALIDATION_PIPELINE.md
+docs/pr/PLAN_PR_DEBUG_VISUALIZATION_LAYER.md
+docs/pr/BUILD_PR_DEBUG_VISUALIZATION_LAYER.md
+docs/pr/APPLY_PR_DEBUG_VISUALIZATION_LAYER.md
+docs/pr/PLAN_PR_HOT_RELOAD_SYSTEM.md
+docs/pr/BUILD_PR_HOT_RELOAD_SYSTEM.md
+docs/pr/APPLY_PR_HOT_RELOAD_SYSTEM.md
+docs/pr/PLAN_PR_MULTI_TARGET_EXPORT.md
+docs/pr/BUILD_PR_MULTI_TARGET_EXPORT.md
+docs/pr/APPLY_PR_MULTI_TARGET_EXPORT.md
 docs/dev/codex_commands.md
 docs/dev/commit_comment.txt
 docs/dev/change_summary.txt

docs/dev/reports/ci_validation_pipeline_validation.txt

@@ -0,0 +1,21 @@
+BUILD_PR_CI_VALIDATION_PIPELINE validation
+
+Files:
+- tools/shared/ciValidationPipeline.js
+- scripts/run-platform-validation-suite.mjs
+- .github/workflows/platform-validation.yml
+- tests/tools/CiValidationPipeline.test.mjs
+- tests/run-tests.mjs
+
+Checks passed:
+- node --check tools/shared/ciValidationPipeline.js
+- node --check scripts/run-platform-validation-suite.mjs
+- node --check tests/tools/CiValidationPipeline.test.mjs
+- node ./scripts/run-node-tests.mjs
+
+Behavior confirmed:
+- CI consumes the platform validation suite as an authoritative gate
+- CI status blocks invalid changes deterministically
+- artifact/report entries are stable and readable
+- branch and trigger context are reported consistently
+- no engine core API changes

docs/dev/reports/debug_visualization_layer_validation.txt

@@ -0,0 +1,27 @@
+BUILD_PR_DEBUG_VISUALIZATION_LAYER validation
+
+Files:
+- tools/shared/debugVisualizationLayer.js
+- tests/tools/DebugVisualizationLayer.test.mjs
+- tests/run-tests.mjs
+- tools/Sprite Editor/index.html
+- tools/Sprite Editor/modules/spriteEditorApp.js
+- tools/Tile Map Editor/index.html
+- tools/Tile Map Editor/main.js
+- tools/Parallax Editor/index.html
+- tools/Parallax Editor/main.js
+
+Checks passed:
+- node --check tools/shared/debugVisualizationLayer.js
+- node --check tests/tools/DebugVisualizationLayer.test.mjs
+- node --check tools/Sprite Editor/modules/spriteEditorApp.js
+- node --check tools/Tile Map Editor/main.js
+- node --check tools/Parallax Editor/main.js
+- node ./scripts/run-node-tests.mjs
+
+Behavior confirmed:
+- dependency graph, validation, remediation, packaging, and runtime state are inspectable in stable debug views
+- debug views are deterministic and readable
+- remediation navigation remains intact
+- accepted Level 15 platform boundaries remain authoritative
+- no engine core API changes

docs/dev/reports/hot_reload_system_validation.txt

@@ -0,0 +1,18 @@
+BUILD_PR_HOT_RELOAD_SYSTEM validation
+
+Files:
+- tools/shared/hotReloadSystem.js
+- tests/tools/HotReloadSystem.test.mjs
+- tests/run-tests.mjs
+
+Checks passed:
+- node --check tools/shared/hotReloadSystem.js
+- node --check tests/tools/HotReloadSystem.test.mjs
+- node ./scripts/run-node-tests.mjs
+
+Behavior confirmed:
+- valid authoring state can trigger controlled runtime reload
+- unchanged packaged state resolves to deterministic reload modes
+- invalid reload attempts are blocked at validation boundaries
+- runtime reload remains subordinate to strict packaging/runtime contracts
+- no engine core API changes

docs/dev/reports/multi_target_export_validation.txt

@@ -0,0 +1,18 @@
+BUILD_PR_MULTI_TARGET_EXPORT validation
+
+Files:
+- tools/shared/multiTargetExport.js
+- tests/tools/MultiTargetExport.test.mjs
+- tests/run-tests.mjs
+
+Checks passed:
+- node --check tools/shared/multiTargetExport.js
+- node --check tests/tools/MultiTargetExport.test.mjs
+- node ./scripts/run-node-tests.mjs
+
+Behavior confirmed:
+- valid packaged projects can emit deterministic web, desktop, and archive export plans
+- target ordering and output layout metadata are stable
+- validation and packaging remain authoritative export gates
+- export reports are readable and deterministic
+- no engine core API changes

docs/dev/validation_checklist.txt

@@ -1,6 +1,5 @@
-- PLAN, BUILD, and APPLY docs are all present
-- codex_commands.md and commit_comment.txt are under docs/dev
-- Full-flow platform validation coverage is explicit
-- Plugin, versioning, and streaming are included in scope
+- All four Level 16 capability groups are present
+- Each capability has PLAN, BUILD, and APPLY docs
+- docs/dev contains codex_commands.md and commit_comment.txt
+- Level 15 self-validating platform remains the prerequisite authority
 - No engine core API changes are authorized
-- APPLY remains docs-only acceptance boundary