Isolate oversized telemetry failures from hosted workspaces

Separate the event that exposes a lifecycle bug from the component that fails the operation. A browser closing after a semantic completion marker can be a cleanup hazard without being the root cause when the server already checkpointed and transitioned state.

Enforce a telemetry collector’s UTF-8 byte limit before spooling or upload. Replace oversized auxiliary payloads with a deterministic envelope containing a digest, byte count, and source type, and preserve the workspace independently of telemetry success. Do not silently truncate authoritative business data.

Recovery should restore exact retained controller bytes when available, validate session scope, and otherwise use the latest durable checkpoint. Any time restoration should be an audited one-time grant of unused duration with old credentials revoked.