Session Database Debugging

Every Capsem VM session produces a ledger in its session directory: ~/.capsem/run/sessions/<id>/ for an ephemeral VM, ~/.capsem/run/persistent/<name>/ for a named one. The ledger is two files that only make sense together:

• session.db -- SQLite, every telemetry table plus the index of captured bodies.
• session.bodies -- the append-only body archive: HTTP, model, tool, exec and security payloads, deflated in blocks of about 1 MiB. SQLite never holds body bytes.

Copy, fork or delete them as a pair; either one alone is useless. A global ~/.capsem/sessions/main.db aggregates stats across sessions.

The session ledger has no migrations. A session.db written by an older build fails to open, loudly and by name, rather than being upgraded in place.

Session identity invariant