Three tangled defects, fixed together because each one hid the others.
DefaultActMatcher matched an exact English prefix and internal/tool.Matcher
delegated straight to it, so no Russian utterance could reach a tool: 55 of the
69 lines in models/seeds/act.txt routed to IntentAct and fell to proposeGap.
Tools now carry spoken aliases from deploy/mavend.json, matched as exact leading
tokens, longest phrase first. Config data, not a stem pattern in code. The
comment claiming "the production matcher is fuzzy" was false and is gone.
Seven lines were exact duplicates inside models/seeds/query.txt, each one a
second identical vector double-weighting its region.
"как дела у сервера" carried both a query and a system label. It leaves
system.txt, because replySystem's stats arm answers "системная статистика пока
не подключена." and always did. The mode inventory records that shape as
act.tool.hoststats rather than a system mode.
Fixture unchanged at 69/91, and it cannot see any of this: no host-stat case and
no Russian act in it. TestActMatcherAliases is the coverage.
docs/evals/2026-08-06-russian-acts-reach-tools.md has the numbers.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0117tgnmbgZpHVV3XSNw8Qua
WorkerConfig, TtsConfig, EmbedderConfig, WeatherConfig and ToolConfig. None of
them is reachable except through a voice block, so they read better beside it.
The VoiceConfig struct only. Its defaults, normalise/validate arms and
UseLLMRouter follow in the next commit, because the pre-commit cap counts a
pure move at twice the block size.
The RouterThreshold doc drifted: it said the default was 0.35 and that 0.0
meant permissive. DefaultRouterThreshold is 0.55 and applyDefaults replaces
anything <= 0, so permissive was never reachable. Fixed the comment, not the
code.