chore: re-vendor both contracts from the merged design package

Only the recorded source revision moves (55a9599 -> b98eaf9). The vendored
specs and the generated types are byte-identical, which is the useful part:
the envelope redefinition landed on a merge commit, not a schema change, so
nothing downstream has to move with it.

public/release-manifest.json

@@ -38,21 +38,21 @@
   },
   "contractSet": {
     "setAlgorithm": "CA_CONTRACT_SET_V1",
-    "setDigest": "sha256:8ae48a17a30f07a0672fbc2c46ea9ebe66637bd16f6914079b3bf31b8009d12f",
+    "setDigest": "sha256:c8a29bdf6deadd8951b0a15426fcc119ff85ee9349acc0e8b200c8a5650d8b31",
     "packages": [
       {
         "packageId": "@tech-log/public-contract",
         "version": "2.0.0",
         "digest": "sha256:8ac71425b38658f34641102b4c2e6e21288c811efebdb92c0a46fb9d4790e23e",
         "runtimeProtocolVersion": 1,
-        "sourceRevision": "55a9599"
+        "sourceRevision": "b98eaf9"
       },
       {
         "packageId": "@tech-log/studio-contract",
         "version": "3.0.0",
         "digest": "sha256:6cae9924403d0761f401643a022980b8e04183eea0d890c143c9fbbbbc7431e4",
         "runtimeProtocolVersion": 1,
-        "sourceRevision": "55a9599"
+        "sourceRevision": "b98eaf9"
       }
     ]
   }