feat: severity rules and the triage inbox #5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/triage"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes BUG-7 (the optional LLM suggestion is not built; see below)
Stacked on #4. Part of ECO-EP1.
What
triage.rs): rules, not a model. Crash/panic 100 > freeze 60 > behavior 20, plus volume (per doubling, capped), distinct installs, recency (day/week), spread across 3+ versions, and a regression bonus. Every point is attributed to a named rule and shown on the cluster page. Weights can be overridden from a TOML file (BREADBUG_TRIAGE_RULES).admin.rs) on its own listener (BREADBUG_ADMIN_ADDR, default 127.0.0.1:8121; disabled unlessBREADBUG_ADMIN_TOKEN_SHA256is set; never routed publicly):default-src 'none'with no scripts,nosniff,no-store,no-referrer; all report-derived text goes through one HTML escaper; 16 KiB body cap on the admin listener.Not built
The optional LLM-suggested severity/summary from the issue. It is advisory-only and off by default in the spec, and I did not want an LLM step reading hostile text before the rest of the pipeline is proven. If wanted later it needs: a local model only, report text passed strictly as data, no tools, output shown as a labeled suggestion.
Tests
-D warningsclean.ae6ca2f3f81a6d27104e