1.1 KiB
Coverage policy
ForgeFlow treats coverage as release evidence, not as a target to game. npm run coverage
enforces 75% statements, 75% lines, 75% functions and 65% branches globally.
The July 2026 hardening pass raised the measured baseline from 69.74% statements/lines, 68.82% functions and 55.38% branches to 81.48% statements/lines, 82.07% functions and 65.59% branches. Node/V8 discovered additional branch counters when previously unexecuted functions became covered; the denominator grew from 2,537 to 3,473 while the new tests added hundreds of asserted decisions. No command builders, platform guards or error adapters were excluded to improve the result cosmetically.
The 65% global gate is paired with scenario-level evidence for the critical boundaries: deploy-key rollback, deployment verification, Gitea authentication and redirects, SSH host identity and output limits, inventory reconciliation, stale plans, configuration recovery, release integrity and updater failure modes. New code must not reduce the global baseline. Future increases must come from additional asserted failure scenarios, not ignore comments or source exclusions.