chore: v0.2.0 - version bump + README on per-call verification

[Mhemd139]

• pyproject.toml 0.1.1 -> 0.2.0 (the per-call verification release)
• README: new Per-call response verification section under the proxy: reference hierarchy, block vs forward rules, SSE one-frame hold, --observe rollout mode, and the COVENANT_SHEKEL_DRIFT pin demo, linking the design spec
• proxy command-table row and intro updated to mention response verification; docker tag in the k8s snippet bumped to 0.2.0

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation

  • Expanded guidance on contract-based verification of tool responses.
  • Documented per-call response verification behavior, including deterministic-violation blocking, degraded scalar retypes, extra-field forwarding, unverified handling, streaming behavior, and a non-blocking observe mode.
  • Updated the Kubernetes deployment example to use version 0.2.0.

• Release

  • Bumped the package version to 0.2.0.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 00b05de7-fbc2-4c5b-85ae-7521e645aef6

📥 Commits

Reviewing files that changed from the base of the PR and between 253ae6b and b211703.

📒 Files selected for processing (1)

• README.md

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

📝 Walkthrough

Walkthrough

The README documents contract-based per-call response verification, including quarantine, SSE, degraded, unverified, verifier-failure, and observe-mode behavior. The package version and Docker build example are updated from 0.1.1 to 0.2.0.

Changes

Runtime contract release

Layer / File(s)	Summary
Response verification documentation README.md	The proxy and runtime guard descriptions now cover contract-based tools/call response verification, quarantine behavior, SSE frame handling, degraded and unverified outcomes, verifier failures, and --observe mode.
Version reference updates pyproject.toml, README.md	The project metadata and Docker image build example are updated to version 0.2.0.

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

Possibly related PRs

• Mhemd139/Covenant#7: Updates related runtime-guard and quarantine documentation.
• Mhemd139/Covenant#13: Covers the related v0.2.0 per-call response verification design.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the version bump and README updates about per-call verification.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/v0.2.0

---

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.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 19: Update the README proxy description to accurately document that
verification is bypassed for responses exceeding _VERIFY_MAX_BYTES (reported as
skipped_large) and non-dict responses (reported as unverified), replacing the
claim that every tools/call response is verified while preserving the quarantine
behavior for responses that are verified.
- Line 134: Qualify the “sub-millisecond” SSE held-frame claim in the README to
reflect that optional Postgres persistence via record_drift can add latency;
state the guarantee only for the in-process path or describe the duration as
implementation-dependent. Do not claim a measured bound unless persistence is
moved off the response path and the resulting latency is verified.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 37954144-0c4b-43b5-8da2-ea7cba7a7e7e

📥 Commits

Reviewing files that changed from the base of the PR and between b4e9969 and 253ae6b.

📒 Files selected for processing (2)

• README.md
• pyproject.toml