workpc is the client machine the voice loop was waiting for (V-515)

Three durable stores said no client machine existed. That was written
when the workstation was only a model host. It is where he sits most of
the day and it has the microphone.

The verdict is unchanged and so is the seam. What changes is the size of
the remaining work: deploying two daemons and asking mavend to listen on
TCP, not acquiring hardware. Note that deploying them does not by itself
prove a wake word — mavwaked gates on energy and has no keyword model
(V-487).

docs/qa.md

@@ -1,6 +1,6 @@
 # QA plan: checking Maven properly
 
-*Last verified: 2026-08-04 @ 8d816f4. Living doc: correct it in place, do not append.*
+*Last verified: 2026-08-05 @ 12667fd. Living doc: correct it in place, do not append.*
 
 Written 2026-08-01, after the 35-PR stack landed and the box came back up.
 Refreshed 2026-08-02 against the live list, after PRs #85-#90.
@@ -255,8 +255,13 @@ room — **463**, written up in `docs/plans/17-where-the-voice-loop-runs.md`.
 So the wake word and the VAD gate are covered by their unit tests and by
 nothing else, and no session at this box changes that. Checking them needs a
 machine with a microphone running both binaries against a TCP-listening mavend.
-`ipc.Dial` already speaks `tcp://host:port?token=...`, so the work is a machine
-and a config line, not protocol work. Until then, **287** can only be
+`ipc.Dial` already speaks `tcp://host:port?token=...`, so the work is not
+protocol work.
+
+That machine is workpc (owner's correction, 05-08-2026). This section used to
+call it a machine Maven does not have. That was written when the workstation
+was only a model host. So the remaining work is deploying two daemons and
+asking mavend to listen on TCP. Until that is done, **287** can only be
 half-answered, and step 2 above is push-to-talk, not the voice loop.
 
 **319's single-token bug is fixed** (01-08-2026). Single-word Russian utterances no longer come