Current authoritative state
Protected shipped truth is exact main@a40b9489665bed7d95af619a6079b9c51cab299a; invalid runtime collaboration states still fall through to the misleading ready label. Closed Draft #167 is historical evidence only.
Issue-specific Draft PR #406 / codex/collaboration-status-validation-208 owns this repair. It is stacked on awareness-containment PR #403 at exact base 66a9caa7cb6a9aa5e399ce5ca76d987737aa7c45; current exact head is 02f55466c0111bb53c6886f5d4a95de2068e944a. This is active-PR behavior, not protected-main shipped truth.
Required behavior
collaborationConnectionLabel() preserves exactly undefined -> Collaboration ready, connecting -> Connecting, connected -> Connected, disconnected -> Disconnected, and offline -> Offline. Every other runtime value fails closed with stable payload-redacted RangeError('Collaboration connection status must be connecting, connected, disconnected, or offline.') instead of presenting an invalid host state as ready.
Provider transport/lifecycle, authorization, tenancy, persistence, credentials, deployment, retention, migration, model policy, and durable audit remain host-owned.
Exact-head evidence
Test-only 05f1c3089379339851170260652e95c5d26cf2b3 reproduces the defect with 1 failure / 29 passing checks. Current GREEN head passes:
- focused awareness contract: 30 / 30 tests;
- full TypeScript suite: 160 files / 891 tests;
- statement, branch, function, and line coverage: 100%;
- typecheck, build, and packed-package consumers.
Repository-local success is not protected integration, independent approval, or release proof. Keep #406 Draft until #403/#405 integrate or the dependency chain is otherwise resolved, and while #118 owns the protected release boundary. Before lifecycle action, refetch exact head/base, reviews, threads, live rules, and every applicable workflow; do not transfer #167 evidence, self-approve, weaken gates, or fabricate release identity.
Current authoritative state
Protected shipped truth is exact
main@a40b9489665bed7d95af619a6079b9c51cab299a; invalid runtime collaboration states still fall through to the misleading ready label. Closed Draft #167 is historical evidence only.Issue-specific Draft PR #406 /
codex/collaboration-status-validation-208owns this repair. It is stacked on awareness-containment PR #403 at exact base66a9caa7cb6a9aa5e399ce5ca76d987737aa7c45; current exact head is02f55466c0111bb53c6886f5d4a95de2068e944a. This is active-PR behavior, not protected-main shipped truth.Required behavior
collaborationConnectionLabel()preserves exactlyundefined -> Collaboration ready,connecting -> Connecting,connected -> Connected,disconnected -> Disconnected, andoffline -> Offline. Every other runtime value fails closed with stable payload-redactedRangeError('Collaboration connection status must be connecting, connected, disconnected, or offline.')instead of presenting an invalid host state as ready.Provider transport/lifecycle, authorization, tenancy, persistence, credentials, deployment, retention, migration, model policy, and durable audit remain host-owned.
Exact-head evidence
Test-only
05f1c3089379339851170260652e95c5d26cf2b3reproduces the defect with 1 failure / 29 passing checks. Current GREEN head passes:Repository-local success is not protected integration, independent approval, or release proof. Keep #406 Draft until #403/#405 integrate or the dependency chain is otherwise resolved, and while #118 owns the protected release boundary. Before lifecycle action, refetch exact head/base, reviews, threads, live rules, and every applicable workflow; do not transfer #167 evidence, self-approve, weaken gates, or fabricate release identity.