feat(frontend): manage custom registries + drop alarming warnings (MCP-1073) (#595)

Web UI registry management for the v0.37.0 blocker:

- Remove the one-time third-party warning gate, the "always quarantined /
  can never skip security review" copy, and the "third-party · unverified"
  badge. Adding a custom source now goes straight through. Provenance is
  surfaced as a neutral Official / Custom badge (MCP-1072 made it
  informational only).
- Add a Registries management section: each configured source renders as a
  card. Official cards are read-only with a "Built-in" tag. Custom cards
  carry a kebab (⋮) menu with Edit and Delete.
- Edit reuses the Add-Registry dialog pre-filled (id shown read-only),
  submitting to PUT /api/v1/registries/{id}.
- Delete opens a destructive confirmation modal, then DELETE
  /api/v1/registries/{id}. Servers already added stay; only the source is
  removed.
- api.ts: add editRegistrySource (PUT) + removeRegistrySource (DELETE)
  clients mirroring the addRegistrySource structured-error contract.

Soften the multiselect suffix ("— unverified" → "— custom") and update
docs/registries.md to describe the new neutral, edit/delete Web UI surface.

Verified: 114 vitest pass (incl. new api-client + manage-registries specs);
make build (frontend embed) green; Playwright CRUD sweep against a fresh
instance (add → edit-persisted → delete, official read-only, no warning).

Related MCP-1073

Author: Dumbris

docs/registries.md

@@ -52,8 +52,8 @@ Provenance is **informational only** (it no longer changes quarantine behavior):
   recorded on its config as `source_registry_id` / `source_registry_provenance`
   and surfaced in the approval/quarantine view.
 - The `list_registries` output (MCP, REST, CLI) includes `provenance` and a
-  `trusted` boolean (derived `official == trusted`) so a UI can show a one-time
-  third-party-registry warning.
+  `trusted` boolean (derived `official == trusted`) so a UI can show a neutral
+  **Official / Custom** badge.
 - **Migration:** earlier builds persisted the two-word tags `official/trusted` /
   `custom/unverified`; these are normalized to `official` / `custom` on read, so
   an existing `config.db` / `mcp_config.json` keeps working unchanged.
@@ -79,9 +79,12 @@ Equivalent surfaces:
 - **REST:** `POST /api/v1/registries` with `{ "url": "https://…", "protocol": "…", "id": "…", "name": "…" }`.
 - **CLI:** `mcpproxy registry add-source <https-url>`.
 - **Web UI:** the **Repositories** page has an **Add Registry** button (URL + optional
-  protocol/name). Each registry in the selector is flagged **Official · trusted** or
-  **Third-party · unverified** from its `provenance`, and the first custom add shows a
-  one-time third-party-registry warning (the acknowledgement is remembered locally).
+  protocol/name) and a **Registries** section listing every configured source as a
+  card with a neutral **Official / Custom** badge (official cards also carry a
+  **Built-in** tag). There is no warning gate — adding a custom source goes straight
+  through. Custom cards expose a **kebab (⋮) menu** with **Edit** (reuses the
+  add dialog, pre-filled, id read-only) and **Delete** (destructive confirmation);
+  official cards are read-only.
 - **macOS tray:** the **Registries** sidebar tab lists every configured registry
   with its provenance/trust badge, offers an **Add Registry** affordance,
   and shows a one-time third-party warning before the first custom add.
@@ -109,6 +112,7 @@ Equivalent surfaces:
 
 - **REST:** `DELETE /api/v1/registries/{id}` → `{ "registry": { … } }` echoing the removed entry.
 - **CLI:** `mcpproxy registry remove <id>`.
+- **Web UI:** the custom registry card's kebab (⋮) → **Delete**, behind a destructive confirmation modal.
 
 Errors share a stable code across surfaces: `registry_not_found` (404),
 `registry_shadows_builtin` (409, built-in cannot be removed),
@@ -134,6 +138,7 @@ Equivalent surfaces:
 
 - **REST:** `PUT /api/v1/registries/{id}` with `{ "name": "…", "url": "https://…", "servers_url": "https://…" }` (all optional) → `{ "registry": { … } }` echoing the updated entry.
 - **CLI:** `mcpproxy registry edit <id> [--name … --url … --servers-url …]`.
+- **Web UI:** the custom registry card's kebab (⋮) → **Edit**, which reuses the add dialog pre-filled with the current name/URL (id shown read-only).
 
 Errors share a stable code across surfaces: `registry_not_found` (404),
 `registry_shadows_builtin` (409, built-in cannot be edited),

frontend/src/services/api.ts

@@ -678,10 +678,10 @@ class APIService {
     return this.request<SearchRegistryServersResponse>(url)
   }
 
-  // MCP-866 / MCP-867: add a user-supplied registry source. The server always
-  // tags an added source custom/unverified (provenance is NOT part of the
-  // request), so every server later discovered through it lands quarantined and
-  // can never skip quarantine. We mirror the structured-error pattern of
+  // MCP-866 / MCP-867: add a user-supplied registry source. The server tags an
+  // added source as custom provenance (provenance is NOT part of the request) —
+  // informational only (MCP-1072); servers added from it follow the global
+  // quarantine default like any other. We mirror the structured-error pattern of
   // addServerFromRegistry so the UI can branch on the stable `code`
   // (invalid_registry_url | registries_locked | registry_shadows_builtin |
   // duplicate_registry).
@@ -730,6 +730,92 @@ class APIService {
     }
   }
 
+  // MCP-1073: edit a user-added custom registry source via
+  // PUT /api/v1/registries/{id}. Only the fields supplied are sent; empty fields
+  // are left unchanged server-side. Built-in registries are read-only and the
+  // backend refuses them with registry_shadows_builtin. Mirrors
+  // addRegistrySource's structured-error contract (registry_not_found |
+  // registry_shadows_builtin | invalid_registry_url | registries_locked).
+  async editRegistrySource(
+    id: string,
+    opts: { name?: string; url?: string; serversUrl?: string }
+  ): Promise<AddRegistrySourceResult> {
+    const body: Record<string, unknown> = {}
+    if (opts.name) body.name = opts.name
+    if (opts.url) body.url = opts.url
+    if (opts.serversUrl) body.servers_url = opts.serversUrl
+
+    const headers: Record<string, string> = { 'Content-Type': 'application/json' }
+    if (this.apiKey) headers['X-API-Key'] = this.apiKey
+
+    try {
+      const response = await fetch(`${this.baseUrl}/api/v1/registries/${encodeURIComponent(id)}`, {
+        method: 'PUT',
+        headers,
+        body: JSON.stringify(body)
+      })
+
+      const payload: any = await response.json().catch(() => ({}))
+
+      if (!response.ok) {
+        if (response.status === 401 || response.status === 403) {
+          if (payload?.code !== 'registries_locked') {
+            this.emitAuthError(payload?.error || `HTTP ${response.status}`, response.status)
+          }
+        }
+        return {
+          success: false,
+          error: payload?.error || `HTTP ${response.status}: ${response.statusText}`,
+          code: payload?.code
+        }
+      }
+
+      return { success: true, registry: payload?.data?.registry }
+    } catch (error) {
+      return {
+        success: false,
+        error: error instanceof Error ? error.message : 'Unknown error'
+      }
+    }
+  }
+
+  // MCP-1073: remove a user-added custom registry source via
+  // DELETE /api/v1/registries/{id}. Servers already added from it stay; only the
+  // source is removed. Built-in registries are read-only (registry_shadows_builtin).
+  async removeRegistrySource(id: string): Promise<AddRegistrySourceResult> {
+    const headers: Record<string, string> = {}
+    if (this.apiKey) headers['X-API-Key'] = this.apiKey
+
+    try {
+      const response = await fetch(`${this.baseUrl}/api/v1/registries/${encodeURIComponent(id)}`, {
+        method: 'DELETE',
+        headers
+      })
+
+      const payload: any = await response.json().catch(() => ({}))
+
+      if (!response.ok) {
+        if (response.status === 401 || response.status === 403) {
+          if (payload?.code !== 'registries_locked') {
+            this.emitAuthError(payload?.error || `HTTP ${response.status}`, response.status)
+          }
+        }
+        return {
+          success: false,
+          error: payload?.error || `HTTP ${response.status}: ${response.statusText}`,
+          code: payload?.code
+        }
+      }
+
+      return { success: true, registry: payload?.data?.registry }
+    } catch (error) {
+      return {
+        success: false,
+        error: error instanceof Error ? error.message : 'Unknown error'
+      }
+    }
+  }
+
   // Spec 070 (CN-001): add a server to upstream by *reference* — the server
   // re-derives and validates the config from the registry entry. The client no
   // longer splits install_cmd / chooses protocol (that client-side parsing was