# Task Card

- Task ID: SUP-RUNTIME-GATE-001
- Owner Agent: SentinelRuntimeAgent (Supervisor)
- Objective: Establish the mandatory runtime gate for rebuilding 7 static HTML pages in `D:\Web\docs\neue desining` to match the reference screenshots: Three-Window Commander Layout, HF Workbench, and AnyCoder Controls. The gate covers two separated platforms with one shared live-log bridge and blocks completion until browser/runtime evidence is attached.
- Inputs:
  - Workspace: `D:\Web\docs\neue desining`
  - Pages:
    - `hf_monitor.html`
    - `hf_editor.html`
    - `dev_coding.html`
    - `dev_settings.html`
    - `dev_rendering.html`
    - `ULTRA ANALYSE*.html`
    - `ultra_future.html`
  - Shared assets:
    - `godmode_live.css`
    - `godmode_live.js`
  - Platform A: HF Workbench (`hf_monitor.html`, `hf_editor.html`)
  - Platform B: Dev / AnyCoder Controls (`dev_coding.html`, `dev_settings.html`, `dev_rendering.html`)
  - Shared bridge: global live-log/state bridge in `godmode_live.js` using local storage plus broadcast channel behavior where available.
  - Reference targets: Three-window commander structure, HF Workbench control surface, AnyCoder-style control panels, cross-page live logs.
- Dependencies:
  - Rebuild implementation task must finish page/layout edits before this gate can pass.
  - Local static server must run from workspace root, for example: `py -3 -m http.server 4173`
  - Chrome DevTools MCP must be available for DOM, console, and network evidence.
  - Puppeteer MCP must be available for smoke-flow evidence.
  - No page may be accepted from visual inspection alone.
- Definition of Done:
  - All 7 pages load through the local server without fatal render, script, stylesheet, or navigation failures.
  - Both platforms remain visually distinct while sharing a consistent rebuild language:
    - HF Workbench pages expose monitor/editor workbench controls.
    - Dev / AnyCoder pages expose coding/settings/rendering controls.
    - Master/future pages expose orchestration, evidence, and migration views.
  - The shared live-log bridge works across at least one HF page and one Dev / AnyCoder page in separate browser tabs.
  - Required checks are recorded with pass/fail status and concrete evidence artifacts.
  - Any failed check blocks acceptance until fixed and rerun from Page Load through Smoke.
- Required Tests:
  - Static file inventory:
    - Confirm all 7 HTML files exist.
    - Confirm each HTML file links `godmode_live.css`.
    - Confirm each HTML file loads `godmode_live.js`.
  - Project runtime checks from AGENTS.md where applicable:
    - `py -3 D:\Web\docs\godmode_setup\verify_devtools_bridge.py`
    - `py -3 D:\Web\docs\godmode_setup\ops\sentinel_runtime_probe.py`
    - `py -3 D:\Web\docs\godmode_setup\verify_hf_runtime.py`
  - If a command is unavailable or not applicable in this static workspace, record the exact failure and mitigation in the evidence log. Do not convert unavailable checks into pass.
- Required Browser Checks:
  - Page Load:
    - Open every page at `public cloud URL /godmode/<page>`.
    - Verify HTTP 200 for HTML, CSS, and JS.
    - Verify each page has a visible topbar, primary page body, platform-specific control surface, and live-log panel.
    - Verify no blank page, broken layout collapse, horizontal overflow at desktop width, or missing shared assets.
  - Interactions:
    - On HF Workbench: trigger representative monitor/editor controls and verify log entries or visible state changes.
    - On Dev / AnyCoder: trigger dispatch/build/test/settings/rendering controls and verify log entries or visible state changes.
    - On master/future pages: trigger runtime/truth/sync/navigation controls and verify expected log/state behavior.
    - Open one HF page and one Dev / AnyCoder page together, trigger an action on one, and verify the shared live-log bridge updates the other without reload when BroadcastChannel is available, or after storage propagation when using fallback.
  - Console:
    - Capture Chrome DevTools console output for every page.
    - Acceptance requires no uncaught exceptions, failed module/script execution, or repeated warning loops.
    - Cosmetic warnings may pass only if classified and justified by SentinelTruthAgent.
  - Network:
    - Capture network requests for every page.
    - Acceptance requires no failed local HTML/CSS/JS asset requests.
    - External or backend endpoints may be absent only if the UI degrades cleanly and the evidence log marks them as inferred/unavailable rather than verified.
    - No secrets, tokens, or keys may appear in network URLs, local storage dumps, visible fields, screenshots, or console output.
  - Smoke:
    - Puppeteer flow must visit all 7 pages in sequence.
    - Validate navigation links between pages.
    - Click at least three controls per platform and one master runtime gate control.
    - Assert `window.GodmodeLive` exists on every page.
    - Assert a dispatch/log action increments or appends observable state.
    - Capture desktop and mobile screenshots for representative pages: one HF page, one Dev / AnyCoder page, and the master page.
- Rollback Plan:
  - Revert only the files changed by the rebuild task.
  - Keep this task card unless the gate definition itself is superseded by a new accepted supervisor card.
  - For UI regressions, restore last known working versions of affected HTML/CSS/JS files and rerun the full gate from Page Load.
  - For bridge regressions, isolate rollback to `godmode_live.js` first, then rerun cross-tab live-log smoke.

## Progress Log

- Start time: 2026-04-21
- Current step: Initial gate card created; runtime execution pending after rebuild implementation.
- Blocking issues:
  - Reference screenshots were not present in the current workspace inventory; visual-match acceptance must attach them or provide a reachable reference path before final approval.
  - Browser evidence is not yet collected; this card defines the gate and cannot be used as proof that the rebuild passed.

## Evidence

- Files changed:
  - `TASK_CARD_supervisor_runtime_gate.md`
- Commands executed:
  - `Get-Location`
  - `Get-ChildItem -Force`
  - `Get-ChildItem -Recurse -File`
  - `Get-Content -Raw C:\Users\immer\.codex\skills\3d-web-game-swarm\SKILL.md`
  - `Get-Content -Raw C:\Users\immer\.codex\skills\3d-web-game-swarm\templates\task-card.md`
  - `Get-Content -Raw C:\Users\immer\.codex\skills\3d-web-game-swarm\templates\evidence-log.md`
  - `Get-Content -TotalCount 80` on representative HTML pages
  - `Select-String` against `godmode_live.js` and HTML files for bridge/log/control hooks
- Test outputs:
  - Pending: this is a planning/gate artifact, not the completed runtime run.
- Browser/devtools outputs:
  - Pending: must be produced with Chrome DevTools MCP and Puppeteer MCP after UI rebuild changes.
- Claim classification:
  - Verified: Workspace contains the listed 7 HTML targets and shared `godmode_live.css` / `godmode_live.js`.
  - Verified: The shared JS contains local storage and BroadcastChannel bridge behavior.
  - Inferred: Platform split maps HF pages to HF Workbench and Dev pages to Dev / AnyCoder controls based on current filenames and page copy.
  - Unknown: Final visual parity with the reference screenshots until screenshots are supplied and browser evidence is captured.

## Abnahmekriterien

- PASS only if all required tests and browser checks are attached as evidence.
- PASS only if both platforms stay separate in navigation, layout intent, and controls while sharing the same live-log bridge.
- PASS only if console and network checks show no blocking runtime errors.
- PASS only if Puppeteer smoke covers all 7 pages and proves at least one cross-platform log/state propagation path.
- FAIL if a page is accepted from screenshot-only review without DevTools and Puppeteer evidence.
- FAIL if any acceptance claim is marked unknown.
- FAIL if rollback notes are missing from the final evidence log.