Repository navigation
docs: reconcile demo-service privacy and collection disclosures - #329
Merged
Merged
Conversation
Owner
Author
|
Validation close-loop: all five reported CI checks reached success (PR docs/hygiene/PMSKit and push hygiene/PMSKit). Local canonical PMSKit tests (1,707), strict docs/links/Mermaid and hygiene tests (334) also passed. This remains a documentation/evidence PR, not closure of the remaining #325 retention, disclosure-exemption or account-owner approval gates. |
This was referenced Sep 16, 2026
jlipworth
added a commit
that referenced
this pull request
Sep 29, 2026
## Summary Consolidates the still-relevant work from `codex/store-demo-provenance` (`7f93e1ee`) and `codex/prerelease-disclosure-audit` (`a61eff14`) onto current main (`181b9431`). No app runtime changes. - Retain the public open-film/derived-artwork provenance snapshot and active capture/reviewer plan; distinguish fixture images from final store images. - Recheck official Blender license pages and Apple screenshot size guidance on 2026-09-29. Preserve historical catalog/hash verification dates and require a fresh deployed-asset check before capture. - Preserve merged #328/#329 privacy wording and archive-report gates rather than replaying stale text. Add the explicit #259 deferral and unchecked exact-candidate export/accessibility gates. - Keep the original disclosure audit as dated evidence, with a subsequent-disposition note. Remove current-sounding simulator/worktree assumptions from the capture plan and add it to the active-plan index. - Add a manifest consistency regression test; this verifies recorded metadata, not the remote asset bytes or legal clearance of eventual compositions. ## Validation - 10 screenshot tooling tests. - Strict MkDocs, rendered/source links, Mermaid, repository redaction and tooling hygiene. - Hermetic PMSKit tests (live probes excluded). - Official source-page verification; no new film download or deployed-server checksum audit. No simulator, live playback, infrastructure changes, account edits, uploads, version changes or physical-device acceptance. No final screenshots produced. No new native build required: docs/spec/test changes only. ## Remaining scope Related #92, #259, #280, #325, #326; this PR closes none of them. Final captures, storefront credits/editorial review, age suitability, exact-candidate reviewer journeys, signed-archive privacy reports and owner-approved account answers remain open. The source branches/worktrees are preserved until this consolidation is reviewed and merged; this PR does not remove them.
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
Related to #325, #280 and #92. Does not close #325: database cleanup/expiry, centralized/edge retention, backup coverage, privileged-access review, final candidate manifests and owner-approved App Store Connect answers remain open. #326 required-reason API work is separate.
Evidence boundaries
Live route access logs are disabled; Jellyfin warning logs have a three-file daily/size rotation (three files observed). The daily reset clears catalog progress, not auth/activity/log/backup data. Loki declares 30 days but deletion enforcement was not established. Config-volume backup status is recent; configured copy counts are not maximum-age guarantees. Source-described Velero schedules were absent from the live schedule list. The audit records each limitation rather than treating settings as deletion proof.
No runtime or manifest changes. No service configuration, credentials, resets, playback/transcodes, App Store Connect answers, legal declarations, versions, uploads or releases were changed. No private endpoints, credentials, user rows or raw logs are included.
Validation
--no-parallel --skip 'Live.*ProbeTests').scripts/ci-hygiene.sh: passed, 334 tooling tests.git diff --check: passed..simidwas absent; no simulator was created. Own-worktree teardown confirms none to remove.Approval gates
Before certifying collection answers, the owner must verify actual auth/device/activity expiry and aggregate ages, centralized-log deletion, edge/provider records, backup inventories/downstream copies and access; confirm received support-data purposes/retention; review the mapping against the exact archives/current account state; and authorize any account or manifest edits separately. This PR improves current wording without representing those gates as complete.