Claude 7d527bdce3 feat(geode): let operators pick any quartz IEventStore backend ...

Geode hard-wired the SQLite EventStore. Add a `[database].backend`
selector (and `--store` CLI flag) so an operator can choose the store
implementation:

  - "sqlite" (default): the SQLite EventStore, unchanged.
  - "fs": quartz's filesystem FsEventStore, rooted at [database].file.
  - any other value: a fully-qualified class name of a custom
    IEventStore on the classpath, instantiated reflectively via one of
    `(NormalizedRelayUrl?, IndexingStrategy)`, `(NormalizedRelayUrl?)`,
    or `()` — the "plug in anything" escape hatch.

Store construction moves into a new StoreFactory (mirrors cli's
StoreFactory) shared by the serve path and the import/export verbs, so
both open the same store from the same config. The SQLite-only
`PRAGMA optimize` maintenance loop now runs only when the resolved
store is the SQLite one.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GG3TBvLUv5uB5js1naG5sc

2026-07-24 16:15:21 +00:00

..

plans

docs(geode): SQLite knobs A/B verdict — no winner, knobs stay off by default

2026-07-04 00:50:37 +00:00

src

feat(geode): let operators pick any quartz IEventStore backend

2026-07-24 16:15:21 +00:00

build.gradle.kts

test(geode): benchmark deletion-settle cost is O(residual), not O(database)

2026-07-08 15:19:30 +00:00

config.example.toml

feat(geode): let operators pick any quartz IEventStore backend

2026-07-24 16:15:21 +00:00