Repository navigation
docs: refresh public presence and App Store drafts - #45
Draft
codepilotios wants to merge 5 commits into
Draft
codepilotios wants to merge 5 commits into
codepilotios wants to merge 5 commits into
Conversation
codepilotios
changed the title
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.
Summary
Why
Public copy said uploads lacked automatic cleanup even though the gateway removes expired upload batches at startup and before saving another upload. The local App Store metadata also retained placeholder URLs after the canonical candidates were documented elsewhere. The live repository audit remains blocked on maintainer-controlled settings, so the escalation record keeps the current verification date and exact scope.
Impact
Beta users get consistent retention wording, and maintainers get submission-ready local metadata and safer screenshot guidance. Repository-setting follow-up remains in #27. This draft PR does not change GitHub settings, publish Pages, upload metadata, submit a build, alter legal terms, or release anything.
Verification
scripts/public-presence-audit.shscripts/privacy-audit.shscripts/tests/privacy-audit-test.shscripts/tests/public-presence-live-audit-test.shscripts/public-presence-live-audit.sh(expected failure: seven maintainer-controlled live-presence findings)