From c421453f5ed170a0667098f84b3a51505a54019a Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 30 Aug 2026 18:06:06 +0000 Subject: [PATCH] chore(ai-slop): drop stale line-number citation from config comment Repo-mode batch-simplify wave 1 (groups: root/agent-adjacent config; GitHub templates & automation YAML). The one applied change: the _comment in .claude/ai-slop.json cited "CLAUDE.md lines 15 and 24" for its reviewed appositive em dashes, but CLAUDE.md was rewritten after that comment was written and its em dashes now sit on other lines. The citation is dropped rather than renumbered so it cannot re-stale; the rest of the comment and both path arrays are byte-identical. All other swept files: reviewed, no changes. Verified: JSON validity; byte-identical excluded_paths and em_dash_allowed_paths vs HEAD; a fresh-context refutation pass ran the ai-slop detector before/after with byte-identical output (the plugin reads only the semantic keys, never _comment); typos, gitleaks, and editorconfig-checker clean repo-wide; check-jsonschema against vendor.dependabot, vendor.github-issue-forms, and vendor.github-issue-config all pass. No related issue: behavior-preserving drift fix from a repo-wide simplification sweep. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01N99bwGABw714WpH99BhhtA --- .claude/ai-slop.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.claude/ai-slop.json b/.claude/ai-slop.json index d8758a8..b72a2c7 100644 --- a/.claude/ai-slop.json +++ b/.claude/ai-slop.json @@ -11,5 +11,5 @@ "CONTRIBUTING.md", ".github/PULL_REQUEST_TEMPLATE.md" ], - "_comment": "CODE_OF_CONDUCT.md is excluded outright because it is verbatim Contributor Covenant v2.1, published in 2021. Its two findings (a negative parallelism on line 17 and a rule-of-three density of 5.5 per 1000 words) are properties of upstream text whose value depends on being unmodified, so rewriting them would fork the document to satisfy a detector. The catalog's own rule-pre-llm-text counter-sign covers exactly this case. The seven em_dash_allowed_paths documents use an inline-header list idiom as their house style: '- **Term** - definition' with an em dash as the separator between the bolded term and its gloss. The em-dash rule is zero-tolerance by design and must never be threshold-tuned, so per-document exemption is the supported mechanism. Exempting a path turns off the em-dash rule for that whole file, not just its list lines; the appositive dashes in CONTRIBUTING.md, in CLAUDE.md lines 15 and 24, and in the PR template's HTML comments are covered by the same entry and were reviewed as acceptable. Every other rule still runs on these files. Add a path here only when the document genuinely needs em dashes; the default posture is that most prose does not." + "_comment": "CODE_OF_CONDUCT.md is excluded outright because it is verbatim Contributor Covenant v2.1, published in 2021. Its two findings (a negative parallelism on line 17 and a rule-of-three density of 5.5 per 1000 words) are properties of upstream text whose value depends on being unmodified, so rewriting them would fork the document to satisfy a detector. The catalog's own rule-pre-llm-text counter-sign covers exactly this case. The seven em_dash_allowed_paths documents use an inline-header list idiom as their house style: '- **Term** - definition' with an em dash as the separator between the bolded term and its gloss. The em-dash rule is zero-tolerance by design and must never be threshold-tuned, so per-document exemption is the supported mechanism. Exempting a path turns off the em-dash rule for that whole file, not just its list lines; the appositive dashes in CONTRIBUTING.md, in CLAUDE.md, and in the PR template's HTML comments are covered by the same entry and were reviewed as acceptable. Every other rule still runs on these files. Add a path here only when the document genuinely needs em dashes; the default posture is that most prose does not." }