1.2 KiB
2026-02-23 Session Notes
Plan Review: PipelineV2Config Restructuring
Session began with a detailed plan to refactor the flat PipelineV2Config type into a nested structure with semantic sub-objects. The configuration currently spans 30+ top-level fields with obvious groupings (reranker*, repair*, document*) that reduce readability.
The plan establishes seven sub-objects: extraction, worker, graph, reranker, autonomous, repair, and documents, while keeping master switches (enabled, shadowMode, mutationsFrozen) flat. Notably, minFactConfidenceForWrite moves to extraction.minConfidence (gating extraction quality), and maintenance settings consolidate under autonomous.* (recognizing maintenance IS the autonomous feature).
Backwards compatibility implemented via loadPipelineConfig() fallback logic: nested keys win when present, flat keys serve as fallback for existing YAML configs.
Plan scope: 15 files require updates across core types, daemon services, pipeline workers, repair system, dashboard, and CLI. Verification includes full build, 396+ tests, typecheck, and manual config parsing validation.
No implementation work commenced in this session — plan review and clarification only.