docs: exempt tool directives from the comment rules (#2183)

Author: ascorbic

AGENTS.md

@@ -338,6 +338,8 @@ Comments are **not**:
 
 Never reference issues, PRs, or review threads in comments -- they're stale narrative the moment the change merges; that context belongs in the commit message and PR description. Never number comments.
 
+Tool directives are exempt from all of the above: `eslint-disable`, `oxlint-disable`, `@ts-expect-error`, `@ts-ignore`, `prettier-ignore`, `v8 ignore`, and similar are machine instructions, not prose, and the short reason attached to one (`// oxlint-disable-next-line no-await-in-loop -- sequential on purpose`) states why the rule doesn't apply at that site. Keep the reason; don't flag it as justification.
+
 ## Imports
 
 - **Internal imports** use `.js` extensions (ESM): `import { X } from "../foo.js"`.

infra/flue-review/.flue/skills/review/SKILL.md

@@ -56,7 +56,7 @@ Breadth first, depth second. The two most common ways to fail are to grade the i
 - **Resources**: leaked handles/timers/listeners, unbounded growth, missing timeouts, retry without backoff.
 - **Tests**: a fix without a reproducing test is not fixed; a mock that returns the thing the test claims to verify is false confidence. A test that cannot fail on a real regression -- a config literal asserted back at itself, an implementation detail asserted straight back (adding a CSS class and testing the class is present), a mocked unit under test, a test exercising only third-party code -- is worse than no test: it inflates coverage and pins intentional changes. Flag it for deletion, or for rewriting against observable behavior.
 - **Logged-out query counts**: any new query on a route an anonymous visitor can hit -- including cold-start or first-request-only queries -- needs a _really_ good reason. Check whether it could piggyback on an existing query, batch, defer with `after()`, or use `requestCached`. A query-count snapshot diff that increases a logged-out route is a finding, not bookkeeping.
-- **Comments**: comments that restate what the code does, justify the decision ("intentionally", "for safety"), address the reviewer, narrate rejected alternatives, or reference issues/PRs/review threads. Comments are evergreen and for future readers of the code; almost all of these should be deleted (or the code made clearer instead). Numbered comments are always wrong.
+- **Comments**: comments that restate what the code does, justify the decision ("intentionally", "for safety"), address the reviewer, narrate rejected alternatives, or reference issues/PRs/review threads. Comments are evergreen and for future readers of the code; almost all of these should be deleted (or the code made clearer instead). Numbered comments are always wrong. Tool directives are exempt: `eslint-disable`, `oxlint-disable`, `@ts-expect-error`, `@ts-ignore`, `prettier-ignore`, `v8 ignore`, and similar are machine instructions, and the short reason attached to one is required context, not justification -- never flag them under this category.
 - **AGENTS.md conventions** (see above).
 
 ## Severity and verdict