Repository navigation
Add private non-Git snapshots and retained restore evidence - #110
Merged
Merged
Conversation
Open
5 of 25 tasks
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.
Outside Git, admitted Linux/macOS Locations now capture private BLAKE3 snapshots and use the existing reviewed CLI/TUI rewind flow. Restores preserve unrelated edits, refuse stale/conflicting plans, and durably retain intents and actual displaced preimages before native replacements. Snapshot-cap warnings keep conversation execution successful.
Integrated current main
913fe1b0, including merged #111's Ctrl+R history search, without conflicts. Its code, docs/specs and 1026-requirement inventory are retained. A combined TUI regression verifies search cancellation, snapshot warnings, draft preservation and subsequent Esc-Esc rewind.The original head failed Linux snapshot proofs/Rust because fsync received cap-std O_PATH directory descriptors. Sync now reopens the pinned directory for I/O, with an explicit Linux O_PATH regression. The macOS ARM proof reported a storage-lock acquisition failure; bounded short lock handoff/interruption handling now retains live-owner exclusion and distinguishes other errors. This retries acquisition before any restore starts, not source mutations.
Current integrated local macOS validation: two storage regressions, 17 file-copy cases, 12 Git snapshot cases, 11 rewind-filtered and nine history-search-filtered TUI cases (one overlap), three real non-Git CLI cases, ten additional parallel file-copy suite repetitions, workspace all-target Clippy with warnings denied, formatting/diff checks, generated SDK consistency and requirement inventory. OpenSpec 1.13.2 strict validation passed 115 items; spec lint reported 0 errors/25 warnings. The original increment also passed the OpenAPI artifact, SDK typecheck/128 tests (10 configured external skips), four server ownership tests and the complete 11-case CLI suite with serialized fixtures; an initial parallel CLI startup stall was recorded in implementation.md. Real terminal captures were visually checked. Native C deprecation/linker warnings were observed. Linux O_PATH execution is unavailable locally on this macOS host; fresh platform CI must pass on the corrected integrated head.
This implements task 3.1 and parts of 3.2–3.4 in #93. Managed keep/rollback resolution, native receipt acknowledgement and journal reclamation remain unfinished; retained records must not be removed to force retry. Git restore journaling, complete historical Git exclusions and broader crash/platform acceptance remain open. Windows file-copy writes remain explicitly unavailable. The daily-coding workstream and combined goal remain incomplete; remaining work is tracked in issue #93.