volter-ai/ztrack-check

Run ztrack as a CI gate

Trust Signals

name	description	required	default
working-directory	Directory containing the .volter tracker config	—	.
root	Path to a committed validated root (the JSON written by `ztrack export`, shape { "issues": [ ... ] }). When set, ztrack validates this root instead of reading a live tracker store (commit existence is verified by default). Recommended for CI because a fresh checkout does not preserve the local tracker store. This does NOT change which preset executes — see `preset` below and SECURITY.md for the fork-PR-safe combination. (If you have an old `.volter/snapshot.json` from a previous ztrack version, re-run `ztrack export` to regenerate it as a validated root.)	—	""
preset	Path to a validation preset module to load INSTEAD OF the checkout's configured .volter/tracker/validation/preset.mts (forwarded as `ztrack check --preset`). Unconfined to `working-directory` — point it at a preset from a checkout you trust (e.g. the base ref in a pull_request_target workflow) so an untrusted PR head's edited preset.mts never runs on your runner. See SECURITY.md.	—	""

no outputs