Expand description
astrs validate [--prove] (blueprint §17).
Runs the full pipeline a manifest goes through before anything is
spawned — parse, structural validation, module expansion, structural
validation again on the flattened result, graph construction, graph
diagnostics — and reports every observation found along the way as
one flat, ordered CliDiagnostic list, stopping early only when a
later stage would be meaningless (there is nothing to expand from a
manifest that never parsed).
Exit code convention (blueprint §17): 0 clean, 1 warnings only,
2 any error — see crate::diagnostic::exit_code_for.
§--prove
With --prove, the graph is additionally handed to astrs-verify,
which discharges the obligations of blueprint §15 through an SMT solver
and returns a VerificationReport. Its results fold into the same
exit-code scale rather than inventing a second one:
- a refuted obligation is an
Severity::Errordiagnostic, so the command exits2— a graph proven to deadlock is not a warning; - an obligation that reached no verdict (a missing service time, an
undecided solver run) is a
Severity::Warning, so the command exits1. “Nothing failed” and “everything was proved” are different claims, and the exit code says which one this run earned; - a build without the
verifyfeature still encodes and prints every obligation, then returnsCliError::ProofUnavailable(crate::error::EXIT_UNAVAILABLE,69), so a script can tell a missing solver from a failed proof by exit code alone.
Structs§
- Validate
Args - Arguments for
astrs validate. - Validate
Report - The result of validating one manifest.
Functions§
- run
- Run
astrs validate, writing a human or JSON report toout.