Maintenance

One backend owns collector/token SQLite storage. Reads use consistent snapshots; a serialized WAL writer commits evidence/receipts and projections atomically.

Reprocess saved evidence

tokeninsights data reprocess
tokeninsights data wait
tokeninsights data wait --connection ssh://you@devbox

Maintenance supports local/SSH only. Temporary TCP viewer credentials cannot run it. Reprocessing is explicit and keeps the published generation until replacement covers the latest accepted inputs. Restart resumes durable pending work.

Commands wait up to 30 seconds for visibility. If that expires, data wait continues waiting without another rebuild. Persistent processing_failed errors can be recovered with explicit data reprocess; published history, evidence and receipts stay intact. Processing failures never reset storage.

Backups

Close all viewers and temporary gateways; wait for the backend's final lease grace and shutdown. Back up collector.sqlite and server.sqlite with any remaining WAL/SHM companions. Restoring retained collector evidence can replay token projections; retaining token history protects usage whose original harness sources were deleted.

There are no application/account/jobs databases or pairing guards in current use. Former user files remain untouched. The redesign runs no migrations/imports and deletes no user files. Do not delete evidence to repair a processing error.

Incompatible storage

Current schemas: collector 20, SQLite token history 1. Role/path/physical contract mismatches and newer files reject without mutation. Only explicit older-local-store recovery asks for confirmation in a terminal:

TokenInsights needs to reset local storage written by an older version.

  collector.sqlite   schema 19 -> 20   reset
  server.sqlite      schema 1          keep

Old files move aside:
  /home/you/.local/share/tokeninsights/collector.sqlite.v19.bak

Usage is rebuilt from saved usage and harness logs.

Reset now? [y/N]

Affected files and WAL/SHM companions move to versioned backups, never deletion. Without a terminal, report the issue and change nothing. Owned/foreign/newer/ mismatched files block reset. Resetting both stores cannot rebuild usage whose native logs were deleted; preserve backups. No automatic schema migration exists.

Retired configuration

Old application/distributed settings, remote.endpoint and old endpoint/access environment variables return concise repair guidance without printing values or rewriting configuration. Edit/remove obsolete keys explicitly. Use --connection for invocation targets and --capture for launch capture. See commands for supported keys and paths.