docs(matrix): LAB-750 ts Workers KV + Cache API backend rows

[27Bslash6]

Companion to cachekit-io/cachekit-ts#81 (LAB-750 — phase-2 edge storage).

• Adds Workers KV and Cache API rows to the Cache Backends table (ts-only, /workers entry).
• Updates footnote ¹: the phase-1 'CachekitIO or custom instance' surface is superseded — records the KV TTL floor (60s clamp-up, ttl <= 0 no-expiry), Cache API semantics (per-data-center, Cache-Control: max-age, synthetic never-fetched key URLs, best-effort eviction), and that backend instances now pass through the minimal/production/secure intents in every ts entrypoint.
• Header last-updated line records LAB-750.

Merge after cachekit-ts#81 so the matrix never claims unshipped support.

Summary by CodeRabbit

• Documentation
  • Updated the SDK Feature Matrix with refreshed version and interoperability details.
  • Added Cloudflare Workers KV and Cache API entries to the Cache Backends table.
  • Clarified support, TTL behaviour, storage mappings, bundling, refresh constraints, and cryptographic implementation details.
  • Updated the DynamoDB backend information and related Workers footnotes.

Description

This PR updates the SDK feature matrix documentation to reflect the latest SDK version releases and refine backend implementation details.

Changes

SDK version updates (LAB-903)
Refreshed the SDK Overview version numbers against the package registries following the protocol 1.1 rollout (envelope bin encoding, cachekit-core 0.4.0):

• cachekit-py: 0.12.0 → 0.17.0
• cachekit-rs: 0.3.0 → 0.5.0 (+ cachekit-macros 0.5.0)
• cachekit-core: 0.3.0 → 0.4.0
• cachekit-ts: 0.1.2 → 0.1.4

cachekit-core protocol 1.1 documentation
Expanded the cachekit-core note to document the v0.4.0 protocol 1.1 writer flip, where StorageEnvelope.compressed_data now emits msgpack bin encoding (via serde_bytes) while readers dual-decode both bin and the legacy array-of-ints format. Added the per-SDK rollout state: cachekit-py ≥ 0.17.0 ships it, while cachekit-rs 0.5.0 and cachekit-ts 0.1.4 still pin the 0.3 line (their 0.4.0 bumps are merged on main but unreleased).

Rust SDK dependency clarification
Updated the cachekit-rs entry to note it now depends on cachekit-core for encryption primitives only (the envelope is unused for stored values), with core-version rollout state consolidated in the cachekit-core note rather than a hardcoded version.

Workers KV TTL behavior clarification (LAB-750)
Refined footnote ¹ describing Workers KV TTL handling. Clarified that KV rejects values under its 60s minimum, so the SDK clamps shorter TTLs up to 60s before the put, and that the ttl <= 0 "store without expiry" behavior is an SDK rule rather than a native KV behavior.

Metadata
Updated the "Last updated" line to 2026-07-29 and added the LAB-903 changelog entry recording where per-SDK rollout state is now documented.

[coderabbitai]

Walkthrough

The SDK Feature Matrix changelog was refreshed, and the Cache Backends table now documents Workers KV and Cache API support alongside updated DynamoDB and Workers footnote details.

Changes

SDK Feature Matrix

Layer / File(s)	Summary
Refresh matrix status and backend semantics sdk-feature-matrix.md	The changelog wording was updated, and the Cloudflare Workers section now includes Workers KV and Cache API rows, revised DynamoDB support, and expanded transport semantics.
Estimated code review effort: 1 (Trivial)	~5 minutes

Possibly related PRs

• cachekit-io/protocol#10: Updates the same Cloudflare Workers backend rows and footnote semantics.
• cachekit-io/protocol#23: Revises the Cache Backends table and Workers/DynamoDB capability wording.
• cachekit-io/protocol#30: Refines Workers TypeScript entrypoint and edge-runtime semantics.

Suggested reviewers: kodus-27b

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: adding TypeScript Workers KV and Cache API backend rows to the SDK feature matrix.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch lab-750-matrix-workers-kv-cache-api

---

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

[27Bslash6]

Conflict in sdk-feature-matrix.md (the "Last updated" changelog line) — not trivial. Both sides edited the same sentence from a shared base but with overlapping semantic content: this PR (LAB-750) rewrites the footnote ¹ description to say the phase-1 ts-Workers surface limitation is now superseded, while origin/main kept the old footnote ¹ text unchanged and appended its own LAB-272 audit note. A naive union would leave two contradictory descriptions of footnote ¹ in the doc — needs a human call on which footnote wording is current.

[27Bslash6]

Auto-rebase: conflict in sdk-feature-matrix.md — the changelog paragraph on both sides describes overlapping landed work (LAB-446/LAB-595/LAB-519/LAB-427 appear in both) with different footnote ¹ claims about the Workers backend surface. Combining isn't a clean union — needs editorial judgment on which claims are current — needs a human call.

[27Bslash6]

auto-rebase: sdk-feature-matrix.md conflict is the shared 'Last updated' changelog paragraph — HEAD's LAB-750 entry and origin/main's LAB-729/430/272 entries both rewrite the same line, and HEAD's footnote ¹ reference may interact with origin/main's own footnote ¹ narrative. Merging changelog prose without dropping/misattributing a fact needs a human, not a mechanical union.

[27Bslash6]

Auto-rebased onto main: only conflict was the "Last updated" banner line in sdk-feature-matrix.md — origin/main's banner was missing a mention of this PR's LAB-750 change (everything else it lists was already identical or a superset), so merged in the missing sentence; the Workers KV/Cache API table rows and footnote had already auto-merged clean with no markers. Stdlib-only vector verify scripts (interop, encryption, wire-format, python-frame, file-backend) all pass. CI will re-run.

[27Bslash6]

Auto-rebased onto main: only conflict was the "Last updated" changelog banner in sdk-feature-matrix.md — both sides had added a distinct, non-overlapping sentence (this PR's LAB-750 Workers KV/Cache API note; main's LAB-903 SDK-version refresh note) to an otherwise identical paragraph, so merged both in as a union with no facts dropped. Everything else (Workers KV/Cache API table rows, footnote ¹ content, SDK overview table, rust-core notes) auto-merged clean. Stdlib-only vector verify scripts (interop, encryption, wire-format, python-frame, file-backend) all pass. CI will re-run.

[coderabbitai]

Actionable comments posted: 1

🤖 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 `@sdk-feature-matrix.md`:
- Line 83: Update the Workers KV TTL wording in the LAB-595 feature note to
state that Cloudflare rejects expirationTtl values from 1 through 59 seconds
because the minimum is 60, rather than clamping them. Keep the SDK’s explicit
ttl <= 0 no-expiry behavior separate from and clearly distinguished from the
native KV contract.

🪄 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: a7f7130e-856f-433a-b606-96b021eef60a

📥 Commits

Reviewing files that changed from the base of the PR and between 44ee437 and 36c4784.

📒 Files selected for processing (1)

• sdk-feature-matrix.md

[kodus-27b]

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

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.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

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

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.

​

[27Bslash6]

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