docs: align README with verified integration scope - #6
Merged
Merged
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
1 participant
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.
Change
Document the passed original Files UI/peer recovery trial, including exact source pins and preserved limitations. Correct the old pending-proof wording in README.md and docs/RECOVERY_WEB.md. Accounts, writable sync, sharing and full server independence remain open.
Scope and verification
Documentation only (2 files). Existing source-bound core evidence inspected; no runtime, permission, workflow or dependency changes. git diff --check passed and 8 local file/anchor references verified. No full application build for this documentation-only change; ordinary CI remains enabled.