Clarify Toolbox modes and targeted validation governance - PR_26155_003-toolbox-targeted-validation-and-project-workspace

Author: ToolboxAid

docs_build/dev/PROJECT_INSTRUCTIONS.md

@@ -1477,3 +1477,55 @@ Rules:
 - If existing Theme V2 cannot support a required Toolbox pattern, document the gap before adding an approved reusable Theme V2 pattern.
 - Reusable Theme V2 patterns must live under `assets/theme-v2/css/` and must not reintroduce legacy/V1 styling.
 - Wireframe-only Toolbox rebuilds must not add implementation logic.
+
+## Targeted Independent Validation Guidance
+
+Tool, page, and `src/` changes must use the narrowest affected validation lane that proves the changed behavior.
+
+Rules:
+- Small scoped tool changes validate the affected tool/page and directly touched shared dependencies only.
+- Small scoped page changes validate the affected page and directly touched shared page dependencies only.
+- Small scoped `src/` changes validate the affected module and directly dependent runtime/tool surface only.
+- Do not trigger broad validation for small scoped changes unless shared runtime behavior, cross-tool launch behavior, engine behavior, or public navigation behavior changed.
+- Do not run full samples validation unless samples are explicitly in scope or the changed shared runtime behavior directly affects samples.
+- Reports must identify lanes run, broad lanes skipped, and the reason broad validation was not required.
+
+## Tool Registry Planning Governance
+
+Runtime database behavior for tools must not be introduced until tool planning metadata has a declared registry or data source.
+
+The declared tool registry/data source must own:
+- tool metadata
+- category
+- route
+- status
+- readiness
+- requirements
+- progress checklist
+- deferred flags
+
+Rules:
+- Toolbox wireframes may show planning metadata as static text only.
+- Future runtime database work must consume the declared data source rather than duplicating tool metadata in page-local code.
+- Tool status, readiness, requirements, progress checklist, and deferred flags must be traceable to the declared registry/data source before database-backed behavior ships.
+
+## Game Debug Configuration Governance
+
+Game debug settings may exist for creator testing and development diagnostics.
+
+Rules:
+- Debug settings must be visible and configurable for creators/testers.
+- Debug settings must not be hidden defaults.
+- Debug settings must be disabled, stripped, or rejected when a game is promoted to playable/public release.
+- Release validation must fail visibly when public/playable promotion includes enabled debug-only settings.
+- Reports for affected game release or publish flows must state whether debug settings were present and how public release gating handled them.
+
+## Project Workspace Naming Guidance
+
+Use `Project Workspace` for user-facing copy and new test/report prose.
+
+Rules:
+- Do not introduce new user-facing `Workspace V2` wording.
+- Do not introduce new report/test prose that describes the current user-facing experience as `Workspace V2`.
+- Existing package scripts such as `npm run test:workspace-v2`, legacy lane identifiers, and historical test suite names may remain until renamed by a dedicated cleanup PR.
+- When a report invokes a legacy command name such as `npm run test:workspace-v2`, the report must explain that the command name is legacy and the user-facing product language is `Project Workspace`.

docs_build/dev/codex_commands.md

@@ -92,7 +92,7 @@ Changes:
 - Added Build Path view rendering as visual path groups using existing tool tiles.
 - Kept Arcade out of Toolbox content.
 - Kept forbidden `Studio` wording out of Toolbox dynamic tool labels except brand usage.
-- Updated active validation scripts and Workspace V2 Playwright assertions for the corrected view-mode contract.
+- Updated active validation scripts and Project Workspace Playwright assertions for the corrected view-mode contract.
 - Added validation and manual test notes.
 - Generated local review artifacts.
 - Created the repo-structured delta ZIP at `tmp/PR_26154_053-toolbox-wireframe-rebuild-rule_view-mode-correction_delta.zip`.
@@ -110,3 +110,34 @@ Required reports:
 - `docs_build/dev/reports/codex_changed_files.txt`
 - `docs_build/dev/reports/codex_review.diff`
 - `docs_build/dev/reports/toolbox_wireframe_rebuild_rule_report.md`
+
+## PR_26155_001
+
+Changes:
+- Read `docs_build/dev/PROJECT_INSTRUCTIONS.md`.
+- Added targeted independent validation guidance to `docs_build/dev/PROJECT_INSTRUCTIONS.md`.
+- Added tools database planning governance requiring tool metadata, category, route, status, readiness, requirements, progress checklist, and deferred flags to come from a declared registry/data source before runtime DB behavior.
+- Added game debug configuration governance for visible creator testing settings and public/playable release rejection or disablement.
+- Added Project Workspace naming guidance; `npm run test:workspace-v2` is treated as legacy test-command naming only.
+- Reviewed `toolbox/index.html` and confirmed Order, Group, Progress, and Build Path remain page modes for the same Toolbox surface.
+- Confirmed Progress and Build Path are not represented as standalone tool tiles or extra accordions.
+- Kept Arcade out of Toolbox content.
+- Kept forbidden `Studio` wording out of Toolbox dynamic tool labels except brand usage.
+- Added targeted validation notes, skipped broad-lane rationale, Project Workspace naming note, and manual test notes.
+- Generated local review artifacts.
+- Created the repo-structured delta ZIP at `tmp/PR_26155_001-project-workspace-governance-toolbox-modes_delta.zip`.
+
+Validation:
+- `node scripts/validate-active-tools-surface.mjs`
+- `node scripts/validate-tool-registry.mjs`
+- Toolbox source checks for view controls, Progress readiness labels, Build Path path groups, absence of extra Progress/Build Path wireframe sections, Arcade absence, forbidden `Studio` label absence, and no inline CSS/JS/event handlers.
+- `npm run test:workspace-v2` (legacy command name for the Project Workspace test lane)
+- `git diff --check`
+- `node --check` for changed JS/MJS files.
+- No new CSS added.
+- Full samples smoke test skipped because samples are not in scope and no shared sample runtime behavior changed.
+
+Required reports:
+- `docs_build/dev/reports/codex_changed_files.txt`
+- `docs_build/dev/reports/codex_review.diff`
+- `docs_build/dev/reports/project_workspace_governance_toolbox_modes_report.md`

docs_build/dev/commit_comment.txt

@@ -1 +1 @@
-Correct Toolbox wireframe view modes on shared tool surface - PR_26154_053-toolbox-wireframe-rebuild-rule
+Add Project Workspace governance and confirm Toolbox page modes - PR_26155_001-project-workspace-governance-toolbox-modes

docs_build/dev/reports/dependency_gating_report.md

@@ -1,6 +1,6 @@
 # Dependency Gating Report
 
-Generated: 2026-06-04T03:43:28.722Z
+Generated: 2026-06-04T03:52:34.901Z
 Status: PASS
 
 ## Gate Order

docs_build/dev/reports/dependency_hydration_reuse_report.md

@@ -1,22 +1,22 @@
 # Dependency Hydration Reuse Report
 
-Generated: 2026-06-04T03:43:28.722Z
+Generated: 2026-06-04T03:52:34.901Z
 Status: PASS
 
 ## Summary
 
-Reused dependency hydration: 0
-Invalidated dependency hydration: 1
+Reused dependency hydration: 1
+Invalidated dependency hydration: 0
 Generated dependency hydration: 0
-Prevented dependency graph hydration: 0
-Prevented helper resolution passes: 0
+Prevented dependency graph hydration: 1
+Prevented helper resolution passes: 4
 Prevented fixture ownership traversal: 0
 
 ## Hydration Decisions
 
 | Lane | Status | Helpers | Fixtures | Imports | Dependency Hydration Hash | Reason |
 | --- | --- | --- | --- | --- | --- | --- |
-| workspace-contract | INVALIDATED | tests/helpers/playwrightRepoServer.mjs; tests/helpers/playwrightStorageIsolation.mjs; tests/helpers/playwrightV8CoverageReporter.mjs; tests/helpers/workspaceV2CoverageReporter.mjs | none | tests/helpers/playwrightRepoServer.mjs; tests/helpers/playwrightStorageIsolation.mjs; tests/helpers/playwrightV8CoverageReporter.mjs; tests/helpers/workspaceV2CoverageReporter.mjs | 0ff8fc92c789456d | Dependency hydration was refreshed after warm-start invalidation. |
+| workspace-contract | REUSED | tests/helpers/playwrightRepoServer.mjs; tests/helpers/playwrightStorageIsolation.mjs; tests/helpers/playwrightV8CoverageReporter.mjs; tests/helpers/workspaceV2CoverageReporter.mjs | none | tests/helpers/playwrightRepoServer.mjs; tests/helpers/playwrightStorageIsolation.mjs; tests/helpers/playwrightV8CoverageReporter.mjs; tests/helpers/workspaceV2CoverageReporter.mjs | 0ff8fc92c789456d | Dependency hydration reused from validated warm-start state. |
 
 ## Safeguards
 

docs_build/dev/reports/execution_graph_reuse_report.md

@@ -1,22 +1,22 @@
 # Execution Graph Reuse Report
 
-Generated: 2026-06-04T03:43:28.723Z
+Generated: 2026-06-04T03:52:34.902Z
 Status: PASS
 
 ## Summary
 
-Reused execution graphs: 0
-Prevented graph rebuilds: 0
-Prevented redundant dependency traversal: 0
-Prevented fixture/helper graph assembly: 0
-Prevented manifest traversal: 0
-Prevented targeted scheduling work: 0
+Reused execution graphs: 1
+Prevented graph rebuilds: 1
+Prevented redundant dependency traversal: 1
+Prevented fixture/helper graph assembly: 4
+Prevented manifest traversal: 1
+Prevented targeted scheduling work: 1
 
 ## Execution Graph Decisions
 
 | Lane | Status | Snapshot Status | Execution Graph Hash | Reason |
 | --- | --- | --- | --- | --- |
-| workspace-contract | INVALIDATED | INVALIDATED | d71814dbea6e33fd | Lane snapshot is part of the selected targeted execution graph. |
+| workspace-contract | REUSED | REUSED | d71814dbea6e33fd | Lane snapshot is part of the selected targeted execution graph. |
 
 ## Safeguards
 

docs_build/dev/reports/failure_fingerprint_report.md

@@ -1,6 +1,6 @@
 # Failure Fingerprint Report
 
-Generated: 2026-06-04T03:43:38.895Z
+Generated: 2026-06-04T03:52:43.267Z
 Status: PASS
 
 ## Summary

docs_build/dev/reports/filesystem_scan_reduction_report.md

@@ -1,6 +1,6 @@
 # Filesystem Scan Reduction Report
 
-Generated: 2026-06-04T03:43:28.704Z
+Generated: 2026-06-04T03:52:34.884Z
 Status: PASS
 
 ## Scan Enforcement

docs_build/dev/reports/incremental_validation_report.md

@@ -1,24 +1,24 @@
 # Incremental Validation Report
 
-Generated: 2026-06-04T03:43:28.723Z
+Generated: 2026-06-04T03:52:34.903Z
 Status: PASS
 
 ## Reuse Summary
 
-Reused manifests: 0
-Invalidated manifests: 1
+Reused manifests: 1
+Invalidated manifests: 0
 Generated manifests: 0
 Skipped manifests: 0
-Prevented lane regeneration: 0
-Prevented discovery scans: 0
-Prevented helper resolution passes: 0
+Prevented lane regeneration: 1
+Prevented discovery scans: 1
+Prevented helper resolution passes: 4
 Prevented fixture resolution passes: 0
 
 ## Incremental Decisions
 
 | Lane | Decision | Invalidated By | Runtime Savings Observation |
 | --- | --- | --- | --- |
-| workspace-contract | INVALIDATED | Persistent manifest input hash changed for workspace-contract.; Persistent manifest hash changed for workspace-contract. | Manifest was regenerated or skipped; no reuse savings for this lane. |
+| workspace-contract | REUSED | unchanged inputs | Reused 1 test input(s), 4 helper(s), and 0 fixture(s). |
 
 ## Invalidation Rules
 

docs_build/dev/reports/lane_compilation_report.md

@@ -1,6 +1,6 @@
 # Lane Compilation Report
 
-Generated: 2026-06-04T03:43:28.722Z
+Generated: 2026-06-04T03:52:34.901Z
 Status: PASS
 
 ## Lane Graph