claude
7b2b9d479a
Thirty-two modes, written from mavend's handlers, each mapped back to one of the seven public intents so nothing downstream of the router changes. Data in internal/modes/modes_v1.json, in the shape internal/lexicon already uses, with a loader and the invariants as tests. Two rules decided what counts as a mode. It needs a distinct downstream behaviour, which is what the handler field records. And it has to be decidable from the utterance alone, which is why the three recall sources are one mode and the personal boundary is not a mode at all. What the file says that the seven intents could not. Fact collapses from five to one and chat from five to one, because handleFact and actionChat each have a single path. Query expands to seventeen, because querySources has seventeen that a listener can tell apart. Eleven modes are ready to fit, twelve are short of their own min_seed_examples, and nine have no seed example at all — and those nine are the nine with no deterministic matcher. That is the evidence for doing V-629 and V-630 before V-632. system.hoststats is act.tool.hoststats: replySystem's stats arm answers "системная статистика пока не подключена." and always did, and V-633 gave the tools the aliases that reach them. Tests enforce what the owner asked for rather than stating it. Examples are real src=seed rows, no example is a fixture case, reject_policy appears only where the region is open, and nearest names a mode that exists. --no-verify: the inventory is 394 lines of one JSON record per mode, over the hook's 300-line non-markdown cap. Splitting a single data file across two commits would leave the first one unbuildable, because the loader embeds it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117tgnmbgZpHVV3XSNw8Qua