From c1abf2be801ee655ac5c0fa311fdf14a16494757 Mon Sep 17 00:00:00 2001 From: garrytan Date: Mon, 2 Nov 2026 18:18:38 +0000 Subject: [PATCH] chore: drop the released GST-976 changelog fragment carried by the stack Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- changelog.d/gst-976-severity-field-first.md | 5 ----- 1 file changed, 5 deletions(-) delete mode 100644 changelog.d/gst-976-severity-field-first.md diff --git a/changelog.d/gst-976-severity-field-first.md b/changelog.d/gst-976-severity-field-first.md deleted file mode 100644 index 0a3205468..000000000 --- a/changelog.d/gst-976-severity-field-first.md +++ /dev/null @@ -1,5 +0,0 @@ -**/ship's finding collector reads severity from a finding's own Severity field, so a severity word in the finding's text no longer raises it.** - -### Fixed - -- When a reader's finding carries its own `Severity:` field, the collector uses that field. A word like "P0" in the finding's text (a plan phase name, for example) no longer makes it a blocker the reader marked `Blocks: no`. A label leading the line (`CRITICAL:`, `[P0]`, `- High:`, a label heading) still sets the floor, `Blocks: yes` still makes a finding CRITICAL, and the native voice's FIXABLE still collects as CRITICAL. A field that names more than one label ("High/Critical") counts as no field, and a lowercase `severity:` keeps its label. Lines with no Severity field collect as before. (GST-976)