chore(conformance): record cachekit-py's encryption 1.5.0, cache-keys 1.3.0 and current python-frame copies (LAB-8295)

changelog.d/20261009_lab-8295.md

@@ -0,0 +1,16 @@
+### Conformance — cachekit-py vendors encryption.json 1.5.0, cache-keys.json 1.3.0 and the current python-frame.json (LAB-8295)
+
+- [`conformance/sdks.json`](conformance/sdks.json) reads cachekit-py at
+  [`d49b984`](https://github.com/cachekit-io/cachekit-py/commit/d49b984ea9560ae936d8215a17ab537cc3994a82), the merge
+  commit of [cachekit-py#561](https://github.com/cachekit-io/cachekit-py/pull/561), which vendors `encryption.json`
+  `1.5.0`, recorded for the first time, and re-vendors `cache-keys.json` `1.3.0` and the current `python-frame.json`,
+  all byte for byte. Every cachekit-py copy was re-hashed at that commit, and only those three changed. In
+  [`conformance/coverage.md`](conformance/coverage.md), cachekit-py's `KEY-2`, `KEY-6` to `KEY-9` move to `covered`;
+  `ENC-1` to `ENC-3`, `ENC-7`, `ENC-9`, `KEY-10`, `PRE-19`, `PRE-23`, `PRE-27` and `PRE-29` move from `uncovered` to
+  `partial (gap)`; and `KEY-1`, `KEY-3` to `KEY-5`, `ENC-5`, `ENC-6`, `ENC-10`, `PRE-16` to `PRE-18`, `PRE-22`,
+  `PRE-25`, `PRE-26`, `PRE-28`, `PRE-31`, `PRE-32` and `IOP-19` from a partial vector count to `partial (gap)`.
+- [Feature matrix](sdk-feature-matrix.md#protocol-compliance) **Test vectors in CI** row records cachekit-py's three
+  copies (unreleased), with one deviation: two `keyring.configuration` cases run as strict expected failures naming
+  [ENC-9](spec/encryption.md#enc-9), because cachekit-py refuses the current key repeated in
+  `CACHEKIT_PREVIOUS_MASTER_KEYS` only on the first call when that key is given as `master_key=`. Note ¹⁶ records all three
+  copies and gives this repo's `cache-keys.json` as `1.3.0`, with what `1.2.0` and `1.3.0` add.