Repository navigation
fix(mobile): integrate account styling and confirmation recovery - #2611
Merged
Merged
Conversation
Issue: #2581 Agent-Task: codex/local/01a164b0-214b-7371-bf06-ca7c00c54137
Issue: #2581 Agent-Task: codex/local/01a164b0-214b-7371-bf06-ca7c00c54137
Issue: #2603 Agent-Task: codex/local/01a164b0-214b-7371-bf06-ca7c00c54137
Issue: #2603 Agent-Task: codex/local/01a164fc-d3fd-7d10-9e86-415381f16211
Issue: #2603 Agent-Task: codex/local/01a164fc-d3fd-7d10-9e86-415381f16211
…dex/2602-2604-account-integration
Combine #2602 at 620bf28 and #2604 at 05b20d6 on main 3fe3693. Preserve the styled AccountAction and pending-deletion label; exercise the actual iOS panel with the account controller and closed in-memory fixture. Source owners and branches remain unchanged. Native and Human gates remain pending. Issue: #2524 Issue: #2581 Issue: #2603 Agent-Task: codex/local/01a1654c-9569-7cb3-a355-ed6c79137709
|
Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
⛔ Files ignored due to path filters: 24
📒 Files selected for processing: 36
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Oct 22, 2026
Contributor
Author
Agent work completed — authorized account integration merge
|
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.
Refs #2524 · Refs #2581 · Refs #2603 · Integrates #2602 and #2604 · Integration claim
Task
codex/local/01a1654c-9569-7cb3-a355-ed6c79137709(integration only). Source ownership:codex/local/01a164b0-214b-7371-bf06-ca7c00c54137(#2602 and initial #2604),codex/local/01a164fc-d3fd-7d10-9e86-415381f16211(#2604 review fixes),codex/local/01a16534-c59b-7a90-b7b9-d2aa1149c60f(#2604 successor).Why the change
The account styling and confirmation PRs conflict on the iOS Sign out row, so this integration preserves the styled control while showing the correct recovery label and confirmation after an unfinished deletion.
Special things to note
3fe369353b6a9f784341f24fba9b555fa2744eab; the shared QA owner still qualifies its binary and loaded JavaScript.1e0ef7e3af5d9462385f817002b40d882459884dcontains fix(mobile): color and align account action symbols #2602620bf28da53739624bff07c3a148ea07cd6b1590and fix(mobile): confirm account actions and clean owned connections #260405b20d6d3c3841a800054f26a993e8ee541391c6. Original source refs remain unchanged. Use a merge commit to preserve both source ancestries. Local mobile typecheck, lint/format/ledger and 1,265 tests passed, 9 skipped; full combined CI is required before merge.Change outline
The product conflict resolution is one label expression against #2602's panel. All account controller, provenance, pairing-save serialization, cleanup and Android behavior stays identical to #2604. Eight added tests run the actual iOS panel through the account controller and closed in-memory fixture, with native component adapters mocked. They cover both actions, cancellation, duplicate confirmation, busy/loading and the five failure/recovery scenarios. Existing tests cover stale identity, expired credentials, restart, write failures and HostSession teardown.
Native capture blocker: this integration task has no device lease; the physical lane is occupied by Batch60 recording QA. No combined before/after native screenshots or VoiceOver qualification exist. Historical color evidence belongs to #2602, not this exact combined head. After the owner's next cut, open
/qa/account-actions?scenario=successonly in__DEV__with a.devapp ID, verifyfixture@example.invalid, and reset between actions. Capture English/Chinese × light/dark × default/intermediate/maximum for rows, both dialogs, Cancel, busy/loading and recovery labels. Runlocal-write,session-write,delete-partial,expired-retryandcompletion-write; confirm counter/state isolation and no repeated completed remote deletion. Batch60's Release package cannot run this fixture. Android, live-service effects and Human optical/behavior acceptance remain separate.Exact-source handoff and verification limits. A separate HTML explainer is omitted for this integration-only conflict resolution: the owning behavior remains the original #2604 implementation, and the complete confirmation/cleanup path and exact changed expression are shown above; no new architecture or policy is introduced.
Summary by CodeRabbit