fix(check): exclude generated files from ESLint targets

[Disble]

Summary

Exclude the directory dharness owns from ESLint's explicit staged targets. ESLint 10 otherwise resolves its generated config factory before applying root ignores and exits 2 with Unexpected function.

Changes

• Preserve project .mjs targets and separator-bounded sibling paths.
• Skip ESLint with an explicit explanation when every target is generated.
• Keep react-doctor, fallow, split layouts, and shared mutation scope unchanged.

Verification

• Regression scenarios observed RED then GREEN; owning package checks and index pre-commit gate passed.
• Real ESLint 10.12.0: generated target exit 2, real source exit 0; binary gate before exit 2 / after exit 0.
• Manual filter and empty-target guard mutations fail the owning scenarios.
• Whole-candidate independent verification PASS.

Chain Context

Field	Value
Tracker	#78
Position	1 of 2
Base	fix/sync-adoption-guidance
Starts at	tracker foundation from v1.13.0
Ends with	generated-target-safe ESLint stage
Follow-up	coverage adoption guidance
Out of scope	coverage behavior and other analyzer/mutation scope

main
 └── tracker
      └── 📍 child 1: fix/sync-guidance-eslint
           └── child 2: fix/sync-guidance-coverage

Tests and documentation stay with the behavior. This unit can be reverted independently.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud