B-G2E6-guard-raw-palette-comment-masking-is-not-string-aware-a
maskComments (scripts/guard-raw-palette.ts, ~line 924) scans for comment openers without tracking string state, so a slash-star inside a string literal opens a phantom comment that runs to the star-slash closing the next real comment — swallowing the string’s closing quote, flipping quote parity, and silently voiding the hex/keyword/functional-colour rules for the rest of the file.
Reproduction (from the PR 1 markdown-editing review fan-out, reviews/01-foundations.md): packages/ts/markdown-ui/playground/app/composables/usePlaygroundProvider.ts held import.meta.glob(’../../vault/*.md’,…) at line 31; scanSource on the file returned hex=[] while the identical SVG fixture lines scanned alone flagged four raw hexes (#e8e4f0, #7c6bb0, #4a4458 x2). maskComments on the real file blanked from the glob’s slash-star through the next JSDoc’s closer. The ring reported files=15, all rules zero — a false measurement on an all-enforce ring.
Any file with an import.meta.glob pattern (or any glob/regex/url string containing slash-star) is affected. The provider file was fixed file-side on md/01-review-fixes (pattern rewritten, fixture isolated + deliberatelyDark, enforcement verified restored with a planted hex); this entry is the guard-side fix: make maskComments string-aware (track quote state for single, double, and template literals before honouring a comment opener), and add a regression test with a slash-star inside a string followed by a hex.