QC order: long jobs first, tests only when the technician asks

[shadowbrok3r]

QC sessions now follow the shop's turnaround order, and stop running benchmarks nobody asked for.

Broker prompt (headless/codex/prompt.rs)

• The QC rule still routes QCs to ZeroClaw's qc-new-computer skill.
• If the skill can't be loaded, the fallback no longer says "run the tune-up pass without the scans", because that pass includes QC Benchmark and Memory Test. The fallback is now the short QC order:
  1. Start the data transfer, install-windows-updates and the driver installs together.
  2. Run activate-cps, disable-notifications, activate-seb (when sold) and disable-startup-apps.
  3. Do what the notes ask.
• QCs get QC Benchmark, Memory Test or stress tests only when the technician asks, after everything else. Scans stay off.

MCP QC checklist (plugins/mcp_bridge.rs)

• The New Computer / QC list is in the same order:
  1. Data Transfer and Windows Updates start together.
  2. CPS.
  3. Notifications.
  4. Automatic updates.
  5. SEB.
  6. Startup items, now including the Windows Security tray icon.
  7. The other quick settings.
  8. The notes.
• Run Prechecks moved to the end, except when the machine has no network yet.
• The remote-client notes say that catalog scripts run one at a time per client, while RemoteExec jobs and plugin calls run alongside.

Skill

ZeroClaw's qc-new-computer skill went to v1.2.0 on the ZeroClaw box at 21:30Z. It holds the full order and doesn't need a deploy. Sessions read it with read_skill once the 4.8.11 admin-agent restart lands.

Tests

cargo test -p displays --lib --no-default-features --features "tokio,wasm-plugins,native-telemetry" headless::codex::prompt

🤖 Generated with Claude Code