Summary
The human output for retrieve query-history showed primary evidence and ordering, but not the graph-safe counts that explain route decisions. After adding documentation roles and query-history thresholds, operators need a compact non-JSON signal summary.
Stack
- Branch: stack/retrieval-route-signal-summary
- Base: stack/query-history-route-threshold
- Parent PR: fanduel/fd-knowledge-graph#9
Expected behavior
- Non-JSON retrieve query-history output includes a per-route signals line.
- The line exposes graph-safe counts only: item counts, analyst_usage evidence count, threshold yes/no, documentation strong/weak role counts.
- JSON output remains unchanged.
Safety
No raw SQL, document bodies, user ids, or properties are printed. The summary uses route signal counts already returned in graph-safe context.
Verification
- ruff check .
- pytest -q
- git diff --check
Summary
The human output for retrieve query-history showed primary evidence and ordering, but not the graph-safe counts that explain route decisions. After adding documentation roles and query-history thresholds, operators need a compact non-JSON signal summary.
Stack
Expected behavior
Safety
No raw SQL, document bodies, user ids, or properties are printed. The summary uses route signal counts already returned in graph-safe context.
Verification