[HouMinXi]

Summary

• Correct the null-deadline test oracle to distinguish invalid trusted configuration from an executed baseline timeout.
• Require returned and persisted FAIL, no mutation acquisition stages or detached launches, and no baseline-timeout/flaky classification. Exercise mutmut discoverable and unavailable paths.
• Remove only this repaired test's Linux CI deselection. No production-code changes.

Contract evidence

The original a141dc1 assertion predates the deliberate 9b3a0fb malformed-outside-gate policy. Invalid configuration truthfully means mutation was not measured; it must not be classified as a baseline timeout.

Validation

• Final-head mutation ledger CI controls module: 503 passed.
• Changed-file Ruff check, Ruff format --check and git diff --check pass.
• Fresh independent five-lens review and sixth requirements acceptance found no blocking implementation findings on the identical candidate tree.
• Based on actual main 7851ee8 after chore(lint): clear retained Ruff debt and gate the full repository #348; no outstanding Ruff dependency. Final head d103d8a.

Limits

This is a bounded test-contract repair, not a full-suite-green claim. Broader real-CLI projection compatibility verification was blocked by auto-review over potential Semgrep data transmission and was not bypassed or counted as passing. No changes here address unrelated baseline failures. Draft for review; merge is not authorized by this PR.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →