feat: let Studio create the topics and projects publishing requires

Publishing needs a topic and nothing could create one. The backend now owns
that surface; this is its consumer — the management contract vendored, a
gateway over its nine operations, and one Studio screen that lists, creates,
and deletes topics and projects.

The screen adds no CSS. It reuses the classes the working-copy list already
uses, so it inherits Studio's spacing, type, and colour rather than growing a
second visual vocabulary beside them. Scope stops at list/create/delete:
renaming, phase changes, and visibility are implemented in the backend and
declared in the contract, but their screens are a separate design.

Two real defects surfaced while making the public port async, and both would
have shipped:

The search page and the header search dialog shared a query key. With an empty
query, `["tech-log","search",""]` was identical for both, so react-query
handed one surface the other's cache — different shapes — and the page died
reading a field that was not there. Keys now name the surface.

The explore filter's selects are uncontrolled and read `defaultValue`, which
React applies once. Their options arrive later now, so the first render had
nothing to match and the value stayed empty: a topic in the URL no longer
showed as selected. The form key includes whether the catalog has arrived, so
it remounts with the options present. Controlled inputs would be the other
answer, but this form submits to build a URL — the URL owns the value.

The route brought its own bookkeeping: a build chunk, a manual accessibility
evidence file, and the CI artifact baseline that counts them. The gate pins a
digest of its own shape precisely so a new route cannot slip in without that
count being reviewed.

Test harnesses that render public screens now assemble the query providers and
await the settled paint, because the screens they render became async.

src/features/tech-log/presentation/public/components/explore-filter-form.tsx

@@ -56,7 +56,11 @@ export function ExploreFilterForm({
       item.title.toLocaleLowerCase("ko-KR") === normalizedProject,
   )?.slug;
   const hasActiveFilter = Boolean((showType && kind) || topic || project);
-  const formKey = [kind, topic, project, showType].join(":");
+  // 선택지는 나중에 도착하는데 아래 select 들은 `defaultValue` 를 쓰는 비제어 요소다 —
+  // 첫 렌더에는 맞출 option 이 없어 값이 비어버린다. 도착 여부를 키에 넣어 그때 폼을
+  // 다시 마운트시키면 defaultValue 가 적용된다. 제어 요소로 바꾸지 않는 이유는 이 폼이
+  // submit 으로 URL 을 만드는 구조라 값의 주인이 URL 이기 때문이다.
+  const formKey = [kind, topic, project, showType, view.ready].join(":");
 
   function submit(event: React.FormEvent<HTMLFormElement>) {
     event.preventDefault();

src/features/tech-log/presentation/public/components/search-dialog.tsx

@@ -23,7 +23,7 @@ export function SearchDialog({
   // result list with a loading skeleton on every key, which is a worse dialog
   // than a stale-free local filter. The predicate is the same one the catalog
   // applies for a non-empty query, so the visible result set is unchanged.
-  const view = usePublicContent(["tech-log", "search", ""], async (queries) => ({
+  const view = usePublicContent(["tech-log", "search", "dialog"], async (queries) => ({
     entities: await queries.searchPublicContent(""),
   }));
   const results = (view.data?.entities ?? []).filter((entity) =>