Blast radius on the PR, a scored risk reading & one analysis comment
When change release analysis is on, the GitHub comment shows blast radius from your catalog, a scored release-risk reading you can open row by row, and a single comment that updates in place.
Blast radius from your catalog
If the repository has a service catalog, the analysis comment folds in blast radius — which services changed, Flows, Wired in, modules, and who uses whom — with a Mermaid diagram. The catalog is the one in the repo being analysed, not a copy Fireweave keeps.
A scored release-risk reading
The comment now leads with a release-risk score Fireweave computes — path, blast, data, size, tests, kill switch, staged rollout, and monitoring — so you can see how the number adds up. A Control point that can turn the change off is part of that reading. The model’s own score is not the one printed. Fireweave does not read CI yet; that row stays unchecked until it can.
Fixed
- A pull request gets one analysis comment that updates in place, instead of a pile of stuck analysing comments