feat(operations): add capacity and resilience gates (#18)

README.md

@@ -83,9 +83,9 @@ Rendezvous is under active roadmap development. The versioned contracts,
 directory leases, authenticated join attempts, LiteNetLib mediator, caller-owned
 SDK coordination, typed connection outcomes, thin public-SDK diagnostic client,
 deterministic NAT topology harness, hostile-input controls,
-observability/operator surface, and secure single-active Linux deployment are
-implemented. Capacity, resilience, packaging, and final production-readiness
-gates remain in progress;
+observability/operator surface, secure single-active Linux deployment, and
+numeric capacity/resilience gates are implemented. Packaging, consumer pilots,
+and final production-readiness gates remain in progress;
 participating games must not treat the current repository as a finished production
 service until those gates land.
 
@@ -103,6 +103,9 @@ operator controls are defined in the
 The pinned non-root container, production topology, graceful drain, Linux
 hardening, smoke procedure, and recovery lifecycle are documented in
 [secure single-active Linux deployment](docs/deployment/linux.md).
+The numeric core-state candidate profile, public launch objectives, accelerated
+soak, resilience matrix, and single-active scaling decision are recorded in
+[capacity and resilience gates](docs/operations/capacity-and-resilience.md).
 The scriptable host/browser/join diagnostic and its stable automation contract are
 documented in the [TestClient integration guide](docs/integration/test-client.md).
 The always-on three-party scenarios, optional Linux namespace topology, and