Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Command overview

All user-facing operations go through prqnt. Global flag:

  • --json — JSON output where the command supports it (errors may still print JSON when --json is set).

Exit semantics

CodeMeaning (typical)
0Success
1Operational / usage error
2Findings or policy violations (check, some repair gates)
3Blocked repair (safety / authorization)
4Stale plan or fingerprint mismatch
5Internal or I/O failure

Exact behavior is covered by CLI integration tests; do not rely on undocumented codes.

Capability map

Command groupPurpose
scanForensic dataset scan (local or s3://)
inspect, rewrite, convertDirect Parquet/CSV utilities (not routed through parqonaut-app)
diagnose, plan, plan-diff, check, repair, verify, doctorRepair and schema workflows via parqonaut-app
batch *Multi-dataset orchestration via parqonaut-app
serveHTTP application server and durable jobs

When to use which command

  • scan — inventory, findings, dataset identity; input to planning.
  • doctor — interactive CLI path: scan + diagnose + plan (optional repair). Not a separate HTTP job in v0.7.
  • plan / repair / verify — durable, evidence-bound repair pipeline with separate output locations.
  • check — CI gate; non-mutating.
  • batch plan|repair|resume|verify — fleet operations with journal and resume semantics.
  • serve — automation, remote operators, async jobs.

Generated reference

Flag-level detail is generated from Clap to avoid drift: