claude
554181ccbd
Found running QA 253 on 02-08. Every one of the four failed the same way: the daemon is right and the step is stale. 253/3 expected mavend to boot with the capture methods unknown when there is no media block. Validate refuses to start instead (config.go:1651), which is the better behaviour — a capture config with nowhere to put the audio is a mistake he should hear at boot. 253/10 expected no :transcript note by default. writeNotes writes one whenever the summary is empty, ignoring save_transcript, so a dead llama-server does not lose the meeting. The step was therefore false in exactly the degradation scenario 253/16 creates. It now says "with a summary present". 255/5 expected "speaker: enrolment on, recognition BLOCKED". That line no longer ships. Recognizes() was written as the gate, documented as one, and never called; calling it turned enabled-with-no-model from a half-working capability into a refusal, and the three methods are now absent. docs/plans/10-speaker-recognition.md described the old wiring and is corrected here too. 252/3 quoted "vision: stored image <id-prefix>". vision.go:199 emits "vision: stored <id>". The steps themselves live in the Vikunja tasks and were rewritten there. docs/qa.md records what changed and why, so the next reader does not re-derive it from a diff. The gap that made the steps unrunnable is V-514, not this: no shipped client can start a recording, so 253 steps 7 to 16 stay blocked. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>