ROADMAP: JSONL export compatibility for SQLite storage backend

[jpleva91]

Source

• Type: ROADMAP
• Location: ROADMAP.md:295 (Phase 10 — Structured Storage Backend)
• Original text: JSONL export compatibility — agentguard export still produces portable JSONL

Task Description

When the SQLite storage backend (#169) replaces flat-file JSONL as the primary persistence layer, the agentguard export command must continue to produce portable JSONL files. This ensures backwards compatibility for users who share governance sessions across teams, import into external analytics tools, or archive sessions outside the repository.

Implementation should include:

• Export adapter: Wire agentguard export <runId> to read from SQLite and emit JSONL with the same schema as today's .agentguard/events/*.jsonl files
• Round-trip guarantee: A session exported from SQLite and re-imported via agentguard import must produce identical event sequences
• Schema stability: The JSONL export format becomes a versioned contract — document the schema in docs/ and add a version field to exported files
• Integration with existing export/import commands: Update src/cli/commands/export.ts and src/cli/commands/import.ts to support both storage backends transparently

Related issues: #169 (SQLite adapter), #170 (Schema design), #171 (Migration utility), #172 (Query API), #202 (Aggregation queries), #203 (JSONL fallback)

Labels

Created automatically by the Backlog Steward skill.

---

Discovered by backlog-steward on 2026-03-11T00:00:00Z