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.

This commit is contained in:

DongHyeonka

2026-08-21 13:30:37 +09:00

parent ab8c6c14db

commit c5e8735041

15 changed files with 296 additions and 92 deletions

									
										src/features/tech-log/contracts/public/canonical-source.json
									
		+1
		-1
	
												View File
												
				@@ -2,7 +2,7 @@

				  "packageId": "@tech-log/public-contract",

				  "version": "2.0.0",

				  "digest": "sha256:8ac71425b38658f34641102b4c2e6e21288c811efebdb92c0a46fb9d4790e23e",

				  "sourceRevision": "0c10a4a",

				  "sourceRevision": "332b11f",

				  "operationIds": [

				    "getPublicSite",

				    "getPublicHome",