Summary

ui/src/ui/views/nodes-exec-approvals.ts:21,90 carries autoAllowSkills: Boolean(defaults.autoAllowSkills ?? false) — an OpenClaw skills-marketplace config flag. RemoteClaw has no skills to auto-allow; this form field has no effect.

Evidence

• ui/src/ui/views/nodes-exec-approvals.ts:21 — form schema field
• ui/src/ui/views/nodes-exec-approvals.ts:90 — defaulting read from defaults.autoAllowSkills
• grep -rn 'autoAllowSkills' ui/ — only the two sites above

Why this is safe

The form field maps to a backend config key that no longer drives behavior (no skills subsystem to gate). Removing it from the UI form is UI-only; if the backend schema still accepts the key, stored values will be silently ignored. If the backend schema still documents it, that's a separate cleanup (coordinate with backend removal).

Changes

• ui/src/ui/views/nodes-exec-approvals.ts:21 — remove autoAllowSkills from the form schema
• ui/src/ui/views/nodes-exec-approvals.ts:90 — remove defaulting read
• Check corresponding backend config schema; coordinate if the field is still documented there
• Update tests touching autoAllowSkills

AC

• grep -rn 'autoAllowSkills' ui/ returns zero hits
• pnpm check green
• pnpm test green
• pnpm test:ui:smoke green

Context

Follow-up to the skills-marketplace gutting. Discovered during the post-#2336 UI remnants audit.