Write a testnet reset runbook

[Otaiki1]

Context

Stellar testnet is reset periodically, which wipes every deployed contract and account. When it
happens, this repo breaks in a specific and confusing way: the contract id in .env no longer
resolves, the live demo link 404s at the contract level, the README's on-chain evidence transactions
vanish, and npm run e2e fails partway.

scripts/e2e.ts already detects resets and prints recovery instructions, and scripts/testnet-health.ts
exists — the knowledge is in the code but not in a document an operator can follow.

Where to build it

• New file docs/runbook-testnet-reset.md.
• docs/troubleshooting.md — link it.
• scripts/e2e.ts — its reset-detection message should point at the runbook.
• README.md — the on-chain evidence table needs a note that these are testnet artifacts.

What to do

• Ordered steps: confirm the reset via testnet-health, redeploy the contract, redeploy/repoint the test token, update .env and app/.env, rerun e2e, rebuild and redeploy the app, update the README's contract id and transaction hashes.
• Note that the app is deployed via the Vercel CLI and is not git-connected, so a redeploy is a manual step with env vars baked at build time.
• Note which README claims become stale and must be re-verified.
• Estimate how long the whole thing takes.

Acceptance criteria

• An operator who has never done it can recover the demo by following the document.

[Iszhyie]

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

Hello Maintainer,
I've gone through this issue carefully and have a clear understanding of the requirements, expected design, and acceptance criteria. This is a good match for my experience with similar tasks, and I'm confident I can deliver a clean, well-tested solution that meets the project's standards.
I'd appreciate the opportunity to work on it and can start right away.

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

[ibochielizabeth-spec]

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

hello maintainer i would like to fix this issues quicky....

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

[drips-wave]

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

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