saphan verify-deploy
Verifies a deployment end to end and reports PASS only with proof for every step: it records the artifact's digest, builds, checks that the digest changed, runs the rollout, then requires the live hea
Verifies a deployment end to end and reports PASS only with proof for every step: it records the artifact's digest, builds, checks that the digest changed, runs the rollout, then requires the live health URL to answer with a 2xx status. ⚠ The rollout is real: this command performs the deployment it verifies. A failed step stops the pipeline with the verdict STOP (exit 2), and the remaining steps are marked skipped. Commands and the URL come from flags or from a project configuration file named with --config; flags win. Each command is split into words (quotes respected) and run directly, not through a shell, so pipes and && need a script.
| flag | type | default | what it does |
|---|---|---|---|
--build-cmd | string | The command that builds the artifact (required, here or in the configuration file). | |
--config | string | A YAML project file whose verify-deploy: section can hold any of these settings; flags override it. | |
--digest-cmd | string | A command that prints the deployable artifact's digest, run before and after the build; an unchanged digest stops the check, while a failure before the build is read as no prior artifact (required). | |
--health-expect | string | Optional text the live health response must contain. | |
--health-url | string | The URL that must answer with a 2xx status after the rollout, the live proof (required). | |
--rollout-cmd | string | The command that performs the rollout (required). | |
--workdir | string | The directory the commands run in. |
Global options apply to every command — see Every command.
saphan verify-affected
Runs a fast, advisory check of what changed between --base and --head: the changed paths are handed to the test adapter configured under [verify.affected], which selects and runs the affected packages
saphan verify-stream
Runs a fixed, deterministic check of a Go stream's local worktree — go build, go vet, go test and gofmt, each step even after an earlier failure — with no language model involved, and stores the verdi