You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jud --replay DIR RUBRIC, or JUD_REPLAY=DIR, answers from the recordings
under a directory through the crate's Replay backend instead of a server:
no key, no network, a state nobody recorded is an error. The README's
command-line transcript runs this way over examples/recordings/ and tests/jud_cli.rs holds it to what the binary prints.
docs/stability.md: what is promised across versions. jud/v1 is stable, a
minor version only adds, readers accept every v1 document for at least
twelve months after a later minor is published, fingerprints exclude the
envelope and never change for a document's spec; the crate's 0.x rule and
the command's contract.
Decision 0020, proposed and not applied: whether a v1 minor stays in the apiVersion string or moves to a minor field under apiVersion: jud/v1,
each option priced.
scripts/record_demo.sh (mise run demo) records the command-line demo as
an asciinema cast, docs/demo.cast, from the recordings, with no network;
regenerated by the release bump so the version it shows is the release's.
mise run ci is an alias of mise run check, the gates in CI order.
Changed
The README opens with the command line for 0.10: a one-line pitch, the mise
install, the cat event.json | jud triage.jud transcript with the verdicts
the binary prints for examples/jud/triage.jud, then the Rust API; one
comparison table of the four properties where the clients differ, the full
grids linked; the live example's capture trimmed to the command and its
output.