CLICommands
spec0 sync-status
Check whether a spec needs republishing (compares git SHA to last published).
Auto-generated from
spec0 commands --output=json. Do not edit by hand — changes are overwritten bynpm run sync:cli-docs.
Usage
spec0 sync-status [ref] [options]Arguments
| name | required | description |
|---|---|---|
ref | no | API reference: <org>/<name>, <name>, or UUID |
Flags
| flag | description | default |
|---|---|---|
--git-sha <sha> | Git SHA to compare against (default: HEAD of current repo) | |
--api <name> | API name (alternative to positional ref) | |
--api-id <uuid> | API id (alternative to positional ref) | |
--org <uuid> | Org id override | |
--output <format> | Output format: text, json, or yaml (default: text) |
Exit codes
Stable contract — branch on these from CI and agents.
| code | meaning |
|---|---|
| 0 | success |
| 1 | generic / unclassified failure |
| 2 | usage error (bad flags, missing args) |
| 3 | not authenticated (no token / token expired) |
| 4 | permission denied (403) |
| 5 | resource not found (404) |
| 6 | conflict (409 — e.g. name already taken) |
| 7 | validation failed (422 — e.g. spec below min score) |
| 8 | rate limited (429) |
| 9 | upstream server error (5xx) |
| 10 | network error (unreachable, timeout) |