From 9b3cc9c9a2bebec29f021640eb2769f0105cced2 Mon Sep 17 00:00:00 2001 From: Dandaedre Date: Thu, 15 Oct 2026 03:38:32 +0200 Subject: [PATCH] docs(M7.3): add lifecycle recovery checks Add hands-on checks for TUI startup without a socket, offline MIDI targets, server loss, and automatic client resynchronization. Validation: git diff --cached --check. --- checklist.md | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+) diff --git a/checklist.md b/checklist.md index d4a5ec6..7b10b56 100644 --- a/checklist.md +++ b/checklist.md @@ -564,3 +564,54 @@ TUI first so the client is rebuilt with the new theme support. - [ ] Optionally launch each explicit name: `default`, `dracula`, `nord`, `gruvbox-dark`, `catppuccin-mocha`, and `solarized-dark`. Report any palette with poor contrast and include the terminal emulator plus its color settings. + +# Disconnected server and offline target checkpoint + +This checkpoint verifies that expected lifecycle failures remain visible but do +not terminate either side. Use the Arch PipeWire profile and leave the browser +closed initially so its configured application target is offline. + +## Start the TUI before the server + +- [ ] Stop every running `fader_master serve` process and confirm + `/run/user/1000/fader_master/control.sock` is absent. +- [ ] Run `cargo run --locked -p fader_master -- tui`. Confirm the TUI opens + instead of returning to the shell, shows `local IPC ยท waiting for server`, and + displays the missing-socket error inside the terminal. +- [ ] Leave that TUI open. In another terminal start: + + ```sh + cargo run --locked -p fader_master -- serve \ + --config examples/profiles/arch-pipewire.toml --audio pulse + ``` + +- [ ] Confirm the existing TUI connects and populates its rows within roughly + one second without being restarted. Browser should remain present as + `offline`; Music, Media, and Master should reflect their actual live state. + +## Exercise an offline mapped application + +- [ ] While Browser is offline, move its CC 49 fader repeatedly and press its + Note 65 mute button several times. Confirm the server stays running and does + not print `mixer object Application "browser" is offline` as a fatal error. +- [ ] Confirm Music (CC 48 / Note 64) and Master (CC 56 / Note 98) remain + controllable. Run `cargo run --locked -p fader_master -- status` and confirm + it still reports the server state. +- [ ] Start browser playback. Confirm Browser becomes online automatically and + adopts its live volume without replaying any movement or mute press made while + it was offline. +- [ ] Move CC 49 without crossing the live Browser volume and confirm pickup + prevents a jump. Cross the live value and confirm Browser control begins. + +## Lose and restore the server + +- [ ] With the TUI still open, stop the server. Confirm the TUI stays open, + remains responsive to navigation, resizing, and theme changes, retains its + last confirmed rows, and shows the connection error inside the terminal. +- [ ] Restart the same server command. Confirm the TUI reconnects within roughly + one second and replaces the retained values with a fresh server snapshot. +- [ ] Confirm no queued volume or mute operation from the disconnected interval + is applied after reconnection, then perform one fresh control change and + verify it synchronizes normally. +- [ ] Report any process exit, terminal corruption, stale write after reconnect, + row loss, repeated error spam, or reconnection taking longer than one second.