Beta
The beta now has stricter checks before it expands
What changed in beta readiness: stronger checks before access expands and a cleaner infrastructure path.
Why it matters
Recent master commits focused on work that is mostly invisible from the outside but important for early access: additional beta gates, CI results, and infrastructure readiness checks.
The team also shaped a limited path for protected private chats. It is not a broad public statement; it keeps a narrow scenario separate from the parts that still need external review.
For participants, the point is simple: the beta should move forward by conditions the team can verify before the next step.