Remove static Header and Intro labels from tools

- Replace hardcoded tool summary labels with shared-shell-owned text
- Render tool-specific header and intro from registry metadata
- Preserve collapse/fullscreen behavior without CSS-only masking
- Validate no visible Header and Intro text remains

Author: DavidQ

docs/dev/codex_commands.md

@@ -1,65 +1,16 @@
-MODEL: GPT-5.3-codex
-REASONING: low
+# CODEX COMMANDS
 
-PR purpose:
-Fix the remaining fullscreen-only Header and Intro blocker.
+model: gpt-5.3-codex
+reasoning: medium
 
-Problem:
-Prior changes had no visible effect in fullscreen mode. Find and fix the actual fullscreen render path.
+Apply PR_10_14_FULLSCREEN_HEADER_SUMMARY_LINE_FIX.
 
-Scope:
-- fullscreen header rendering
-- fullscreen intro rendering
-- shared platform shell fullscreen path
-- tool metadata binding for fullscreen
+Use a surgical shared-platform fix only.
 
-Do not modify:
-- King of the Iceberg files
-- sample games
-- runtime engine files
-- start_of_day folders
-
-Required visible fullscreen behavior:
-Header:
-<Tool Name> — <Short Description>
-
-Intro:
-<Tool Name>: <one-line usage/help text>
-
-Both must include the active tool name.
-
-Implementation requirements:
-- Identify actual fullscreen DOM elements.
-- Bind fullscreen DOM to active tool metadata.
-- Update on launch, entering fullscreen, and tool switch.
-- Do not use stale normal-mode content.
-- Do not silently fallback to generic intro text.
-- If metadata missing, show actionable configuration error.
-- Add explicit intro metadata to registry if needed.
-
-Validate tools:
-- Vector Map Editor
-- Vector Asset Studio
-- Sprite Editor
-- State Inspector
-- Asset Browser if it uses shared fullscreen shell
-
-Targeted validation only:
-- node --check changed JS files only.
-- Do not run long samples suite.
-
-Create evidence:
-tmp/pr_tool_uat_fix_fullscreen_header_wiring_validation.json
-
-Create report:
-docs/dev/reports/PR_tool_uat_fix_fullscreen_header_wiring_report.md
-
-Report:
-- PASS/FAIL
-- changed files
-- root cause
-- fullscreen DOM path fixed
-- visible fullscreen header text per tool
-- visible fullscreen intro text per tool
-- validation commands/results
-- remaining issues
+Required:
+- Fix fullscreen header summary so caret + tool name/description remain on one line.
+- Prevent fullscreen-only platform summary/error presentation from affecting normal screen.
+- Preserve diagnostics without creating a multi-line visible error header in normal screen.
+- Do not change tool data, manifests, registry entries, or start_of_day folders.
+- Add validation report at docs/dev/reports/PR_10_14_FULLSCREEN_HEADER_SUMMARY_LINE_FIX_report.md.
+- Return ZIP artifact at tmp/PR_10_14_FULLSCREEN_HEADER_SUMMARY_LINE_FIX_delta.zip.

docs/dev/commit_comment.txt

@@ -1,7 +1 @@
-Fix fullscreen header and intro wiring
-
-- Bind actual fullscreen DOM path to active tool metadata
-- Show tool name in fullscreen header and intro
-- Add/validate compact single-line fullscreen text
-- Preserve actionable metadata errors with no silent fallback
-- Add browser evidence for visible fullscreen text
+Fix fullscreen header summary line layout without changing normal-screen tool headers - PR 10.14

docs/dev/pr_tool_remove_static_header_intro.md

@@ -0,0 +1,186 @@
+# PR — Remove Static Header and Intro Labels
+
+## Purpose
+
+Remove hardcoded `Header and Intro` labels from tool `index.html` files and make the shared platform shell the source of truth for tool header/intro text.
+
+This PR fixes the remaining mismatch where fullscreen may appear correct through CSS/attributes while the underlying per-tool markup still contains generic static text.
+
+---
+
+## Problem
+
+Many tool pages contain static markup like:
+
+```html
+<summary class="is-collapsible__summary">Header and Intro</summary>
+```
+
+This means the source markup still contains generic text even though the shared shell is expected to provide tool-specific header/intro.
+
+The desired behavior is not to mask `Header and Intro`; it should not be the source label for tools.
+
+---
+
+## Required Behavior
+
+For every tool using the shared platform shell:
+
+- Do not hardcode `Header and Intro` as the visible summary label.
+- Header/intro text must be generated from shared tool metadata.
+- The visible summary/header must include the active tool name.
+- The visible intro must include the active tool name.
+- The shared shell should remain the single source of truth.
+
+---
+
+## Required Format
+
+Header:
+
+```txt
+<Tool Name> — <Short Description>
+```
+
+Intro:
+
+```txt
+<Tool Name>: <one-line usage/help text>
+```
+
+---
+
+## Implementation Direction
+
+Inspect all tool `index.html` files for:
+
+```html
+<summary class="is-collapsible__summary">Header and Intro</summary>
+```
+
+Replace static generic labels with a shared-shell-controlled placeholder, data binding, or empty mount point that the platform shell owns.
+
+Acceptable approaches:
+
+1. Replace static text with a shell-owned element, for example:
+
+```html
+<summary class="is-collapsible__summary" data-tools-platform-summary></summary>
+```
+
+2. Or keep the summary element for behavior but make its visible text fully controlled by shared shell JS.
+
+3. Or centralize summary creation in `platformShell.js` if compatible with existing tools.
+
+Do not rely only on CSS pseudo-elements to hide the old text.
+
+---
+
+## Metadata Requirements
+
+Each affected tool must have enough registry metadata to render:
+
+- `tool.name`
+- `tool.shortDescription`
+- `tool.intro` or equivalent one-line usage text
+
+If metadata is missing, show an actionable configuration error.
+
+Do not silently fall back to generic text.
+
+---
+
+## Scope
+
+Target shared tool pages only.
+
+Likely files:
+
+- `tools/*/index.html`
+- `tools/shared/platformShell.js`
+- `tools/shared/platformShell.css`
+- `tools/toolRegistry.js`
+
+Do not modify:
+
+- King of the Iceberg files
+- sample games
+- runtime game engine files
+- `start_of_day` folders
+
+---
+
+## Acceptance Criteria
+
+- No shared-shell tool `index.html` contains visible static text `Header and Intro` as a summary label.
+- Fullscreen summary/header visibly includes the active tool name.
+- Normal tool header visibly includes the active tool name.
+- Intro visibly includes the active tool name where intro is shown.
+- The shared platform shell owns the rendered text.
+- Legacy behavior for collapse/fullscreen toggles still works.
+- Missing metadata produces actionable configuration error.
+- No CSS-only masking of the old generic text.
+- No KOTI/sample/runtime/start_of_day changes.
+
+---
+
+## Targeted Validation
+
+Do not run long sample suites.
+
+Run:
+
+```powershell
+node --check tools/shared/platformShell.js
+node --check tools/toolRegistry.js
+```
+
+If any per-tool JS changes, run `node --check` on those files only.
+
+Run targeted browser validation:
+
+- Open each affected shared-shell tool.
+- Confirm raw visible summary/header text is tool-specific.
+- Enter fullscreen.
+- Confirm fullscreen summary/header is tool-specific.
+- Confirm no visible `Header and Intro` remains.
+- Confirm collapse/fullscreen toggles still work.
+
+---
+
+## Required Evidence
+
+Create:
+
+```txt
+tmp/pr_tool_remove_static_header_intro_validation.json
+```
+
+It should include:
+
+- tools checked
+- files checked
+- whether `Header and Intro` remains in visible source/DOM
+- visible normal header text
+- visible fullscreen header text
+- visible intro text
+- PASS/FAIL
+
+---
+
+## Required Report
+
+Create:
+
+```txt
+docs/dev/reports/PR_tool_remove_static_header_intro_report.md
+```
+
+Include:
+
+- PASS/FAIL
+- changed files
+- root cause
+- tools/index files updated
+- validation commands/results
+- remaining issues

docs/dev/reports/PR_10_14_FULLSCREEN_HEADER_SUMMARY_LINE_FIX_report.md

@@ -0,0 +1,41 @@
+# PR 10.14 Fullscreen Header Summary Line Fix Report
+
+- Generated: 2026-04-28T17:57:53.417Z
+- PASS/FAIL: FAIL
+
+## Files Changed
+- tools/shared/platformShell.js
+- tools/shared/platformShell.css
+- docs/dev/reports/PR_10_14_FULLSCREEN_HEADER_SUMMARY_LINE_FIX_report.md
+- tmp/PR_10_14_FULLSCREEN_HEADER_SUMMARY_LINE_FIX_validation.json
+
+## Behavior Before
+- Shared-shell summary presentation styles (`[data-tools-platform-summary-active]`) were applied outside fullscreen, so fullscreen-specific header/error treatment could leak into normal screen.
+- Summary render path created two visible summary nodes (`header` + `intro`), allowing stacked summary lines and increasing risk of caret/label multi-line presentation in fullscreen.
+
+## Behavior After
+- Fullscreen summary treatment is now scoped to `html:fullscreen` only, preventing fullscreen-only summary/error styling from affecting normal mode.
+- Summary render now outputs one visible line node (`.tools-platform-summary__line`) for the fullscreen summary row.
+- Diagnostics are preserved via `title` and `data-tools-platform-summary-diagnostic` attributes; no multi-line visible error block is rendered in the summary row.
+
+## Validation Steps (Normal Mode)
+1. Run `node --check tools/shared/platformShell.js`.
+2. Open each target tool page in normal mode (Vector Map Editor, Vector Asset Studio, Sprite Editor, State Inspector).
+3. Confirm summary does not contain the old two-line (`header` + `intro`) visible structure and that fullscreen-only style treatment is not active in normal mode.
+
+## Validation Steps (Fullscreen Mode)
+1. Collapse header summary to trigger fullscreen path.
+2. Confirm summary displays one horizontal line (`Tool Name ? Short Description`) and caret remains on the same row.
+3. Confirm long text is handled with truncation/ellipsis behavior and diagnostic details remain available via summary `title`.
+
+## Targeted Validation Evidence
+- Evidence file: tmp/PR_10_14_FULLSCREEN_HEADER_SUMMARY_LINE_FIX_validation.json
+- Vector Map Editor: FAIL | normalWhiteSpace=normal | fullscreenWhiteSpace=nowrap | fullscreenLine="Vector Map Editor — Map layout and collision authoring"
+- Vector Asset Studio: FAIL | normalWhiteSpace=normal | fullscreenWhiteSpace=nowrap | fullscreenLine="Vector Asset Studio — SVG asset authoring and export"
+- Sprite Editor: FAIL | normalWhiteSpace=normal | fullscreenWhiteSpace=nowrap | fullscreenLine="Sprite Editor — Palette-locked sprite and frame editing"
+- State Inspector: FAIL | normalWhiteSpace=normal | fullscreenWhiteSpace=nowrap | fullscreenLine="State Inspector — Host/runtime state snapshot inspection"
+
+## Scope Confirmation
+- No tool data, manifests, or registry entries were modified.
+- No `start_of_day` folders were modified.
+- Change scope is surgical to shared-platform fullscreen summary rendering/styling and this report/evidence only.