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.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 3a4e9ba3-224b-4c4f-9a60-215effb35625

📥 Commits

Reviewing files that changed from the base of the PR and between 05c89fb and 5cfbbb5.

📒 Files selected for processing (1)

• sdk-feature-matrix.md

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