Add docs for emergency pause recommended usage and steps to resume safely

[Chucks1093]

Summary

The emergency pause is a critical safety mechanism but using it incorrectly — pausing without a recovery plan or unpausing before a fix is deployed — can cause harm. Contributors and operators need documented guidance on when to pause, what to do while paused, and how to safely unpause.

Scope

• Document the conditions that warrant a pause: suspected exploit, critical bug in trade logic, abnormal treasury drain
• List the steps to take while paused: assess impact, communicate with community, prepare fix or migration
• Explain when it is safe to unpause: fix deployed and verified, or migration complete
• Add a warning that unpausing without a fix leaves the same vulnerability active

Acceptance Criteria

• Conditions for pausing are clearly listed
• Steps to take while paused are documented
• Unpause safety criteria are stated
• Warning about unpausing without a fix is included

ETA: 12 hours

---

Coordinate on Telegram

[goodness-cpu]

@goodness-cpu has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Maintainer, I can fix this issue.

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

[Oluwasuyi-Timilehin]

@Oluwasuyi-Timilehin has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, I’m a full stack developer with hands-on experience building with variety of tools including Nextjs, nodejs, nestjs, React, Typescript and more
I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 4 HOURS

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

[Alaka-ibr]

@Alaka-ibr has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, will love to work on this.

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

[wheval]

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

Hello i would love to work on this.

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

[drips-wave]

Congratulations, @wheval! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

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

[BWM0223]

PR #497 submitted — emergency pause docs. Payment wallets ready: ETH 0xeaCAb48a4bfA0CED0e668c166615927115655594 | SOL C3MD2yfWYebB8FYXpq6ooqzU5GCQB1bDxbDhQf1JfiCW | BTC bc1qtmlgtvg7xgv0zry3ct90elp3y7d3ffdutk4e2f