This document defines operational phase gates for Wave 5 execution.

Technical details are intentionally referenced from existing docs rather than duplicated.

• Eliminate CI/install ambiguity and baseline failures.
• Confirm branch, workflow, and reproducibility standards.

• CI reliability, lockfile integrity, workflow consistency.
• Baseline issue taxonomy and milestone setup.

• Stable deterministic CI baseline.
• Phase 1 audit closure checklist.

• Existing OSS hardening and governance docs.

• DevEx/CI fixes, docs cleanup, workflow polish.

• W5-M1: Baseline Stabilized

• Expand smart contract migration through scoped modules.
• Preserve contract boundary decisions and ADR alignment.

• core_game extension and adjacent contract tracks (rewards, achievements, admin_registry).

• Incremental contract capabilities behind passing CI.
• Updated migration progress mapping.

• Soroban foundation architecture and ADR 0001.

• SC beginner/intermediate/advanced issues.

• W5-M2: Soroban Contract Expansion

• Scale integration ergonomics for frontend and tooling contributors.
• Standardize client, tx, and event handling patterns.

• SDK client improvements, registry loading, event parsing consistency, wallet tx flow expansion.

• Reusable integration primitives with docs and examples.

• Soroban SDK guide + wallet foundation docs.

• FE + SDK track issues with clear acceptance tests.

• W5-M3: Integration Layer Expansion

• Improve event ingestion resilience and projection consistency.
• Build reliable observability and replay-safe processing.

• Cursor progression, projection improvements, worker flow hardening, monitoring hooks.

• Stable indexer foundation for read APIs and analytics.

• Backend indexer foundation + security foundation.

• BE + QA + DevOps issues.

• W5-M4: Indexer Reliability

• Increase contributor throughput without degrading quality.
• Improve onboarding and review ergonomics.

• Task decomposition, labels, templates, contributor scripts, review workflows.

• Higher merge velocity and reduced reviewer friction.

• GitHub strategy and Wave orchestration docs.

• DX + Docs + Automation issues.

• W5-M5: Contributor Throughput

• Ensure migration components are testnet-operational.
• Validate cross-track integration behavior.

• Deploy flow validation, environment sanity checks, integration verification.

• Testnet readiness checklist completed or explicitly blocked.

• Soroban deployment flow and CI maturity.

• SC/SDK/BE/QA integration tasks.

• W5-M6: Testnet Ready

• Raise confidence for post-Wave progression toward production quality.
• Prioritize security, reliability, and maintainability debt.

• Security hardening, flaky-test elimination, operational runbook tightening.

• Hardened baseline and prioritized post-Wave backlog.

• Security foundation and phase completion data.

• Security, QA, DevOps, and advanced SC work.

• W5-M7: Hardening Gate

• Every issue must map to exactly one active phase milestone.
• Cross-phase issues require explicit maintainer waiver.
• Unmapped issues are deferred to backlog until phase alignment is clear.