Josh Creek de263f30e8 docs: explain why the matchmaking control plane is Go, fix stale status ...

Add a Go-vs-C#/Rust/C++ rationale for the matchmaking control plane to
TECH_STACK.md, and point at it from MATCHMAKING.md and README.md.

Also correct CLAUDE.md and README.md, which still described the backend
as unstarted/not built even though server/ has ~13k lines of Go across
matcher, allocator, api, store, security, supervisor and agones.

2026-09-04 19:10:09 +01:00

..

ADR-001-matchmaking-platform.md

docs: lock matchmaking platform architecture

2026-08-31 20:06:45 +01:00

MATCHMAKING-SLOs.md

docs: define matchmaking launch SLOs

2026-08-31 20:07:41 +01:00

MATCHMAKING.md

docs: explain why the matchmaking control plane is Go, fix stale status

2026-09-04 19:10:09 +01:00

OBSERVABILITY.md

test(multiplayer): verify observability manifests locally

2026-09-01 17:34:15 +01:00

SUPPLY-CHAIN.md

feat: enforce supply chain policy

2026-08-31 21:32:03 +01:00

TECH_STACK.md

docs: explain why the matchmaking control plane is Go, fix stale status

2026-09-04 19:10:09 +01:00

THREAT-MODEL.md

fix(multiplayer): bound workload credential lifetime

2026-09-03 21:27:26 +01:00