[eslint-refiner] ESLint Refiner - daily report (2026-09-28)

[github-actions[bot]]

ESLint Refiner — daily report (2026-09-28)

Overview: Disciplined 0-issue day. HEAD advanced to 60ff367 (#63786), an 11th consecutive shallow-clone squash artifact — this one docs-only (dictation glossary), no actions/setup/js changes. All 62 registered rules remain reviewed at least once. Today's effort raised the verification bar on 4 standing "chronic ungrounded" theories from corpus-count checks to full content-level review, and definitively retired all 4 — none survived scrutiny against the live corpus.

Key metrics

Metric	Value
Rules registered	62 (unchanged since 09-19)
Issues filed today	0
Open eslint-factory-labeled issues	5 (#63781, #63566, #63359, #62560, #62317)
Theories retired this run	4
Oldest open issue awaiting expiry	#62317 (7 days), #62560 (6 days) — both past the historical ~1-week first-expiry window

What was checked (and closed out)

4 chronic theories re-verified and retired

1. no-unsafe-promise-catch-error-property blanket-hasGuard gap — the rule collects unsafe .message/.stack/etc. accesses per-callback and only suppresses them at function-exit if any instanceof Error / getErrorMessage() / typeof-object guard appeared anywhere in the callback, rather than checking guard position per-access. Theoretically this could hide an early unguarded access if a later unrelated guard exists in the same callback. Previous runs (09-15, 09-27) only counted the 26 live .catch(err => {...}) sites in the corpus; this run read the full body of all 26. Every single one uses exactly one unsafe-property access, nested directly inside its own guarding expression (err instanceof Error && err.stack ? err.stack : getErrorMessage(err) or equivalent) — the divergence shape (two separate accesses, one earlier/unguarded) does not occur anywhere. Closing this theory unless a future callback grows a second access.
2. Bare RegExp(...) without new — zero occurrences anywhere in the corpus (only an unrelated escapeRegExp helper name). Retired.
3. no-json-stringify-equality indirect-variable/indirect-template-literal gap — re-grepped every non-test = JSON.stringify(...) assignment; all ~24 are single, unrelated serialize-for-logging/cache-key/payload idioms. evaluate_outcomes.cjs:1057 remains the one direct-comparison call site, and the rule already correctly flags it. 5th+ consecutive non-refile — retiring from active rotation (same status as expired no-json-stringify-equality: misses indirect template-literal comparisons (live gap: trace_graders.cjs gradeLoops) #57869/no-json-stringify-equality: still misses indirect template-literal comparisons -- recurrence of expired issue 57869 #59892).
4. core-method-resolve.ts 2-hop alias theory — const x = core; still has zero matches in the corpus after 5+ checks since 09-23. Retired.

Open issues snapshot

• no-math-minmax-array-spread: false positive on identifiers holding statically-bounded arrays #63781 — no-math-minmax-array-spread identifier-initializer false positive (filed 09-27, 1 day old)
• require-escaped-regexp-interpolation: no recognition for regex-fragment constants (5 sites already need manual disable, 1 unsupp #63566 — require-escaped-regexp-interpolation regex-fragment-constant gap (filed 09-26, 2 days old)
• require-fetch-response-body-try-catch: chain-unwrap gap hides .catch()/.then()-chained body reads (recurrence of #61542) #63359 — require-fetch-response-body-try-catch chain-unwrap gap, recurrence of require-fetch-response-body-try-catch: trailing .catch()/.then() on the body-read call hides it from the rule #61542 (3 days old)
• no-string-fallback-for-non-string-message: false positive on type-narrowed catch-param alias (recurrence of #60757) #62560 — no-string-fallback-for-non-string-message alias-type-narrowing FP, recurrence of no-string-fallback-for-non-string-message: false positive on type-narrowed catch-param alias (safeoutputs_cli.cjs:48) #60757 (6 days old)
• require-invalid-date-check-before-compare: arithmetic-derived duration variables still escape tracking (recurrence of #60577) #62317 — require-invalid-date-check-before-compare arithmetic-derived-duration recurrence of require-invalid-date-check-before-compare misses arithmetic-derived duration variables (live gap in check_rate_limit.cjs) #60577 (7 days old)

Outstanding maintenance items (not actionable by this workflow)

• Issues auto-expire (~1 week) without a fix. Two confirmed cases (prefer-actions-exec-over-child-process: false positive on shim.cjs dual-mode standalone/github-script files #61044, require-spawnsync-error-check: CHILD_PROCESS_OBJECTS name allowlist misses the common cp require alias #61543) had the underlying rule bug genuinely fixed upstream, yet the tracking issue still expired not_planned instead of being closed as fixed — this workflow has no close_issue/add_comment capability to reconcile that. A human or PR-capable workflow should periodically re-verify expired issues against current rule source before assuming they're unfixed.
• try-catch-rule-utils.ts VariableDeclaration-suggestion gap (affects ~14 fs-sync/child-process rules) has been filed and expired twice (eslint-factory: shared try/catch suggestion builder silently skips VariableDeclaration call sites #57868, eslint-factory: shared try/catch suggestion builder still skips VariableDeclaration call sites -- recurrence of expired issue 57 #59891) with no source fix — this workflow can describe but not submit the fix (no create_pull_request safe-output).
• README doc debt: only 2 of 62 rules are documented in eslint-factory/README.md.

Next actions

1. Check require-invalid-date-check-before-compare: arithmetic-derived duration variables still escape tracking (recurrence of #60577) #62317 and no-string-fallback-for-non-string-message: false positive on type-narrowed catch-param alias (recurrence of #60757) #62560 for expiry first thing next run (both now past the ~1-week window) and re-verify current source before deciding whether to refile.
2. Pick a genuinely fresh previously-zero-call-site candidate (e.g. no-json-stringify-set-or-map's let-binding gap, or no-github-request-interpolated-route's out-of-scope Octokit-client list) rather than re-checking today's 4 now-retired theories.
3. Continue watching for a real (non-squash) diff in actions/setup/js — git-log-based change detection has been dead for 11 consecutive runs.

Generated by 🤖 ESLint Refiner · claude · agent · 233 AIC · ⌖ 7.67 AIC · ⊞ 5.9K · ◷

• expires on Sep 28, 2026, 9:35 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by ESLint Refiner.

A newer discussion is available at Discussion #64187.