MEMBERS-DIRECTORY-001O — Preserve visibility-toggle focus after authoritative settlement - #648
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
Closed
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 #647
Officer impact: No live officer workflow changes. In the preserved future My Account interface, a keyboard or screen-reader user who changes the officer-finder checkbox can return to that same checkbox after the current save and authoritative readback settle, instead of being stranded when native pending disablement evicts focus. Any other connected control deliberately focused while the request is pending keeps focus. The connected interface remains unavailable on production.
Officer documentation:
SYSTEM_DESIGN.md,IMPLEMENTATION_PLAN.md,SECURITY.md, anddocs/officers/EVENTS_SHOP_MEMBERS.md(one current-source boundary/ledger addition and one no-terminal source-evidence procedure; Mermaid unchanged).Deployment evidence: Source and synthetic tests only. The exact six-file candidate is commit
c930dcd88aa46d654305cc9aec1ad743fe4fa95f, treef5f598aab4efb8a4ad7d8668be2ad2e4b6a9ad7f, with binary diff SHA-2561d06e5f300c3e5362009881d6bfd28dce0e029cee510ec93f8eee283244ce961. Node 20 verification passed: named tests 21/21, full profile 152/152, full frontend 1,237/1,237, TypeScript, scoped lint, lint baseline, repository Node tests 105/105, diagnostic build, and diff-check. Exact-head CI run31763516255passed all five jobs. Netlify deploy preview6a7e7bd690347c0008f4aac7is ready on the exact head, remains unpublished, passed header and redirect checks, changed no Pages-owned files, and deployed no Netlify or Edge Functions.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.Outcome
Trustworthy unchanged-runtime RED was 5 failed exact restoration cases with 14 containment controls already passing. Final independent focus/race, security/privacy, frontend/accessibility, and backup-officer reviews all returned GO. #637 Reload recovery, #643 rejected-removal focus, #645 confirmed-photo focus, native checkbox markup, error association, confirmations, and exact service behavior are preserved.