FIX: carapace python CI failures after 0-5 Clawmark rescale#14
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Diagnosis
The
pythonCI job (pip install -e ".[dev]" && pytestinpython/) has been failing onmainsince the v0.5.0 release. The audit work in #13 (CHANGELOG + publish workflow only) does not touch the python pipeline; the failure pre-existed.Root cause is a stale version assertion in
python/tests/test_v04_features.py::test_v04_public_entrypoint_exports:This test was added with the v0.4 trust stack (2026-05-16). The package was later bumped to
0.5.0inpython/carapace/__init__.py(commit5c9c1ec, 2026-05-20) as part of Phase B catalog/receipts work, but the v0.4 export test was never updated. It has been failing every CI run since.Not related to the 0-5 Clawmark rescale (#12) — that landed correctly with the matching test/fixture updates in
python/tests/test_v05_phase_b.py. The catalog tests are clean; allclawmark_scoreliterals andscore_thresholdreferences inpython/tests/are already on the 0-5 scale.Fix
Replaced the brittle exact-version assertion with a stable check that
>= "0.4.0"(lexicographic, fine for the foreseeable0.xline).The exact-version contract is already covered by
test_v05_phase_b.py::TestSDKExports::test_version_is_v050, which asserts__version__ == "0.5.0". The v0.4 test's purpose is to confirm the v0.4 trust-stack APIs (EpistemicLog,ComplianceProfile,EscalationPolicy, etc.) are still re-exported from the top-level package — that contract is preserved.Scope
python/tests/test_v04_features.pyis touched (one test, one assertion).CHANGELOG.md, nopyproject.toml.Test plan
pythonjob goes green on this branchtest_v04_public_entrypoint_exportsstill passes when the package eventually bumps to0.6.0(lexicographic>= "0.4.0"holds)EpistemicLog,ComplianceProfile,evaluate_compliance,EscalationPolicy,check_escalation,BUILTIN_PROFILES) still verifiedhttps://claude.ai/code/session_01UEu5f1gCA5nGnZrf67RK1c
Generated by Claude Code
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.