The hook blocks edits to linter/formatter configs so an agent fixes the code
instead of weakening the checks. It did not cover the cheapest way to weaken
them: adding one path to an ignore file. Measured against the hook, with the
file already on disk:
.eslintignore -> allow
.prettierignore -> allow
.stylelintignore -> allow
.markdownlintignore -> allow
Nor did it cover the current config names — only the legacy `.stylelintrc*`
and `.markdownlint.json` spellings were listed, so a project using the
documented `stylelint.config.js`, `.markdownlint.jsonc` or markdownlint-cli2
had no protection at all.
First-time creation stays allowed by the existing existence check, so
scaffolding a fresh ignore file is unaffected.
Nguyen Thanh Dat
9a44131a1a