Repository navigation
docs: clarify Screen Recording recovery after ad-hoc upgrades - #7
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
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.
ScreenCaptureKit can deny capture with
-3801while ContextLens still appears enabled in macOS Settings. Document the successful manual macOS 26 recovery: remove only ContextLens from the upper Screen & System Audio Recording list, add/Applications/ContextLens.appagain, enable it and relaunch.Add a prominent recovery link under README Get started. Expand the existing troubleshooting guide with the normal first-time grant flow, an eight-step recovery procedure, the distinction from the separate System Audio Recording Only list, and a capture-based success check. Explain that an ad-hoc upgrade can lose authorization even with one installation. Keep the technical guide in
docs/permissions.mdunchanged.Only
README.mdanddocs/troubleshooting.mdchange. Both already have regular-file exemptions in the unchanged release-input freshness policy;docs/permissions.mdis also exempt and unchanged. The actual protected-input identity is identical before and after this commit:7903bf47ef0c274bc25493250aa7a450037c3d1997545cbe1f1f771a80a7a0e6(514 protected files). The existing freshness checker accepts the documentation-only descendant of main. This proof does not alter or attest to candidate artifacts.Validation: local links, all five documentation tests, all 14 official-channel/freshness regression tests and staged publication audit passed. Full CI and Publication Security passed on
be9fccc8e703400a152d325b59feafea631a2586. Independent pinned Gitleaks 8.30.1, current-tree and full reachable-history audits also passed with zero findings.Swift code, signing, packaging, permission behavior, version metadata, release safeguards and acceptance records remain unchanged. No private screenshots, logs, certificate identities or internal engineering reports are added. The existing official candidate is untouched. No automatic merge or publication is included.