Implement ProjectData terminal archive-sharding bridge - #1983
Conversation
|
Warning Review limit reachedNext included review available in 36 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (68)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
|
@coderabbitai review |
|




Summary
Implements the Fable-approved ProjectData terminal archive-sharding bridge from
tasks/active/2026-08-31-projectdata-terminal-archive-sharding.md.last_message_at), comments, lifecycle/control state, and rejects unsafe late writes/wakessql.databaseSize, and the unsafe-deploy routing guard01M1CZT4PEWX62RS4V95DT48YSfor active-session SessionData direct ownershipMigrations
0132_project_data_terminal_archive_sharding.sql0133_project_data_archive_recovery_cursors.sql043-projectdata-terminal-archive-sharding044-projectdata-archive-paged-manifestsAll migrations are append-only. Archive sharding remains production-disabled by default and fails closed.
Validation
Safety / review state
DRAFT — DO NOT MARK READY OR MERGE.
No staging or production deployment occurred. No production configuration was changed. No production migration, cleanup, enablement, or raw transcript/message deletion was run. The coordinator remains explicitly disabled unless
PROJECT_DATA_ARCHIVE_SHARDING_ENABLED=true.The remote commit is a connector-published exact tree snapshot of reviewed local head
3341e54616f0d746204d6eba18a323025ff50843; its tree SHA isff3fd6823ba96dd6d43a7eaa53269c34e44951e6.