qa reads /trace for the query chain again (V-564)

2026-08-06 00:52:59 +04:00
parent eec3d9bed2
commit cf28f6fdf0
2 changed files with 25 additions and 5 deletions
@@ -423,11 +423,15 @@ something only a ZIM answers, with the search block on. Live search leads and th
 ZIMs are the fallback since 02-08-2026. **286**'s remaining half is doc and
 git ingestion, which is build work, not a check.

-**Do not read `/trace` for this.** `/trace` is the nudge-rule trace: rule,
-severity, predicate, gate, selected. No query-source field exists anywhere in the
-codebase. The only evidence of which query source claimed a turn is the
-`voice: search:` and `voice: kiwix:` lines in `docker compose logs mavend`
-(`actions_query.go:589` and `:660`).
+**Read `/trace` for this.** It carries two tables since 06-08-2026 (V-564). The
+nudge-rule trace it always had, and below it the **turn decisions**: one
+collapsible record per utterance. Each names every claimant, what it would have
+made the turn, the score it reported, and whether it won, declined, lost or was
+**never asked**. That last one answers "did Kiwix pass, or was it never
+reached". The log lines cannot tell you that. The ring holds the last 25 turns
+in daemon memory and is empty after a restart, so read it in the same sitting.
+`/chat` still shows the claiming source as a badge, and the `voice: query
+claimed by source` line is still in `docker compose logs mavend`.

 Run 02-08-2026, 20 turns. **Search leads and the personal boundary holds.** Every
 world question that reached the boundary was claimed by search. All three