fix(jsonrpc-agent): claim the renamed route in the persistent-tools replay catalog

The rename to deepseek-official reached cordis.snapshot.yml but not its
persistent-tools sibling, so the replay catalog no longer owned the route the
agent asks for. The SDK server then mounted the real adapter, which failed the
turn on a missing key. Re-records the six transcripts and the two diagnostics
cards that still carried the old route name.

examples/jsonrpc-agent/persistent-tools.snapshot.cordis.yml

@@ -1,5 +1,8 @@
 # Keyless replay keeps the persistent-tool composition intact and replaces
-# only its live DeepSeek adapter with the fixture-backed provider.
+# only its live DeepSeek adapter with the fixture-backed provider. The catalog
+# below claims the same `deepseek-official` route the agent asks for: an
+# unowned route makes the SDK server mount the real adapter, which then demands
+# a key this keyless lane has no way to supply.
 - id: base
   name: '@cordisjs/plugin-include'
   config:
@@ -13,7 +16,7 @@
             name: '@deepseek-ai/dsh-llm-replay'
             config:
               providers:
-                - id: deepseek
+                - id: deepseek-official
                   name: DeepSeek
                   models:
                     - id: deepseek-v4-flash