Skip to main content
Realtime changes require focused protocol and compatibility checks. The detailed setup and operator procedures are maintained privately.

Validation and Delivery Evidence

Validate the exact source being proposed with the relevant focused checks. Record the commands and their outcomes, and distinguish local checks, CI, deployment identity and production behavior. A successful source check alone is not evidence of a deployment. Keep independent review and applicable release gates.

Label-gated heavy PR CI (ready-for-ci)

Heavy PR workflows require the ready-for-ci label. Add it only after independent review approves the proposed head and the PR is ready to merge. Verify locally or on an authorized development runner beforehand. Unlabelled jobs are skipped; skipped jobs are not executed verification. The label gate and draft status are separate conditions. See the checked-in workflow definitions for the current eligible jobs.

Existing-client transition

Realtime migrations preserve supported clients until compatibility acceptance allows retirement of the earlier transport. A persisted change and its realtime delivery have distinct outcomes; a transport failure must not be presented as loss of the saved change.

Mobile screen sharing

Screen sharing depends on browser and operating-system capture support and user permission. Unsupported capture must show guidance. Receiving a shared screen and using the collaborative editor remain separate capabilities.

Local Cloudflare runtime verification

Realtime protocol acceptance uses an isolated local Worker and Durable Object runtime, with disposable data. It checks access, collaborative updates and recovery behavior. Local acceptance does not establish hosted media behavior or authorize a deployment.

Completed Live finalization receipts

A completed session must have confirmed erasure and billing outcomes before finalization is acknowledged. An in-memory completion flag alone cannot prove that durable work finished; unresolved outcomes remain visible.

Portable offline retry planning

Offline recovery uses finite retries with retained progress. Stopping retries preserves unresolved documents and must not be reported as confirmed recovery. Retry planning alone does not prove durable storage, provider behavior or live acceptance.