Schedule quarterly chaos game-days with scenario library and post-mortem template

[thlpkee20-wq]

Description

Chaos tests exist but are ad-hoc. Schedule recurring game-days with a versioned scenario library (DB primary loss, Redis split-brain, Horizon outage) and an automated post-mortem skeleton generated from observed metrics.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Relevant code: ops/chaos/, src/__tests__/
• Scenarios must declare blast radius and abort criteria

Suggested execution

• Fork the repo and create a branch
• git checkout -b feat/chaos-game-day-library
• Implement changes
  • Add ops/chaos/scenarios/*.yaml
  • CLI npm run chaos:run -- --scenario=...
  • Auto-generate post-mortem skeleton with metric snapshots
• Validate security and correctness assumptions

Test and commit

• Run tests
  • npm test
• Cover edge cases
  • Abort criterion triggers cleanup and rolls back
• Include test output and notes

Example commit message

feat: chaos game-day scenario library

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[Zainab5970]

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

please can i work on the issue

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

[Imole203]

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

I will love to work on this issue,pls 🙏 give me

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