[Docs] No staging deploy/rollback runbook - deploy-staging.yml has rollback logic, STAGING_ENABLED gating, and STAGING_SSH_* secrets documented nowhere

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

docs/runbooks/ contains only indexer-recovery.md, yet deploy-staging.yml implements a non-trivial pipeline: staging-previous backup/rollback, vars.STAGING_ENABLED == true gating, required secrets (STAGING_SSH_HOST/USER/KEY/PORT), server-side migrate:up, and backend/frontend health checks. There is no runbook telling an on-call engineer how to enable staging, which secrets/vars to set, or how to manually roll back to remitlend-*:staging-previous when the automated rollback also fails.

Acceptance criteria

• A docs/runbooks/staging-deploy.md (linked from runbooks/README.md) documents required GitHub secrets/vars and the STAGING_ENABLED toggle
• Includes manual rollback steps using the staging-previous tag and rollback compose file
• Covers the health-check ports (backend 3001/health, frontend 3000) and where to read logs

Files to touch

• docs/runbooks/README.md
• .github/workflows/deploy-staging.yml
• docker-compose.staging.yml

Out of scope

• Documenting a production deploy pipeline that does not yet exist
• Secret rotation policy

[AdeMi20]

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

Hey , can i pls be assigned these

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

[eyooTech]

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

Hello

Let me help you work on this

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

[drips-wave]

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

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

[drips-wave]

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

😎 @eyooTech: You earned 200 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.