Repository navigation
Description
Delivery contract from the rmux helper audit
Specify record() and stop() for retained observations with explicit coverage and storage guarantees.
First deliver a bounded recorder for output and state events actually observed after installation. Record stream identity, epoch, local sequence, timestamp, capabilities, gaps, and retention boundaries. Separate terminal-output recording from engine request/response tapes such as those proposed in #738: they answer different questions.
Offer memory retention first if useful. An optional disk sink needs an explicit acknowledgement/flush policy, format version, truncated-tail recovery, and retention limits. A reconnecting consumer can replay retained observations while the recorder remains alive. Recorder downtime is a gap; a tmux restart creates a new lifetime. Durable storage of received records does not make missing records recoverable.
A state journal may retain observed lifecycle changes and bounded snapshots, but cannot infer overwritten intermediate state. Action/input recording is opt-in and independently bounded.
Acceptance covers late consumers, retention eviction, reconnect inside and outside coverage, recorder restart, disk truncation if disk storage is offered, and explicit loss reporting. Strong storage guarantees require actual crash tests.
Do not describe this as a terminal checkpoint. rmux's retained output ring, revisioned state journal, and recovery keyframe state establish three distinct mechanisms. Stock captures do not expose every hidden state field required for exact continuation.
Delivery links: #800, #801. Track this work under #629 in the libtmux project.
Independent PR delivery
Follow the minimal slice and shared compatibility contract in #629. Build and test against master with every other unmerged feature branch absent. Cross-links above identify semantic contracts and future consumers; use a private adapter where needed instead of introducing a merge dependency. Preserve existing facade behavior and the inspected engine-ops interfaces. Leave deferred acceptance criteria open after an MVP lands.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsTodo
Activity
capture_pane#456tony commentedon Nov 1, 2026
UNVERIFIED — qualification result; implementation remains open.
A bounded recorder is possible in the library, but no Python recorder satisfying the declared source, payload kinds, eviction/gap reporting and export/redaction contract was demonstrated in this delivery. An immutable capture value is an available proposed input; it is not a recorder or durable storage.
No recorder PR is selected under the limited delivery rule. Retain one declared source and bounded in-memory records as the useful first slice; independently qualify eviction, late readers, source loss, redaction failure and bounded/versioned export before exposing it. Persistent recording and crash guarantees remain follow-ups. Neither sampled captures nor an in-memory ring can replay bytes that were never recorded. This is missing implementation evidence, not proof that tmux must change.
Evidence and canonical scope: capture-value input, byte source owner, sampled source owner.