Repository navigation
Conversation
Since SUB-1333 the Idempotency-Key ledger, sessions, and blueprints live in SQLite, but the server help, volume-guard reasons, book pages, and the idempotency smoke script still described the file-backed ledger. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
SUB-1333 moved the
Idempotency-Keyledger into SQLite, and sessions and blueprints already lived there. But the--session-store-dirhelp, the volume-guard reasons, several book pages, andscripts/idempotency-smoke.shstill described the file-backed ledger and treated the session directory as live storage.session_store_dirandblueprint_diras one-time import sources that move toarchive/.database_pathand says to back up its directory, including the WAL file, while the server is stopped.~/.submilli/server/db.Fixes SUB-1745
🤖 Generated with Claude Code
Main integration preserves the unified volume directory layout and refreshes existing AI-assisted authorship hashes. The smoke check now installs a temporary local package before Blueprint validation, removes it to test pre-dispatch failure, and checks the current
runsschema, disconnect handling, and retained evidence after session deletion. Same-repository source links are checked against the checkout to avoid the observed GitHub 503 failures; missing-link fixtures remain enforced.Validation: Rust formatting, workspace Clippy, shell syntax, and the normal idempotency smoke checks passed using local mock HTTP only. Ten smoke cases passed; the optional slow waiter check was not run, and the unwritable-ledger case remains covered by existing in-process fault tests. Independent clean-code, correctness, and edge-case review completed, including focused review of the final smoke adjustment. Current-head CI is running.
Analytics impact: none; factual storage wording and build-time checks do not change routes, forms, tracking hooks, or event contracts.
After deployment: PR author verifies the updated storage reference pages. Existing authorship labels are preserved; human editorial requirements still apply before publication.