Qwen 3 integration + agent plan + playbook loop

Pulled qwen3 (8.2B, 40K context, thinking, tool-calling). Created
agent-qwen3 profile. Ran structured plan: 5 contracts (16/16 filled
via hybrid), 5 intelligence questions (2/5 — same RAG counting gap).

Key playbook entry generated: "count/aggregation questions must use
/sql not /search. RAG returns 5 chunks from 10K — cannot count the
full dataset." This routing rule is now in the playbooks database
for future agent runs to learn from.

Pattern confirmed across qwen2.5, mistral, AND qwen3: the structured
matching path (hybrid SQL+vector) is production-ready across all
models. The RAG counting gap is a routing problem, not a model
problem — the fix is query classification, not a better model.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

lakehouse.toml

@@ -70,3 +70,9 @@ cycle_interval_secs = 120                 # periodic wake if no triggers
 cooldown_between_trials_secs = 10         # min gap between trials
 min_recall = 0.9                          # never promote below this
 max_trials_per_hour = 20                  # hard budget cap
+
+# Model roster — available for profile hot-swap
+# qwen3: 8.2B, 40K context, thinking+tools, best for reasoning tasks
+# qwen2.5: 7B, 8K context, fast, good for SQL generation
+# mistral: 7B, 8K context, good for general generation
+# nomic-embed-text: 137M, embedding-only, used by all profiles