[Quality][High] authentication and account recovery: atomic rollback — QE-2026-08

[Baskarayelu]

Objective

make sign-in, refresh, verification, logout, and recovery flows safe across expiry, retries, multiple tabs, and device changes. Specifically, implement and verify atomic rollback so the repository provides a deterministic, reviewable guarantee under normal, invalid, repeated, concurrent, and failure conditions.

Why this matters

The current behavior or coverage needs a production-grade guarantee here: stale tokens and ambiguous recovery state can expose accounts or make legitimate users repeat sensitive actions. Without this work, partial writes or emitted side effects surviving a failed operation could survive review or deployment.

This is a substantive engineering change. It is not a typo fix, formatting-only change, documentation-only change, or trivial dependency update.

Priority

High

Scope

Area: security / UX correctness

Starting points:

• meridian-api/src/auth/
• Add or update the closest focused unit, integration, property, or contract test beside the implementation.

Verify the existing implementation before changing it. Keep the change focused on this issue and preserve existing public behavior unless the acceptance criteria require a documented compatibility change.

Acceptance criteria

• make related writes and externally observable effects atomic or compensating; expose a clear failure result without partial state.
• Preserve compatible public behavior and make any required migration, error, or response-shape change explicit.
• Ensure rejected, stale, repeated, and failed operations leave no unauthorized or partial state.
• Add focused regression coverage that proves the invariant at the actual integration boundary.

Required validation

• inject failures at each side-effect boundary and verify database, contract state, queues, and events remain consistent.
• Run formatter, lint, type/build checks, and the complete repository test suite.
• Run applicable security, contract, migration, gas/resource, or accessibility checks and record commands and results.
• Confirm generated artifacts, secrets, disabled checks, and unrelated refactors are absent from the change.

Documentation requirements

Document the design and invariants, failure behavior and compatibility impact, migration or rollback considerations, operational limitations, and security assumptions where applicable.

Out of scope

No unrelated refactors, typo or formatting-only changes, docs-only changes, broad dependency upgrades, disabled CI, generated noise, or secrets.

Contributor deliverables

Wait for maintainer assignment. Open a focused branch and reference this issue with Closes #<issue-number> or Fixes #<issue-number>. Check off every criterion, link the implementation and tests, include commands and results, and include a short security/correctness note.

Maintainer quality bar

The PR must change real behavior, address every criterion, include meaningful success and failure-path tests, cover relevant edge cases, remain focused, document compatibility, and provide complete validation evidence. Issue creation does not guarantee reward eligibility; PR quality is evaluated independently.

[ojuotimi932]

@ojuotimi932 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer Can I resolve this kindly assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ojuotimi932 to this issue.

[Peolite1]

@Peolite1 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

i would love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Peolite1 to this issue.

[drips-wave]

Congratulations, @ojuotimi932! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @ojuotimi932: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@ojuotimi932's PR #1688 was approved and merged by @Baskarayelu.

🏆 @ojuotimi932: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (551 total points). Track your full progress on GrantFox.

👏 Great work, @ojuotimi932! Keep contributing to Remitwise-Org.

[drips-wave]

This issue has been completed by @ojuotimi932 as part of the Stellar Wave Program's 8th Wave 🥳

😎 @ojuotimi932: You earned 100 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.