V2 pre-beta audit: event names, table schema, and migration-sensitive data #34832

Summary

Run a focused pre-beta audit of V2 event names/versions, database table schemas, and migration-sensitive records before user data starts accumulating.

Why

Release-prep discussion flagged these as expensive to change after beta users exist:

• event names and versions
• table schemas
• migration-sensitive data
• v2 event suffixes that may not need to become durable API/history
• storage/system-context work from the rapid iteration phase

Scope

• Review V2 event names and versioning for durability/backcompat risk.
• Review table schemas for fields that will be hard to migrate later.
• Review system-context / synthetic-message records for migration and replay safety.
• Identify anything that should change before beta, versus items safe to migrate later.
• Produce a short checklist/outcome comment before closing.

Related work

• V2: define protocol/schema boundary for API payloads #34362 — protocol/schema boundary
• V2: route progressive AGENTS.md through durable Instructions #34341 — progressive AGENTS/system-context loading
• V2 TUI: follow-up prompts should render optimistically #34766 — follow-up prompt timeline rendering (session/event projection implications)
• feat(tui): add configurable sidebar width #34830 — V2 beta storage/database isolation

Source

Discord V2 TODO LIST discussion: https://discord.com/channels/1391832426048651334/1520962938733723720