Repository navigation
Publish encrypted local workbench and file-management workflows - #55
Merged
Merged
Conversation
Add explicit encrypted startup, adoption and recovery with native-owned custody. Preserve readable-export boundaries and current platform qualification limits. Publish instruction history, bounded file discovery, Markdown review and exact saved-revision compilation continuity. Retain newer public integration modules and keep historical recovery source unmounted.
Release the journal lock when custody ends, including when a duplicate descriptor survives. Preserve active-owner refusal and cover the lifetime with a deterministic regression. Resolve Windows SQLCipher build inputs explicitly and keep unsupported capture revalidation fail-closed without a redundant cfg closure. Record local validation and independent review; require replacement three-OS CI before main.
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.
Publish the complete local capability workbench: encrypted startup and recovery, instruction-history persistence, bounded Agent files and Markdown review, and exact saved-skill continuation into Compile. Reconcile the authored snapshot onto public main while preserving the independent VUSL direction and both newer LNSAT offline inspection modules.
Changes
Validation
Exact head:
f3b1c29c5c050e195e96de780b93ab61504543bd.All seven jobs pass in both the pull-request matrix and branch matrix: portable Rust and encrypted desktop source checks on macOS, Windows and Linux, plus preview/review artifacts. Formatting, tests, warnings-denied Clippy and native development builds pass; no installer is produced.
Local evidence:
No failed checks were waived. The development ledger retains initial failures and the reviewed corrections.
Boundaries
Source publication only. Windows encrypted startup/recovery remains unsupported despite successful source builds; Linux GUI/custody and current-artifact native workflow qualification remain open. Readable originals, deliberate instruction exports and separate recovery key files retain their confidentiality disclosures. Live providers, remote transport, scheduling and agent execution are not activated.
No executable release, normal workspace/key/vault access, website deployment or LNSAT/VUSL repository edits. All 247 original snapshot paths remain unchanged. The final diff contains 248 authored regular files, with no symlinks or deletions, and excludes build outputs, app data and private raw evidence.
Next: a fresh isolated native folder-picker and complete local editing/compilation/recovery qualification. Exact evidence and remaining limits are in
docs/development.mdunder the October 29 full application source publication receipt.