mirror of
https://github.com/usestrix/strix.git
synced 2026-08-18 17:52:32 +02:00
Ahmed Allam
e833278499
The six state tools added with the coverage ledger and the threat model had no renderer in either UI, so they fell through to the generic fallback: a raw key/value dump of the arguments, which printed a whole threat-model document inline as one value. The five calibration fields on a vulnerability report were likewise reaching the markdown report and SARIF but not the screen, so the agent's own confidence and the case against a finding were invisible to anyone watching the scan. Go TUI gets a coverage renderer (outcome-colored rows, state transitions, and the ledger's history and author) and a threat-model renderer (staleness, amendments, and a heading-level preview instead of the full document), both registered in the dispatch switch. list_coverage and get_threat_model join the output-heavy tools that collapse to a preview. The React viewer gets the same two as tool families, so an unknown future tool matching /coverage/ or /threat_model/ lands on the right renderer rather than the fallback. Both vulnerability renderers now show confidence, its rationale, counterevidence, the conditions that would move severity, and how a fix was verified.