fix(#4788): code spans in the decision bold lead-in are opaque to the separator grammar (#4883)

* test(#4788): failing-first — code spans in the decision bold lead-in are opaque to the separator grammar

* fix(#4788): the decision lead-in runs are code-span-aware — a backticked span is data, never grammar

* chore(#4788): backfill changeset PR number (4881)

* chore(#4788): correct changeset PR number (4883, was a guessed 4881)

---------

Co-authored-by: sim <sim@local>
This commit is contained in:
Tom Boucher
2026-09-19 22:46:48 -04:00
committed by GitHub
parent 5906a24ede
commit 09e1110e68
3 changed files with 110 additions and 11 deletions

View File

@@ -0,0 +1,5 @@
---
type: Fixed
pr: 4883
---
**Decision bullets with code spans in their titles now parse** — a backticked token like `node:http` or `*-UAT.md` inside a decision's bold lead-in was treated as a malformed separator and the whole decisions block failed to parse, hard-blocking the decision-coverage gate; backticked spans are now opaque to the grammar, while a bare colon outside a code span still fails loud. (#4788)