Migrate catalog and schema-driven configuration as the first full feature module

[quinCode]

Migrate catalog and schema-driven configuration as the first full feature module

Parent

#2

What to build

Migrate configuration discovery and schema-driven configuration into the new architecture as the first complete vertical feature. This should flow from LLMSTP-core config contract through CoreGateway, UI backend schemas, generated TypeScript client, and a React feature module.

This slice is the template for later feature modules and should demonstrate the intended end-to-end architecture.

Acceptance criteria

• UI backend exposes normalized endpoints, attacks, judges, inputs, output directories, and config schemas.
• CoreGateway consumes core contract data and normalizes it into the UI application model.
• React feature module displays available config choices based on capabilities.
• React feature module renders schema-driven configuration fields using generated UI API types.
• Feature tests cover loading, empty states, unsupported capabilities, and schema rendering.
• Backend tests cover catalog normalization and schema response behavior.
• Existing source config files in core remain read-only from the UI.

Blocked by

• Scaffold React/Vite/TypeScript shell with generated API client #6