Skip to content

FIX: carapace python CI failures after 0-5 Clawmark rescale#14

Merged
ryan10sa-star merged 1 commit into
mainfrom
claude/fix-carapace-python-ci
May 23, 2026
Merged

FIX: carapace python CI failures after 0-5 Clawmark rescale#14
ryan10sa-star merged 1 commit into
mainfrom
claude/fix-carapace-python-ci

Conversation

@ryan10sa-star

@ryan10sa-star ryan10sa-star commented May 23, 2026

Copy link
Copy Markdown
Collaborator

Diagnosis

The python CI job (pip install -e ".[dev]" && pytest in python/) has been failing on main since 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:

assert carapace.__version__ == "0.4.0"

This test was added with the v0.4 trust stack (2026-05-16). The package was later bumped to 0.5.0 in python/carapace/__init__.py (commit 5c9c1ec, 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; all clawmark_score literals and score_threshold references in python/tests/ are already on the 0-5 scale.

Fix

Replaced the brittle exact-version assertion with a stable check that

  1. Verifies a version string is exported, and
  2. Asserts it is >= "0.4.0" (lexicographic, fine for the foreseeable 0.x line).

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

  • Only python/tests/test_v04_features.py is touched (one test, one assertion).
  • No protocol source, no fixtures, no workflows, no CHANGELOG.md, no pyproject.toml.

Test plan

  • CI python job goes green on this branch
  • test_v04_public_entrypoint_exports still passes when the package eventually bumps to 0.6.0 (lexicographic >= "0.4.0" holds)
  • All other v0.4 export assertions (EpistemicLog, ComplianceProfile, evaluate_compliance, EscalationPolicy, check_escalation, BUILTIN_PROFILES) still verified

https://claude.ai/code/session_01UEu5f1gCA5nGnZrf67RK1c


Generated by Claude Code


View with Codesmith Autofix with Codesmith
Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.

@ryan10sa-star ryan10sa-star marked this pull request as ready for review May 23, 2026 05:54
Copilot AI review requested due to automatic review settings May 23, 2026 05:54
@ryan10sa-star ryan10sa-star merged commit 9928187 into main May 23, 2026
2 checks passed
@ryan10sa-star ryan10sa-star deleted the claude/fix-carapace-python-ci branch May 23, 2026 05:54

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants