From 3c4b09ec8a2274a5892bb1603df9780386afe488 Mon Sep 17 00:00:00 2001 From: Tamir Dresher Date: Sun, 14 Jun 2026 07:41:35 +0300 Subject: [PATCH] fix(docs): rephrase 'fenced code block' row in skill-security-scanner table MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit CI failure on dev tip (567f4475, Squad CI run 27488323855): test/docs-build.test.ts > 'all code blocks are properly fenced (even count of backticks)' → expected 1 to be 0 test/docs-build.test.ts > 'code blocks contain language specification or valid content' → expected 1 to be greater than 1 Root cause: a 4-backtick table cell intended to display a literal triple-backtick: | Inside a fenced code block (\\\\ \\\ \\\\) | Suppressed | made the regex /\\\/g see 5 triple-backtick occurrences across the file (instead of the 2 from the real bash example), tripping both the even-fence check and the line-count > 1 check. Rephrased the table to say 'three backticks' / 'single backtick' in prose — no embedded delimiters, no need to defend against the markdown fence escape mechanism. Reads cleaner anyway. Verified locally: 22/22 docs-build tests pass; npm run build in docs/ completes (171 files emitted; pagefind indexes 168 pages, 6911 words). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- docs/src/content/docs/features/skill-security-scanner.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/content/docs/features/skill-security-scanner.md b/docs/src/content/docs/features/skill-security-scanner.md index 43d5dd70e..5e3fe415a 100644 --- a/docs/src/content/docs/features/skill-security-scanner.md +++ b/docs/src/content/docs/features/skill-security-scanner.md @@ -66,8 +66,8 @@ The scanner is markdown-aware, which means it understands when a "dangerous" pat | Where pattern appears | Action | |----------------------|--------| -| Inside a fenced code block (```` ``` ````) | **Suppressed** — treated as documentation, not advice | -| Inside an inline code span (`` ` ``) | **Suppressed** — treated as a reference | +| Inside a fenced code block (three backticks) | **Suppressed** — treated as documentation, not advice | +| Inside an inline code span (single backtick) | **Suppressed** — treated as a reference | | In prose with a placeholder token (``, ``, `xxx`, `***`) | **Suppressed** — clearly an example | | In prose without any of the above | **Flagged** as a finding |