feat: read the profile's topics from Studio, and add working-copy deletion

Two things an author could not control from Studio.

The profile's "주요 관심 주제" was four strings in the JSX. Creating or removing
a topic in Studio changed nothing, and correcting the list meant a rebuild and
a redeploy. It now renders the published topic list. The old literal opened
with "Backend Architecture", which no record in the catalogue actually carries
— the profile was advertising a topic that did not exist, and nothing could
have caught that while the list lived in the markup.

The working-copy list gained a delete control. It routes by kind because the
contract and the storage both do: Case and Reference share one table split by
type, Question is its own. Decision has no delete — its lifecycle is accept,
reject, supersede, which records what happened rather than erasing it — so the
control does not appear for it.

The list summary carries no version, so deletion reads the working copy first
and uses the version it finds. A stale version from a list left open should
fail as a conflict, not delete whatever is there now.

public/release-manifest.json

@@ -38,28 +38,28 @@
   },
   "contractSet": {
     "setAlgorithm": "CA_CONTRACT_SET_V1",
-    "setDigest": "sha256:0872fd944d931d70550549496a8086322ea6c86adc1d5802030300eb0076d2f2",
+    "setDigest": "sha256:f3124d4f29c487d1d6b4f42326393c91ad0542ecb4b60c0ce09a62fb452bb173",
     "packages": [
       {
         "packageId": "@tech-log/management-contract",
         "version": "1.0.0",
-        "digest": "sha256:e16a9695e9034a273c769792ea8901fd706c61514137228b2c20e1b117ea0c01",
+        "digest": "sha256:9efc7709b29404db96a7cc7acecdd9ec7b27cb95f3389e5da2c4953e2e3e23aa",
         "runtimeProtocolVersion": 1,
-        "sourceRevision": "0c10a4a"
+        "sourceRevision": "332b11f"
       },
       {
         "packageId": "@tech-log/public-contract",
         "version": "2.0.0",
         "digest": "sha256:8ac71425b38658f34641102b4c2e6e21288c811efebdb92c0a46fb9d4790e23e",
         "runtimeProtocolVersion": 1,
-        "sourceRevision": "0c10a4a"
+        "sourceRevision": "332b11f"
       },
       {
         "packageId": "@tech-log/studio-contract",
         "version": "3.0.0",
         "digest": "sha256:6cae9924403d0761f401643a022980b8e04183eea0d890c143c9fbbbbc7431e4",
         "runtimeProtocolVersion": 1,
-        "sourceRevision": "0c10a4a"
+        "sourceRevision": "332b11f"
       }
     ]
   }