[luckyPipewrench]

What changed

• Bumps pipelock-verify to 0.4.1 so receipts from Pipelock's parallel receipt chains verify. The fix for the signed group_binding field in session_open merged in fix: verify session_open group_binding signed by Pipelock #50 but isn't released yet, and 0.4.0 rejects every shard of such a run.
• The README and CLI docstring now state what CHAIN VALID covers. It checks the extracted ActionReceipt v1 entries only, and it doesn't show that the chain's end is present or that a single shard is a complete group.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 2a0fb67b-d2f3-4be3-99dd-271c6ed05ce9

📥 Commits

Reviewing files that changed from the base of the PR and between 0c2fa52 and 5379af0.

📒 Files selected for processing (5)

• CHANGELOG.md
• README.md
• pipelock_verify/__init__.py
• pipelock_verify/__main__.py
• pyproject.toml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Summary

Summary by CodeRabbit

• New Features
  • Verification now accepts signed group-binding data for receipts from runs with multiple receipt chains.
  • Released as version 0.4.1.
• Documentation
  • Clarified what a valid verification result confirms—and what it does not, including chain completeness, parallel-group completeness, and wrapped evidence entries.
  • Documented the verifier’s exit codes and how they differ from newer end-of-chain proof behavior.

Walkthrough

This release updates verification documentation and CLI exit-code descriptions. The package version changes from 0.4.0 to 0.4.1.

Changes

0.4.1 Release

Layer / File(s)	Summary
Verification scope and CLI documentation CHANGELOG.md, README.md, pipelock_verify/__main__.py	The documentation describes group_binding support, the limits of receipt and chain verification, and the CLI exit-code distinction from applicable Go releases.
Release version metadata pipelock_verify/__init__.py, pyproject.toml	The package and project versions change from 0.4.0 to 0.4.1.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 5379a

The release clarifies what verification establishes and updates the package version. The supplied implementation and test evidence support those changes, with no identified merge-blocking risk.

Architecture Summary

Architecture risk: 🔵 Low · up to 5379a

The change affects 4 systems.

Changed systems: pipelock_verify, CHANGELOG.md, pyproject.toml, README.md

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — pipelock_verify (service) was modified; 2 changed files map to changed impact.
• observed — CHANGELOG.md (service) was modified; 1 changed file maps to changed impact.
• observed — pyproject.toml (service) was modified; 1 changed file maps to changed impact.
• observed — README.md (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in CHANGELOG.md: Adds the 0.4.1 release heading and a Fixed entry documenting support for the signed group_binding field in verify() and verify_chain() for multi-chain Pipelock runs. It distinguishes per-receipt and per-chain verification from whole-group verification and notes that single-chain receipts continue to verify as before.
• observed — Modified behavior in CHANGELOG.md: Adds a Documentation entry recording that the README no longer claims exit-code parity with pipelock verify-receipt or unqualified parity with the Go verifier, and clarifies what valid chains, shards, and recorder-file entries do not establish or check.
• observed — Modified behavior in README.md: The parity statement now specifies signature, chain-linking, and canonical-form checks, and states that the conformance files are verified identically by both implementations.
• observed — Modified behavior in README.md: The CLI documentation retains exit codes 0 for success and 1 for failure, and adds that newer Pipelock releases may return 3 for a valid chain without a proven end. The new section explains that CHAIN VALID covers extracted ActionReceipt v1 signatures, signer consistency, and receipt links, but does not check other recorder entries, prove chain completeness, or establish parallel-shard group completeness. It notes that an unused rotation endorsement caused by truncation before its boundary is rejected, and identifies Pipelock’s group verifier as responsible for group-level checks.

Pre-merge checks · 5

Passed checks (5 passed)

Check name	Status	Explanation
Title check		The title clearly summarizes the release preparation and documentation changes that define what a valid verification result proves.
Description check		The description directly explains the 0.4.1 release, parallel receipt-chain verification, and the documented limits of CHAIN VALID.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 2…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

_{A rabbit checks the signed receipts,
And hops through chains with careful feet.
“A valid chain,” it says, “is clear,
But group-wide proof is not in here.”
A fresh new version greets the year,
While carrots mark the release near.}

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

[luckyPipewrench]

/review

[luckyPipewrench]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[github-actions]

AI PR Review

Verdict: clean
Review profile: default with gpt-6-luna (high reasoning); candidate judge gpt-6.1-sol (low reasoning).
Findings: high 0, medium 0, low 0.

Findings

No verified material findings were published.

Review details: binding and coverage

Command: /review
Model: gpt-6-luna (high reasoning)
Candidate judge: gpt-6.1-sol (low reasoning)
Binding: base 0c2fa527c226d4db626a1f3f97ea174eca0b7bd1 head 5379af0439b3bbd6d92a59808017e013f9ddad53
Reviewed range: 0c2fa527c226d4db626a1f3f97ea174eca0b7bd1..5379af0439b3bbd6d92a59808017e013f9ddad53 (whole pull request)
Review identity: 4f509e49a3814c19a852669df854c2bb
Classification: source:other, config, docs
Completeness: 6/6 representable units reviewed; 0 omitted or unrepresentable; 0 deletion-collapsed.

Capacity plan: default leaves 0 representable units outside its limit; deep leaves 0.