CI/CD Notes

Pipeline Stages

1. Restore dependencies.
2. Format and lint.
3. Build backend and frontend projects.
4. Run unit tests.
5. Run integration tests with Testcontainers for changed critical services.
6. Validate OpenAPI/event schemas.
7. Build Docker images.
8. Run migration dry checks where possible.
9. Publish artifacts/images.
10. Deploy by environment with approvals for production.

Quality Gates

• Backend nullable warnings treated seriously.
• TypeScript strict checks required.
• Event schema compatibility check required for contract changes.
• Financial migrations require review from finance-domain owner.
• Security-sensitive changes require security review.

Детальный список blocking checks: CI Quality Gates. Правила rollout, risky flags, kill switch, rollback/forward-fix и production approvals: Rollout, Feature Flags И Release Safety. Incident lifecycle, severity, commander, evidence, communication, postmortem и follow-up описаны в Incident Management Standard.

Test Strategy

Area	Required Tests
Identity	registration, login, MFA, refresh rotation, token reuse compromise.
Accounting	ledger balancing, deposit callback, withdrawal hold, payout fail, rollback, concurrency.
Execution Gateway	duplicate callbacks, invalid signature, win without bet, rollback.
Incentive	activation, wager progress, expiry, redemption, rollback.
KYC	document upload, approve/reject, audit.
Frontend	guards, forms, DynamicContent states, critical flows.

Release Notes

Every release should include:

• services changed;
• migrations;
• event contract changes;
• operational risks;
• feature flags;
• rollback notes;
• manual reconciliation steps if needed.
• active feature flags, kill switches and rollout cohort.