CLI reference / product

stado product

Invocation

stado product [OPTIONS] <COMMAND>

Purpose

The Wisent product catalog: install, update, sign and build every product surface

Required inputs and options

Output and state effect

This command group selects one of the subcommands listed below; use its exact child invocation to perform an operation.

Refusals

• Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.

Subcommands

• catalog — Read and validate the authoritative Wisent product catalog
• dependencies — Read from each product's source every call it makes to another catalog product (program, resolver, hosted API, state directory, environment) and refuse a product the catalog does not show running without it: a dependency undeclared, declared with no alternative (bound; by design when the catalog says why in bound_because), or with no alternative_source in the workspace
• registry — Mutate the authoritative product registry without replacing neighboring records
• create — Provision private repositories and a preview product through Wisent Integrations
• install — Install one product surface from its canonical recipe or exact qualified release
• update — Update one product surface while retaining exact rollback bytes
• finish — Finish, with this binary, an installation whose build an install retained after its quality gates and build passed: sign, stage, place and activate it without building again. An installation of the running Stado hands its built Stado this step; a revision with no retained build is refused
• status — Inspect recorded installation, source, signatures, actual readiness and the operation holding its lock, with its step
• remove — Remove only owned paths and the declared service surface
• rollback — Restore exact retained installation bytes without rebuilding
• locks — List every product surface lock, its recorded owner, process identity, observed state and corruption
• sync — Reconcile installed surfaces against canonical origin/main
• signing — Inspect and preserve stable Apple native code identity
• paths — Inspect actual executable ownership: PATH collisions and executables in ~/.stado/bin and ~/.local/bin no installed product owns
• cargo — Run Cargo against canonical checkouts or declared release-worker source inputs
• compiler-cache — Report, install or remove the compiler cache (Kache) every Cargo build Stado runs goes through
• build-trees — List or remove the rebuildable trees in the workspace's checkouts — CACHEDIR.TAG directories, Stado's former install runs, desktop .build — from this process
• node-runtime — Report or install the Node.js release every Node product build Stado runs uses
• source-bundle — Release build step: the checkout's files in a reproducible $WISENT_OUTPUT_DIR/release/<name> with each file's digest, and release/SOURCE_REVISION from $WISENT_SOURCE_COMMIT when it is set
• python — Release steps of a Python product: its wheel and sdist, their PyPI upload, or a zip application
• npm — Release steps of an npm package
• schema — Release steps of a database-schema product on any engine: sqlite, postgres or supabase
• deliver — Release deliveries to hosting providers, run by a manifest's deliveries
• linkage — Prove each .app bundle's @rpath dependencies resolve inside it, as dyld resolves them
• crx3 — Pack a browser extension directory as a signed CRX3 and its Omaha update manifest, refusing a key whose extension id is not the pinned one
• tree-archive — Pack one directory, under its own name, as a reproducible .tar.gz: path order, no owner, time zero, modes 0755/0644, links kept
• swift — Build and index canonical Swift sources or restore release dependencies
• editor — Serve editor build settings or inspect live workspace instances
• surface — Refuse a Swift package revision whose version tag disagrees with what it did to the library's public API, as swift api-digester reads it against the released tag
• documentation — Check actual published documentation and GitHub repository policy, or generate a documentation site's search index
• changelog — Move CHANGELOG.md's Unreleased entries into changelog/: as the given release in the version-bump commit, or as spilled parts while the release is prepared