Piik/docs/status.md

Current Status

Last updated: 2026-08-19

Phase

https://share.bonfire.icu runs 769de201f7cc with simplified entry, bounded clarity-first controls, persistent rooms, and reusable links. Peer/LiveKit is unconfigured, so production remains one host connection per viewer and P2P/TURN.

Current Snapshot

• Capture precedes room creation; live source/quality changes preserve peers and picture pause keeps audio/connections. Quality defaults to maintain-resolution with balanced/fluid options.
• Optional ACCESS_PASSWORD uses a stateless 12-hour HMAC HttpOnly Strict cookie; host auth stays internal and signaling role-bound.
• Without ROOM_DATABASE_PATH, rooms are temporary. With it and the password, sequential links persist after stop; SQLite stores only room ID and host-token digest.
• Old production keeps coturn UDP/TCP. The candidate uses self-hosted STUN-only ordinary ICE, separate SFU/UDP roots, and bounded failure; HTTPS/WSS stays TLS/TCP. Selected-edge TURN is future work, not dormant config.
• SFU normally feeds one or two roots. Downstream cap is two, browser relay one; exceptional central edges need a separate cap. Production routing is off.
• Configured fallback adds a non-secret standby URL and token-free DNS/TLS warmup; absent configuration adds no field, import, request, participant, or edge.
• Each viewer advertises relay capacity 0/1; detected mobile/iPad clients are leaves. Withdrawal does not move a healthy edge. Browser relays stay one-child and host two-child.
• Production has memory-only video settings and manual readback. Automatic HIGH/FALLBACK plus one shared on-demand LOW is accepted but not deployed; local A+B and authenticated P2P Viewer C are read-only evidence. Browser audio is request/presence-only.

Verified Evidence

• Release 769de201f7cc passed CI/hygiene/typecheck, 22 files/274 tests, both builds, and zero production dependency vulnerabilities.
• Chrome 151 synthetic 1/3/5/8 kept host/relay edges at 2/1 and all viewers decoding; slowest first frame was 1.05 seconds and one three-viewer relay close recovered in 5.32 seconds.
• Synthetic Chrome 151 720p30 propagated balanced/clarity to one host and three viewers without peer changes; decoding and 2/1 fanout continued. This proves control continuity only.
• Chrome 151/LiveKit localhost A/B measured cold active/render at 1.481/2.257 seconds versus standby 0.200/0.320 with host edges at two. It includes SDK/prewarm and is not public-network evidence.
• Atomic activation passed health/access, exact bundle, SQLite preservation, services, and logs; the old release is rollback-ready. Responsive 320/375/390 px checks passed without live media.
• Host A+B aligns capture/outbound identity, deltas, path, and nullable transport-bound codec/scalabilityMode. Authenticated Viewer C is limited to the current ordinary or peer-assisted P2P hop and its connection/revision; two-second windows are at most 2 KiB, sanitized, generation-bound, and read-only. Stale, ambiguous, and SFU-fed evidence fails closed; no raw media metadata is retained.
• HTTPS/WSS, access and room/WebSocket auth, renewal, public STUN, and authenticated TURN/UDP/TCP relay-only paths pass; TURN/TLS is off.
• Draft #16/#18/#22/#23/#25/#28 passed isolated experiments only. ADR-0006 reached host setup/one encoder output, then timed out before viewer 1 decoded/rendered.

Unverified Boundaries

• Full-resolution 30-minute runs, relay CPU/GPU, controlled loss/RTT, and depth latency are unverified. Production 769de201f7cc game sharing is reported low-FPS/high-load; latest main, preview cost, codec, and hardware encoding are not yet compared.
• Android Chrome/iOS Safari leaves are unverified; runtime conservatively marks detected mobile/iPad clients as leaves.
• 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. Production reports poor film audio and voice-call self-echo under system capture; there is no app audio ceiling or Web process isolation. Diagnose A/B/C and sync, then gate Windows 11 game-process audio; Windows 10 stays unresolved without system fallback.
• Production 769de201f7cc reportedly sustains native qualityLimitationReason=bandwidth and severe blur with one capable LAN/direct viewer; only Host refresh restores quality. Within the five-second grace, stable-clientId Viewer refresh retains its peerId/HostPeer, while Host refresh rebuilds peers/capture; churn persistence is also reported. This prioritizes but does not prove sender/PC/GCC/capture generation over network or lifecycle causes.
• ADR-0007 remains incomplete. A+B/C browser support and the reported case are unverified; the controller, LOW, and an authenticated SFU last-hop C generation are absent. Weak paths must share one LOW; fail closed protects HIGH only exceptionally, and an unreliable supported cohort fails acceptance.
• Browser relays re-encode. ADR-0006 is no-go-unclassified: downstream checkpoints and two-edge/FIFO/TURN gates are absent. Spikes prove one WebCodecs object, not hardware; GCC+RTX is no-go and no-RTX weakens stats.
• Browser fanout is host two/viewer one; any accepted endpoint relay stays capped at two downstream edges.
• ADR-0005's candidate is process-wide STUN-only ordinary ICE plus separate LiveKit SFU/UDP and bounded failure, with no all-room TURN wire. It is default-off; enabling it requires non-empty exact room IDs, and missing/blank fails startup. The old release is isolated rollback.
• Pinned LiveKit 1.13.5 Dynacast enables all qualities at or below the room's maximum request, so a HIGH root is expected to keep LOW enabled. It remains a bounded rejection/verification spike, not evidence that on-demand LOW can stop.
• The corrected standby smoke is localhost/headless/video-only; public DNS/TLS reuse, transport, audio, shaping, load, mobile, endurance, and sub-25 ms overlap remain open.

Next Milestone

Use correlated Host A+B/Viewer C to compare exact production and current main on one wired/direct game fixture. Record actual codec/encoder, game FPS, CPU/GPU, preview on/off and A+B while separately rebuilding one HostPeer, replacing capture, and fully refreshing Host. Only a proven stuck generation justifies guarded recovery; never reconnect periodically, force AV1, or raise ceilings blindly.

After that reproduction, test simulcast/LiveKit/SVC in order and stop at the first fit before custom LOW, independently of ADR-0006. Diagnose audio A/B/C, sync, and voice-source leakage in parallel when it does not displace that P0; maxBitrate is not a quality fix. WebRTC/LiveKit owns congestion/layers; the app owns two-state policy. An isolated exact room later gates peer/SFU UDP and bounded failure before replacing the old release. Selected-edge TURN, if later justified, is a separate complete change rather than part of this canary. Post-gate UI adds local volume/mute, names/roster, endpoint details, and RTP loss.

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 20-viewer gate must pass before the current default eight changes to target 20.

Observed disconnects retain 5-second grace plus at most 3 seconds to a decodable picture; silent partitions add detection delay.

ADR-0004 fails closed. Native shared encode and packet/layer striping remain separate experiments, not ways to relabel a failed browser route.

Blockers And Decisions

Peer assistance and automatic routing remain No-Go until ADR-0004/0005 migration gates pass. Without LiveKit, two mobile leaves can fill both host roots; use an isolated exact-room canary only. Deferred architecture audit: docs/maintenance.md.

• Whole-system versus selected-game audio for the first release.
• Initial deployment region and network cohort.
• Project license and distribution model.