Bug: `type: 'radio'` renders as text field and isn’t supported in collection builder

[bobbwal]

Problem

type: 'radio' renders as a text input in code‑based collections, and the collection builder UI doesn’t offer a radio field
type.

Expected

• Code‑based schemas with type: 'radio' render radio inputs.
• The collection builder allows radio and supports options (enum, enumLabels).

Impact

Radio fields are documented but aren’t usable in either code‑based or UI‑built collections.

Repro

Code‑based

  {
    type: 'radio',
    title: 'Priority',
    enum: ['low', 'medium', 'high'],
    enumLabels: ['Low', 'Medium', 'High'],
    default: 'medium'
  }

Result: renders as a text input.

UI builder

1. Admin → Collections → Add Field
2. Field Type dropdown
3. radio missing