Preserve reviewed replacement photo across saved-photo removal (#633) - #634
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
12 tasks
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.
Closes #633
Officer impact: In the preserved future My Account interface, removing the current saved photo no longer silently discards a separate replacement the person is reviewing. The action is explicitly named Remove current saved photo, and keyboard focus returns to the current Remove action, ready Save action, or persistent file input. This connected interface remains unavailable.
Officer documentation: Updated
SYSTEM_DESIGN.md,IMPLEMENTATION_PLAN.md,SECURITY.md, and the optional-directory Mermaid, one-sentence text alternative, and no-terminal source-evidence procedure indocs/officers/EVENTS_SHOP_MEMBERS.md.Deployment evidence: Source/test/merge candidate only. Availability is byte-identical literal
false; production remains inert #623 deploy6a7e072f8f346b0008510d29. No Firebase, Rules, indexes, Functions, provider, account, sign-in, production-data, deployment, or connected/live action is included.Outcome
Verification
--noEmit: passed.git diff --check: passed.Exact reviewed head:
38fb2b79665510317aa8ab889627f6b89ece7ea4Exact tree:
2cbc73167092d83a3d81155e9d3f520cc32b41e0Exact base/sole parent:
d5a218a3ceebdfa758067ae7510803c75564c3c0Exact six-path binary diff SHA-256:
e57f4962c73851f10f4a3e813e76fe6c8136e09fcfb958e0c15e055bfb7454e9Boundaries
No client-service contract change, inbound WebP validation change, admin-finder change, Account wiring/CSS change, backend/Rules/index/Function change, provider/data/release action, biometric/photo-query behavior, or #507 activation. Active #616 Strava blobs and its separately claimed SECURITY OAUTH-001A2L/RISK-024 hunk are preserved byte-for-byte.