Migrate CLI tests to native PromptKit sources

This commit is contained in:
2026-10-04 12:04:14 +00:00
parent 2027b80311
commit 54c8e9011e
3 changed files with 286 additions and 396 deletions

View File

@@ -3,7 +3,8 @@
## Status, Baseline, And Authority
Planned on 2026-10-04 against Scriptorium
`82b0f231b6ba71328f65f9a501143b2eedbe5d9c`. All thirteen stages are pending.
`82b0f231b6ba71328f65f9a501143b2eedbe5d9c`. Stages 1–5 are complete; stages
6–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
@@ -333,7 +334,14 @@ all effective definitions can be constructed offline with their resource origins
## Stage 5: Migrate CLI Parsing And Application-Inspection Tests
Status: Pending. Depends on Stage 4.
Status: Complete. CLI parser/config tests now protect ordered repeatable source
selection and whole-list overrides, native shared definition helpers, retired
flags and application fields, and application-only inspection with missing or
invalid framework paths. Focused CLI parser/config tests and `internal/config`
pass, as does the native definition-fixture render. The production build passes.
Full CLI tests retain only the execution/inspection fixture migrations assigned
to Stage 6; repository-wide test, race, and vet checks also reach the HTTP/report
constructor migrations assigned to Stage 7.
Files: `internal/adapter/cli/config_test.go` and parser/configuration sections
and shared helpers of `run_test.go`.