diff --git a/checklist.md b/checklist.md index 865bd8d..514f175 100644 --- a/checklist.md +++ b/checklist.md @@ -474,3 +474,70 @@ physical position reaches or crosses the current live volume. any wrong target, duplicate button toggle, startup/reconnect/default-output jump, or server error. Pickup state is not displayed explicitly in the TUI yet, so judge this checkpoint by the observed audio values and behavior. + +# Buffered interaction and synchronization checkpoint + +This checkpoint exercises the new bounded command path. Volume motion may be +coalesced while an older audio request is in flight, but the final requested +value must always be applied. Mute presses are edges and must never be +coalesced. The TUI now updates its local view immediately while socket requests +run on a background thread. + +## Restart on the new build + +- [ ] Stop any server and TUI started from an older build. +- [ ] Start playback in Qobuz and a browser, then run: + + ```sh + cargo run --locked -p fader_master -- serve \ + --config examples/profiles/arch-pipewire.toml --audio pulse + ``` + +- [ ] In another terminal run + `cargo run --locked -p fader_master -- tui` and confirm Music, Browser, Media, + and Master reach stable live values without a startup volume change. + +## TUI responsiveness and local updates + +- [ ] Select Music and hold `→` long enough to generate a burst of changes. + Confirm the displayed value responds immediately, shows pending work when + applicable, and the TUI continues to accept navigation and redraw normally. +- [ ] While volume work is pending, resize the terminal and move the selection + with `j`/`k`. Confirm neither input nor drawing freezes behind an audio or + socket round trip. +- [ ] Release the key and confirm Music settles at the final displayed value in + the desktop mixer within about one second; it must not walk through a long + backlog of every intermediate value. +- [ ] Repeat a short burst on Master. Confirm the default output converges while + the Music and Browser application gains remain unchanged. + +## MIDI bursts and ordered buttons + +- [ ] First cross the pickup point for CC 48, then sweep it rapidly back and + forth for several seconds. Stop at a distinct position and confirm Music + converges to that final position without freezing the server or TUI. +- [ ] Repeat with CC 56 and confirm only the default output Master converges. +- [ ] Move CC 48 and CC 49 in quick alternation. Confirm Music and Browser each + settle at their own final fader position; coalescing one target must not lose + the other target's update. +- [ ] Press button 64 twice quickly. Confirm Music returns to its original mute + state after exactly two toggles; no press may be lost or duplicated. +- [ ] Repeat the rapid double press with Master button 98 and confirm the output + returns to its original mute state without changing application mute states. + +## Confirm synchronization and lifecycle + +- [ ] Change Music volume externally in the desktop mixer while the controls + are idle. Confirm the TUI adopts the external value within roughly 250 ms and + does not write the old local value back. +- [ ] After that external change, move CC 48 without crossing the new value and + confirm pickup prevents a snap-back. Cross it, stop moving, and confirm the + final physical position wins and the pending indication clears. +- [ ] Quit the TUI immediately after a volume key press. Confirm it restores the + terminal cleanly, the server stays alive, and reopening the TUI shows the + confirmed final state. +- [ ] Run `cargo run --locked -p fader_master -- status` and confirm the server + still reports `status=ready` with the same final values. +- [ ] Report any persistent pending marker, missed/duplicate mute, value that + rebounds after settling, final value that takes more than about one second, + `buffered audio dispatch lane overflowed` error, or server/TUI freeze.