Skip to content

armgit / Piik

Public Imported from GitHub
0

Free, open-source screen sharing for private live streams with friends. Watch together in a browser or self-host Piik. 免费开源的私密屏幕共享,支持游戏直播、一起看电影与自部署。

docs: record cf149df production cutover (#90)

AAAe9f0178e1a4b
diff --git a/docs/deployment.md b/docs/deployment.md
index 5a89796d..e2c81841 100644
--- a/docs/deployment.md
+++ b/docs/deployment.md
@@ -1,6 +1,6 @@
# Minimal Deployment
-Last verified against upstream documentation: 2026-08-20.
+Last verified against upstream documentation: 2026-08-21.
This section documents the repository's UDP-only deployment candidate: one
Node.js process provides the built Web client, room API, and WebSocket signaling
@@ -14,21 +14,24 @@ current controller's automatic final media fallback. This capacity is dormant un
the peer-assisted experiment, or required STUN discovery. LiveKit remains
ICE/UDP only. Source no longer contains the rejected participant-wide Peer ICE TURN
candidate; stale `PEER_ICE_TURN_*` keys fail startup even when blank. A
-default-off selected-edge source candidate exists but is not deployed. Production advertises
-STUN-only ICE and the tracked coturn example remains
-`stun-only`. The shared host still retains its older authenticated-relay daemon
-configuration and firewall range, but the application advertises no credential.
-
-Production currently runs `fdd14ba0d9b5ea4c43aa0f6a3a29e0eacf182612` for exact
-room `1` on the existing shared public IP, with health 200 and SQLite v3. The
-current Screener, LiveKit, coturn, and nginx services each report
-`NRestarts=0`. The preceding `fdd14ba` deployment completed successfully and
-remains the rollback target. Rolling back the admission-policy cutover requires
-`89e6d7649169` plus the environment backup recorded below; only deeper
-pre-access `9610032fc5f5` may restore matching v1 state. The production
-application TURN tuple is absent and the failed canary backup is inactive. This
-is a bounded smoke, not broad-rollout acceptance. The selected-edge TURN tuple
-is disabled in production.
+the selected-edge source tuple is enabled in production only for the controller's
+single exceptional edge. Production ordinary peer ICE remains STUN-only and the
+tracked coturn example remains `stun-only`; the shared host retains its older
+authenticated-relay daemon configuration and firewall range. The application
+does not pre-advertise TURN credentials to ordinary peers.
+
+Production currently runs exact `cf149df2411798cd632cc92a562b0a35146e0c1b`
+on the existing shared public IP, with local/public health 200 and SQLite v3
+integrity. The 893,953-byte artifact has SHA-256
+`80918716aefdbb958289b06b6f31551b78dbbaf7fb0f16980eb38d127e158e14`.
+The 2026-08-20T17:48:29Z UTC cutover held the deployment lock for 9,256.904 ms;
+local health returned 562.657 ms after service stop (509.983 ms after the
+symlink switch). Screener, LiveKit, coturn, and nginx are active/running with
+`NRestarts=0`. SQLite v3 contains five rooms including room `1`, with the
+service owner/mode preserved. The prior `fdd14ba` remains the rollback target.
+The selected-edge UDP tuple is configured with TTL 120, but no real TURN/SFU
+media canary was triggered; this remains a bounded configuration smoke, not
+broad-rollout media acceptance.
## Topology and prerequisites
@@ -110,7 +113,9 @@ ICE. The accepted ladder is direct/peer UDP, then the revision-bound SFU/UDP
virtual parent, then optional authenticated TURN for one controller-selected
exceptional edge. LiveKit participants receive only revision-bound `sfu-config`
URL/token messages and negotiate within LiveKit's separate ICE domain. The
-selected-edge TURN config/wire is source-only and not yet deployed.
+selected-edge TURN config/wire is deployed in the `cf149df` release with one
+UDP URL and a 120-second credential TTL. It was not exercised by a real media
+session during this cutover.
`PEER_ASSISTED_MEDIA=true` is the process-wide topology/SFU switch. Every normal
room gets its own bounded controller state; ordinary peer connections remain
@@ -195,11 +200,12 @@ MAX_SFU_ROOTS_PER_ROOM=2
The rejected `PEER_ICE_TURN_*` participant-wide tuple is removed; supplying any
stale key, even blank, fails startup. The source candidate uses the complete
`SELECTED_EDGE_TURN_URLS`, `SELECTED_EDGE_TURN_SHARED_SECRET`, and
-`SELECTED_EDGE_TURN_CREDENTIAL_TTL_SECONDS` default-off tuple with one explicit
-TURN/UDP URI, an independent secret and bounded TTL. Enable it only after the
-all-room peer/SFU tuple and bounded coturn service are ready; roll back by
-removing the application tuple before changing coturn or firewall state. Credentials
-never enter URLs, logs, browser persistence, room rows, or SQLite.
+`SELECTED_EDGE_TURN_CREDENTIAL_TTL_SECONDS` tuple with one explicit TURN/UDP URI,
+an independent secret and bounded TTL. The current production tuple uses the
+coturn UDP endpoint and a 120-second TTL; only the controller-selected edge may
+receive a short-lived grant. Roll back by removing the application tuple before
+changing coturn or firewall state. Credentials never enter URLs, logs, browser
+persistence, room rows, or SQLite.
`PEER_ASSISTED_ROOM_IDS` is retired. Supplying it, even blank, fails startup so
that a stale room-1 deployment cannot silently retain the old scope. With
@@ -284,11 +290,12 @@ Room allocation has two deliberately small policies:
to `ROOM_TTL_SECONDS`; a private grant cannot outlive its room. Stopping sharing
does not immediately delete it. Public-watch remains available but explicit.
-The built-in `node:sqlite` schema v2 stores only each room ID, a SHA-256 Host
-token digest, and one nullable SHA-256 Viewer-grant digest in the same `STRICT`
-row. `NULL` means public-watch; a checked 32-byte BLOB means private-link. It
-must not contain plaintext tokens or grants, passwords, cookies, names,
-participants, SDP, ICE candidates, IP addresses, TURN credentials, or media.
+The built-in `node:sqlite` schema v3 stores each room ID, a SHA-256 Host token
+digest, one nullable SHA-256 Viewer-grant digest, and optional validated Viewer
+password material in the same `STRICT` row. `NULL` means public-watch or no
+password; checked BLOBs mean private-link/password state. It must not contain
+plaintext tokens or grants, passwords, cookies, names, participants, SDP, ICE
+candidates, IP addresses, TURN credentials, or media.
Protect and back up the file as service state. The tracked
systemd unit creates `/var/lib/screener` with `StateDirectory=screener` and mode
`0700`; the production path above is writable despite `ProtectSystem=strict`.
@@ -413,6 +420,37 @@ including room `1`; the current Screener, LiveKit, coturn, and nginx services
each report `NRestarts=0`. Host display-name remains source-only/not deployed.
No selected-edge TURN enablement occurred.
+The all-room routing and selected-edge configuration cutover used exact source
+`cf149df2411798cd632cc92a562b0a35146e0c1b` and immutable artifact
+`screener-cf149df2411798cd632cc92a562b0a35146e0c1b-20260820T173812Z-git.tar.gz`
+(893,953 bytes, SHA-256
+`80918716aefdbb958289b06b6f31551b78dbbaf7fb0f16980eb38d127e158e14`). The
+single lock-held run started at 2026-08-20T17:48:24.554Z and finished at
+2026-08-20T17:48:33.809Z (9,256.904 ms). Screener stopped at
+17:48:29.425Z, the symlink switched at 17:48:29.478Z, and local health was
+ready at 17:48:29.988Z: 562.657 ms from stop, or 509.983 ms from switch.
+The two transient local connection-refused probes were within that normal
+restart window; no browser or media benchmark was run.
+
+The final release removed `PEER_ASSISTED_ROOM_IDS`, set
+`PEER_ASSISTED_MEDIA=true` for every room, and configured one selected-edge
+TURN/UDP URL with a 120-second TTL. Ordinary peer ICE remained STUN-only; the
+coturn, nginx, LiveKit, firewall, and listener baselines were preserved, while
+the application environment changed only for the selected tuple and retained
+root ownership and mode 0600. Local/public health, the built asset, three neutral
+routes, and the anonymous Host-admission boolean passed. SQLite v3 integrity,
+owner/mode, checksum, five-room count, and room `1` were unchanged.
+Screener, LiveKit, coturn, and nginx were active/running with
+`NRestarts=0` at the final audit. The selected-edge tuple was not exercised
+by a real TURN session and no SFU frame or quality result was claimed.
+
+This release also carries the Web Host display-name path and the best-effort
+window-scoped display-audio request hint. Native H.264 opt-in source remains
+available in the repository, but no packaged native sender was deployed; VP8
+remains the Web default. The prior stale `NRestarts=31` rollback is historical
+evidence only, and the final wrapper records restart counts without asserting
+an obsolete baseline.
+
Enabling persistence does not migrate rooms that existed only in memory. The
deployment restart invalidates those temporary links; the first subsequently
created persistent room receives ID `1`.
@@ -428,8 +466,9 @@ compatibility.
The rejected candidate names `PEER_ICE_TURN_URLS`,
`PEER_ICE_TURN_SHARED_SECRET`, and
`PEER_ICE_TURN_CREDENTIAL_TTL_SECONDS` must remain absent from production and
-now fail startup even when blank. They are not aliases for the source-only
-selected-edge tuple, which is not deployed.
+now fail startup even when blank. They are not aliases for the selected-edge
+tuple; ordinary peer edges remain STUN-only while only the current controller
+edge may use the configured selected-edge transport.
## HTTPS and WSS ingress
@@ -521,13 +560,13 @@ canary pass silently.
## Self-hosted STUN
-This subsection describes the current temporary STUN-only deployment template,
-not the optional selected-edge target or the current shared-host coturn state. That
-host retains an older authenticated-relay configuration and TCP/UDP 3478 plus
-UDP 49152-49251 firewall range, while Screener advertises no TURN credential and
-the final canary audit found zero allocations. Authenticated selected-edge
-fallback is source-complete and default-off; its rollout stays blocked on
-retained SFU/UDP media and one forced-relay edge acceptance.
+This subsection describes the temporary STUN-only deployment template, not the
+enabled selected-edge production environment or the current shared-host coturn
+state. That host retains an older authenticated-relay configuration and TCP/UDP
+3478 plus UDP 49152-49251 firewall range. In this template Screener advertises
+no TURN credential and the canary audit found zero allocations; production
+selected-edge issuance remains limited to the controller's one configured edge
+and still lacks a real forced-relay media acceptance.
Copy [`deploy/coturn/turnserver.conf.example`](../deploy/coturn/turnserver.conf.example)
to an untracked service-owned location and use the tracked
diff --git a/docs/project-memory.md b/docs/project-memory.md
index 4f553771..8b8d6b32 100644
--- a/docs/project-memory.md
+++ b/docs/project-memory.md
@@ -25,15 +25,15 @@ Last updated: 2026-08-21
- Keep experiments bounded: the standard representation sequence is below; native RTP relay, encoded-object striping, and FEC remain separate.
- ADR-0006 remains no-go. Native H.264 opt-in loopback (Chrome 151, 1280x720) rendered 298/299 with zero fatal/encoder errors; VP8 remains default. Pion timing, hardware attribution, multi-viewer/endurance/public/packaged proof remain open.
- Mobile Web Host is unsupported; feature-detect and fail clearly. Mobile Viewer stays leaf-only. After Windows native, gate Android 14+; iOS waits for stable iOS 27 ScreenCaptureKit.
-- ADR-0005 accepts direct/peer UDP, bounded SFU roots, then optional selected-edge TURN. Source has a default-off, undeployed one-shot rebuild after SFU; participant-wide TURN remains rejected and ordinary peer ICE stays STUN-only.
+- ADR-0005 accepts direct/peer UDP, bounded SFU roots, then optional selected-edge TURN. Production now enables the one-shot selected-edge tuple after SFU; participant-wide TURN remains rejected and ordinary peer ICE stays STUN-only. No real TURN/SFU media canary has yet been run.
- The controller is process-enabled, not room-allowlisted: `PEER_ASSISTED_MEDIA=true` gives every normal room the same direct/peer -> SFU -> selected-edge path with per-room state. Room `1` is historical smoke. Preserve sticky P2P, mobile leaves and break-before-make; recovery gets one attempt per layer (ICE restart, same-parent rebuild, alternate peer, then SFU), never three identical retries.
- C+B quality reparenting is edge-local and cooldown-bound; no score, timer, or global parent penalty.
- Flagship media is UDP; HTTPS/WSS stays TLS/TCP; the old release remains rollback-only.
- Treat settings as ceilings and degradation as unclassified. Use correlated Host A+B/Viewer C and one-variable evidence; never force AV1, infer by UA, or create a composite score.
- System capture can cause film-audio loss/self-echo; Web cannot isolate processes. Diagnose A/B/C and sync; Windows 11 native game-tree audio is a candidate, Windows 10 unresolved. See `docs/research/browser-screen-audio-quality.md`.
-- Viewer-local names and the opt-in Web participant roster remain control-plane-only. The Web Host name change is source-only after its failed activation; names stay socket/localStorage-only, and Native remains outside the capability boundary.
+- Viewer-local names and the opt-in Web participant roster remain control-plane-only. Web Host names are deployed in the current release and stay socket/localStorage-only; Native remains outside the capability boundary.
- Do not add scene detection, dynamic-FPS control, or forced AV1 without negotiation, encode, game, CPU/GPU, and sender evidence.
-- ADR-0002 grant/public access and the v3 room-password migration are deployed; Host display-name remains source-only. Names/presence remain session-only without account or roster tables.
+- ADR-0002 grant/public access, the v3 room-password migration, and Web Host display names are deployed. Names/presence remain session-only without account or roster tables.
- Deferred architecture audit: `docs/maintenance.md`.
## Current Execution Principle
@@ -43,18 +43,17 @@ Last updated: 2026-08-21
## Current Implementation
- The repository is one npm package using Node.js 24, React, TypeScript, Vite, native WebRTC, `ws`, Zod, Vitest, and separate coturn.
-- Production serves `fdd14ba0d9b5ea4c43aa0f6a3a29e0eacf182612` at `https://share.bonfire.icu` after the `2026-08-20T16:09Z` Host display-name cutover rolled back on stale `NRestarts=31` data. Health is 200; SQLite v3 retains four rooms including room `1`. That rollback still has the historical room-1 gate; source removes it for the next release. `31bee238` is historical rollback evidence.
-- The current Screener, LiveKit, coturn, and nginx services each report `NRestarts=0`. The Host display-name artifact was not retained as an active release, so Host names remain source-only/not deployed; selected-edge TURN remains disabled.
-- Production ICE is STUN-only; stale `PEER_ICE_TURN_*` keys fail startup even blank. Source has a default-off coturn REST rebuild for the original failed Host/ViewerRelay edge after Viewer-root SFU exhaustion; it is undeployed/unverified and production advertises no TURN credential.
-- Production requires an independent `HOST_ADMISSION_PASSWORD` only for creation/Host role. Default private fragment grants, room passwords, and explicit public-watch authorize Viewers; four anonymous Chrome routes stayed neutral until authorization. There are no accounts/JWT/session rows; SQLite v3 still contains all four rooms, including room `1`.
-- Production uses nginx, Node.js 24.19.0, coturn 4.17.2, and LiveKit 1.13.5 on UDP 7882 (TCP fallback off). No application TURN tuple is advertised; coturn retains the old authenticated-relay ports. Services are healthy with zero restarts.
+- Production serves exact `cf149df2411798cd632cc92a562b0a35146e0c1b` at `https://share.bonfire.icu`. The immutable artifact is 893,953 bytes with SHA-256 `80918716aefdbb958289b06b6f31551b78dbbaf7fb0f16980eb38d127e158e14`; the 2026-08-20T17:48:29Z UTC cutover held the deployment lock for 9,256.904 ms and reached local health in 562.657 ms from stop (509.983 ms from symlink switch).
+- The current Screener, LiveKit, coturn, and nginx services are active/running with `NRestarts=0`; local and public health are 200. SQLite v3 is intact with five rooms including room `1`, and the DB owner/mode remain `screener:screener`/0600.
+- Production ICE remains ordinary STUN-only. `PEER_ASSISTED_MEDIA=true` enables the controller for every normal room, and selected-edge TURN is now configured for the single UDP tuple with TTL 120; the coturn daemon and nginx/LiveKit/firewall/listener baselines were unchanged. No real TURN/SFU media canary or quality claim is implied.
+- Production requires an independent `HOST_ADMISSION_PASSWORD` only for creation/Host role. Default private fragment grants, room passwords, and explicit public-watch authorize Viewers; anonymous routes remain neutral until authorization. There are no accounts/JWT/session rows; SQLite v3 stores room identity only.
+- Production uses nginx, Node.js 24.19.0, coturn 4.17.2, and LiveKit 1.13.5 on UDP 7882 (TCP fallback off). Ordinary peer ICE receives no TURN; the selected-edge tuple is configured only for the current controller edge, with no credential pre-advertised to ordinary peers. Coturn retains the old authenticated-relay ports. Services are healthy with zero restarts.
- ADR-0005 source rejects `PEER_ASSISTED_ROOM_IDS`; `PEER_ASSISTED_MEDIA=true` enables every room, while ordinary peer ICE stays STUN-only. A stale room-ID variable fails startup. `screener-v2` is the only deployed signaling literal; there is no v1 parser or translator.
- Chrome 151/LiveKit localhost A/B cut failure-to-active/render from 1.481/2.257 seconds to 0.200/0.320; 31 new frames and 25 ms sampling kept host edges at two. It is headless synthetic 720p30 and includes SDK/network prewarm, not public-network evidence.
- Chrome 151 synthetic topology/quality runs kept fanout 2/1 and decoding; one relay close recovered in 5.32 seconds. Control evidence only.
- Room `1` publishes `HIGH+LOW` with Dynacast off and subscriber `HIGH` ceilings, and now has bounded local quality reparenting. Both remain unverified on real media; test zero-child leaves and calibrated C+B loss before broad rollout.
- C+B uses three hard-bad pairs, one-use samples and guarded intent/cooldown. Deployed admission rescue moves the oldest childless zero-capacity Host leaf below an unassigned one-slot relay in one revision; no score/timer/global rebalance. Deployment passed, but no real room triggered it.
-- Source-only Web Host name/presence leaves Native wire/media unchanged and separates Viewer roster from Host diagnostics; the Host-name artifact was not activated.
-- Native H.264 opt-in is source-complete for one loopback; VP8 remains default and Web/production are unchanged. See `docs/research/native-h264-opt-in-path.md`.
+- Web Host name/presence and the best-effort window-scoped audio request hint are deployed; both remain control-plane/capture hints and do not change the Native wire. Native H.264 opt-in source is present but no packaged native sender is in the release; VP8 remains the Web/production default. See `docs/research/native-h264-opt-in-path.md`.
## Provisional Quality Targets
diff --git a/docs/status.md b/docs/status.md
index 1b4d3821..fc26b1bb 100644
--- a/docs/status.md
+++ b/docs/status.md
@@ -4,18 +4,21 @@ Last updated: 2026-08-21
## Phase
-`https://share.bonfire.icu` currently serves `fdd14ba0d9b5ea4c43aa0f6a3a29e0eacf182612`
-with health 200 after the sole Host display-name cutover at `2026-08-20T16:09Z`.
-Prepare/release and health passed; a stale `NRestarts=31` assertion triggered
-automatic rollback. SQLite v3 has four rooms including room `1`; the
-application/database stayed healthy, and current Screener, LiveKit, coturn, and
-nginx services each report `NRestarts=0`. Host display names remain
-source-only/not deployed.
-Ordinary ICE is STUN-only; source flag `PEER_ASSISTED_MEDIA=true` enables the
-bounded peer/SFU-UDP controller for every room (at most two roots). Room `1` is
-historical smoke only. The old
-`fdd14ba0d9b5` is the healthy v3 rollback target; older schema details are in
-`docs/deployment.md`. Native is no-go and not in production.
+`https://share.bonfire.icu` currently serves exact `cf149df2411798cd632cc92a562b0a35146e0c1b`.
+The 893,953-byte artifact has SHA-256
+`80918716aefdbb958289b06b6f31551b78dbbaf7fb0f16980eb38d127e158e14`.
+The 2026-08-20T17:48:29.425Z cutover held the lock 9,256.904 ms and reached
+local health 562.657 ms after stop.
+SQLite v3 passed integrity checks with five rooms including room `1`; the
+application/database stayed healthy. Screener, LiveKit, coturn, and nginx are
+active/running with `NRestarts=0`, and local/public health are 200.
+Ordinary ICE remains STUN-only; `PEER_ASSISTED_MEDIA=true` enables the
+bounded peer/SFU-UDP controller for every room (at most two roots), while the
+selected-edge UDP tuple is configured with TTL 120. Room `1` is historical
+smoke only. No real TURN/SFU media canary has run. Web Host names and the
+best-effort window-scoped audio request hint are deployed; Native H.264 source is
+available but no packaged native sender is deployed, and VP8 remains the Web
+default.
## Execution Principle
@@ -24,30 +27,29 @@ Flagship first; parallelize design/research/code/tests/audit. Ship minimum runna
## Current Snapshot
- Capture precedes room creation; source/quality changes preserve peers and pause keeps audio/connections. Quality defaults to `maintain-resolution` with balanced/fluid options.
-- Production access is `screener-v2`: Host admission, private grants/passwords, and public codes authorize Viewers. SQLite v3 retains four rooms and checked material; raw credentials are never stored.
-- The Host display-name change is source-only after the failed `61a87ae` activation; it did not alter the deployed wire or UI.
-- Source-only Native v2 uses memory-only rooms, 300s reclaim and `ROOM_TTL`; production does not run it.
+- Production access is `screener-v2`: Host admission, private grants/passwords, and public codes authorize Viewers. SQLite v3 retains five rooms and checked material; raw credentials are never stored.
+- Web Hosts can set their local/session display name, and the current release advertises it through the existing presence wire. The name is not an account identity.
+- Native v2 remains source-only (memory rooms, 300s reclaim); production does not run it.
- PR #44's STUN-only/SFU-UDP router and token-free fallback prewarm are process-enabled for all normal rooms: roots <=2, browser relay <=1, bounded failure. Room `1` is historical smoke; mobile/iPad viewers are leaves, healthy edges sticky, and HTTPS/WSS stays TLS/TCP.
- After an answer, a generation-bound 15s initial-connect deadline enters ICE restart; success/replacement/disposal cancels it. It is deployed but not mobile-verified.
- Room `1` can publish exactly `HIGH+LOW` with Dynacast/backup codec off and subscriber `HIGH` ceilings; it has no retained real media frame.
- Room `1` C+B reparenting remains uncalibrated. Deployed admission rescue promotes an unassigned one-slot relay over the oldest childless zero-capacity Host leaf, with no scores or periodic optimization.
-- Web opt-in roster code includes Host self-name, but the Host display-name change is source-only/not deployed; Native wire/media remains unchanged.
+- Web roster includes Host self-name and requests window-scoped display audio where supported; both are hints, and Native wire/media is unchanged.
## Verified Evidence
-- Historical `31bee238` deployment passed 28 files/421 tests and both builds; no real admission rescue was triggered.
- Chrome 151 synthetic `1/3/5/8` and 720p30 quality-change runs kept 2/1 fanout and decoding; slowest first frame was 1.05 seconds and one relay close recovered in 5.32 seconds. This is control evidence only.
- Host A+B and authenticated P2P Viewer C are sanitized, generation-bound, read-only, and fail closed for stale, ambiguous, or SFU-fed evidence; no raw media metadata is retained.
-- SVC is `no-go-web-svc-cross-path-hardware-contract`: no direct/peer selection, cross-PC shared encode, or portable hardware proof; pinned screen share is `L1T3`. No browser run was warranted.
- The `a11a73d` built-in TURN canary is rejected: local allocation passed, but direct Host/Pion Viewer failed before forced relay. Full rollback restored STUN-only client ICE and zero allocations.
-- Native loopbacks (Chrome 151): VP8 299 decoded; H.264 opt-in 299 decoded/298 rendered at 1280x720, with no fatal/encoder errors. H.264 Annex-B; hardware preference is not proof. Pion timing and multi-viewer/FIFO/endurance/public/native proof remain open; production stays VP8.
+- Chrome 151 loopbacks decoded VP8 299 and H.264 opt-in 299/298 rendered at 1280x720 without fatal/encoder errors. Hardware attribution, Pion timing, multi-viewer/endurance/public/native proof remain open; production stays VP8.
- Access protocol/config/HTTP/storage/SQLite/signaling focused tests pass, including commit-first teardown and v1 rollback.
-- Source adds selected Host ingress + peer last-mile for every enabled room; Peer ICE STUN-only; focused routing/config tests pass.
-- The `61a87ae` Host-name artifact was rolled back after a stale restart-count assertion; `fdd14ba` is healthy and Host display-name remains source-only. Selected-edge TURN is disabled.
+- Source adds selected Host ingress and peer last-mile for every enabled room; focused routing/config tests pass with Peer ICE STUN-only.
+- `61a87ae` Host names, `d1a4fd4` window-audio hint, and `cf149df` all-room routing are active; the stale restart assertion is historical only.
+- Final gates preserved service/config baselines, asset/routes/admission checks, and the DB v3/5-room checksum. Selected-edge is configured, but no real TURN or SFU session ran.
## Unverified Boundaries
-- Room 1 proved LiveKit participant entry but not a retained SFU frame, retry/failback, selected UDP pair, admission rescue, edge cap, quality, or resource deltas. Former game-share load/blur remains unclassified.
+- The final deployment proves process/config health, not a retained SFU frame, retry/failback, selected UDP pair, admission rescue, edge cap, quality, or resource deltas; game-share load/blur remains unclassified.
- Android Chrome/iOS Safari Viewer leaves remain unverified and conservatively leaf-only. Mobile Web Host is unsupported; native senders are planned only.
- Silent partitions can wait 30 to 60 seconds for heartbeat detection before the default 5-second grace; this remains unverified.
- Real audio and heterogeneous clients remain unverified. System capture can lose film audio or echo voice calls; Web has no process isolation. Diagnose A/B/C and sync; gate Windows 11 game audio; Windows 10 unresolved.
@@ -73,9 +75,10 @@ duration; VP8 and explicit H.264 Viewer decode/render are recorded. Hardware
preference is not physical proof. Next prove fresh Pion
outbound diagnostics before viewer 2/FIFO/hardware/endurance/deploy.
Audio A/B/C may proceed without displacing P0.
-Ordinary Peer ICE stays STUN-only; participant-wide TURN is removed. Selected-edge
-is source-complete/default-off/undeployed; Host ingress still needs one forced-relay
-canary before activation. Retained performance/resource benchmarks follow landing.
+Ordinary Peer ICE stays STUN-only; participant-wide TURN is removed. The
+selected-edge tuple is configured in production, but Host ingress still needs one
+forced-relay canary before any media-success claim. Retained performance/resource
+benchmarks follow functional landing.
ADR-0004 still requires a full-resolution 30-minute `1/3/5/8` network,
resource, quality, latency, recovery, and browser/mobile-leaf matrix. A separate