Expand description
opys query — run SQL over the live corpus store.
Read-only by default: a plan-guarded SELECT (nothing else can execute), and
the command never flushes, so the files are unreachable. With --write,
INSERT/UPDATE/DELETE run against the store, the normal sync pass reconciles
and relocates, and the result is validated with verify — the files are
written only if verify passes. So a raw SQL edit gets full power but can
never leave the inventory in a state the CLI would reject; a corrupting edit
changes nothing on disk (the store mutation is in-memory and simply not
flushed).