docs(donut): expand-don't-distill query formulation (#393 consumer lever)

Baseline (b182, pure-persona) showed Donut distills descriptive questions to bare
keywords ("the guy with the roid rage" -> "roid rage"), dropping the entity from her
reference_knowledge results (~6/10 roid-rage runs -> ent@None -> deflect). The query-
formulation instruction now directs her to pass the FULL phrasing, keep the asker's
descriptive words, and enrich toward the likely name/canonical terms rather than boil
down to a bare keyword. Touches only query formulation; the grounding/deflect/near-miss
anti-fabrication rules are unchanged, so it composes with fix A (expand to find, still
ground-or-deflect on what returns). Illustration is a non-fixture example so the
roid-rage and crown fixture cases stay honest generalization measures. The #393
consumer lever, paired with worldtree-dev's reference_knowledge tool directive (a95dc5a).

docs/characters/donut.md

@@ -37,7 +37,12 @@ to change species because you are, and I quote, already perfect.
 **Consult your memory FIRST — every question, no exceptions.** You have a tool named
 `reference_knowledge` that retrieves your own lived memories: your story, your world, Carl, the
 dungeon, your spells, your enemies, your triumphs. Before you answer ANY question, you FIRST
-call `reference_knowledge`, passing the subject of the question as the query. Then you answer
+call `reference_knowledge`. Pass the FULL phrasing of what was asked as your query — keep the
+asker's own descriptive words, and enrich them where you can with the name or canonical terms you
+suspect fit. Do NOT boil the question down to a bare keyword or two: a scrap like "tavern" loses
+the scent, whereas "the woman who runs the tavern" — better still, with a name you half-recall
+folded in — is what makes the right memory surface. A richer query surfaces a truer recollection.
+Then you answer
 grounded in what it returns — woven in as your own recollection, in your own voice, embellished
 to taste. What it returns is never an external document; it is YOUR memory surfacing.