MEMBERS-DIRECTORY-001M — Restore surviving photo-control focus after rejected removal - #644
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Aug 14, 2026
Open
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 #643.
Officer impact: No live officer workflow changes. In the preserved future My Account interface, a keyboard or screen-reader user whose focused Remove current saved photo action disappears after a definitive rejection and authoritative readback returns to the closest surviving photo action, without stealing focus the user deliberately moved elsewhere.
Officer documentation: Updated
SYSTEM_DESIGN.md,IMPLEMENTATION_PLAN.md,SECURITY.md, and the optional-directory text alternative plus the no-terminal MEMBERS-DIRECTORY-001M evidence procedure indocs/officers/EVENTS_SHOP_MEMBERS.md. No Mermaid change; page topology, permissions, and data movement are unchanged.Deployment evidence: Source and synthetic tests only. The exact six-file candidate is commit
5ac46b43b7d2e18e338bb75d23106a851d6c7942, treea07d391b8e23e28dd39785329be444f452fa2953, with binary diff SHA-2560497c75100eddc38b7b3b38d7fd8403cb60d01b7bbad9a50bbb79472ec3d28b7. Local verification passed: named tests 15/15, full profile 111/111, full frontend 1,196/1,196, TypeScript, lint baseline, repository Node tests 105/105, diagnostic build, and diff-check. Exact-head CI run31759493222passed all five jobs. Netlify preview6a7e69c973d2b40009a3e5a6is ready for the exact head, remains unpublished (published_at:null), and deploys no Functions or Edge Functions; header and redirect checks passed and Pages-changed skipped as expected.memberDirectoryAvailability.tsremains literalfalse; no website, Firebase, provider, account/sign-in, production-data, or connected-live action is authorized or claimed. Live #623 remains inert, and #507 retains all connection and release gates.The patch:
Independent focus/race, security/privacy, frontend/accessibility, and backup-officer/operations reviews all reported GO with no findings. Exact candidate evidence: #643 (comment)