Keep scenario stepping and pause usable from the keyboard

Author: antropos17

DESIGN.md

@@ -86,6 +86,12 @@ keyboard recovery control.
 Environment stays readable without a workspace snapshot; unknown repository
 counts stay absent until data arrives.
 
+Manual scenario steps keep keyboard focus on the same enabled control; completion
+or a failed step returns entry to main. Pausing remains available during an
+in-flight step and stops future scheduling, while the current transaction can
+finish. A changing Play/Pause/New run action label uses an ordinary button,
+without a contradictory toggle pressed state. Respect another chosen control.
+
 ## Motion
 
 No authored animation or transition in the workspace, including modal scale/fade, progress interpolation, hover motion and smooth route scrolling. Update status immediately without recreating the page. Native dialog handles focus and Escape; returning focus must not move the document. Game canvas motion belongs to gameplay and remains independent of workspace chrome.

docs/CONTEXT.md

@@ -82,7 +82,7 @@ and external AI CLIs require a direct user request. Never merge old work implici
 - Existing Commons run 49092854-f9bd-4b7a-8d12-4ac5ea0e5f70 retains the approved,
   unmerged safe-timer change from job 811bdb98-bcbb-4b65-80b9-f19693aef6b4.
   Preserve it. 29 earlier lab experiments were verified before this release work.
-- Public source: antropos17/commit-zero at e788d0e; all three CI jobs and fresh evidence preflight passed. Preserve separate histories.
+- Public source: antropos17/commit-zero at 5392fc0; all three CI jobs passed with local dfa9ecb's identical tree. Preserve separate histories.
   README GIF is a 15.8s condensed walkthrough of retained Sequence Kit work,
   not a continuous live recording. Static fallback included; desktop/mobile and all
   three CI jobs passed. Evidence: runtime/verification/github-readme-gif-2026-10-19.json.

docs/ECOSYSTEM-DECISIONS.md

@@ -47,6 +47,19 @@ No substitute model is inferred from a familiar display name.
 
 ## Other adopted decisions and their evidence
 
+The [W3C button pattern](https://www.w3.org/WAI/ARIA/apg/patterns/button/)
+(accessed 2026-10-19) distinguishes a stable-label toggle from an action button
+with changing labels, and describes focus staying on actions in the same
+context. Actual Chrome fixtures showed focus loss after Next step and an
+unavailable Pause during an in-flight transaction. Decision: retain native
+action buttons, restore manual-operation entry after the DOM commit, and keep
+Pause available until future scheduling stops. The existing small
+[React layout effect](https://react.dev/reference/react/useLayoutEffect)
+runs after committed updates; it performs no state update, network call or
+layout loop. Expected benefit: keyboard users can complete and pause the
+deterministic cycle. Browser fixtures check terminal/new-run history, failure
+without automatic write retry, and pause with/without another focus choice.
+
 | Question | Decision and verification |
 | --- | --- |
 | Hosted request/response patterns | Four disconnected text contracts share host context and evidence validation. [Primary sources, offline fixtures and activation gaps](PROVIDER-DRAFTS.md). |

docs/FIRST-RUN.md

@@ -24,6 +24,11 @@ It uses isolated fixture actors and does not modify a saved user run.
 The [PR diff capture](media/scenario-pr-2026-10-19.png) is an actual Chrome
 capture after completing the deterministic ten-step example in disposable
 services. Conversation, checks and changed files remain inspectable after merge.
+Use **Next step** with Enter or Space to continue from the same control. At the
+last step, focus returns to content. **New run** preserves the completed run's
+export. **Pause cycle** stops future scheduled steps; a step already sent to the
+service can finish. A failed step never advances the view optimistically, and
+**Retry** refreshes the saved state without repeating the write.
 At narrow widths, focus the code region and use arrow keys or swipe sideways to
 read complete lines. Scenario checks are predefined results, not executed code.
 

docs/HANDOFF-2026-10-19.md

@@ -8,18 +8,18 @@ tracks dated decisions and receipts; this file is the operational entry point.
 ## Repositories and state
 
 - Working repository: `X:\ai-github`, branch `codex/development-foundation`,
-  latest fully checked local commit `e61e129` at this checkpoint. The local data and model
+  latest fully checked local commit `dfa9ecb` at this checkpoint. The local data and model
   installation are here. Recheck status before acting; this file can age.
 - Public repository: [antropos17/commit-zero](https://github.com/antropos17/commit-zero),
-  `main` at `e788d0e2f522585cd4777047160509dbbe4982f3` after a normal push.
+  `main` at `5392fc00b2ac2f8faedc507acc63311705a93dcc` after a normal push.
   Its separate checkout is `.cache/publication`. The histories are unrelated;
-  the public tree matches local `e61e129` (`91e7019472b547a688a36e4822fe6b7677786352`).
-  Service-health recovery/manual-refresh focus changes are awaiting final gates.
+  the public tree matches local `dfa9ecb` (`ceec86201675ecda32f8c844123f5994c1b8ac28`).
+  Keyboard scenario-control changes are awaiting final gates.
   Do not merge histories, reset the local branch or force push. Recheck remote
   before publishing anything else.
-- Public CI [run 39228142114](https://github.com/antropos17/commit-zero/actions/runs/39228142114)
-  passed full gate, Chromium and runtime dependency audit for `e788d0e`. Fresh
-  `evidence:status -- --github` confirmed exact main/CI and both local receipts. The
+- Public CI [run 39233009471](https://github.com/antropos17/commit-zero/actions/runs/39233009471)
+  passed full gate, Chromium and runtime dependency audit for `5392fc0`. Local
+  `evidence:status` confirmed equal trees and current full/browser receipts. The
   preceding retry-fixture failure at `5f9f88e` is preserved in the mission log.
 - This mission has not run local or hosted model inference, spawned product
   agents, submitted promotional posts or created a new release. Prior retained
@@ -116,22 +116,25 @@ source-evidence unit passed at `e61e129`. Its preflight compares both full recei
 on the same frozen source. `npm run evidence:status -- --github` is the live operational check;
 hardcoded revisions here describe the last checkpoint at documentation time.
 
-The pending health unit adds a named busy region, settled failure and explicit
+The health unit adds a named busy region, settled failure and explicit
 last-available data. Environment remains accessible without a workspace snapshot;
 unknown repository counts are omitted. Manual workspace/health recovery restores
 its control or content entry after React updates, while respecting another focus
 choice or route. Four focused Chrome tests and UI DOM/axe/build/serving passed.
 The scenario assertion follows the actual returned step and forbids reset/advance
 requests. [Desktop error](media/service-health-unavailable-2026-10-19.png) and
 [narrow dark retained state](media/service-health-last-known-2026-10-19.png)
-are real disposable-service captures. Full source/browser gates remain.
+are real disposable-service captures. Full 81/81 and Chrome 18/18 passed on the
+same frozen source before commit/publication. The next keyboard unit preserves
+manual step focus and keeps Pause usable during the current transaction; its
+four focused Chrome tests passed, with full gates pending.
 
-- Latest local frozen full gate at `e61e129`: 81/81 Node tests, compiled DOM/axe
+- Latest local frozen full gate at `dfa9ecb`: 81/81 Node tests, compiled DOM/axe
   2/2, build and static serving passed. Stable source hash
-  `d3ab286ac18b39386976ac5278b923aebc2e4e066c7e509a26208793c3cce5e5`;
-  receipts `runtime/verification/evidence-preflight-{full,browser}-2026-10-19.json`
-  and `evidence-status-hosted-2026-10-19.json` (ignored by Git).
-- Installed Chrome browser suite passed 15/15 at desktop and 390px. Real captures
+  `b68e7f8a312d9ac724e2e845eb690f0db19313e4badf3e96fb5c6590398d9360`;
+  receipts `runtime/verification/health-recovery-{full,browser}-2026-10-19.json`
+  (ignored by Git).
+- Installed Chrome browser suite passed 18/18 at desktop and 390px. Real captures
   are `runtime/verification/commons-first-run-{desktop,narrow}-2026-10-19.png`,
   `commons-provider-offline-desktop-2026-10-19.png` and catalog captures. Tests
   used in-memory services; provider-health responses were controlled in the
@@ -177,14 +180,16 @@ are real disposable-service captures. Full source/browser gates remain.
   `runtime/verification/startup-busy-baseline-2026-10-19/`. Focused UI and all 12
   Chrome journeys passed, including actual Tab/Enter and the real retry HTTP 200;
   its full gate and public CI passed at `746729d`. [Actual error view](media/workspace-unavailable-2026-10-19.png).
-- The pending identity unit adds `shared/local-model-artifact.mjs` and
+- The completed identity unit adds `shared/local-model-artifact.mjs` and
   `npm run model:inspect [-- --hash]`. It checks file metadata/digest without
   reading a token, loading a model or probing a provider. Synthetic fixtures cover
   missing/mismatch/escape/cancellation; the real stream cancelled after 165 MB.
   The declared 4096-token local window and input/output budget are preparation,
   with tokenizer and hardware fit unqualified. Actual byte identity does not
   qualify either proposed role. Focused UI and grouped Chrome 12/12 passed,
-  including narrow artifact details. The frozen real CLI hash and full gate remain.
+  including narrow artifact details. The frozen real CLI hash matched the pinned
+  artifact and full gate passed; the later public retry-fixture failure was
+  repaired in `ae6569b`, without model inference.
 - `npm run benchmark:backend` used a disposable PGlite snapshot of five projects
   and 1,000 messages. Twenty samples per path: current normalized message-write
   p50 9.09 ms versus retained legacy pattern 42.99 ms. This verifies a prior
@@ -198,7 +203,7 @@ are real disposable-service captures. Full source/browser gates remain.
 
 ## Next work, in order
 
-1. Complete health/retry recovery: run grouped Chrome and `npm run check` on frozen source,
+1. Complete keyboard scenario controls: run grouped Chrome and `npm run check` on frozen source,
    commit it, copy the unpublished local commit into the separate public
    checkout, compare Git trees, push without force and inspect public CI.
    Record exact SHA and receipt.

docs/MISSION-2026-10-19.md

@@ -12,7 +12,7 @@ Start: 03:46:17 UTC. Deadline: 15:46:17 UTC. Final integration reserve begins 14
 
 ## Current action
 
-Finish service-health recovery and manual workspace refresh focus. Four actual Chrome failures were reproduced and preserved; four focused recovery tests now pass. Run focused UI, then freeze source for full Chrome/full gates and publication. Keep all new profiles disabled. The final integration reserve still begins at 14:16:17 UTC.
+Finish keyboard scenario controls after two preserved Chrome failures. Next step now retains entry, terminal/error steps fall back to content, and Pause remains available during a transaction without cancelling its committed work. Verify current-step completion, no future scheduling, chosen-input focus and preserved exports; then frozen full gates and publication. Keep all new profiles disabled. The final integration reserve still begins at 14:16:17 UTC.
 
 ## Decisions and limits
 
@@ -90,4 +90,7 @@ Finish service-health recovery and manual workspace refresh focus. Four actual C
 - 09:36 UTC: Chrome exposed and preserved four UI failures: settled health errors kept Checking services; initial workspace Retry stole the search focus; Environment disappeared when the workspace snapshot failed; the toolbar refresh lost focus after its temporary disabled state. Baselines are under `runtime/verification/health-focus-baseline-2026-10-19`, `health-without-workspace-baseline-2026-10-19` and `workspace-toolbar-focus-baseline-2026-10-19`. New scoped busy/error/last-available states, independent diagnostics and manual focus restoration passed four focused Chrome tests, including light/dark 390px axe. Diagnostic refresh checks the exact returned scenario step and rejects reset/advance requests. Real captures were inspected and copied to docs/media with digests `d26cd5a6` and `032e4796`. Focused UI and frozen full gates remain. Vendored Impeccable craft/state guidance was read as a reference; its separate context engine was not run, PRODUCT.md is absent, and existing DESIGN.md remains authoritative.
 ## Next checkpoint
 
-Focused health/workspace Chrome passed 4/4, and focused UI passed DOM/axe 2/2, build and serving. Freeze source for the complete 18-test browser suite and full gate; then commit/publish and validate the exact source/public CI association. Next inspect keyboard use of scenario controls. Keep the final 90-minute reserve from 14:16:17 UTC.
+- 09:50 UTC: health/manual-refresh recovery committed locally as `dfa9ecb16afea0c7d5e31ff6bc029a9483fef1ac` after full 81/81 and Chrome 18/18 on the same frozen hash `b68e7f8a312d9ac724e2e845eb690f0db19313e4badf3e96fb5c6590398d9360`. Receipts: `runtime/verification/health-recovery-{full,browser}-2026-10-19.json`. Normal publication produced `5392fc00b2ac2f8faedc507acc63311705a93dcc`, identical tree `ceec86201675ecda32f8c844123f5994c1b8ac28`. CI39233009471 passed all three jobs. Local preflight confirmed current full/browser receipts and both clean equal trees.
+- Chrome then reproduced Next step losing focus after a successful transaction and Pause being disabled while a cycle request was pending. Both traces are retained under `runtime/verification/scenario-keyboard-baseline-2026-10-19`. An initial three-test focused correction passed; the strengthened pause cases also distinguish restoring the control from respecting another chosen input. No model calls or retained-store writes.
+
+Run focused UI, freeze complete source for all browser groups and full gate, then commit/publish the keyboard unit. Next inspect competing bookmark writes and remaining release acceptance gaps. Keep the final 90-minute reserve from 14:16:17 UTC.

prototype/app/App.jsx

@@ -186,17 +186,17 @@ export function App() {
     [toast, setToast] = useState("");
   const main = useRef(null);
   const handledRoute = useRef(null);
-  const refreshOrigin = useRef(null);
+  const operationOrigin = useRef(null);
   useLayoutEffect(() => {
     if (busy) return;
-    const pending = refreshOrigin.current;
-    refreshOrigin.current = null;
+    const pending = operationOrigin.current;
+    operationOrigin.current = null;
     if (pending && location.hash === pending.hash &&
         (document.activeElement === document.body || document.activeElement === pending.trigger))
-      (pending.trigger.isConnected ? pending.trigger : main.current)?.focus({ preventScroll: true });
+      (pending.trigger.isConnected && !pending.trigger.disabled ? pending.trigger : main.current)?.focus({ preventScroll: true });
   }, [busy, data, error]);
   function refreshWorkspace(event) {
-    refreshOrigin.current = { trigger: event.currentTarget, hash: location.hash };
+    operationOrigin.current = { trigger: event.currentTarget, hash: location.hash };
     workspace.setPlaying(false);
     void workspace.refresh();
   }
@@ -389,10 +389,16 @@ export function App() {
                   </span>
                   <button
                     id="playback-toggle"
-                    disabled={!data || busy || Boolean(error)}
-                    aria-pressed={playing}
-                    onClick={() => {
+                    disabled={!data || (busy && !playing) || Boolean(error)}
+                    title={playing ? "Pause future steps. The current step can finish." : undefined}
+                    onClick={(event) => {
+                      if (playing) {
+                        if (busy) operationOrigin.current = { trigger: event.currentTarget, hash: location.hash };
+                        workspace.setPlaying(false);
+                        return;
+                      }
                       if (data.step === 10) {
+                        operationOrigin.current = { trigger: event.currentTarget, hash: location.hash };
                         void workspace.newRun().then((next) => {
                           if (next && next.runId !== data.runId) {
                             routeScroll.delete("#/home");
@@ -405,18 +411,15 @@ export function App() {
                       workspace.setPlaying(!playing);
                     }}
                   >
-                    {data?.step === 10
-                      ? "New run"
-                      : playing
-                        ? "Pause cycle"
-                        : "Play cycle"}
+                    {playing ? "Pause cycle" : data?.step === 10 ? "New run" : "Play cycle"}
                   </button>
                   <button
                     id="playback-next"
                     disabled={
                       !data || busy || Boolean(error) || data.step === 10
                     }
-                    onClick={() => {
+                    onClick={(event) => {
+                      operationOrigin.current = { trigger: event.currentTarget, hash: location.hash };
                       workspace.setPlaying(false);
                       void workspace.advance();
                     }}

scripts/project-map.mjs

@@ -25,7 +25,7 @@ export const areas = {
       "prototype/app/components/project-contributions.jsx",
       "prototype/app/components/project-timeline.jsx",
     ],
-    tests: ["tests/interface.dom.mjs", "tests/agent-catalog.test.mjs", "tests/agent-fixtures.test.mjs", "tests/browser/commons-first-run.spec.mjs", "tests/browser/scenario-pr.spec.mjs", "tests/browser/workspace-recovery.spec.mjs", "tests/browser/service-health.spec.mjs"],
+    tests: ["tests/interface.dom.mjs", "tests/agent-catalog.test.mjs", "tests/agent-fixtures.test.mjs", "tests/browser/commons-first-run.spec.mjs", "tests/browser/scenario-pr.spec.mjs", "tests/browser/workspace-recovery.spec.mjs", "tests/browser/service-health.spec.mjs", "tests/browser/scenario-keyboard.spec.mjs"],
     docs: ["DESIGN.md", "docs/AGENT-CATALOG.md", "docs/FIRST-RUN.md"],
   },
   commons: {

scripts/test-ui.mjs

@@ -26,6 +26,10 @@ export const browserGroups = Object.freeze([
     name: "account-recovery",
     files: Object.freeze(["account-recovery.spec.mjs"]),
   }),
+  Object.freeze({
+    name: "scenario-keyboard",
+    files: Object.freeze(["scenario-keyboard.spec.mjs"]),
+  }),
   Object.freeze({
     name: "history-and-pr",
     files: Object.freeze([