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

changelog.d/20261009_lab-8699.md

@@ -0,0 +1,13 @@
+### Conformance — cachekit-ts runs `encryption.json` 1.5.0 and the current `python-frame.json` (LAB-8699)
+
+- `conformance/sdks.json` reads cachekit-ts at
+  [`83e0566`](https://github.com/cachekit-io/cachekit-ts/commit/83e0566251b0b0d2cad4557b37b3041c9b2aa9a0),
+  the merge commit of [cachekit-ts#230](https://github.com/cachekit-io/cachekit-ts/pull/230), which re-vendors
+  `encryption.json` 1.5.0 and the current `python-frame.json` byte for byte. Every cachekit-ts copy was re-hashed at
+  that commit, and only those two changed. `conformance/coverage.md` is regenerated. For cachekit-ts, every vector
+  mapped to ENC-1 to ENC-3, ENC-5 to ENC-7, ENC-9, ENC-10, PRE-16 to PRE-18, PRE-22, PRE-25, PRE-28 and IOP-19 is now
+  vendored, so each reads `partial (gap)`, held back from `covered` only by its recorded gap. ENC-1, ENC-2, ENC-3,
+  ENC-7 and ENC-9 move there from `uncovered`, the rest from a partial vector count.
+- The feature matrix records what cachekit-ts does with the new rows, all unreleased until a cachekit-ts release
+  carries them. No row that binds cachekit-ts fails, so the matrix records no deviation. The **Test vectors in CI**
+  cell and note ¹⁶ record both copies.