Repository navigation
docs(quality,e5): a security page listing a gap the page it links to had closed - #120
Merged
Merged
Conversation
…had closed Two records disagreeing about one check, and a third describing an absence that is now only partly an absence. 40-quality/security.md carried "Mobile backup exclusion" under Known outstanding items, saying whether the iOS exclusion covers the file the app actually opens was an open question — and linked, for that claim, to the E5 section that had settled it on 2026-09-06. A re-check named the path, read the flag back per node rather than trusting the write, and reported `flagged=7 unflagged=0` against Documents/persisted_data on an iPhone 12 mini. The row pointed at its own answer for eight days. Removed with the reason kept rather than quietly deleted: a security page that overstates a gap is read exactly as carefully as one that understates one. E5's Android note said nothing records the same passes on Android. Two Android hardware runs have happened since and are recorded in the product repository: E5-R10 closed on a Galaxy A51 on 2026-09-09, and E2-R23 and E5-R28 walked on the same handset on 2026-09-13. Neither is one of the three gates, so the note stays — narrowed to the two that really are unrecorded there, the local-notification banner and the two-device pairing UAT. The backup exclusion is app-wide on Android and reaches every release build by construction. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Wessel Verheij <info@nightworks.io>
|
github-actions
Bot
added
the
awaiting-maintainer
github-actions
Bot
added
awaiting-maintainer
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.
One check, two records, opposite answers
40-quality/security.mdlisted Mobile backup exclusion under Known outstanding items:The link in that sentence points at the E5 section which says, in its own words:
That re-check targeted
Documents/persisted_data, walked it with an enumerator, read the flag back per node rather than trusting the write, and reportedflagged=7 unflagged=0on an iPhone 12 mini — with the developer console independently showing that store'sdatabase.sqliteat 2,637,824 bytes, which is what rules out the empty 4 KB stub the earlier check may have read.The row pointed at its own answer for eight days.
Removed with the reason kept rather than quietly deleted. A security page that overstates a gap is read exactly as carefully as one that understates one, and this is the second record on that page to have lagged the feature page it cites.
And one absence that is now partly filled
E5's Android note said "Nothing here records the same passes on Android." Two Android hardware runs have happened since, recorded in the product repository rather than on that page:
E5-R10async cold-start recovery signalE2-R23+E5-R28device walkNeither is one of the three gates, so the note stays — narrowed to what is genuinely unrecorded on Android: the local-notification banner and the two-device pairing UAT. The backup exclusion is app-wide there and reaches every release build by construction rather than by a device run.
manifest_check.pyandintegrity.pyboth clean.