Make role rotation and timelock cancellation atomic and observable

[Jagadeeshftw]

Area: Governance / auditability · Estimated effort: 8–12 h

Problem

test_admin_rotation.rs, timelock docs, and role separation notes cover rotation, but event/state assertions need to prove no half-rotated authority is observable.

Design decision required

Define pending versus active role state and whether cancellation invalidates prior nonces or scheduled operations.

Requirements

• Test schedule, execute, cancel, expiry, replacement, and concurrent caller cases
• assert events and authority at each ledger boundary.

Acceptance criteria

• No intermediate state grants two admins or none unexpectedly, cancellation prevents execution, and events provide a complete audit trail.

Out of scope

• Unrelated refactors, dependency upgrades, or behavior changes outside the stated scope.
• Closing, deleting, or weakening existing tests to make the change pass.

Verification

cargo test --manifest-path contracts/bounty_escrow/Cargo.toml -p escrow admin_rotation -- --nocapture

PR requirements

• Explain the before/after behavior and include the evidence requested above.
• Add regression tests for the changed behavior and report relevant build, test, lint, and artifact results.
• Keep the PR focused and reference this issue.
• Please open the PR within 48 hours of assignment so the work remains active; ask a question in the issue if the scope needs clarification.

Good luck, and please join the contributor Telegram group if you want to discuss the work: https://t.me/+u5qmu35nZ7I0OTU1

[DevScoopee]

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

Hi, i fully understood what needs to be done. Kindly assign

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

[dotmantissa]

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

Please, assign this issue to me.

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

[Jagadeeshftw]

@DevScoopee — Wishing you the best of luck on this work! You are now assigned to Make role rotation and timelock cancellation atomic and observable (#1741). Your immediate focus is make role rotation and timelock cancellation atomic and observable. Please read the complete issue description before starting, address every requirement and acceptance criterion in your PR, and raise a high-quality, focused implementation with the relevant tests and verification evidence. A clear, well-tested PR will make the result much easier to validate. Please open the PR within 48 hours of this assignment; if no PR is opened within that period, the issue may be unassigned so the work can be reassigned. You are also welcome to join our contributor Telegram group: https://t.me/+u5qmu35nZ7I0OTU1

[drips-wave]

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

🧑‍💻 @DevScoopee: 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 🌊