Repository navigation
v0.9.4
Fixed
redis_memory_pressure_rca's top-levelpressureflag no longer decides by comparing another finding'scauseagainst the literal sentence "Healthy — within thresholds". Behaviour is unchanged, but rewording that sentence — or normalising its em dash in a style sweep — would have reported pressure on a healthy broker. It now reads the measured condition, and an AST-based structural test pins the whole package against a decision being taken on a finding's prose.agent-guardrails.mdandSKILL.mdclaimed the four RCAs "rank findings worst-first" and that "priority is in the payload, not implied by list position". Neither was ever true here: there is norankkey, and findings are appended in the order the checks run — and the claim sat in the table telling operators not to spend prompt budget on it. The docs now say order is not severity, and point at theevidencenumber each finding does carry.
Full notes: CHANGELOG.md