CLI command
probierz stado author
Author and verify one product-owned journey on a Stado host, then return its accepted bytes to the exact submitting checkout.
Invocation#
probierz stado author [APP_ID] [JOURNEY]Required inputs and options#
- `<appId>`, `<journey>`, `--target`, and `--desc` are required.
- `--host` defaults to `stado:gcp`; `--no-watch` returns after accepted submission while retaining the source-bound recovery receipt.
- `--app-binary-path <file> --app-repo <path>` is available only for TUI authoring. It gives the remote authoring loop an immutable executable and exact committed source without invoking Cargo during provisioning; a candidate product spec may still run its own declared commands.
- The selected surface's `testDirectory` defaults to `tests`. Set `surfaces.tui.testDirectory: stado-rs/tests` to keep a Rust product's accepted spec under `stado-rs/tests/` while `--app-repo` still names the complete committed repository.
Output and state effects#
The worker verifies the staged product through the normal Probierz runner and returns reports plus a receipt-bound copy of the accepted bytes. Collection installs those bytes in the product-owned test location in the original submitting checkout, recreates the toolkit registration using local paths, preserves the local manifest repository root, and returns the accepted spec, registration, manifest, authoring receipt, and source receipt. The source receipt also retains the selected test directory, which must still match the local manifest before collection can install files. `stado collect` and `stado resume` reuse that receipt after an interrupted watch without deleting previously collected reports.
Exact refusals#
- Missing app/journey, target, or description is refused with an exact `stado author needs …` error.
- An accepted path outside the selected product test directory, receipt bytes/path/source identity that do not match submission, recovery in a checkout without its source receipt, or a checkout changed after submission is refused before publication.
- A TUI target requires an installed command, immutable native executable with `--app-repo`, or Cargo-release application source; unknown options, unexpected arguments, valueless flags, mutually exclusive provisioning modes, and remote/authentication failures are refused.
Source snapshot#
Generated from the Rust binaries at https://github.com/wisent-ai/probierz.git revision `c589d6917201c31f57e6a7f24522c0d50ae5bd0f`.
Combined help SHA-256: `43f0d9cd136ac2c46ec3eedb2824bd5d6168f235dea4caaa50610c005f40c84a`; binary SHA-256: `7e42c843082863ed265817de90a110a2f27546426a54d372e10009fd665a4d8e`.