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(deploy): record memory room release (#212)

AAAefe258e5c1f3
diff --git a/README.md b/README.md
index 2db08a91..f5675269 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,7 @@ Screener is a private, low-latency screen-sharing project for one game player an
The first measurable Web proof of concept is implemented. A host captures a screen, window, or browser tab and shares a random four-digit room code plus an independent fragment invitation. During a share, the host can change between three ceiling profiles without reopening the source picker, pause and switch sources, and switch video codec while paused. Code-only entry defaults to `open` after site access and may instead require a room password or be disabled; a valid grant enters directly. Rooms are process-memory state with a configurable dormant lease and disappear on restart. Lightweight deployments may keep independent direct WebRTC connections. The flagship deployment enables the all-room controller with bounded peer descendants and one LiveKit Host publication serving admitted Viewer subscriptions; short-lived TURN may be authorized only for a controller-selected exceptional media edge. Production admits 20 viewers and deployments may configure 1 through 20, but that admission limit is not a performance promise.
-This is not yet a broadly validated product release; [Current status](./docs/status.md) owns the deployed revision and validation evidence. The deployed flagship boundary is the all-room bounded peer/SFU-UDP controller on `screener-v7`, with ordinary peer ICE kept STUN-only and short-lived TURN limited to controller-selected exceptional media edges. The optional Windows native sender remains source-only and is not a production runtime. Mobile devices are Web viewers only; ordinary Android and iOS browsers do not expose reliable screen capture for a Web Host. Real cross-network SFU/TURN media, game audio, a sustained public-network 1:20 session, mobile browser lifecycle behavior, and latency targets still require the documented manual test matrix.
+This is not yet a broadly validated product release; [Current status](./docs/status.md) owns the deployed revision and validation evidence. The deployed flagship boundary is the all-room bounded peer/SFU-UDP controller plus the memory-resident room/access model on `screener-v8`, with ordinary peer ICE kept STUN-only and short-lived TURN limited to controller-selected exceptional media edges. The optional Windows native sender remains source-only and is not a production runtime. Mobile devices are Web viewers only; ordinary Android and iOS browsers do not expose reliable screen capture for a Web Host. Real cross-network SFU/TURN media, game audio, a sustained public-network 1:20 session, mobile browser lifecycle behavior, and latency targets still require the documented manual test matrix.
## Run locally
diff --git a/docs/adr/0001-p2p-first-media-topology.md b/docs/adr/0001-p2p-first-media-topology.md
index 8e94ffca..a0d5b8ae 100644
--- a/docs/adr/0001-p2p-first-media-topology.md
+++ b/docs/adr/0001-p2p-first-media-topology.md
@@ -31,7 +31,7 @@ contradict the private-room cost model or duplicate mature WebRTC capabilities.
## Current Ownership
[ADR-0005](./0005-automatic-hybrid-media-routing.md) owns current routing
-invariants and assisted-route roles; the Browser `screener-v7` migration is
+invariants and assisted-route roles; the Browser `screener-v8` runtime is
implemented and deployed, while real-network validation remains open. [ADR-0004](./0004-peer-assisted-media-experiment.md)
owns only historical peer-assisted evidence. Access and room lifetime are owned
by [ADR-0002](./0002-memory-resident-protected-rooms.md).
diff --git a/docs/adr/0002-memory-resident-protected-rooms.md b/docs/adr/0002-memory-resident-protected-rooms.md
index 95e7c4be..ff669d33 100644
--- a/docs/adr/0002-memory-resident-protected-rooms.md
+++ b/docs/adr/0002-memory-resident-protected-rooms.md
@@ -1,6 +1,6 @@
# ADR-0002: Memory-Resident Rooms And Scoped Viewer Access
-- Status: Accepted; source implemented, production release pending
+- Status: Accepted; implemented and deployed
- Date: 2026-08-23
## Context
@@ -144,6 +144,7 @@ Current source implements this decision and has removed the old room modes,
and migration surface atomically on the single `screener-v8` wire. Focused source coverage spans allocation,
leases, orthogonal grant/code admission, rotate/revoke, password policy, local
profile replay, restart loss, HTTP, signaling, and browser storage privacy.
-Production still runs the older SQLite-backed release; do not report this
-decision as deployed until the new source is released and its deployment checks
-pass.
+Production release `352c457` runs this `screener-v8` model. The atomic cutover,
+restart-loss smoke, orthogonal grant/code admission, stale-v7 rejection,
+no-SQLite runtime, and read-only rollback restoration checks passed; exact
+operational evidence is owned by deployment and verification status.
diff --git a/docs/adr/0005-automatic-hybrid-media-routing.md b/docs/adr/0005-automatic-hybrid-media-routing.md
index 63f1699a..604eb0fc 100644
--- a/docs/adr/0005-automatic-hybrid-media-routing.md
+++ b/docs/adr/0005-automatic-hybrid-media-routing.md
@@ -149,7 +149,7 @@ and server-issued candidate connection identity. Parent and child therefore
prepare the same connection even when the parent's child set is unchanged by a
direct/selected-transport replacement; neither endpoint infers candidate
authority from an assignment-list difference.
-The Browser route release uses the single `screener-v7` wire. On each WebSocket,
+The current Browser runtime uses the single `screener-v8` wire. On each WebSocket,
the server sends the exact prepare before its TURN grant or SFU configuration;
the candidate child is queued before a peer parent is allowed to start its
offer. WebSocket ordering is the companion-delivery contract, so clients keep
@@ -309,7 +309,7 @@ deployment-wide.
## Current Deployment Boundary
-Production release `6b87732` runs the `screener-v7` Browser runtime. Its exact
+Production release `352c457` runs the `screener-v8` Browser runtime. Its exact
configuration, rollback artifacts, and postflight evidence are owned by the
deployment document; real heterogeneous-network and SFU/TURN media validation
remains open.
diff --git a/docs/deployment.md b/docs/deployment.md
index 2ae1f306..7e22c4e6 100644
--- a/docs/deployment.md
+++ b/docs/deployment.md
@@ -2,7 +2,7 @@
Last verified against upstream documentation: 2026-08-23.
-This page records exact release `6b87732` production facts and the current source
+This page records exact release `352c457` production facts and the current source
deployment contract. Product direction and pending migrations are owned by
[project memory](./project-memory.md) and [the TODO ledger](./todo.md).
@@ -25,20 +25,22 @@ 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 runs exact `6b87732b5f97b7836f628a2c333d0c3f05990c99`, release
-`6b87732`, from `/opt/screener/releases/6b87732`. The immutable source archive
+Production runs exact `352c4578954c399e56a2578cf3e22f5e0cfc2bad`, release
+`352c457`, from `/opt/screener/releases/352c457`. The immutable runtime archive
SHA-256 is
-`3e88575e3842074f3ecb5dcbd548c159d13a113316d70f680ac6629e39a7f733`.
-Immediate rollback is `/opt/screener/releases/9461e20`, with the verified
-pre-cutover SQLite/environment/LiveKit backup at
-`/opt/screener/backups/6b87732-precutover-20260823T115350Z`. Local and public
-health return 200; Screener, LiveKit, coturn, and nginx are active, and the
-restarted Screener/LiveKit services report `NRestarts=0`.
-
-The release deploys the single Browser `screener-v7` wire, 20-Viewer room
-admission, the uniform endpoint media-copy cap `2`, the one-controller
-exact-candidate route runtime, and stale-client rejection before room
-authority. LiveKit is dedicated, has `room.auto_create: false` and
+`d7feb021821b2af3db5180aed780da67ca582abfb3fe7a8805f6c6d88042bd3c`.
+Immediate rollback is `/opt/screener/releases/6b87732`, with the verified
+pre-cutover SQLite/environment/LiveKit/unit backup at
+`/opt/screener/backups/352c457-precutover-20260823T135843Z`. Local and public
+health return 200; Screener, LiveKit, coturn, and nginx are active with
+`NRestarts=0`.
+
+The release deploys the single Browser `screener-v8` wire, random four-digit
+memory rooms with a 24-hour dormant lease, orthogonal grant/code admission,
+20-Viewer room admission, the uniform endpoint media-copy cap `2`, the
+one-controller exact-candidate route runtime, and stale-v7 rejection before
+room authority. The service unit has no writable room StateDirectory and the
+old live SQLite path is absent. LiveKit is dedicated, has `room.auto_create: false` and
`max_participants: 21`, and is admitted to one global publication ingress plus
twenty subscription egress handles. Selected TURN has two logical allocations.
These bounds are fail-safe admissions, not throughput or quality claims.
@@ -140,7 +142,7 @@ TURN when configured; only an unavailable logical ingress uses the Host
publication/SFU path. A Host-SFU ingress may itself use selected TURN. 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 deployed in the current `6b87732` release with one UDP URL, a
+config/wire is deployed in the current `352c457` release with one UDP URL, a
120-second credential TTL, and two logical allocations. It was not exercised by
a real media session during this cutover.
@@ -298,7 +300,7 @@ lifetime. An actively connected Host prevents expiry; explicit stop or Host
disconnect starts the lease, and only the exact Host token renews it before
expiry. Viewer activity never renews ownership. `ROOM_DATABASE_PATH` and
`ROOM_TTL_SECONDS` fail startup even when blank.
-Production `6b87732` accepts 1 through 20 and explicitly selects 20. This is an
+Production `352c457` accepts 1 through 20 and explicitly selects 20. This is an
admission limit, not evidence that every publisher, network, or quality profile
can sustain that many streams.
`ENDPOINT_MEDIA_COPY_CAPACITY` defaults to 2 and accepts only 1, 2, or 3. It is
@@ -314,12 +316,11 @@ TURN allocation admission.
Supplying the removed `MAX_PEER_RELAY_DOWNSTREAM_EDGES`, even blank, fails
startup.
-Production release `6b87732` runs the deployed server and Browser assets
-atomically on `screener-v7`. The memory-room candidate advances server and
-Browser assets together to `screener-v8`; stale v7 Browser and executable-sender
-wires fail before room authority. Native senders and helpers are outside this
-release. Restore the exact prior environment, LiveKit configuration, database
-backup, server, and Web assets together when rolling back.
+Production release `352c457` runs the deployed server and Browser assets
+atomically on `screener-v8`; stale v7 Browser and executable-sender wires fail
+before room authority. Native senders and helpers are outside this release.
+Restore release `6b87732` with the exact precutover environment, unit, LiveKit
+configuration, and SQLite backup when rolling back.
The four `LIVEKIT_*` values must either all be absent or all be present, and a
complete tuple requires `PEER_ASSISTED_MEDIA=true` plus explicit positive
diff --git a/docs/project-memory.md b/docs/project-memory.md
index b19ac69e..0c4d221f 100644
--- a/docs/project-memory.md
+++ b/docs/project-memory.md
@@ -28,8 +28,8 @@ Last updated: 2026-08-23
- Canonical source is the root `main` branch. Audit/integration boundaries require it to be clean, and new branches/worktrees start from its exact commit only after accepted truth is merged.
- Current source admits up to `20` Viewers and implements the uniform `1/2/3` endpoint cap, single Browser `screener-v8` wire, exact prepare candidate, first-decoded-frame commit, strict rollback revision, decoded-progress stall, and one event-driven room controller. Older Browser and executable-sender wires fail before room authority. SFU admission uses exact publication and Viewer-subscription handles with explicit no-default ingress/egress capacities and a listener-fenced dedicated LiveKit owner. Selected TURN uses its own explicit no-default deployment capacity and exact logical-allocation ledger shared by independent peer edges and Host-SFU ingress.
-- Current source implements the memory-resident room model: random free four-digit codes, the configurable dormant lease, exact-Host resume, restart loss, local creation-preference replay, orthogonal Viewer grants and `open | password | disabled` code entry, and direct invitation/policy controls. SQLite room persistence, `ROOM_DATABASE_PATH`, and `ROOM_TTL_SECONDS` are removed. Production still runs the older SQLite-backed release until this source is deployed.
-- Production runs exact `6b87732b5f97b7836f628a2c333d0c3f05990c99`, release `6b87732`, wire `screener-v7`; `9461e20` is the rollback release.
+- Current source and production implement the memory-resident room model: random free four-digit codes, the configurable dormant lease, exact-Host resume, restart loss, local creation-preference replay, orthogonal Viewer grants and `open | password | disabled` code entry, and direct invitation/policy controls. SQLite room persistence, `ROOM_DATABASE_PATH`, `ROOM_TTL_SECONDS`, and the writable room StateDirectory are removed from the v8 runtime; the stopped v7 SQLite snapshot exists only in the verified rollback backup.
+- Production runs exact `352c4578954c399e56a2578cf3e22f5e0cfc2bad`, release `352c457`, wire `screener-v8`; `6b87732` is the immediate rollback release.
- Production implements the current endpoint-cap and route-controller contract, admits 20 Viewers, uses LiveKit admission of one publication ingress plus 20 subscription egress handles on a dedicated non-auto-create instance, and bounds selected TURN to two logical allocations.
- Production retains access controls, self-check, diagnostic export, signaling watchdog behavior, 64/128/256 audio choices, and selected-edge transport. Real heterogeneous-network and SFU/TURN media evidence remains open.
- `screener`, LiveKit, coturn, and nginx are healthy; local and public health return 200 and `screener` has `NRestarts=0`. Deployment detail is owned by [deployment](./deployment.md).
@@ -38,7 +38,7 @@ Last updated: 2026-08-23
## Current Priority
1. Keep this truth set and [the TODO ledger](./todo.md) concise and internally consistent.
-2. Release live audio and paused video-codec switching next, follow with evidence-led H.264 diagnosis, the strict-NAT emulator gate, connection feedback, then the source-complete memory-resident room/access slice and the remaining functional roadmap. Distribution packaging starts only after those TODOs are complete. Parallel branches may finish earlier but do not change this merge/deployment order.
+2. Release live audio and paused video-codec switching next, follow with evidence-led H.264 diagnosis, the strict-NAT emulator gate, connection feedback, and the remaining functional roadmap. Distribution packaging starts only after those TODOs are complete. Parallel branches may finish earlier but do not change this merge/deployment order.
## Working Rules
diff --git a/docs/research/peer-assisted-media.md b/docs/research/peer-assisted-media.md
index 2ca95469..9dbf20ac 100644
--- a/docs/research/peer-assisted-media.md
+++ b/docs/research/peer-assisted-media.md
@@ -520,7 +520,7 @@ event arrives later. The application therefore needs a small text-message
challenge rather than waiting for either protocol Ping/Pong or the old socket's
close event.
-Under the current `screener-v7` Browser wire, the Web client sends
+Under the current `screener-v8` Browser wire, the Web client sends
`signaling-challenge { sequence }`, and the server sends the exact
`signaling-challenge-response { sequence }` only to that requesting socket.
Server and Browser assets deploy atomically; stale Browser and executable-sender
diff --git a/docs/session-handoff.md b/docs/session-handoff.md
index cd72cf1f..1de39e1b 100644
--- a/docs/session-handoff.md
+++ b/docs/session-handoff.md
@@ -31,17 +31,17 @@ Current high-signal boundary:
- docs/status.md owns the exact source/production/hold state.
- docs/todo.md is the only executable work ledger and owns ordering.
-- ADR-0005 owns the accepted automatic route model. The Browser `screener-v7`
- source is implemented and deployed as release `6b87732`; real external-network
+- ADR-0005 owns the accepted automatic route model. The Browser route remains
+ implemented and deployed in release `352c457`; real external-network
and SFU/TURN media evidence remains open. Do not rerun broad or
executable/native test suites unless the current acceptance boundary
specifically requires them.
- ADR-0002 owns the source-implemented room model: one process-memory RoomStore,
random free four-digit codes, configurable 24-hour dormant leases, restart
loss, local Host preference replay, an independent expiring Viewer grant, and
- open/password/disabled code entry. Current source uses the single
- `screener-v8` wire and has removed SQLite; production has not deployed this
- room/access/UI slice and remains on the older v7 SQLite boundary.
+ open/password/disabled code entry. Current source and production use the
+ single `screener-v8` wire and no SQLite runtime; `6b87732` plus the verified
+ precutover SQLite snapshot remains the immediate rollback boundary.
- docs/maintenance.md owns the reusable mechanism-simplification review. SQLite
is its reference case because the bounded restart-experience loss did not
justify the persistence surface; accepting that tradeoff changed the contract,
diff --git a/docs/status.md b/docs/status.md
index be3dab70..0b13b994 100644
--- a/docs/status.md
+++ b/docs/status.md
@@ -6,9 +6,9 @@ This is the current execution index. Git history owns completed timelines; [veri
## Production
-- `https://share.bonfire.icu` runs exact `6b87732b5f97b7836f628a2c333d0c3f05990c99`, release `6b87732`, wire `screener-v7`; `9461e20` is the rollback release and its pre-cutover environment/config/SQLite backup is retained.
-- `screener`, LiveKit, coturn, and nginx are active; local/public health return 200, both restarted services report `NRestarts=0`, and SQLite schema v3 remains protected with mode 0600.
-- Production admits one Host plus 20 Viewers, applies endpoint capacity `2`, rejects stale Browser and executable-sender wires before room authority, and runs the one-controller exact-candidate route model. LiveKit is dedicated with `room.auto_create: false`, `max_participants: 21`, global admission `1` publication ingress / `20` subscription egress; selected TURN has `2` logical allocations.
+- `https://share.bonfire.icu` runs exact `352c4578954c399e56a2578cf3e22f5e0cfc2bad`, release `352c457`, wire `screener-v8`; `6b87732` is the immediate rollback release and `/opt/screener/backups/352c457-precutover-20260823T135843Z` retains its verified environment/unit/LiveKit/SQLite boundary.
+- `screener`, LiveKit, coturn, and nginx are active; local/public health return 200 and all services report `NRestarts=0`. The v8 unit has no writable room `StateDirectory`, the process has no SQLite descriptor, and the old live SQLite path is absent.
+- Production admits one Host plus 20 Viewers, applies endpoint capacity `2`, rejects stale v7 Browser and executable-sender wires before room authority, and runs the one-controller exact-candidate route model. Rooms use random free four-digit codes, a 24-hour dormant lease, restart loss, local Host creation preferences, independent Viewer grants, and `open | password | disabled` code entry. LiveKit remains dedicated with `room.auto_create: false`, `max_participants: 21`, global admission `1` publication ingress / `20` subscription egress; selected TURN has `2` logical allocations.
- Production still has access/privacy controls, self-check, diagnostic export, signaling watchdog behavior, 64/128/256 audio choices, and selected-edge transport. These deployment facts do not close the real heterogeneous-network, SFU/TURN media, mobile, or endurance evidence boundaries.
## Current Source
@@ -16,20 +16,20 @@ This is the current execution index. Git history owns completed timelines; [veri
- Canonical source is the root `main` branch; auxiliary branches and worktrees do not own current truth. Audit/integration boundaries require a clean root, and dependent work starts only from its exact commit.
- Current source implements one steady outbound media-copy cap for every non-server endpoint: default `2`, static `1/2/3`, a peer child or Host publication consumes one slot, upstream receive is free, a committed selected TURN transport replaces the same copy while hidden carry consumes another, and no Browser/UA/visibility tier exists. One shared guard owns the accounting and transition work is bounded by `min(C + 1, 3)`.
- Current source and production admission support one Host plus up to `20` Viewers. Focused controller coverage includes `C=1/2/3`, a 20-Viewer graph, and the passed local 20-Viewer Browser smoke; real external-network media and resource measurements remain open.
-- The single Browser `screener-v8` source boundary rejects stale Browser and executable-sender wires before room authority and carries the exact deployment cap plus exact prepare candidate in the authenticated route contract. Production remains on `screener-v7` until this incompatible room slice is atomically released.
+- The single Browser `screener-v8` boundary rejects stale Browser and executable-sender wires before room authority and carries the exact deployment cap plus exact prepare candidate in the authenticated route contract.
- Current source also implements explicit no-default SFU ingress/egress capacities and exact `reserved | committed | draining` accounting. The listener owner reconciles its dedicated non-auto-create LiveKit namespace before serving, creates each generation before token issuance, releases only after delete-plus-absence proof, and reclaims Host-offline generations through bounded exact-participant checks. Selected TURN has an independent explicit no-default deployment capacity; one process-local ledger charges every exact peer-selected edge and Host-SFU ingress through reserve, commit, drain, and release.
- Current source implements automatic P2P-first routing with one active upstream, an acyclic source-reachable graph, exact Browser v7 prepare tuple, first-decoded-frame make-before-break, strict rollback revision, and bounded wait or failure.
- One event-driven controller owns the committed graph and at most one room-serial child operation. The operation owns one deterministic tuple list/cursor, one current candidate and reservations, fact version, and one total deadline. Failed tuples are operation-local; exhaustion retires invalid/overflow edges but retains healthy bootstrap media. Bounded-gap preflights resources, replans the remaining suffix, and restores a healthy retired edge through one final ordinary candidate. Admission commits synchronously before graph promotion; release uses the resource-set difference and room disposal returns all resources. One Host publication serves exact Viewer subscription handles, selected TURN changes only transport, and actual global resource release wakes registered waiting rooms.
- Parent selection is deterministic rather than random or score-based: hard eligibility filters, then shallowest result, remaining sender capacity, stable join order, and peer identity. The exact candidate child's first new decoded frame is the only application media-ready event. Moderate bitrate, FPS, or visual degradation remains with stock WebRTC/LiveKit adaptation and diagnostics; only hard connection failure or a non-paused decoded-frame stall invalidates a route edge. Viewer connection feedback and the strict-NAT emulator gate are accepted follow-up work, not deployed behavior.
- Browser initial capture and source switching already request available share audio through one shared capture boundary and visibly retain video-only sharing when no audio track is returned.
- Live 64/128/256 audio-ceiling mutation and paused-share video codec switching are accepted but not yet implemented on canonical `main`. H.264 startup blur/low-FPS reports remain an evidence-led diagnosis, not a presumed codec defect. Public-server and fully local distribution packages are later work after the functional, NAT, and real-network ledger is complete.
-- Current source implements one process-memory RoomStore with random four-digit codes, a default 24-hour dormant lease, exact-Host resume, restart loss, local Host preference replay, independent token invitations and `open | password | disabled` code entry, and no SQLite. The Host UI separates the invitation, room-code entry policy, password, grant update, and grant revoke controls. Production still uses the old 12-digit/SQLite and `private-link | public-watch` surfaces until this source is deployed.
+- Current source and production implement one process-memory RoomStore with random four-digit codes, a default 24-hour dormant lease, exact-Host resume, restart loss, local Host preference replay, independent token invitations and `open | password | disabled` code entry, and no SQLite runtime. The Host UI separates the invitation, room-code entry policy, password, grant update, and grant revoke controls.
## Current Milestone
1. Release live audio-ceiling mutation and paused-share codec switching on the deployed generation/transition boundary.
2. Reproduce the H.264 startup report before any codec-specific repair, and build the strict-NAT emulator gate before any manually approved canary in an operator-owned test room.
-3. Add first-frame-driven Viewer connection stages, then release the source-complete memory-resident room/access slice and finish the remaining accepted functional and real-network work.
+3. Add first-frame-driven Viewer connection stages, then finish the remaining accepted functional and real-network work.
4. Validate and deploy each coherent slice in this order with its focused browser/network/resource and rollback gates; distribution packaging remains outside this milestone.
## Active Boundaries
@@ -37,11 +37,11 @@ This is the current execution index. Git history owns completed timelines; [veri
- `fix/configurable-relay-cap` is an old, incomplete draft and must not be merged as-is.
- Open PR #192 and the Native stack are evidence/research, not pending product releases. Native senders, capture helpers, shared-encode executables, and their test binaries are outside the current Browser milestone and are not built or run.
- Deployed surfaces and retained candidates that still need product decisions are indexed only in [the TODO ledger](./todo.md); do not extend or roll them back automatically.
-- Room entry, sharing controls, ID lifetime, and storage semantics are implemented in current source. Production remains divergent until that complete `screener-v8` slice atomically replaces the old access and persistence model at its accepted release boundary.
+- Room entry, sharing controls, ID lifetime, storage semantics, v8 stale-client rejection, restart loss, and rollback restoration are aligned between current source and production.
- Real SFU/TURN recovery, heterogeneous networks, mobile lifecycle, audio/A-V device behavior, and endurance/resource measurements remain external acceptance evidence, not blockers for unrelated reversible work.
## Current Hold
-The Browser route is implemented and deployed, and the room source slice is complete but not
-deployed. Later TODO work is intentionally paused until the owner chooses the next slice; do not
-start deployment, route rollback, Native/executable work, or broad cleanup without a new instruction.
+The Browser route and memory-room slices are implemented and deployed. Later TODO work is
+intentionally paused until the owner chooses the next slice; do not start live-media deployment,
+route/room rollback, Native/executable work, or broad cleanup without a new instruction.
diff --git a/docs/todo.md b/docs/todo.md
index 4b9d0783..8a0bb240 100644
--- a/docs/todo.md
+++ b/docs/todo.md
@@ -12,10 +12,6 @@ Only items in **Now** are executable after their stated decision gate. A branch
4. **Gate the strict-NAT guessed-candidate experiment.** Build only the isolated endpoint-dependent NAT emulator and browser harness first. Standard ICE must fail in the owned fixture, the capped candidate set must pass the documented repeatability, deadline, privacy, and cleanup gates in stable Chrome and Firefox, and fallback must remain unchanged. Only then may one manually approved, operator-owned test room run a default-off, kill-switched canary with explicit consent from both endpoints and exact room/edge/generation/budget bounds; failure closes the candidate. Do not ship guessed candidates to ordinary rooms or infer NAT type from IP, UA, carrier, or two STUN observations.
5. **Make Viewer connection progress explicit.** Derive one stable stage from existing access, route, peer/SFU, media, autoplay, and bounded-failure state. Keep the overlay until a composited current-generation frame, show `Play` only for actual autoplay rejection, preserve a still-valid old frame during recovery, and expose retry only through the bounded controller. Measure the existing token-free SFU prewarm and route stages before adding another connection mechanism.
-## Queued After Connection Feedback
-
-1. **Release memory-resident rooms and clear sharing controls.** The `screener-v8` source implementation and local gates are complete. At this accepted release boundary, run production preflight, atomically replace `ROOM_DATABASE_PATH` / `ROOM_TTL_SECONDS` with `ROOM_LEASE_SECONDS`, deploy server and Browser assets together, verify old v7 clients fail before room authority, confirm restart-wide room loss and same-browser preference replay, then run postflight and rollback verification. Do not migrate SQLite rooms or preserve a v7 compatibility path.
-
## Accepted Later Roadmap
These items are real product work, ordered after the current release boundary; they are not permission to resume an old branch wholesale.
diff --git a/docs/verification-status.md b/docs/verification-status.md
index 0c8bd9b9..dbfe9207 100644
--- a/docs/verification-status.md
+++ b/docs/verification-status.md
@@ -10,10 +10,11 @@ Capacity and routing entries below describe the exact tested source or release o
## Deployment Evidence
-- Production runs exact `6b87732b5f97b7836f628a2c333d0c3f05990c99`, release `6b87732`, wire `screener-v7`, from `/opt/screener/releases/6b87732`; the immutable archive SHA-256 is `3e88575e3842074f3ecb5dcbd548c159d13a113316d70f680ac6629e39a7f733`. `9461e20` remains the rollback release, and `/opt/screener/backups/6b87732-precutover-20260823T115350Z` contains the verified pre-cutover SQLite/environment/LiveKit configuration.
-- The 2026-08-23 postflight found `screener`, LiveKit, coturn, and nginx active with zero restarts after cutover; local and public `/healthz` returned 200. The deployed browser bundle is `assets/index-BzbOwAcC.js`, SHA-256 `680bc27dcb3951cdbde54acaa4c7a456682946c1ba72076e956fc9ce6525f91f`, matching the locally built artifact and containing the single `screener-v7` wire literal.
-- Production uses endpoint capacity `2`, room admission `20`, a dedicated LiveKit instance with `room.auto_create: false` and `max_participants: 21`, global SFU admission `1` ingress / `20` egress, and selected TURN admission `2`. These are conservative bounded admissions, not throughput or quality claims. LiveKit listed zero rooms after startup, and SQLite v3 remains integrity-ok with six rooms, owner `screener:screener`, and mode 0600.
-- Rollback evidence confirms the old release entrypoint is readable, every pre-cutover backup checksum passes, the backed-up database remains schema v3/integrity-ok with six rooms, and the current and rollback release regular-file sets share zero inodes.
+- Production runs exact `352c4578954c399e56a2578cf3e22f5e0cfc2bad`, release `352c457`, wire `screener-v8`, from `/opt/screener/releases/352c457`; the immutable runtime archive SHA-256 is `d7feb021821b2af3db5180aed780da67ca582abfb3fe7a8805f6c6d88042bd3c`. `6b87732` is the immediate rollback release, and `/opt/screener/backups/352c457-precutover-20260823T135843Z` contains the verified environment/unit/LiveKit/SQLite boundary.
+- The 2026-08-23 postflight found `screener`, LiveKit, coturn, and nginx active with zero restarts; local and public `/healthz` returned 200 and the Screener journal contained no error line. The deployed browser bundle is `assets/index-BVK8yQk2.js`, SHA-256 `388a093734e8dc37a07b859651ea15d4098a8c8f13864ca9d70eb99128a911a3`, matching the locally built artifact and containing one `screener-v8` and zero `screener-v7` literals.
+- Production uses endpoint capacity `2`, room admission `20`, random free four-digit memory rooms, `ROOM_LEASE_SECONDS=86400`, a dedicated LiveKit instance with `room.auto_create: false` and `max_participants: 21`, global SFU admission `1` ingress / `20` egress, and selected TURN admission `2`. The v8 service has no StateDirectory or SQLite descriptor; the old live SQLite file/directory is absent and LiveKit listed zero rooms after startup.
+- A public control-plane smoke passed site access, four-digit creation, Host v8 authentication, stale-v7 rejection before authority, independent code-only and grant Viewer admission, grant rotation that preserved the code Viewer, signaling challenge, and exact room abandonment. A separate service-restart smoke rejected the old Host token and Viewer grant, atomically created a password-policy replacement room, and abandoned it.
+- Rollback evidence confirms release `6b87732` and its old environment/runtime imports are readable, every precutover backup checksum passes, the backed-up database remains schema v3/integrity-ok with six rooms, and the current and rollback release regular-file sets share zero inodes.
- Share audio presets, local-only diagnostics, self-check, diagnostic export, signaling-partition recovery, and selected-edge transport remain deployed surfaces. Their real-route media behavior and target-browser field availability remain unverified.
## Retained Functional Evidence
@@ -42,7 +43,7 @@ Capacity and routing entries below describe the exact tested source or release o
- Observability: the UI and local stats plumbing are deployed, including identity-bound relayed-detail retention and export freshness guards, but target-browser availability and actual values remain unverified for Host SFU sender evidence, codec/fmtp and encoder implementation/power efficiency, media-source and encoded FPS, A/V playout/jitter/concealment, selected candidate endpoints, and bounded same-pair STUN-response observation. These fields diagnose and have no recovery authority; they do not by themselves prove hardware encode, synchronization quality, or route quality.
- Mobile: Android/iOS remain Viewer-only. Autoplay, rotation, iOS lock-screen/page reclamation, background reconnection, and network changes need device evidence. AirPlay/system mirroring is Viewer-local output, not a portable in-app WebRTC output contract.
- Native: ADR-0006 has one-Viewer evidence only. Viewer2/FIFO, hardware diversity, endurance, downloaded-package/public-host, game A/V, and browser diversity remain open.
-- Access and operations: the v8 candidate still needs production preflight/postflight for atomic environment replacement, stale-v7 rejection before authority, restart-wide room loss, same-browser recreation, fragment/rotate/revoke behavior, and exact request/nginx/journal inspection. Preserve the stopped v7 SQLite backup only as the rollback boundary; the v8 runtime must create no room database or writable room directory. The isolated VM/IP gate remains required before clean-port migration; shared-IP smoke cannot approve it.
+- Access and operations: v8 production preflight/postflight, atomic environment/unit replacement, stale-v7 rejection, restart-wide room loss, password-profile creation, grant/code orthogonality, rotate/revoke, no-SQLite runtime, and exact current journal/nginx sentinel checks passed. Three historical rotated nginx access logs containing the current site secret in old `/r/...` request paths were deleted, and all remaining plain/gzip nginx logs plus Screener/LiveKit journals rescanned with zero site-secret hit. Headful same-browser preference replay and the isolated VM/IP clean-port matrix remain open; shared-IP smoke cannot approve them.
## Evidence Rules
diff --git "a/docs/\346\226\271\346\241\210\350\256\276\350\256\241.md" "b/docs/\346\226\271\346\241\210\350\256\276\350\256\241.md"
index c3fa2f96..62c21a2c 100644
--- "a/docs/\346\226\271\346\241\210\350\256\276\350\256\241.md"
+++ "b/docs/\346\226\271\346\241\210\350\256\276\350\256\241.md"
@@ -360,7 +360,7 @@ Token-free SFU standby prewarm 保持可选且不创建 participant、publicatio
8. 当前发布只验收 Web Host、Viewer 和 browser relay。Native sender、capture helper 与 shared-encode executable 排在整体 roadmap 最后,不参与当前构建、路由验收或发布。
9. 当前功能、NAT 与真实网络 TODO 完成后,再分别设计和交付公网服务器一键部署包与完全不依赖外部服务的本地 Host-server 包。
-生产仍运行 `screener-v7` route release `6b87732`;当前房间 source 使用 `screener-v8`。内部不兼容 wire/schema 原子切换,Git commit 与部署备份承担回滚,不保留兼容实现。
+生产已运行 `screener-v8` room/route release `352c457`。内部不兼容 wire/schema 原子切换,Git commit 与部署备份承担回滚,不保留兼容实现。
任何一步只实现当前消费者需要的接口。不得为未来账号、第三种媒体拓扑或原生 sender 预建抽象层。