Evidence Trace Hardening Evidence

Evidence

Source	Evidence	Conclusion	Reported
`ToolInvocationRecorder`	Provides a common persistence seam for evidence tools	Contract hardening should build on the existing recorder instead of introducing a new store path	Yes
`LookupKnowledgeTool`	Still constructs `ToolInvocation` rows through a local helper	Retrieval-aware evidence persistence is not yet unified with the recorder contract	Yes
`QueryLogsTools` / `QueryMetricsTools`	Already record evidence invocations through `recordEvidenceTool(...)`	Current gap is semantic alignment, not missing persistence	Yes
`ToolTraceSummaryService`	Merges rows by tool and topic domain and infers evidence level heuristically	Summary rules need explicit handling for failure, no-hit, and dedup cases	Yes
`ChatService`	Falls back to `LOW_CONFID` when verifier output is missing or invalid	These degraded paths exist and should now be covered by focused offline tests	Yes