chore(conformance): record cachekit-ts's encryption 1.5.0 and current python-frame copies (LAB-8699)

[27Bslash6]

Records cachekit-ts's re-vendored fixtures from cachekit-io/cachekit-ts#230 (merged as 83e0566): encryption.json 1.5.0 and the current python-frame.json, which carry cachekit-io/protocol#180 and cachekit-io/protocol#181. No spec or fixture change.

• conformance/sdks.json reads cachekit-ts at 83e0566. All eight copies were re-hashed from that commit, and only two changed: encryption.json is now 1a8a3735…961589 and python-frame.json b677d5f1…5600d0.
• conformance/coverage.md is regenerated. cachekit-ts's copies of both fixtures are now the current revision. Its summary row goes from 9 / 73 / 12 (covered / partial / uncovered) to 9 / 78 / 7: ENC-1, ENC-2, ENC-3, ENC-7 and ENC-9 move from uncovered to partial (gap), and ENC-5, ENC-6, ENC-10, PRE-16 to PRE-18, PRE-22, PRE-25, PRE-28 and IOP-19 move from a partial vector count to partial (gap). Every mapped vector is now vendored; only each requirement's recorded gap keeps it from covered. No other SDK's column changed.
• In sdk-feature-matrix.md, the TypeScript Test vectors in CI cell records what the SDK's tests drive from each copy. No row that binds cachekit-ts fails, so it records no deviation. Note ¹⁶ records both copies. Its cachekit-ts encryption.json sentence, which still said 1.3.0, now says 1.5.0.
• A changelog fragment, changelog.d/20261009_lab-8699.md.

Merged with main after cachekit-io/protocol#186 (the cachekit-rs record) landed in the same three files. The matrix keeps main's text and re-applies only the TypeScript clauses, and coverage.md is regenerated from the merged tree. The cachekit-ts moves are unchanged, and no other SDK's column moves.

Verification

• python3 tools/conformance.py check --base origin/main: OK, and coverage.md is current.
• python3 tools/test_conformance.py: all 284 cases pass, re-run on the merged tree.
• Pre-commit hooks pass.

Closes LAB-8699

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 19 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Repository: cachekit-io/protocol/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 91be39cd-228d-42ed-8e54-b2d25834cd61

---

📥 Commits

Reviewing files that changed from the base of the PR and between a42e442 and 4842ab3.

---

📒 Files selected for processing (4)

• changelog.d/20261009_lab-8699.md
• conformance/coverage.md
• conformance/sdks.json
• sdk-feature-matrix.md

---

---

• 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

---

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

[kodus-27b]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the `@kody start-review` command at the root of your PR.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Providing Context (Files & MCPs)

Add these hints in your PR description (or a comment) to unlock deeper checks:

• Ticket / Acceptance Criteria: `Refs: ABC-123` (Linear/Jira/Asana/ClickUp/Trello) or a direct ticket link.
• Bugfix Validation: a Sentry/Datadog/Bugsnag event link (or paste the stack trace/error message).
• Endpoint Risk: mention the route (e.g., `POST /api/payments`) or controller/action name.
• Attach a repo file as context: use an explicit marker like `@file:docs/guide.mdx#L10-L50` (replace with your real path).
• API Contract Docs: include `@file:openapi.yaml` or `@file:swagger.json` when changing routes/schemas.
• Definition of Done / Standards: include `@file:DOD.md` or `@file:CONTRIBUTING.md` if your repo has them.
• Design System Source of Truth: include `@file:ui/index.ts` (replace with your DS entrypoint path).
• Feature Flags: include the flag key/name and `@file:flags.ts` / `@file:config.json` (and optionally the PostHog flag name).
• Edge/CDN Rules: link the Cloudflare rule/zone or describe the intended redirect/header behavior.
• Attach an MCP tool output: use `@mcp<provider|tool>` (replace with an installed MCP provider + tool, e.g., `@mcp<sentry|events.search>`).

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

[kodus-27b]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the `@kody start-review` command at the root of your PR.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Providing Context (Files & MCPs)

Add these hints in your PR description (or a comment) to unlock deeper checks:

• Ticket / Acceptance Criteria: `Refs: ABC-123` (Linear/Jira/Asana/ClickUp/Trello) or a direct ticket link.
• Bugfix Validation: a Sentry/Datadog/Bugsnag event link (or paste the stack trace/error message).
• Endpoint Risk: mention the route (e.g., `POST /api/payments`) or controller/action name.
• Attach a repo file as context: use an explicit marker like `@file:docs/guide.mdx#L10-L50` (replace with your real path).
• API Contract Docs: include `@file:openapi.yaml` or `@file:swagger.json` when changing routes/schemas.
• Definition of Done / Standards: include `@file:DOD.md` or `@file:CONTRIBUTING.md` if your repo has them.
• Design System Source of Truth: include `@file:ui/index.ts` (replace with your DS entrypoint path).
• Feature Flags: include the flag key/name and `@file:flags.ts` / `@file:config.json` (and optionally the PostHog flag name).
• Edge/CDN Rules: link the Cloudflare rule/zone or describe the intended redirect/header behavior.
• Attach an MCP tool output: use `@mcp<provider|tool>` (replace with an installed MCP provider + tool, e.g., `@mcp<sentry|events.search>`).

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.