Invocation#

bash

spis crawl-tui --host <target> [--record <slug>] [--max-records <n>] [--max-states <n>] [--max-depth <n>]

Crawl installed terminal applications in an isolated real tmux PTY on a pinned Stado host.

Inputs and options#

--host <target> is required in coordinator mode; --record <slug> limits the tui-examples selection.
--max-records <n> defaults to 50 and must be 1–50.
--max-states <n> defaults to 200 and must be 1–5000; --max-depth <n> defaults to 4 and must be 0–12.
--worker and --artifact-uri are worker-facing options.

Output and state effects#

Coordinator mode submits the exact revision. Worker mode writes per-record evidence and target/spis-tui-crawls/<timestamp>/batch.json, may publish the run, prints the JSON summary, and errors if any TUI record failed.

Refusals#

These messages are emitted by the current Rust implementation:

--host is required; TUI crawls execute as pinned Stado jobs
--max-records must be 1..50, --max-states 1..5000 and --max-depth 0..12
--host cannot be used with --worker
--artifact-uri must be under stado://spis-crawls/tui-examples/
Unknown input is unknown argument: VALUE; a batch with failed records ends with N TUI records could not be crawled.