0 Fork 0

Files

T

Accepted native Client lifecycle and Windows capture aspect phase. All Web/Server and three-platform Client checks passed.

2026-09-05 22:41:46 +08:00

Project Instructions

Authority And Scope

Read and follow the complete repo-tracked ponytail skill before coding, review, or design work. It is required guidance for the smallest correct result; project authority and delivery constraints remain owned here.
Within higher-priority instructions, the latest explicit user decision defines the task. Review, research, implementation, deployment, and cleanup grant only the authority inherent in that task type.
Model recovery from the smallest underlying authority and connection state. Restart, crash, timeout, and network loss do not justify parallel states or case-specific fallbacks when their required action is the same.
Ordinary scoped work uses the lean path: inspect the affected owner and code, make the smallest coherent change, run focused checks, inspect the diff, and stage the requested files. Use the full integration/release path only for an explicitly requested release or a material contract, route/security, infrastructure, persistence, or irreversible change.
Until a public release is explicitly declared, keep one current internal contract. Delete replaced wire/config/API surfaces; do not add compatibility aliases, dual readers/writers, migrations, or tests for stale private clients.

Screener is private game screen sharing for one Host and up to 20 authenticated Viewers, with Web Host/Viewer/relay as the current product surface.
Current product truth is split by owner: rooms/access, routing/transport, media quality, and presentation/lifecycle.
Media stays automatic and P2P-first; central services provide room authority, signaling, STUN, observability, and bounded LiveKit SFU/UDP fallback. Route changes must preserve the single-graph, single-operation model in ADR-0005.
WebRTC and LiveKit own network and media adaptation. Do not add custom quality scores, ladders, all-pairs probes, periodic rebalancing, or hand-built SFU representations without a new accepted decision backed by primary evidence.

Start substantial work by reading project memory, status, TODO, and only the relevant product module, ADR, research, or operations document. Then inspect branch, HEAD, status, staged diff, and worktrees.
Product modules own current behavior; ADRs own non-obvious decisions and consequences; research owns evidence and license boundaries; deployment owns operational reference. Status is the current execution/deployment index, TODO is the only work ledger, and Git/PRs own completed history.
Give every durable fact one owner. Update memory or status only when its compact snapshot materially changes. Ordinary UI detail, protocol field listings, self-evident code, test inventories, routine validation, and agent process do not belong in long-lived product truth.
If semantics remain disputed, record the hold in TODO and freeze only dependent work. Never encode a guess as accepted truth.

Never commit credentials, TLS private keys, raw access tokens, or real user data. Commit placeholders and document local secret injection.
Keep media credentials short-lived and narrowly authorized. Do not log or persist private media-path identifiers beyond their accepted owner.
Block the current phase on P0 security, privacy, authorization, irreversible- data, generation, bounded-resource, or rollback failure, and on P1 failure of that phase's core path.

Canonical root must be clean current main at audit/integration boundaries. Create branches/worktrees from that exact commit; old branches and worktrees are never truth sources.
main is a low-frequency integration branch, never a workbench. Keep work on branches/worktrees and merge only one complete, user-accepted phase per PR, after its related implementation, tests, documentation, and acceptance are complete. Use one squash commit and leave main unchanged between phases. Do not merge intermediate checkpoints, release records, metadata-only edits, or follow-up cleanup; fold them into the next phase. A P0/P1 emergency may bypass batching only when the user explicitly authorizes it, still through one coherent PR.
Preserve user work. Branch, truth-checkpoint, PR, release, recovery, and cleanup rules are owned by CONTRIBUTING.md; do not mirror that workflow here.

Prefer the simplest cohesive design that is easy to use and maintain. Reuse mature components, keep ownership explicit, and remove superseded paths in the same change instead of retaining speculative flexibility or technical debt.
Judge a change by evidenced user value against its full implementation, maintenance, compatibility, and failure cost. A large measured gain may justify broad or breaking work; a small or speculative gain does not justify material complexity or risk.
After completing a material module, run one ablation pass and remove every new component, state, dependency, or branch that is not needed for the verified result or an accepted contract.
Use primary sources for non-trivial design and bugs. Add focused tests in proportion to risk; batch full browser/network/endurance checks at acceptance.
Keep scripts deterministic, fast, cross-platform, and CI-runnable. Support Windows, macOS, and Linux; use LF and ASCII filenames for new files.
Before finishing material work, inspect status, report untracked artifacts, and stage requested files unless told otherwise.