Grandfather existing lint violations

Status: implementation complete. Wrapper and shouting-rule rollout pass local validation, including the full repository test suite. PR CI/reviews are monitored.

Request and decisions#

Add grandfatherRule({ allowedUpTo, ...rule }: StrictRule & { allowedUpTo: Date }) and carry over no-shouting-constants from the existing worktree, enabling it with the wrapper. Use the requested example cutoff, 2026-11-10T00:00:00Z (inclusive).

Blame the source actually being linted. A diagnostic's start line determines its age, using Git author time. Uncommitted/untracked lines remain violations, even before a future cutoff. Only proven old lines are suppressed. Missing history must not silently exempt code: report violations when no repository or file history exists, and surface unexpected Git failures. Shallow boundary commits cannot prove a line's age. Preserve rule metadata, listeners, and fixes.

Checklist#

Integration spec using real dated Git commits and real oxlint. Ten wrapper tests in lint/grandfather-rule.test.ts.
Reusable wrapper with lazy blame lookup per linted source. lint/grandfather-rule.ts; documented in the adjacent Markdown file.
Carry over and enable the shouting rule with the wrapper. Plugin registration uses the requested cutoff; root config sets error severity.
Check cutoff boundary, edits/new files, report locations, and metadata/fixes. Real Git/oxlint coverage also includes shallow clones, worktrees, and Git errors.
Run validation, update draft PR, and arrange review monitoring. Full repository install, lint, typecheck, format, knip, and tests pass. Draft PR #2620 has a 24-hour monitor.

Implementation log#

Created from current origin/main, carrying only the relevant rule from no-shouting-constants; the old worktree remains available.

CI lint and autofix now fetch full history. Monitor monitor-grandfather-lint-pr checks PR #2620 every 20 minutes through 2026-09-11 09:00 UTC.

All local checks passed. OS: 3,121 passed, 18 expected failures, one existing skip. The wrapper also covers history across renamed paths with brackets.

API follow-up: allowedUpTo now sits at the top of the rule object; pre-built rules can be spread into that same argument. Blame behavior is unchanged.