PR_26155_100-102-tool-display-mode-nav, oops, jumped the gun.

Author: ToolboxAid

docs_build/dev/codex_commands.md

@@ -111,6 +111,34 @@ Required reports:
 - `docs_build/dev/reports/codex_review.diff`
 - `docs_build/dev/reports/codex_changed_files.txt`
 
+## PR_26155_100-102
+
+Changes:
+- Read `docs_build/dev/PROJECT_INSTRUCTIONS.md`.
+- Updated shared Tool Display Mode body layout to identity row plus navigation row.
+- Kept character image and tool name on the first row.
+- Kept Previous/Next navigation on the second row.
+- Changed missing previous/next targets from disabled buttons to disabled text.
+- Kept enabled Previous/Next controls as registry-driven links.
+- Added the targeted `tool-display-mode` Playwright lane.
+
+Validation:
+- `node --check assets/theme-v2/js/tool-display-mode.js`
+- `node --check tests/playwright/tools/ToolDisplayModeNavigation.spec.mjs`
+- `node --check tests/playwright/tools/ToolNavigationPrevNext.spec.mjs`
+- `node --check scripts/run-targeted-test-lanes.mjs`
+- `npm run test:lane:tool-display-mode`
+- `npm run test:lane:tool-navigation`
+- `npm run test:workspace-v2`
+- `git diff --check`
+
+Required reports:
+- `docs_build/dev/reports/tool-display-mode-nav-layout.md`
+- `docs_build/dev/reports/tool-display-mode-registry-links.md`
+- `docs_build/dev/reports/tool-display-mode-targeted-msj-tests.md`
+- `docs_build/dev/reports/codex_review.diff`
+- `docs_build/dev/reports/codex_changed_files.txt`
+
 ## PR_26154_053
 
 Changes:

docs_build/dev/commit_comment.txt

@@ -1 +1 @@
-Add registry-driven tool navigation links and Tool Display previous/next controls - PR_26155_096-099-tool-navigation
+Refine Tool Display Mode previous next row layout and targeted coverage - PR_26155_100-102-tool-display-mode-nav

docs_build/dev/reports/tool-display-mode-nav-layout.md

@@ -0,0 +1,45 @@
+# Tool Display Mode Navigation Layout
+
+PR: PR_26155_100-tool-display-mode-nav-layout
+
+## Summary
+
+- Updated `assets/theme-v2/js/tool-display-mode.js` so Tool Display Mode body renders two explicit rows.
+- Row 1 uses `tool-display-mode__identity-row content-cluster` with:
+  - character image
+  - tool name
+- Row 2 uses `tool-display-mode__navigation-row content-cluster` with:
+  - Previous link/text
+  - Next link/text
+- Character and tool name are no longer appended as separate stacked body children.
+- Navigation no longer renders buttons inside Tool Display Mode.
+- No CSS was added.
+
+## Layout Markers
+
+- `data-tool-display-mode-row="identity"`
+- `data-tool-display-mode-row="navigation"`
+
+These markers are markup-only validation hooks and do not add styling or behavior.
+
+## Validation
+
+- PASS: `node --check assets/theme-v2/js/tool-display-mode.js`
+- PASS: `node --check tests/playwright/tools/ToolDisplayModeNavigation.spec.mjs`
+- PASS: `npm run test:lane:tool-display-mode`
+- 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 the Tool Display Mode body shows the character and `Game Design` on the first row.
+3. Confirm the second row shows `Previous: Project Workspace` and `Next: Game Configuration`.
+4. Confirm Tool Display Mode navigation uses links/text only and no buttons.
+
+## Theme V2 Gap Findings
+
+No Theme V2 gap was found. Existing `content-cluster`, `btn`, `btn-secondary`, and `pill` classes were sufficient.

docs_build/dev/reports/tool-display-mode-registry-links.md

@@ -0,0 +1,46 @@
+# Tool Display Mode Registry Links
+
+PR: PR_26155_101-tool-display-mode-registry-links
+
+## Summary
+
+- Previous/Next navigation remains registry-driven through `getToolNavigationTargets(toolSlug)`.
+- Tool pages do not hardcode previous or next labels/routes.
+- Enabled previous/next controls render as anchors.
+- Missing previous/next controls render disabled text with a `pill` class instead of a broken link.
+- Multi-path next destinations still route to Toolbox Group view with the target group expanded.
+- Current `role` query parameter is preserved when building navigation links.
+
+## Verified Routes
+
+- Game Design:
+  - Previous: Project Workspace
+  - Next: Game Configuration
+- Project Workspace:
+  - Previous: AI Assistant
+  - Next: Game Design
+- Game Configuration:
+  - Previous: Game Design
+  - Next: Design Tools through `toolbox/index.html?view=group&group=design`
+- AI Assistant:
+  - Previous: disabled text
+  - Next: Project Workspace
+
+## Validation
+
+- PASS: `npm run test:lane:tool-display-mode`
+- PASS: `npm run test:lane:tool-navigation`
+- PASS: `git diff --check`
+
+## Manual Test Notes
+
+1. Open `toolbox/project-workspace/index.html?role=user`.
+2. Confirm Previous/Next routes match registry build order.
+3. Open `toolbox/game-configuration/index.html?role=admin`.
+4. Confirm Next routes to `toolbox/index.html?view=group&group=design&role=admin`.
+5. Click the link and confirm only the Design accordion is expanded.
+
+## Skipped Lane Rationale
+
+- Game Design, Game Configuration, and Project Workspace runtime lanes were skipped because no tool repository, save/update, validation, handoff, or project data behavior changed.
+- Engine and samples lanes were skipped because no engine runtime or sample JSON behavior changed.

docs_build/dev/reports/tool-display-mode-targeted-msj-tests.md

@@ -0,0 +1,54 @@
+# Tool Display Mode Targeted MSJ Tests
+
+PR: PR_26155_102-tool-display-mode-targeted-msj-tests
+
+## Summary
+
+- Added `npm run test:lane:tool-display-mode`.
+- Added `tool-display-mode` lane registration to `scripts/run-targeted-test-lanes.mjs`.
+- Added `tests/playwright/tools/ToolDisplayModeNavigation.spec.mjs`.
+- Updated the existing `ToolNavigationPrevNext` expectations to match the new `Previous:` / `Next:` link labels.
+
+## Targeted Coverage
+
+The new lane validates:
+
+- Game Design row layout:
+  - identity row
+  - navigation row
+  - character and tool name in the first row
+  - Previous/Next anchors in the second row
+- Game Design registry links:
+  - `Previous: Project Workspace`
+  - `Next: Game Configuration`
+- Project Workspace registry links.
+- Game Configuration multi-path fallback to Toolbox Group view.
+- AI Assistant missing previous target as disabled text with no `href`.
+- No console errors, page errors, failed requests, or navigation buttons inside Tool Display Mode navigation.
+
+## Validation Results
+
+- PASS: `npm run test:lane:tool-display-mode`
+  - 4 tests passed.
+- PASS: `npm run test:lane:tool-navigation`
+  - 5 tests passed.
+- PASS: `npm run test:workspace-v2`
+  - 4 tests passed.
+- PASS: `git diff --check`
+
+`npm run test:workspace-v2` is a legacy command name. User-facing naming remains Project Workspace.
+
+## Impacted Lanes
+
+- `tool-display-mode`
+- `tool-navigation` because existing expectations were updated to the new labels.
+- `workspace-contract` through the legacy `npm run test:workspace-v2` command because shared Tool Display Mode behavior changed.
+
+## Skipped Lanes
+
+- `game-design`, `game-configuration`, and `project-workspace`: skipped because no tool-owned runtime or mock repository behavior changed.
+- `build-path` and `tools-progress`: skipped because registry build order data and Admin Tools Progress table behavior were not changed in this stack.
+- `engine-src`: skipped because no `src/` engine/shared runtime code changed.
+- `samples`: skipped because sample JSON and sample runtime behavior are out of scope.
+
+Full suite is required only when shared runtime, shared parser, shared DB, shared Theme V2, or cross-tool integration behavior changes beyond the targeted Tool Display Mode surface.