Link Tools Progress and add tool previous next navigation - PR_26155_096-099-tool-navigation

ToolboxAid · ToolboxAid · commit 77aa206b3deb · 2026-06-04T21:24:05.000-04:00
diff --git a/assets/theme-v2/images/badges/ChatGPT Installer.exe b/assets/theme-v2/images/badges/ChatGPT Installer.exe
diff --git a/assets/theme-v2/images/badges/Microsoft.Services.Store.winmd b/assets/theme-v2/images/badges/Microsoft.Services.Store.winmd
diff --git a/docs_build/dev/codex_commands.md b/docs_build/dev/codex_commands.md
@@ -80,6 +80,37 @@ Required reports:
 - `docs_build/dev/reports/theme_css_entrypoint_closeout_report.md`
 - `docs_build/dev/reports/migration_final_status_report.md`
 
+## PR_26155_096-099
+
+Changes:
+- Read `docs_build/dev/PROJECT_INSTRUCTIONS.md`.
+- Added registry route/navigation helpers in `toolbox/toolRegistry.js`.
+- Made Admin Tools Progress tool names link through shared registry route data.
+- Added disabled planned rendering for route-less tools.
+- Added Previous Tool and Next Tool controls to shared Tool Display Mode.
+- Added registry-driven multi-path fallback from Game Configuration to Toolbox Group view.
+- Added Toolbox URL state support for `view=group&group=<slug>`.
+- Added the targeted `tool-navigation` Playwright lane.
+
+Validation:
+- `node --check toolbox/toolRegistry.js`
+- `node --check admin/tools-progress.js`
+- `node --check assets/theme-v2/js/tool-display-mode.js`
+- `node --check toolbox/tools-page-accordions.js`
+- `node --check tests/playwright/tools/ToolNavigationPrevNext.spec.mjs`
+- `npm run test:lane:tools-progress`
+- `npm run test:lane:tool-navigation`
+- `npm run test:workspace-v2`
+- `git diff --check`
+
+Required reports:
+- `docs_build/dev/reports/tools-progress-tool-links.md`
+- `docs_build/dev/reports/tool-display-mode-prev-next.md`
+- `docs_build/dev/reports/tool-display-mode-multi-path-fallback.md`
+- `docs_build/dev/reports/tool-navigation-targeted-msj-tests.md`
+- `docs_build/dev/reports/codex_review.diff`
+- `docs_build/dev/reports/codex_changed_files.txt`
+
 ## PR_26154_053
 
 Changes:
diff --git a/docs_build/dev/commit_comment.txt b/docs_build/dev/commit_comment.txt
@@ -1 +1 @@
-Hydrate Admin Tools Progress and restore Toolbox group colors - PR_26155_092-095-tools-progress-group-colors
+Add registry-driven tool navigation links and Tool Display previous/next controls - PR_26155_096-099-tool-navigation
diff --git a/docs_build/dev/reports/tool-display-mode-multi-path-fallback.md b/docs_build/dev/reports/tool-display-mode-multi-path-fallback.md
@@ -0,0 +1,46 @@
+# Tool Display Mode Multi Path Fallback
+
+PR: PR_26155_098-tool-display-mode-multi-path-fallback
+
+## Summary
+
+- Game Configuration now has registry navigation metadata for multiple valid next choices.
+- Multiple next choices route to Toolbox Group view instead of inventing a per-page target.
+- The fallback route is registry-driven:
+  - `toolbox/index.html?view=group&group=design`
+- The current `role` query parameter is preserved when the Tool Display Mode link is created.
+- `toolbox/tools-page-accordions.js` now reads `view=group&group=<slug>` on initial load.
+- When a group slug is provided, only the requested group accordion opens.
+
+## Files
+
+- `toolbox/toolRegistry.js`
+- `assets/theme-v2/js/tool-display-mode.js`
+- `toolbox/tools-page-accordions.js`
+- `tests/playwright/tools/ToolNavigationPrevNext.spec.mjs`
+
+## Validation
+
+- PASS: `node --check toolbox/toolRegistry.js`
+- PASS: `node --check toolbox/tools-page-accordions.js`
+- PASS: `npm run test:lane:tool-navigation`
+- PASS: `git diff --check`
+
+## Manual Test Notes
+
+1. Open `toolbox/game-configuration/index.html?role=admin`.
+2. Confirm Next Tool reads `Next Tool: Design Tools`.
+3. Confirm the link target is `toolbox/index.html?view=group&group=design&role=admin`.
+4. Click the link.
+5. Confirm Toolbox opens in Group view.
+6. Confirm only the Design group accordion is expanded.
+
+## Validation Scope
+
+Impacted lane:
+- `tool-navigation`
+
+Skipped lanes:
+- Build Path lane was skipped because the workflow table and project-specific Build Path behavior were not changed.
+- Game Configuration runtime lane was skipped because no configuration repository, handoff, validation, or output behavior changed.
+- Full samples smoke test was skipped because samples are out of scope.
diff --git a/docs_build/dev/reports/tool-display-mode-prev-next.md b/docs_build/dev/reports/tool-display-mode-prev-next.md
@@ -0,0 +1,56 @@
+# Tool Display Mode Previous Next
+
+PR: PR_26155_097-tool-display-mode-prev-next
+
+## Summary
+
+- `assets/theme-v2/js/tool-display-mode.js` now adds Previous Tool and Next Tool controls inside the shared Tool Display Mode body.
+- Controls are generated from `getToolNavigationTargets(toolSlug)` in `toolbox/toolRegistry.js`.
+- Controls follow the registry build order used by Admin Tools Progress.
+- Disabled controls render as disabled buttons when no previous or next target exists.
+- Role query parameters are preserved on generated navigation links.
+
+## Examples Verified
+
+- Game Design:
+  - Previous Tool: Project Workspace
+  - Next Tool: Game Configuration
+- Project Workspace:
+  - Previous Tool: AI Assistant
+  - Next Tool: Game Design
+
+## Files
+
+- `assets/theme-v2/js/tool-display-mode.js`
+- `toolbox/toolRegistry.js`
+- `tests/playwright/tools/ToolNavigationPrevNext.spec.mjs`
+
+## Validation
+
+- PASS: `node --check assets/theme-v2/js/tool-display-mode.js`
+- PASS: `npm run test:lane:tool-navigation`
+- PASS: `npm run test:workspace-v2`
+- PASS: `git diff --check`
+
+`npm run test:workspace-v2` is a legacy command name. User-facing naming remains Project Workspace.
+
+## Manual Test Notes
+
+1. Open `toolbox/game-design/index.html?role=user`.
+2. Confirm Tool Display Mode shows Previous Tool: Project Workspace.
+3. Confirm Tool Display Mode shows Next Tool: Game Configuration.
+4. Confirm both links preserve `role=user`.
+5. Open `toolbox/project-workspace/index.html?role=user`.
+6. Confirm Previous Tool and Next Tool render from registry build order.
+
+## Validation Scope
+
+Impacted lane:
+- `tool-navigation`
+
+Additional shared navigation gate:
+- `workspace-contract` through the legacy `npm run test:workspace-v2` command.
+
+Skipped lanes:
+- Game Design, Game Configuration, and Project Workspace runtime lanes were skipped because page-specific runtime behavior was not changed.
+- Full samples smoke test was skipped because no sample JSON or sample loader behavior changed.
diff --git a/docs_build/dev/reports/tool-navigation-targeted-msj-tests.md b/docs_build/dev/reports/tool-navigation-targeted-msj-tests.md
@@ -0,0 +1,47 @@
+# Tool Navigation Targeted MSJ Tests
+
+PR: PR_26155_099-tool-navigation-targeted-msj-tests
+
+## Summary
+
+- Added `npm run test:lane:tool-navigation`.
+- Registered the `tool-navigation` lane in `scripts/run-targeted-test-lanes.mjs`.
+- Added `tests/playwright/tools/ToolNavigationPrevNext.spec.mjs`.
+- The lane covers Admin Tools Progress links, route-less planned rendering, Tool Display Mode previous/next controls, Game Design previous/next, multi-path fallback, role preservation, direct Group view routing, and console/page errors.
+
+## Validation Results
+
+- PASS: `node --check tests/playwright/tools/ToolNavigationPrevNext.spec.mjs`
+- PASS: `npm run test:lane:tools-progress`
+- PASS: `npm run test:lane:tool-navigation`
+  - 5 tests passed.
+- PASS: `npm run test:workspace-v2`
+  - Legacy command name; user-facing naming remains Project Workspace.
+- PASS: `git diff --check`
+
+## Concurrent Run Note
+
+The first attempt ran `tools-progress` and `tool-navigation` concurrently. Tools Progress passed, but Tool Navigation hit a Playwright artifact race:
+
+`ENOENT: no such file or directory ... .playwright-artifacts-0/...zip`
+
+The same `tool-navigation` lane was rerun by itself and passed cleanly with 5/5 tests.
+
+## Targeted Checks Covered
+
+- `admin/tools-progress.html`
+- `toolbox/project-workspace/index.html`
+- `toolbox/game-design/index.html`
+- `toolbox/game-configuration/index.html`
+- `toolbox/index.html?view=group&group=design`
+
+## Skipped Lanes
+
+- `game-design`: skipped because Game Design save/update/validation behavior was unchanged.
+- `game-configuration`: skipped because configuration repository, handoff, validation, and output behavior were unchanged.
+- `project-workspace`: skipped because project repository and project lifecycle behavior were unchanged.
+- `build-path`: skipped because Project Build Path table behavior was not changed.
+- `engine-src`: skipped because no engine or shared `src/` runtime code changed.
+- `samples`: skipped because samples are out of scope and no sample assets or manifests changed.
+
+Full suite is required only when shared runtime, shared parser, shared DB, shared Theme V2, or cross-tool integration behavior changes beyond the targeted navigation surfaces.
diff --git a/docs_build/dev/reports/tools-progress-tool-links.md b/docs_build/dev/reports/tools-progress-tool-links.md
@@ -0,0 +1,50 @@
+# Tools Progress Tool Links
+
+PR: PR_26155_096-tools-progress-tool-links
+
+## Summary
+
+- `admin/tools-progress.html` remains hydrated by `admin/tools-progress.js`.
+- Tool names now render as links when shared registry route data provides an `entryPoint`.
+- Route generation is centralized in `toolbox/toolRegistry.js` through `getToolRoute(tool)`.
+- Route-less tools render as text with a `Planned - Route pending` pill instead of a broken link.
+- No routes were hardcoded in `admin/tools-progress.js`.
+
+## Files
+
+- `toolbox/toolRegistry.js`
+- `admin/tools-progress.js`
+- `tests/playwright/tools/ToolNavigationPrevNext.spec.mjs`
+
+## Evidence
+
+- Admin Tools Progress rows still hydrate from `getActiveToolRegistry()`.
+- The new test verifies every active registry tool with route data renders a matching link.
+- The route-less rendering path is covered with a route-less fixture through the exported row renderer.
+
+## Validation
+
+- PASS: `npm run test:lane:tools-progress`
+- PASS: `npm run test:lane:tool-navigation`
+- PASS: `npm run test:workspace-v2`
+- PASS: `git diff --check`
+
+`npm run test:workspace-v2` is a legacy command name. User-facing naming remains Project Workspace.
+
+## Manual Test Notes
+
+1. Open `admin/tools-progress.html`.
+2. Confirm each routed tool name is clickable.
+3. Confirm the links use `toolbox/<tool>/index.html` routes from the registry.
+4. Confirm route-less tools would show text with `Planned - Route pending` rather than a broken link.
+
+## Validation Scope
+
+Impacted lanes:
+- `tools-progress`
+- `tool-navigation`
+- `workspace-contract` through the legacy `npm run test:workspace-v2` command because shared route/navigation wiring changed.
+
+Skipped lanes:
+- `game-design`, `game-configuration`, and `project-workspace` runtime lanes were skipped because no mock repository, save/update, validation, or project data behavior changed.
+- `engine-src`, `samples`, and archive lanes were skipped because this PR does not touch engine runtime, sample JSON, or archived reference material.

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-Hydrate Admin Tools Progress and restore Toolbox group colors - PR_26155_092-095-tools-progress-group-colors`
	`1`	`+Add registry-driven tool navigation links and Tool Display previous/next controls - PR_26155_096-099-tool-navigation`