fix: clarify coverage adoption and lint generated files safely

[Disble]

Summary

• Make optional coverage-tier adoption actionable for agents without silently enabling it.
• Keep generated .dharness/ modules out of ESLint's explicit target list.
• Integrate two independently tested work units before release-please produces the patch release.

Verification

• Independent whole-change verifier: PASS, no blockers.
• Go build, vet, full suite, formatting, and both local-gate refusal scenarios passed.
• Real sync human/JSON output checked; ESLint 10.12.0 defect reproduced.
• Staged mutation: 15/16 killed, score 0.94; one equivalent survivor under source scoping.
• Linux/Windows race-test CI must pass before integration.
• No ESLint 9 or complete real Vitest-adoption E2E claim.

Chain Context

This is the draft/no-merge tracker. Do not merge until both children are integrated and the final tree passes CI.

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

Children start at v1.13.0 and end with the verified hotfix. Out of scope: new coverage runners, policy changes, shared mutation scoping, dependency changes, and manual version/tag generation.

Tracking: odd/tasks/sync-guidance-hotfix-release.md.

Child PRs

• ESLint: fix(check): exclude generated files from ESLint targets #79
• Coverage: fix(sync): offer actionable optional coverage adoption #80

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
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