Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude/ai-slop.json
Original file line number Diff line number Diff line change
Expand Up @@ -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."
}
Loading