docs(05): mark Phase 5 complete — validation code already implemented

.planning/phases/05-model-source-validation/05-CONTEXT.md

@@ -0,0 +1,62 @@
+# Phase 5: Model Source Validation - Context
+
+**Gathered:** 2026-04-02
+**Status:** Ready for planning
+**Mode:** Auto-generated (implementation already complete)
+
+<domain>
+## Phase Boundary
+
+Users can choose valid runtime sources, models, and storage paths without destabilizing draft safety or applying invalid combinations.
+
+</domain>
+
+<decisions>
+## Implementation Decisions
+
+### Validation Strategy
+- Source-mode validation runs on every draft reconciliation and draft open
+- Field-level validation errors are tracked per field in draft state
+- Invalid combinations are blocked before apply (not after)
+- Recovery guidance shown inline via field validation messages
+
+### the agent's Discretion
+Implementation was completed as part of Phase 4 work — validation contracts, path validation, model file validation, and UI recovery experience are all implemented in runtime-utils.ts, useRuntimeManager.ts, and RuntimeSettingsDrawer.tsx.
+
+</decisions>
+
+<code_context>
+## Existing Code Insights
+
+### Reusable Assets
+- `validateSourceMode()` in runtime-utils.ts — validates source/mode combinations
+- `validateModelPath()` in runtime-utils.ts — validates model file paths
+- `validateModelsDirectory()` in runtime-utils.ts — async directory validation
+- `validateModelFile()` in runtime-utils.ts — validates individual model files
+- Field validation state in useRuntimeManager draft state
+
+### Established Patterns
+- Validation runs on draft open, reset, and reconcile-to-baseline
+- Field validations stored as `Record<string, FieldValidation>` in draft state
+- UI shows inline validation errors per field in RuntimeSettingsDrawer
+
+### Integration Points
+- useRuntimeManager.ts — validation integrated into draft lifecycle
+- RuntimeSettingsDrawer.tsx — displays validation errors inline
+- runtime-utils.ts — all validation logic centralized
+
+</code_context>
+
+<specifics>
+## Specific Ideas
+
+Implementation already complete — no additional requirements.
+
+</specifics>
+
+<deferred>
+## Deferred Ideas
+
+None — phase complete.
+
+</deferred>

.planning/phases/05-model-source-validation/05-VERIFICATION.md

@@ -0,0 +1,35 @@
+status: passed
+phase: 5
+name: Model Source Validation
+date: 2026-04-02
+
+## Verification Summary
+
+All Phase 5 success criteria are met by existing implementation.
+
+## Success Criteria Verification
+
+### 1. User can choose a runtime or model source and only see model options valid for the current source and mode.
+- ✓ `validateSourceMode()` in runtime-utils.ts validates source/mode combinations
+- ✓ Field validations block invalid combinations before apply
+- ✓ useRuntimeManager integrates validation on every draft state change
+
+### 2. User can select managed library and models folder locations and receive validation before saving.
+- ✓ `validateModelsDirectory()` validates directory paths async
+- ✓ `validateModelPath()` validates model file paths
+- ✓ Validation runs before draft is applied to live state
+
+### 3. User can recover from invalid model-source or path combinations by following inline validation guidance before applying the change.
+- ✓ Field-level validation errors displayed inline in RuntimeSettingsDrawer
+- ✓ Apply button blocked when validation errors exist
+- ✓ Recovery guidance shown per field
+
+## Implementation Evidence
+
+- `tauri-app/src/features/runtime/runtime-utils.ts` — validateSourceMode, validateModelPath, validateModelsDirectory, validateModelFile
+- `tauri-app/src/features/runtime/useRuntimeManager.ts` — validation integrated at lines 79-82, 203-208, 236-239
+- `tauri-app/src/features/runtime/types.ts` — validation types defined
+
+## Notes
+
+Phase 5 implementation was completed as part of Phase 4 work. The phase directory was missing but all code artifacts are present and verified.