AUTH-006H — Restore focus to an unconfirmed profile-name Save result - #654
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 #653
Outcome
When an exact current My Account full-name Save owned keyboard focus and the update or required authoritative reread cannot be confirmed, the existing fixed uncertainty alert now receives otherwise-lost focus once. The alert remains truthful about uncertainty, and Try profile again remains the next Tab stop.
Officer impact: No new officer action and no live-site claim. This is source-only keyboard recovery for members using the existing profile-name editor.
Officer documentation: SYSTEM_DESIGN.md, IMPLEMENTATION_PLAN.md, SECURITY.md, and docs/officers/EVENTS_SHOP_MEMBERS.md.
Deployment evidence: Exact-head CI run 31770307722 completed successfully with all five jobs green. Netlify deploy 6a7e9af0dd5db60008769dec is a ready deploy-preview for the exact candidate, has published_at null, deployed no Functions or edge Functions, passed header and redirect checks, and leaves Pages-changed neutral as expected. The preview Account route returns 200 with X-Robots-Tag: noindex. No production website publication, runmprc.com revision change, Firebase deployment, provider configuration, account or sign-in action, production-data action, or connected-live behavior occurred. Production remains the inert #623 release, and optional-directory availability remains byte-for-byte false.
Exact reviewed candidate
Verification
Safety boundaries
The focus state stores only opaque generation and attempt identifiers. It adds no read, write, retry, request, provider call, log, payload field, or stored member value. Initial-load errors remain unfocused; AUTH-006G confirmed-success behavior remains unchanged; stale application, Firestore, identity, UID, generation, attempt, reread, retry, and unmount work is fenced. No Account service, Function, Rule, schema, index, package, workflow, provider, account, data, deployment, directory connection, photo-query, facial-recognition, matching, embedding, similarity, or biometric behavior changes.