Local history and sensor checks

These commands work in Standard mode without ROS or a model connection. History is local. Task and retained-result files remain authoritative; the catalog indexes their metadata and records source changes explicitly.

flightops history import-task /path/to/task.json
flightops history import-results /path/to/retained-results.json
flightops history list --kind task
flightops history search delivery --scope task
flightops history show task:THE_TASK_ID
flightops history view -o /new/path/history.html

Use flightops history --database /path/to/catalog.sqlite3 … for a selected catalog. The default lives under the Flightops state directory. Lists accept exact project, robot, asset, unit, installation and attempt filters and a limit of 1–100. Search treats its text literally; --scope selects native, task, or retained authorities. JSON output includes source state at the last explicit import; reimport each original source to check for changes. The dark HTML view is an offline metadata snapshot with expandable details and no external assets; it never replaces an existing file.

flightops history put RECORD.json accepts a validated versioned native record. It records a historical claim; it cannot grant current authorization or turn an imported review into independent verification.

flightops history rebuild
flightops history backup /new/backup/directory
flightops history --database /new/catalog.sqlite3 restore /path/to/backup

Rebuild regenerates indexes from stored records and projections; it does not reread original source files. Native records and source-state labels survive. Backup includes an inventory of captured, missing, changed, or excluded evidence; payload inclusion requires explicit artifact selection and permitted source policy. Read the inventory before treating any backup as a complete evidence copy. Restore refuses to replace an existing database. See catalog behavior for authority and retention details.

flightops checks
flightops checks --context /path/to/observed-context.json

Checks report deterministic eligibility and missing prerequisites. They never execute, change parameters, start applications, or authorize actions. See the check context contract for evidence and scope inputs.

Selected recording backup and restore

flightops history backup /new/backup --include-artifact recording-segment:SEGMENT_ID
flightops history --database /new/catalog.sqlite3 restore /new/backup --include-artifact recording-segment:SEGMENT_ID

Each command independently selects and permits retention of those artifact IDs. A selected recording also needs its current catalog retain policy and every upstream source policy to allow retention. Use repeated --allow-source ID to express local current permission for a required upstream source. Neither flag changes a denied source policy. Omitting selection inventories recording payloads as excluded. Restore installs authorized copies under the new database's owned payload directory and never activates a backed-up collector service.

--max-recording-bytes and --max-recording-seconds can lower the bounded copy budget. Inspect all inventory dispositions: a successful metadata backup can still contain missing, changed or excluded payloads.