AAA
89a03e6470
## Problem and outcome / 问题与结果 This maintenance phase fixes failures around native capture startup, room reconnection and media handoffs. Capture mutations stay cancellable, relayed-content failures remain request-scoped, and failed media connections return to the existing route controller. Windows Auto codec selection measures delivered cadence instead of timer-sensitive per-frame work estimates. The phase preserves P2P-first routing, one committed graph and one route operation. It adds no signaling replay mechanism, changes no wire/schema version, and includes no interaction prototype or 4K feature work. ## Release notes ### 中文 Piik v1.6.8 是一次稳定性修复，重点改善 Windows 原生采集、断线恢复和分享过程中的控制响应。 #### 修复与改善 - **更准确地选择编码器。** Windows 的自动模式按实际出帧表现评估 H.264，并正确区分启动预热和持续性能不足，减少计时误差导致的不必要 VP8 回退。硬件编码事件改为异步等待。 - **改善断线与线路切换。** 房间信令短暂断开后保留观众成员身份 20 秒；修复线路切换、SFU 订阅恢复及声音重协商卡住的问题。失效连接及时交回现有路由控制器处理，原生 SFU 发送端不再把短暂断连直接判为终止。 - **保持 App 控制响应。** 开始分享和更换来源时仍可取消操作；合法消息突发不再直接关闭控制连接。中继信令的单条内容错误不会连带结束整场原生分享。 - **修正设备列表与配置保存。** 来源或麦克风数量达到上限时保留可用列表；配置替换失败时保留原有设置。 - **改善紧凑布局和辅助功能。** 调整手机横屏下的画面与播控布局、画质预设标签和长邀请链接显示，修正部分提示与辅助功能语义。 - **加强站点访问保护。** 站点登录 Cookie 使用独立随机签名密钥，应用自身阻止被其他页面嵌套。发布说明也会在合并前检查。 #### 升级说明 通信协议和持久化格式保持不变。设置了站点密码时，App 或 Server 重启后需要重新输入站点密码；持久化房间和邀请授权不受这项 Cookie 调整影响。Piik 操作页面不再支持嵌入 iframe。 ### English Piik v1.6.8 is a stability update focused on Windows native capture, connection recovery and responsive sharing controls. #### Fixes and improvements - **More accurate codec selection.** Windows Auto mode evaluates H.264 using delivered frames and distinguishes startup warmup from sustained performance limits, reducing unnecessary VP8 fallback caused by timing noise. Hardware encoder events now use asynchronous waiting. - **Improved reconnection and route handoffs.** Viewer membership survives brief signaling outages for 20 seconds. Fixes cover route activation, SFU subscription recovery and stalled audio renegotiation. Failed connections return to the existing route controller, and the native SFU publisher no longer treats a transient disconnect as immediate termination. - **Responsive App controls.** Starting a share and replacing its source remain cancellable. Valid message bursts no longer close the control connection, and an invalid relayed payload cannot terminate the entire native sharing session. - **Device lists and saved settings.** Source and microphone enumeration retain a usable list at their limits. Failed configuration replacement preserves the previous settings. - **Compact layouts and accessibility.** Improved picture and playback-control layout on landscape phones, quality preset labels and long invitation links, with corrected tooltip and accessibility semantics. - **Stronger site-access protection.** Login cookies use an independent random signing key, and the application prevents embedding by other pages. Release notes are also checked before merge. #### Upgrade notes Wire protocols and persistent formats are unchanged. If a site password is configured, restarting the App or Server requires entering it again; this cookie change does not revoke persisted rooms or invitation grants. Piik operation pages can no longer be embedded in an iframe. ## Verification / 验证 - `npm run check`: passed, 76 test files / 1,171 tests, TypeScript and production Web build. - `npm run check:go-core`: passed; full Go/native checks also passed during integration of the capture changes. macOS cgo builds remain native-runner checks. - Windows native Host gates: Auto, H.264 and VP8 passed during the phase; final control changes rechecked with Auto, including live/paused quality, source replacement, failure retirement and subsequent sharing. - Embedded SFU browser VP8 recovery: passed with production Host/Viewer route owners. - Embedded SFU native H.264, two rooms: passed, including recovered decoded video/audio, independent room retirement and resource cleanup. - Documentation, repository hygiene and diff checks: passed. Final follow-up changes only align operations documentation with the PR note check. - Go race checks could not run locally because no cgo/GCC toolchain is available; the existing Linux CI race job remains required. AMD/Intel hardware, broader device combinations, public-NAT field reports and long endurance are not established by these local checks. ## Impact / 影响 Compatible patch release after v1.6.7. The cookie and frame-protection effects are disclosed in the public upgrade notes. No automatic retry budget, room-code admission policy, room lifetime or media topology is replaced. Reports without matched diagnostics and unmeasured native performance costs remain in the TODO ledger.
6.5 KiB
Current Status
Last updated: 2026-09-29
This is the compact execution/deployment index. Product modules own behavior, verification status owns unresolved physical limits, and Git/PRs own completed history.
Accepted Release Contract
- Browser/server v23, Native control v9 and capture v7 form the current contract. Versioning owns compatibility between published Web/App/Server versions.
- Hosted Server defaults to SQLite schema 2. Room authority has no inactivity expiry; explicit replacement/deletion or grant rotation/revocation ends the corresponding authority. Explicit memory mode and App Local end rooms at process exit. Site access retains its separate 24-hour idle lifetime within one service run; service restart requires site-password entry again.
- Browser/App entry lifecycle and current-edge reconnect ownership repairs are implemented. Browser node-local pooling and detailed local Debug export remain part of the accepted media surface. Product modules own their behavior; configuration owns Debug activation, report contents and disclosure.
- Shared feedback composition is implemented: generic loading uses the wink mascot, concrete media waits use their owning comic, and waiting captions are secondary to literal status. Website reduced-motion preference and player tooltip placement follow the same presentation owners.
- Camera sharing and Host microphone commentary are accepted product features. Both Browser and native App audio use the existing media routes; device selection and sharing settings keep their current resource owners. The capture assessment owns platform behavior and the remaining physical evidence limits.
Website delivery includes a bilingual reader documentation center generated from the repository's guides alongside the homepage, with search and detailed troubleshooting separate from the homepage FAQ.
Deployment
Source, package identity, GitHub repository and local worktree paths use Piik.
Runtime code keeps only the Piik wire labels and stored keys.
The immutable release descriptor, runtime REVISION and operator deployment
record own exact identity and postflight results.
The existing deployment uses one Go process for Web, room authority/signaling, Binding-only STUN on UDP 3478/3479/3480 and optional SFU on UDP 7882. nginx owns HTTPS; external LiveKit/coturn services remain disabled. Participants, routes and media remain process-only. This private service is not a public demonstration.
The separate US public demo is deployed with open site entry, persistent room authority and P2P-only media. Cloudflare fronts HTTP/WSS and caches static bundles; STUN uses a separate DNS-only hostname. Caddy owns origin HTTPS, and the standard systemd service runs the published Server package. Public DNS, HTTPS, runtime assets, all three STUN listeners and a bounded browser P2P sharing/stop check passed; the browser check used synthetic video on one network. The operator record owns exact identity and postflight evidence.
TODO owns remaining verification and follow-up work. The owner declared the first
public release on 2026-09-12. Source is public, main protection is active, and
piik.tv runs on GitHub Pages behind Cloudflare with HTTPS. The private service
remains a separate deployment. Release descriptors and GitHub deployment records
identify published artifacts and website revisions.
The matching Server and three App packages are published on GitHub and Gitee; anonymous mirror downloads match the original checksums. Public-repository CI and native packaging passed. App entry, update links and bounded two-build interoperability have acceptance evidence. Accepted product changes publish automatically; standalone website and documentation changes validate and deploy the website without creating App/Server versions. GitHub/Gitee release comparison, mirror publishing and PR-sourced notes follow versioning. Verification status owns the remaining physical limits; shared lessons live in engineering.
Media Evidence And Limits
- Compatible Native consumers share one complete stock WebRTC encoding and adaptation pipeline per local output. Different weak demands stay independent; suitable received media can be forwarded without decoding/re-encoding. Pion/LiveKit retain transport, estimation, pacing and forwarding ownership.
- Windows H264/VP8 have bounded encoding/adaptation evidence. Actual Native relay checks cover compatible sharing, weak-budget separation and rejoining, source retirement and large encoded-frame delivery. These results do not establish a universal encoder count, CPU saving or Browser-equivalent quality.
- Windows Host acceptance covers live and paused settings, quiet-source preparation/restore, source changes and subsequent sharing. The owner confirmed Windows 10 whole-display capture resolved. Specific new game/device failures should be reopened from new evidence.
- Native Host publication through embedded SFU retains video/audio; Browser to App fanout and App-exit fallback have bounded physical checks. Two independent Native sessions have simultaneous media/retirement evidence.
- The Linux runtime container has non-root/read-only, memory/SQLite, diagnostic export, STUN and listener-lifecycle evidence. This does not establish every operator's proxy/firewall or public-media configuration.
- The independent Browser producer in ADR-0014 is integrated. Bounded H264/VP8 checks cover direct and received-track sharing, weak-child isolation/recovery, live/quiet settings, pause, source change and ordinary fallback. Its native allocation and complete-frame output replace the earlier payload-only Worker path. Fewer full encodes are established; total CPU gains depend on codec/hardware. Browser research owns these measurements and failed controls. The owner accepted this scoped Browser composition for release; actual deployment identity stays in the runtime descriptor.
- Slow adaptation recovery, the extreme CPU-overload sampling limit and missing broad device/network/endurance results remain explicit in encoder research and verification status. macOS/Linux physical capture is deferred by the owner; Windows App and Browser are this phase's primary targets.