test: forward HNSW sidecar failure and recovery witness - #7
Draft
RecursiveIntell wants to merge 1 commit into
Draft
RecursiveIntell wants to merge 1 commit into
RecursiveIntell wants to merge 1 commit into
Conversation
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.
Scope
Dependent on draft #6. Forward-sync
tests/storage_lifecycle.rsfrom the editable Libraries owner at0b099ec416de60f6adafb182f1d1e83795d05c56; the complete test-file blob matches that owner. The new test deliberately obstructs the local HNSW graph-file path, verifies the SQLite fact remains readable and the pending index operation records a failed attempt, then removes the obstruction and verifies an explicit flush clears pending work and writes the graph file. Add paired-root CI commands for strict Clippy and the fourstorage_lifecycletests under hnsw-only. No production-source change.Evidence
Limits and rollback
This is a deterministic local sidecar-write obstruction with same-process explicit recovery. It does not simulate a process crash/restart or prove ClaimLedger append-to-projection recovery, broad durability, whole-mirror parity, or release readiness. Roll back by closing this dependent draft or reverting the exact two-file commit; do not copy dirty overlays, merge, or activate by implication. Public Evidence Editor and LongMemEval reviewed the narrow candidate at
/home/sikmindz/semantic-parity/semantic-memory-sidecar-review-20260928/.