[ccoventry]

Release note: Changed: Start Capture Batch greys out the moment it's clicked and says which check it's on (OBS, disk space, the picked demos, maps, Steam) until the batch starts.

Closes #953. From the #942 progress audit (plan C).

What changes

• New studio/src/capture_precheck.js (createCapturePrecheck): on the click, Start greys out, the footer bar shows with the sliding block, and the status line reads each check as it runs:
  • "Getting ready to capture…" (at once)
  • "Checking OBS…" (OBS mode)
  • "Checking the disk space…"
  • "Checking the picked demos are where they were (3 of 12)…"
  • "Checking the maps and demos for known problems…" (crash-prone maps, the entity limit, camera data)
  • "Checking the game and HLAE paths…"
  • "Checking whether the game is already open…"
  • "Checking Steam…"
• A check that stops the batch brings Start back (through refreshLaunchGuard, so the disk-space guard still has the last word) and puts the reason on the line: the same text as its toast, the existing "Not started — …" lines for Steam and a game with other settings, or "Not started." when a question was answered no.
• refreshLaunchGuard no longer re-enables Start while the checks run (it's called by the disk check itself and by every settings edit).
• A second click while checking does nothing.
• changed_demos (lib.rs) now emits changed_demos_progress { done, total }, throttled to ~33 ms with the last demo always sent, for the "3 of 12" count. changedDemos(demos, onProgress) in ipc_bridge.js listens only while it runs; captureDemosReady / pickedDemosPresent pass onProgress through.

Decisions

• Kept to the pre-check step and its status line, not the batch footer: open PR Render while capturing: each clip renders as soon as it's recorded, and a long batch waits for space instead of filling the drive (#861) #885 (Render while capturing) reworks that footer. Once the checks pass, the line hands over to the batch as today (the "Initializing" toast, then capture_status). This PR touches only the click handler and the refreshLaunchGuard guard in capture_pane.js; Render while capturing: each clip renders as soon as it's recorded, and a long batch waits for space instead of filling the drive (#861) #885's hunks are elsewhere in the file. The handler body moved into a runChecksAndStart arrow at the same indent, so the diff stays small.
• "Checking Steam…", not "Waiting for Steam…": Steam is usually ready and the check is instant. When it does wait, its own toast with Cancel says so, as before.
• A game already open: its window asks what to do and starts the batch itself, so Start comes back behind it with "Not started yet: the game is already open." in case the answer is no.
• The sliding block is the page's own .progress-bar-container.indeterminate. It can move to progress_view.js once Master Queue scan: show progress while it looks for demos, and one bar through grouping and splits #951 lands.
• The crash-map, entity-limit and camera checks share one line: each is quick unless it asks a question, and then the question says which.

Test done

• npm run test:unit: 79 files, 714 tests pass (new capture_precheck.test.js: each line, the count, begin/stop/hand-over on fake elements).
• CI=1 npx playwright test on the new capture-precheck.spec.js (4) plus master-pane, queue-scan, split-maps, running-game and recent-projects: 39 pass. The new spec runs the real initCaptureUI. It checks that Start greys out and the line reads "Checking the disk space…" while that check is still held (the first line shows at once). It checks that the demo check's count shows, that a second click and a guard refresh leave Start greyed out, that a missing demo brings Start back with the reason and hides the bar, and that a "no" says "Not started."
• npm run build: ok.
• cargo test -p desktop-studio: 185 pass (new: the per-demo count, and the throttle that always sends the last demo). cargo fmt --all --check and clippy 1.98.1 -p desktop-studio --all-targets -D warnings: clean.
• Not run in the real app. Look: pick highlights, click Start Capture Batch. Start should grey out at once and the line under the buttons should step through the checks. With many demos picked, the demo check counts. Then try one that stops: untick everything after a missing demo, or rename a picked demo on disk. Start should come back with the reason on the line. In OBS mode with OBS closed, the line should stay on "Checking OBS…" while it launches OBS.

🤖 Generated with Claude Code