[Disble]

Summary

Report absent coverage-tiers.json as an optional adoption decision under Left to you, not completed enforcement. Provide executable guidance to the agent before the adoption-only skill is installed.

Changes

• Separate sync-owned wiring from agent-owned policy, prerequisites, native config, tests, scripts and CI.
• State existing-path scope, Vitest-only integration and coverage-versus-mutation limits.
• Preserve no-declaration/no-write behavior and existing adopted/removed-policy safety.
• Keep repeated human/JSON regression tests, skill updates and seven prompt snapshots together.

Verification

• Human and JSON regression observed RED then GREEN, repeated sync leaves policy absent and native config unchanged.
• Actual built executable output checked in a disposable split project.
• Existing coverage wiring, skill, report and golden tests pass; index pre-commit gate passed.
• Manual adoption guard removal fails the owning test.
• Whole-candidate independent verification PASS.

Chain Context

Field	Value
Tracker	#78
Position	2 of 2
Base / depends on	fix/sync-guidance-eslint / #79
Starts at	generated-target-safe ESLint unit
Ends with	actionable non-enabling coverage adoption offer
Follow-up	final tracker integration, release-please patch release
Out of scope	native Jest/Go coverage, dependency installs and CI generation

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

Roughly 280 changed lines repeat the same approved prompt across seven golden fixtures; they are mechanical snapshots, not independent behavior. The cohesive authored unit stays with its tests and documentation.

[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