fix(web-ui): render localized setup-field labels in the plugin config drawer

[Weegy]

Problem

Clicking Config on a plugin attached to an orchestrator (/operator/agents/<slug>) replaced the entire page with the route error boundary — „Etwas ist schiefgelaufen".

Reproduced live on odoo-bot-harness.fly.dev; the captured console error is unambiguous:

Minified React error #31 … args[]=object with keys {en}
  → [web-ui] route error boundary caught

Root cause

Since #602 (OM-17) manifestLoader normalises every setup field's label and help into a { <locale>: text } map (normalizeLocalized(f['label']) ?? { en: key }). The store's setup form and credentials editor were updated to resolve those with pickLocalized. PluginsDnd was not — it still rendered field.label straight into JSX, which is React #31 "Objects are not valid as a React child". The throw happens on the first render after the drawer opens, so it propagates to app/error.tsx.

PluginSetupFieldDto declared label: string / help?: string, which is precisely why typecheck never caught the drift against the real payload.

This was not an edge case. Scanning the live /plugin-catalog response: 192 of 192 setup fields across 27 plugins are maps — not a single one ships a bare string. Every plugin with setup fields was unconfigurable from the orchestrator page.

Changes

File	Change
PluginsDnd.tsx	Resolve label/help via pickLocalized(…, useLocale()), falling back to field.key exactly as the loader does
_lib/agents.ts	PluginSetupFieldDto.label/help → LocalizedMarkdown | string
_lib/localized.ts	pickLocalized returns a bare string as-is — without that branch a pre-#602 payload would fall through to Object.values('abc') and render 'a'
__tests__/PluginsDnd.localizedFields.test.tsx	New regression test

Test plan

• New test: drawer opens, map resolves, active locale wins, bare string still renders, empty map falls back to the key
• Negative control — reverting only the render change fails 3 of the 4 with the exact React chore: apply byte5ai engineering-standards (initial bootstrap) #31 message
• npm run typecheck clean
• npm run lint — 0 errors (52 pre-existing warnings)
• npm run i18n:check — OK, 4086 keys
• Full web-ui suite — 998/998 passed (110 files)
• Post-merge: re-verify the drawer on the harness deployment

No new user-facing strings; the labels come from plugin manifests, so no messages/*.json change is involved.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}