Lift more native Python unittest assertions

[TSavo]

Summary

• expand the existing Python py-tests lifter surface for native unittest.TestCase assertions
• lift assertIsNone, assertIsNotNone, assertTrue, and assertFalse into normalized contracts
• emit structured lift-gap warnings for unsupported unittest assertions instead of fake contracts
• add package and RPC protocol coverage for normalized output and gaps

Verification

• python3 -m pytest implementations/python/provekit-lift-py-tests/tests -q
• cargo test -p provekit-cli --test cmd_mint_python_project_implications --manifest-path implementations/rust/Cargo.toml python_implication_consumer_mints_bridge_from_manifest_rpc -- --nocapture
• git diff --check

[coderabbitai]

Warning

Review limit reached

@TSavo, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 58 minutes and 20 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fdd17b17-5b98-4d5c-b229-67ddf5f2b016

📥 Commits

Reviewing files that changed from the base of the PR and between 1890ff8 and 107de4c.

📒 Files selected for processing (3)

• implementations/python/provekit-lift-py-tests/src/provekit_lift_py_tests/layer2.py
• implementations/python/provekit-lift-py-tests/tests/test_daemon_protocol.py
• implementations/python/provekit-lift-py-tests/tests/test_layer2.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/python-unittest-lifter-20260529

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1763dd6aed

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Limit lift-gap claims to unittest assertions

In pytest tests that use mocks, calls like mock.assert_called_once_with(...) or spy.assert_any_call(...) satisfy this startswith("assert") check even though they are mock-verification APIs, not unittest TestCase assertions. Because the caller then adds the test to claimed_tests without emitting a contract, those tests are no longer left for Layer 0/3 as the README dispatch model describes, so existing mock-heavy pytest tests can be swallowed with only a lift-gap warning. Please gate this path on an actual unittest-style receiver/context (e.g. self.assert... in a TestCase method) rather than any attribute named assert*.

Useful? React with 👍 / 👎.