Summary

ui/src/ui/views/config-form.render.ts has a plugins entry in SECTION_META (label "Plugins", description "Plugin management and extensions") plus a custom plugins SVG icon. The config form is data-driven: section metadata renders only when the backend config schema emits a matching section. Most likely a schema orphan post-plugin-gutting, but needs schema audit first.

Evidence

• ui/src/ui/views/config-form.render.ts:244 — plugins: { label: "Plugins", description: "Plugin management and extensions" } in SECTION_META
• ui/src/ui/views/config-form.render.ts:192-203 — plugins icon SVG in sectionIcons
• No plugins section schema found in a cursory grep, but formal schema inspection needed

Blocked by

Schema audit (tracked separately as the SECTION_META orphan audit spike) must confirm the backend config schema does NOT emit a plugins section before this removal is safe. If the schema still emits it, removing the metadata would leave users seeing an unnamed/unexplained section.

Changes (after unblock)

• ui/src/ui/views/config-form.render.ts:244 — delete plugins entry from SECTION_META
• ui/src/ui/views/config-form.render.ts:192-203 — delete plugins SVG icon from sectionIcons

AC

• Schema audit confirms plugins section is not emitted by config schema
• grep -rn '"plugins"\|plugins:' ui/src/ui/views/config-form.render.ts returns zero hits
• pnpm check green
• pnpm test green
• pnpm test:ui:smoke green

Context

Follow-up to the plugin-system gutting. Discovered during the post-#2336 UI remnants audit. Note: additional SECTION_META entries (talk, broadcast, audio, discovery, models) are suspected schema orphans and should be classified in the same schema-audit spike.