verifier-gui

# Silo GUI Verifier The handle the `verify` skill looks for: how to get the running Silo app under control and capture evidence from it. Silo is a Tauri desktop app; its surface is pixels + a dev-only RPC bridge. This skill drives that bridge. **It does not judge.** It launches, drives, captures. The verdict is `verify`'s. ## Golden rule 1: verify in a sandbox workspace, never the user's The app may be the user's live session with real workspaces and terminals. **Do all verification in a workspace you create from a temp dir, and delete it when done.** Never `openTerminal`/`deleteWorkspace`/`openFile` against an existing workspace — you'd pollute or destroy real state. Create → activate → verify ��� delete. This also makes destructive paths (workspace delete, session kill) safe to exercise. ## Golden rule 2: one turn, not one op per turn The wall-clock cost here is **agent turns**, not the RPC bridge — each bridge call is ~milliseconds on localhost, but every separate `Bash` tool call is a full model round-trip (seconds). So **issue a whole drive + capture sequence as a single `Bash` call.** The `silo()` helper is just `curl`; bash variables (`WS_ID`, `WS_DIR`) persist _within_ one invocation, so create → activate → drive → screenshot → decode all belong in **one** block (see §2). A 6-step flow then costs 2 turns, not 7. Only split into a separate turn when you genuinely must: - **The final `Read /tmp/silo.png`** — `Read` is its own tool, so capture-in-one-turn then ...