---
phase: 05-tech-debt
plan: "01"
subsystem: ui
tags: [react, typescript, zod, registry, backend-selection]

# Dependency graph
requires:
  - phase: 05-tech-debt
    provides: Wave-0 TDD stubs for registry shape and consumer access patterns (05-00)
provides:
  - BACKEND_REGISTRY enriched with displayName, description, fields shape
  - BackendSelectionStep driven by Object.entries(BACKEND_REGISTRY) — no hardcoded BACKENDS
  - schemas/index.ts using .fields access
  - RemoteConfigStep.tsx using .fields access
  - Dead BackendFormValues<T> export removed from schemas/index.ts
affects: [06-new-backends, phase-6, BackendSelectionStep, RemoteConfigStep, schemas]

# Tech tracking
tech-stack:
  added: []
  patterns:
    - "Registry-driven UI: Object.entries(BACKEND_REGISTRY) replaces hardcoded arrays — adding a backend to registry auto-surfaces in UI with zero additional UI code"
    - ".fields access: all consumers use BACKEND_REGISTRY[type].fields, not the registry entry directly"

key-files:
  created: []
  modified:
    - src/schemas/registry.ts
    - src/schemas/index.ts
    - src/components/wizard/RemoteConfigStep.tsx
    - src/components/wizard/BackendSelectionStep.tsx

key-decisions:
  - "Registry shape change to { displayName, description, fields } makes the registry the single source of truth for both field definitions AND display metadata"
  - "displayName and description strings preserved exactly as in the former BACKENDS const to keep test assertions green without changes"
  - "BackendFormValues<T> removed — confirmed no consumers existed (tsc --noEmit: zero errors)"

patterns-established:
  - "Registry-driven card list: Object.entries(BACKEND_REGISTRY).map(([type, entry]) => <BackendCard ... />)"
  - ".fields access pattern: BACKEND_REGISTRY[backendType].fields for all field iteration"

requirements-completed: [TECH-03, TECH-04]

# Metrics
duration: 5min
completed: 2026-03-30
---

# Phase 5 Plan 01: Registry Enrichment & BackendSelectionStep Wiring Summary

**BACKEND_REGISTRY enriched with displayName/description/fields, BackendSelectionStep driven by Object.entries(BACKEND_REGISTRY), and dead BackendFormValues<T> export removed**

## Performance

- **Duration:** ~5 min
- **Started:** 2026-03-30T09:36:00Z
- **Completed:** 2026-03-30T09:39:00Z
- **Tasks:** 2
- **Files modified:** 4

## Accomplishments
- Changed BACKEND_REGISTRY from `Record<BackendType, FieldDef[]>` to `Record<BackendType, { displayName, description, fields: FieldDef[] }>`
- BackendSelectionStep now uses `Object.entries(BACKEND_REGISTRY)` — Phase 6 new backends auto-appear in UI with zero additional UI code
- All consumers (schemas/index.ts, RemoteConfigStep.tsx) updated to `.fields` access
- Dead `BackendFormValues<T>` export removed from schemas/index.ts — no consumers existed

## Task Commits

Each task was committed atomically:

1. **Task 1: Enrich BACKEND_REGISTRY and update all consumers** - `d495552` (feat)
2. **Task 2: Wire BackendSelectionStep to registry + remove dead export** - `52318d5` (feat)

## Files Created/Modified
- `src/schemas/registry.ts` - Changed shape from flat FieldDef[] to { displayName, description, fields: FieldDef[] }
- `src/schemas/index.ts` - Updated `.fields` access in buildZodSchema; removed BackendFormValues<T> export
- `src/components/wizard/RemoteConfigStep.tsx` - Updated two `.fields` accesses
- `src/components/wizard/BackendSelectionStep.tsx` - Replaced BACKENDS const with Object.entries(BACKEND_REGISTRY), added BACKEND_REGISTRY import

## Decisions Made
- displayName and description strings preserved exactly from the former hardcoded BACKENDS const so all test assertions remain green without modifying tests
- BackendFormValues<T> removed with confidence after tsc --noEmit confirmed zero usages

## Deviations from Plan

None - plan executed exactly as written.

## Issues Encountered
None.

## User Setup Required
None - no external service configuration required.

## Next Phase Readiness
- TECH-03 and TECH-04 complete; registry is now the single source of truth for display + field data
- Phase 6 (New Backends) can add a backend by adding one entry to BACKEND_REGISTRY — it auto-surfaces in BackendSelectionStep, buildZodSchema, and RemoteConfigStep with no additional UI changes
- Plan 05-02 (ReviewStep scriptTargets filtering) is independent and can proceed

---
*Phase: 05-tech-debt*
*Completed: 2026-03-30*