Add dream-tunable balancedFloorKeywords to floor tool-intent queries at Balanced (#486)

[rockfordlhotka]

Problem

Short user queries that need a tool (e.g. "what's on my todo list?") score ~0.0 and route Low, where the small model fails to pick the right MCP tool under heavy injected context. The keyword router is a cognitive-complexity classifier — blind to "this needs a tool." The dream detects the problem (panicEscalation) but had no lever: adding topic words as highSignalKeywords over-routes to expensive High and is stripped by the TopicBlocklist; threshold nudges can't move a ~0.0 query.

Solution

A new dream-tunable balancedFloorKeywords list. When a user-message prompt matches a floor keyword and the computed tier is Low, escalate to Balanced (never High). Exempt from TopicBlocklist — it is meant to hold topic/tool words. Seeded empty; the dream owns it.

Changes

• TierSelectorConfig — nullable BalancedFloorKeywords property.
• KeywordTierSelector — compiled default (empty, add-only); merged via existing MergeKeywords (auto-exempt from the blocklist since the list name lacks "high"); Low→Balanced override in ClassifyCore after the active-thread override, gated on Origin == "user-message" and tier == Low so it structurally cannot reach High; floor count added to the reload log.
• routing-dream.md — documents the lever as job 4, cross-references it from the panicEscalation bullet, and keeps the "reject topic words" rule scoped to highSignalKeywords only. Added the field to the response-format JSON example.
• Tests — 5 new: Low→Balanced escalation (user origin), no effect for subagent origin, never-High, non-matching trivial chat stays Low, and the TopicBlocklist-exemption proof.

Risk

Low — purely additive. The empty default means zero behavior change until the dream (or an operator) populates the list. Existing routing paths untouched.

Verification

Full solution builds with 0 errors; all 78 KeywordTierSelectorTests pass (5 new).

Deferred

Optional analyzer support (balancedFloorCandidates in TierRoutingAnalyzer) is not in the acceptance criteria — the dream can already derive candidates from flaggedClusters[].samplePrompt. Skipped to keep the PR focused; can be a follow-up.

Closes #486

🤖 Generated with Claude Code