AAA
4ff970f483
## Problem and outcome Website visitors can download the usual Windows x64, macOS Apple silicon and Linux x64 App packages directly from clearly labeled platform cards. Each card includes a verified Gitee alternative, with shared setup guidance and a More downloads link for the full release list. The homepage reuses the application's 20 bilingual greetings, and the sample game no longer displays an invented title. Website builds resolve links from the latest published GitHub release and validate matching mirror assets. Website deployment follows main CI so newly published packages reach the next site build. Version selection and release notes now share a product-change filter: standalone website, documentation and maintenance changes do not create App/Server releases or affect the next product version. ## Verification - `npm run check`: 57 test files / 759 tests, TypeScript and product production build passed. - Website build passed with real GitHub/Gitee v1.0.0 metadata and with the explicit local fallback. - English and Chinese browser checks at 390px and 1440px passed: platform links, More downloads, greeting selection and language switching. - All 23 website film check groups passed; the final shared artwork change rebuilt successfully. - Documentation, repository hygiene and diff checks passed. Real Git-history tests cover product/website mixtures and moves across the release boundary; the accepted phase plans `publish: false`. ## Impact GitHub remains the version authority; Gitee is a download mirror. Unavailable mirror metadata falls back to its release page. Product runtime behavior and package compatibility are unchanged. Physical macOS/Linux capture and broader device/network limits remain documented.
97 lines
5.7 KiB
Markdown
97 lines
5.7 KiB
Markdown
# Current Status
|
|
|
|
Last updated: 2026-09-12
|
|
|
|
This is the compact execution/deployment index. Product modules own behavior,
|
|
[verification status](./verification-status.md) 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.
|
|
The coordinated brand/protocol cutover requires matching Web/App/Server
|
|
artifacts and a reload of incompatible active pages.
|
|
- 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.
|
|
- 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](./reference/configuration.md#diagnostics) owns Debug activation,
|
|
report contents and disclosure.
|
|
|
|
## Deployment
|
|
|
|
Source, package identity, GitHub repository and local worktree paths use Piik.
|
|
Runtime code keeps only the Piik wire labels and stored keys. The coordinated
|
|
private cutover requires matching App/Server/Web packages; unavailable old
|
|
Browser credentials cannot be reconstructed from stored digests.
|
|
The immutable release descriptor, runtime `REVISION` and operator deployment
|
|
record own exact identity and postflight results. Old active pages reload at
|
|
the signaling v23 boundary.
|
|
|
|
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](https://demo.piik.tv) is deployed with open site
|
|
entry, persistent room authority and P2P-only media. Caddy owns 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](./todo.md) owns the current maintenance phase. 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](./reference/versioning.md). [Verification status](./verification-status.md#candidate-evidence-boundary)
|
|
owns the remaining physical limits; shared lessons live in
|
|
[engineering](./reference/engineering.md).
|
|
|
|
## 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](./research/browser-local-encoding-pool.md)
|
|
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](./research/webrtc-encoder-pool.md) and verification status.
|
|
macOS/Linux physical capture is deferred by the owner; Windows App and
|
|
Browser are this phase's primary targets.
|