Piik/docs/status.md

Current Status

Last updated: 2026-08-27

This is the current execution index. Git history owns completed timelines; verification status owns evidence boundaries.

Production

• https://share.bonfire.icu runs exact application/runtime revision 73ed920a229bfc64c89b97045c00d6cd75216f3a, release 73ed920, wire screener-v13, from /opt/screener/releases/73ed920. The immutable runtime tar SHA-256 is 351053e497e8eee17956f4cec86305b05d805c80deb40b2cf4cd2668eaf08583; its 41-file manifest SHA-256 is bb993950a30a0b99b9b6185aa13777edcccbdcdaebdfb1b05b3c3499a1e78479.
• The served Browser entry references assets/index-CaM3Pn5_.js; the public asset SHA-256 is 3c64cd75a7d67716f7600465a1742b1c02f3b00e71a1039649604aaf6d08f816. Public /healthz returns 200. The release postflight found Screener, LiveKit, coturn, and nginx active with zero restarts.
• Production enables SQLite room authority at /var/lib/screener/rooms.sqlite; live participants, routes and media remain process-only. A controlled restart retained the room authority and Host-owned capture while the Viewer rebuilt media without a page refresh. Lightweight mode remains available when ROOM_DATABASE_PATH is unset and reacquires a room rather than persisting the old authority.
• Public media listeners remain STUN-only UDP 3478 and LiveKit UDP 7882. Web ingress is TCP 80/443; Node 8787 and LiveKit control/signaling 7880 are private. TURN, ICE/TCP, media TCP, TLS relay, port 5349, and relay ranges are disabled.
• Browser video uses the content-independent H.264 sender gate with VP8 fallback, plus the locked pre-share VP8 | Auto | H264 Host selector and resolved codec display. Video retains contentHint = "motion"; audio uses music. The SFU publisher uses the Host's one codec decision, leaves representation construction to pinned LiveKit, enables Dynacast, uses server send-side BWE, keeps AdaptiveStream disabled, and configures no external ICE servers on Browser SFU PCs.
• Screen audio provides live 64/128/192 kbps ceilings with 128 default. SFU publication uses stereo, DTX off, and RED off. Early autoplay presentation is gated by current media connection state.

Current Source

• Canonical source uses the strict screener-v14 Browser/server contract. Optional SQLite stable authority, non-expiring local preferred code, atomic room replacement and the Host codec selector remain implemented; production selects stable storage. Graceful restart, crash, timeout and network loss use one reconnect state. LiveKit room teardown cannot stop Host-owned capture.
• One event-driven controller owns the committed graph and one room-serial child operation. Initial direct acquisition uses a five-second foreground window; exact transport-connected progress may retain that candidate through the total deadline, while first decoded frame remains the only commit proof. SFU provides working media before finite background direct convergence. Healthy decoded edges remain sticky.
• WebRTC/LiveKit own media adaptation. With the per-share convergence gate enabled, one fresh degraded native edge may enter the existing serial route operation after availability work. A candidate commits only after first-frame readiness and fresh healthy native proof while the old edge remains degraded. Peer candidates stay first and bounded SFU is only the suffix after healthy Peer escape fails. The gate defaults off.
• Screener has no custom SFU layer list, quality score, layer selector, all-pairs probe, parent-wide prediction or periodic rebalancing. P2P and SFU still recover their current route before actual failure enters reassignment.
• Viewer hidden/freeze/pagehide suppress decoded-stall routing authority; visible/resume/pageshow rebaseline and rearm current-frame proof. SFU pagehide no longer triggers LiveKit's automatic disconnect. Native Viewer controls still own playback, and manual reconnect stays on the current route.

Current Milestone

Native-edge local convergence is implemented and locally accepted in source. Production remains on the evidence-only screener-v13 release until the current application release and scoped postflight complete.

Active Boundaries

• Desktop Host background capture remains unconfirmed. The current-browser screening did not reproduce a Host-page drop; accepted Viewer lifecycle work prevents frozen JavaScript wall time from becoming an immediate route failure but is not capture keepalive.
• Current-path quality can drive opt-in local convergence in source and remains diagnostic in production until deployment. Weighted/global optimization remains parked.
• Repository simplification does not change or deploy product behavior beyond deleting proven dead private surfaces.
• Native/executable senders, shared encode, distribution packages, broad UI polish, and bilingual support remain outside the current release.

Current Hold

No source or deployment P0/P1 is open. Native-edge convergence release and postflight are the current task; broader product evidence remains parked.