fix(types): preserve arbitrary tm.ok result payloads

[marlon-costa-dc]

Goal

Keep the no-matcher tm.ok overload generic for any Result payload while retaining the TestResultValue bound for structural matchers.

Root cause

The closed TestResultValue bound caused Mypy to degrade valid downstream Result payloads to object, producing 159 var-annotated errors in flext-infra.

Changes

• Open only the no-kwargs overload to arbitrary TResult.
• Retain the bounded kwargs overload.
• Add a Pydantic payload type-inference regression.

Evidence

• make fmt WHAT=check: 169 files formatted.
• make check: 7/7 gates, 0 errors.
• focused test: 1 passed.
• Python review: no findings.

Tracker: flext-vaw

---

Summary by cubic

Preserves arbitrary tm.ok result payload types to restore correct type inference and prevent downstream MyPy degradations. Old: tm.ok constrained payloads to TestResultValue, often collapsing them to object. New: tm.ok(result) is generic over TResult; tm.ok(result, **kwargs) remains bounded to support structural matchers. No runtime behavior change.

• Adjusts overloads and adds a safe cast in the kwargs path; matcher parameter validation is unchanged.
• Adds a regression test to ensure pydantic.BaseModel payloads retain their type through tm.ok.
• Satisfies Linear flext-vaw by eliminating spurious var-annotated errors in flext-infra; no migration required.

^{Written for commit 203c081. Summary will update on new commits.}

[sonarqubecloud]

Quality Gate passed

Issues
0 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