docs(truth): separate source and deployment revisions

docs/project-memory.md

@@ -27,7 +27,7 @@ Last updated: 2026-08-24
 
 ## Current Source And Production
 
-- Exact main and production run Browser runtime `2726edde9b87f31fd76e749de47972ef817a9bd5`, release `2726edd`, on the single `screener-v10` Browser wire. Auxiliary branches and older worktrees do not supersede canonical `main`.
+- Current canonical source and production use the single `screener-v10` Browser wire. Production was built from integrated main `2726edde9b87f31fd76e749de47972ef817a9bd5` as release `2726edd`; auxiliary branches and older worktrees do not supersede canonical `main`.
 - Current source and production admit up to `20` Viewers and implement the uniform `1/2/3` endpoint cap, exact prepare candidate, first-decoded-frame commit, strict rollback revision, decoded-progress stall, a two-stage direct/SFU operation deadline, and one event-driven room controller. A short-lived exact-generation decoded-frame observer proves only the pending candidate inside the existing total deadline; the periodic stats sampler remains responsible for active-path diagnostics and stalls. Ordinary peer ICE is STUN-only and the sole application fallback is SFU/UDP; stale TURN environment keys fail startup. SFU admission uses exact publication and Viewer-subscription handles with explicit no-default ingress/egress capacities and a listener-fenced dedicated LiveKit owner.
 - Current source and production use the memory-resident room model: random free four-digit codes, the configurable dormant lease, exact-Host resume, restart loss, local creation-preference replay, orthogonal Viewer grants and `open | password | disabled` code entry, and direct invitation/policy controls. SQLite room persistence, `ROOM_DATABASE_PATH`, `ROOM_TTL_SECONDS`, and a writable room StateDirectory are absent from the current runtime.
 - Exact production artifacts, rollback boundary, services, and ports are owned by [deployment](./deployment.md) and indexed by [status](./status.md).

docs/status.md

@@ -36,12 +36,12 @@ This is the current execution index. Git history owns completed timelines; [veri
 - `fix/configurable-relay-cap` is an old, incomplete draft and must not be merged as-is.
 - Open PR #192 and the Native stack are evidence/research, not pending product releases. Native senders, capture helpers, shared-encode executables, and their test binaries are outside the current Browser milestone and are not built or run.
 - Deployed surfaces and retained candidates that still need product decisions are indexed only in [the TODO ledger](./todo.md); do not extend or roll them back automatically.
-- Room lifetime, authorization/storage semantics, restart loss, Browser v10 entry/presentation, and rollback restoration are aligned between exact main and production.
+- Room lifetime, authorization/storage semantics, restart loss, Browser v10 entry/presentation, and rollback restoration are aligned between current source and production.
 - Real SFU recovery, heterogeneous networks, mobile lifecycle, audio/A-V device behavior, and endurance/resource measurements remain external acceptance evidence, not blockers for unrelated reversible work.
 
 ## Current Hold
 
-There is no active P0/P1 source or deployment hold. Exact main and production run the postflight-clean
+There is no active P0/P1 source or deployment hold. Current source and production run the postflight-clean
 Browser v10 contract. Physical H.264 quality, audio, heterogeneous-network, SFU,
 background, and mobile evidence remains open. Native/executable work and broad repository cleanup
 remain outside the current evidence boundary.