Repository navigation
Clarify private-session cloud authority and local visibility - #19
Merged
Merged
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Clarify that private-session invalidation revokes cloud authority immediately while device-local visibility follows the host's explicit authorization policy. The previous guide prescribed hiding every host's local content; that prevented documenting an independently authorized local collection without changing the package's existing token/session guarantees.
Retain strict account-fenced cache guidance, including Apple TV without independent local authorization. Document original-owner retention, isolated selection on confirmed account changes, durable claims before unbound collection exposure, exact checkpoint provenance, and a nonautomatic first session for fetch-before-send reconciliation. No executable behavior, API, dependency pin, or package release changes.
Adopt agent-guidelines 0.0.51 from 0.0.48 in a separate commit; the synchronized tree exactly matches the central tag and the generated-file rule remains present.
Validation: 87 Swift tests in 15 suites passed on Xcode 27.2/Swift 6.4.2; DocC generated with warnings as errors; complete package format/lint, consumer integration, Markdown wrapping, and diff checks passed. The agent-guidelines audit confirmed unchanged compiler/dependency/logging boundaries, shared ignore patterns, package badge policy, and the registered ☁️ logging identity. Documentation scenario walkthroughs cover independently authorized local renewal, strict cache cold opening, sign-out/owner changes, and initial remote reconciliation. This is the package-contract portion of WortJagd #117; consumer activation and runtime acceptance remain separate.