Release sequencing

Ship only after device, runtime, and domain stay aligned.

The next release path is not only UI polish. It includes queue health, replay safety, physical-device navigation, and domain presentation parity.

Phase A

Keep physical-device UITest lane stable and scriptable with one command.

Phase B

Re-profile with full connected runtime stack and compare against the baseline leak traces.

Phase C

Deploy this static package to Cloudflare Pages and bind both apex and www domains.

Phase D

Promote the release only when device smoke, runtime readiness, and archive/export evidence all stay green.