AAA
01821ae7ac
Public invitations could stop after an early tunnel-process exit, and connection progress and Viewer status did not consistently describe the current attempt or Host state. This maintenance release adds bounded startup retries, aligns enhanced NAT retry feedback across entry paths, and fixes camera-preview and room-entry layout. The existing route owner and published contracts remain in place. Four-attempt progress is advertised and opted into; older readers retain supported messages. Interaction/chat experiments are outside this PR. Validation: npm run check (74 files, 1072 tests and production build), npm run check:go (including Windows capture compile), documentation/repository hygiene, 10 production Viewer-entry discovery cases, and a real public-link gate with remote HTTP/WebSocket access and shutdown cleanup all passed. Existing device/network evidence limits remain documented. ## Release notes ### 中文 这是一次维护更新，重点改善公网邀请启动、连接重试反馈和分享状态提示，并修正两处界面布局问题。 - 公网邀请服务在连接就绪前意外退出时，会自动重试，最多重试 3 次；所有尝试仍共用 30 秒启动预算。 - 增强穿透连接在首次尝试失败后最多重试 3 次，重试进度显示为 1/3、2/3、3/3。邀请链接和房间号加入都支持新版进度提示。 - 修正观众状态提示：房主离线时不再误报“没有可用的媒体线路”，服务器连接恢复与媒体恢复也会分别呈现。 - 修正电视内房间号输入界面的居中位置，以及摄像头选择预览被裁切的问题。 - 尚未确认来源声音状态时，不再提前提示“未分享来源声音”。 本次保持现有版本兼容；新版重试进度需要页面与服务端均支持。额外重试不能保证所有网络都能直连。 ### English This maintenance update improves public invitation startup, connection retry feedback, and sharing status messages, with two layout fixes. - If the public invitation service exits before connecting, Piik retries up to three times within the existing shared 30-second startup budget. - Enhanced NAT traversal now allows up to three retries after the initial attempt, shown as 1/3, 2/3, and 3/3. Both invitation links and room-code entry support the updated progress display. - Viewer status now distinguishes an offline host from an unavailable media route, and reports server reconnection separately from media recovery. - Fixed the alignment of room-code entry inside the TV and cropping in camera-selection previews. - The missing-source-audio notice now waits until the source's audio availability is known. Existing version compatibility is preserved. Updated retry progress requires support from both the page and server. Additional retries cannot guarantee a direct connection on every network.
Piik standards
Current product and engineering rules live here. Start with the affected subject; the ownership map explains where each fact belongs. AGENTS.md owns task authority and Contributing owns delivery.
| Subject | Standard |
|---|---|
| Module responsibility, resources, interfaces and contextual consistency | Engineering |
| Product names, terminology, Chinese/English voice and content layers | Naming and copy |
| Room authority, invitation/password access and persistence | Rooms and access |
| Automatic routes, capacity, P2P/SFU transitions and route operations | Routing and transport |
| Capture, encoders, media adaptation and audio | Media quality |
| Workflow, playback, presentation and Browser/App lifecycle | Presentation and lifecycle |
| Evidence behind each status, indicator, overlay and notice | Media status |
| Cast, symbols, colour, animation, tooltips and playful copy | Visual language |
| Website, README and introduction-film composition | Public introduction |
| Runtime settings, defaults, bounds and diagnostics | Configuration |
| Compatibility, build identity, publication and release notes | Versioning |
| Documentation responsibilities and updating a rule | Documentation ownership |
Before another implementation of a familiar concept, identify its fact, owner, scope and lifetime. Apply the existing rule, or explain the contextual difference at that rule's owner. Source schemas and focused tests own exact implementation details; standards need not repeat every field or function.
ADRs preserve decisions and supersession. Research preserves dated observations and limits. TODO owns work that remains, including accepted targets not yet implemented. A recorded target is not a claim of completed verification. User guides remain in the documentation index.