v0.5: Python SDK assertion alignment + release prep (Beta-2; closes v0.4.0 follow-up b)#9
Open
eriknewton wants to merge 1 commit into
Open
v0.5: Python SDK assertion alignment + release prep (Beta-2; closes v0.4.0 follow-up b)#9eriknewton wants to merge 1 commit into
eriknewton wants to merge 1 commit into
Conversation
- pyproject.toml + __init__.py version bump 0.4.0 -> 0.5.0 - Validator error messages cite SPEC sections (attestation: SS11.5.5/SS11.5.6; envelope: SS11.5.4) for operator legibility - requirements.lock: Pygments 2.19.2 -> 2.20.0 (CVE-2026-4539), python-multipart 0.0.26 -> 0.0.27 (CVE-2026-42561) - 16 new tests: error text alignment, schema URN emit, forward-compat read (v0.4 + v0.5), pyproject version assertion - 946 tests passing (930 baseline + 16 new), zero regressions Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
eriknewton
added a commit
that referenced
this pull request
May 14, 2026
…nd guards, predicate opacity docs (#17) Closes sweep findings #3, #8, #9, #10: - #3: read-side schema accepts non-empty strings for reference type and relationship; emit vocabulary documented; non-canonical values warn. - #8: DISPUTE_RESOLVED validator uses Draft202012Validator with FormatChecker; transaction_record_hash pattern enforced. - #9: apply_dispute_resolved_to_attestation guards session match, agreement match, agreed state, and fulfillment-state preconditions. - #10: predicate documented as opaque reference slot for v0.5.2; preservation tests added; standalone primitive deferred to v0.6. Co-authored-by: Claude <noreply@anthropic.com>
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
1 participant
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.
Summary
What this PR ships
now cites the relevant SPEC section (§11.5.5 relationship vocabulary,
§11.5.6 required keys, §11.5.4 envelope references) for operator legibility
existing v0.4 callers continue working unchanged
python-multipart 0.0.26->0.0.27 (CVE-2026-42561)
What this PR does NOT ship
Tests added
tests/test_v05_error_text_alignment.py(6 tests): provoke each validator error,assert message contains "SPEC §11.5"
tests/test_v05_schema_urn_emit.py(3 tests): schema $id and package versioncarry v0.5
tests/test_v05_forward_compat_read.py(6 tests): v0.4 and v0.5 shapedreferences both validate; all types and relationships accepted
tests/test_v05_pyproject_version.py(1 test): pyproject.toml declares 0.5.0Castle-walking test answer
Concordia is the Heralds layer (Castle Layer 4: Cryptographic Receipts and
Reputation). No Castle Layer 1 enforcement surface touched. This PR aligns
Python validators with an already-ratified spec; no new enforcement claims.
Hard-gate checklist
Flags / deviations
None.
Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com