Migrate CLI execution tests to native definitions

This commit is contained in:
2026-10-04 12:15:10 +00:00
parent 54c8e9011e
commit 5c302f18ac
2 changed files with 360 additions and 239 deletions

View File

@@ -3,8 +3,8 @@
## Status, Baseline, And Authority
Planned on 2026-10-04 against Scriptorium
`82b0f231b6ba71328f65f9a501143b2eedbe5d9c`. Stages 1–5 are complete; stages
6–13 are pending.
`82b0f231b6ba71328f65f9a501143b2eedbe5d9c`. Stages 1–6 are complete; stages
7–13 are pending.
This plan is for a Luna coding agent: implement the stages in sequential order,
normally one stage per implementation prompt. The
[feature roadmap](promptkit.md) owns the target state, scope, and confirmed
@@ -381,7 +381,14 @@ are protected without imposing filesystem validation on configured YAML paths.
## Stage 6: Migrate Existing CLI Execution And Definition-Inspection Coverage
Status: Pending. Depends on Stage 5.
Status: Complete. CLI run, render, report, deadline, and definition-inspection
fixtures now use native keyed definitions and ordered framework sources. Backend
definitions live in framework files, built-in backend overlays are accepted,
and tests retain source precedence, retries, version selection, required and
optional inputs, profile inheritance, provider data, and inspection boundaries.
`go test ./internal/adapter/cli ./internal/format` passes, as does the native
build. Repository-wide test, race, and vet checks stop only on removed
PromptKit constructors in HTTP/report fixtures assigned to Stage 7.
Files: remaining execution/inspection sections in
`internal/adapter/cli/run_test.go`; formatting fixtures only if affected.