Invocation#

bash

spis crawl-cli --host <target> [--record <slug>] [--journeys <file>] [--secret-env <NAME=SKARBIEC_ITEM>]... [--max-commands <n>] [--max-depth <n>]

Crawl installed command-line products in a real isolated PTY on a pinned Stado host.

Inputs and options#

--host <target> is required in public coordinator mode.
--record <slug> limits the crawl to one cli-examples record.
--journeys <file> supplies declared non-destructive journeys; --secret-env <NAME=SKARBIEC_ITEM> may be repeated for Stado-injected secrets.
--max-commands <n> defaults to 250 and must be 1–5000; --max-depth <n> defaults to 4 and must be 0–16.
--worker and --artifact-uri are worker-facing execution options shown by command help.

Output and state effects#

Coordinator mode submits the exact Spis revision to Stado. Worker mode writes per-product crawl evidence plus target/spis-cli-crawls/<timestamp>/batch.json, optionally publishes that run under stado://spis-crawls/cli-examples/, prints the batch JSON, and fails if any record failed.

Refusals#

These messages are emitted by the current Rust implementation:

--host is required; CLI crawls execute as pinned Stado jobs
--max-commands must be 1..5000 and --max-depth must be 0..16
--host and --secret-env are coordinator-only in worker mode.
--artifact-uri must be under stado://spis-crawls/cli-examples/
Unknown input is refused as unknown argument: VALUE; a completed batch with failures refuses with N CLI records could not be crawled.