Problem
Coverage status behavior is distributed across raw-string switches. The incomplete_tool status can have known empty skipped files and constraints after a reviewer result exists, but summary rendering currently treats it as unknown.
Impact
Equivalent coverage states can be rendered inconsistently, making review completeness harder to interpret.
Acceptance criteria
- Define a centralized, typed representation for coverage statuses and their result-produced, label, and completeness semantics.
- Include
incomplete_tool with its intended behavior.
- Update pipeline and summary consumers to use the centralized semantics.
- Add regression coverage for
incomplete_tool rendering.
Evidence: PR #540 review at internal/reviewplan/summary.go.
Problem
Coverage status behavior is distributed across raw-string switches. The
incomplete_toolstatus can have known empty skipped files and constraints after a reviewer result exists, but summary rendering currently treats it as unknown.Impact
Equivalent coverage states can be rendered inconsistently, making review completeness harder to interpret.
Acceptance criteria
incomplete_toolwith its intended behavior.incomplete_toolrendering.Evidence: PR #540 review at
internal/reviewplan/summary.go.