EchoMuse v2.9.11

v2.9.11 — diagnostics for on-device wake word

A small, low-risk update. It changes no behaviour: it adds two numbers to
the status report the device already sends every 30 seconds.

Only useful if you run on-device wake word (Config -> Wake word -> Score on
device). If you don't, this update is optional — nothing else differs from
v2.9.11's predecessor.

What it adds

• The device now reports the slowest single wake-word inference in each
  window, and the longest gap between audio frames reaching the scorer.

Why

• When on-device scoring falls behind, it drops audio frames rather than
  ever stalling the microphone. The drop count alone says it happened but
  not why, and there are only two possible causes, needing opposite fixes:
  inference running slow, or audio arriving in bursts. These two numbers
  tell them apart. Drops have been rare in testing (58 in ~925,000 frames,
  with no effect on the audio path), so this is groundwork for trusting
  on-device detection rather than a fix for anything you would notice.

Cost

• Two integers on an existing message, and one clock reading per audio
  frame on a path that takes no locks. No measurable CPU or memory change.

Requires nothing of you. Existing settings, wake word assets and rollback
slot are untouched, and a device that has never had on-device scoring
enabled behaves exactly as before.

What's Changed

• controller: stream Home Assistant TTS during generation by @kopiro in #47
• controller: tell the dashboard when a newer controller is published by @wilbowes in #48
• docs: journal the streaming TTS merge, the meter gap, and controller-v2.11.0 by @wilbowes in #49
• dashboard: line up the Link meter with Latency and Temp by @wilbowes in #50
• wakeword: distribute the on-device assets, and instrument what a drop was by @wilbowes in #51
• ci: verify the release binary carries the tag, not a string-layout artifact by @wilbowes in #52

New Contributors

• @kopiro made their first contribution in #47

Full Changelog: v2.9.10...v2.9.11