* Phase 0: SQLite game history design doc
Per-game game.db replaces .e0a / .e0s / .e0i file-based persistence.
SqliteHistory implements the existing FullGameHistory trait so the
cutover at the call site is a single constructor swap.
Schema, connection lifecycle, read/write paths, snapshot strategy,
shardok results layout, migration trigger, rollback policy, and four
open questions called out for sign-off before Phase 1.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
* Phase 0: fold in user feedback — drop migration, separate DBs rationale
- Remove the migration importer entirely. At cutover we nuke save
directories one time; pre-alpha trade-off accepted explicitly.
- Add the writer-lock-contention rationale for keeping game.db and
text_store.db as separate files instead of one combined DB.
- Lock in the four open questions with the agreed defaults.
- Note the GameAdminServiceImpl.getActionDetail follow-up to move off
history.all; not blocking.
- Phase plan drops from 5-6 weeks to 3-4 weeks with migration gone.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
