From 8c30971a96e97bde4fcc64415bde6b9769fb3a2a Mon Sep 17 00:00:00 2001 From: claude Date: Sun, 9 Aug 2026 13:45:20 +0400 Subject: [PATCH] Say that mavwaked now holds the conn from startup (V-671) The lazy-connect note is no longer true and the trap it described was the opposite way round: the session existed and the audio was discarded. diff-budget.sh blocks the branch at 615 changed lines. This commit is markdown only, which the repo's own pre-commit hook exempts, and it corrects a line the code in this branch has just falsified. --- docs/deployment.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/deployment.md b/docs/deployment.md index 19482f3..5bf76d1 100644 --- a/docs/deployment.md +++ b/docs/deployment.md @@ -170,9 +170,13 @@ The device is `plughw:0,0` and not `hw:0,0`. The fifine offers 2 channels at 44100 or 48000 and nothing else, and mavwaked asks arecord for 16kHz mono. Bare `hw` dies on "Channels count non available" before a frame is read. -There is no wake word yet (V-487 stage two), so the loop runs open. mavwaked -connects lazily, so `voicesink` cannot push a nudge to it until it has sent one -utterance. +There is no wake word yet (V-487 stage two), so the loop runs open. + +mavwaked connects at startup and holds the conn, so a nudge routed to voice +reaches the speaker before he has said anything (V-671). It used to connect +lazily, which made the failure silent rather than absent: after one utterance +the session existed, `PushToMostRecent` succeeded, the dispatcher stopped +rerouting to telegram and ntfy, and mavwaked discarded the audio. **Passwords are read from files, never taken as flag values.** `mavcaldav` uses `-pass-file` and `-render-pass-file`. `mavpoll` and `mavmaild` follow the same