Phase 6: Stabilization and Release

[automoto]

Overview

Final hardening pass before the v0.1.0 tag. API freeze, all CI green, all success criteria from the PRD confirmed.

Exit Criteria: All success criteria in PRD section 13 are met and Phase 5.5 is complete.

Tasks

• API review and freeze — audit all exported types, methods, and constants for naming consistency and completeness
• Memory leak validation — 10,000 login/logout cycles with no growth in C heap or cgo.Handle map
• All CI checks green on Linux (unit tests + lint + vet)
• Manual test plan (docs/test.md) verified on all three platforms (macOS done; Linux and Windows via Phase 5.5)
• All GoDoc comments present and accurate (enforced by linter)
• Tag v0.1.0 release

Success Criteria Checklist

• A Go developer can authenticate with EOS using DevAuth in under 20 lines of code
• Two game processes can discover each other via lobby search, join a lobby, and exchange P2P packets
• SDK runs correctly on Windows x64, Linux x64, and macOS
• All public API methods accept context.Context and return error
• Thread safety is fully abstracted; no public API requires the user to call runtime.LockOSThread()
• Web API client works with CGO_ENABLED=0
• All exported types and functions have GoDoc comments
• Memory leak tests pass (10,000 login/logout cycles)
• Getting-started documentation enables a new user to have a working lobby in < 30 minutes
• P2P wrapper overhead < 5ms per send/receive (excluding network latency) — benchmark already shows ~24µs/op (~210× headroom)

Dependencies

• Blocked by Phase 4 (Web API Client)
• Blocked by Phase 5 (Documentation)
• Blocked by Phase 5.5 (Cross-Platform Distribution)