Repository navigation
feat(persistence): Compact release databases - #88
Merged
Merged
Conversation
Archive complete daily rating records in bounded compressed groups. Validate saved payloads before removing source rows, and resume from durable checkpoints after interruptions. Prune unused internal history and compact stores during coordinated release startup. Keep charts, exports, MCP reads, and corrections able to access every historical observation.
Repack large stores with 16 KiB pages and prefetch live rating links. Prepare persistence off the UI thread and show startup progress. Verify that history survives compaction and WAL reopening.
hubab1
force-pushed
the
codex/release-storage-compaction
branch
from
October 24, 2026 22:36
0995441 to
20f8ca4
Compare
hubab1
marked this pull request as ready for review
October 24, 2026 22:37
Archive prior days during ingestion and update older days in place. Keep the existing-data migration complete after its first successful run. Serialize worker transactions to preserve concurrent archive edits.
Reject shared clients until migration finishes and validate every saved archive before replacing it. Defer disk-full compaction without hiding corruption errors. Keep the pending flag so a later launch can retry safely.
Recognize SQLite error codes carried in Core Data error metadata. Keep corruption fatal and preserve history during a compaction retry.
Keep past ratings when providers report missing or mismatched storefronts. Make explicit clearing atomic across live rows, archives, and summaries. Read only required history chunks under a shared writer lease. Defer unused archive fetches and expose migration progress and read errors.
hubab1
changed the base branch from
codex/keyword-navigation-performance
to
main
October 26, 2026 21:22
5 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Why
Repeated ratings and internal framework changes inflated release databases. Automatic storefront cleanup also erased valid history, while small history responses decoded lifetime data. Compact ingestion and coordinated reads preserve historical dates and values without recurring archival scans. Merge #87 first.