Isolate pipeline configuration discovery

This commit is contained in:
2026-09-16 04:26:24 +00:00
parent 869e68e834
commit df213bc2ba
8 changed files with 137 additions and 19 deletions

View File

@@ -36,7 +36,19 @@ migration plan; that history remains in Git.
## Stage 1 — Isolate command configuration discovery
Status: Not started
Status: Complete — 2026-09-16
Completion: Added an invocation-local pipeline discovery dependency with the
production resolver as its default, then moved the affected missing-config tests
onto real resolver calls over temporary candidate paths. The command-boundary
coverage verifies successful default selection reaches the configured loader and
that discovery failures stop before bootstrap, typed loading, or execution.
Checks:
- `go test ./internal/app -run 'TestResolvePipelineConfigPath|TestExecute.*Missing|TestExecuteSessionInitMissingDefaultConfig'` — pass.
- `GOWORK=off go test -race ./internal/app` — pass.
- `GOWORK=off go test ./...` — pass with ConfigKit v0.1.2.
Purpose: Make missing-config command tests deterministic before changing the
dependency, while exercising the real discovery logic.