Migrate HTTP and report fixtures to PromptKit sources

This commit is contained in:
2026-10-04 12:20:43 +00:00
parent 5c302f18ac
commit 9ea9d0706d
3 changed files with 167 additions and 119 deletions

View File

@@ -3,8 +3,8 @@
## Status, Baseline, And Authority
Planned on 2026-10-04 against Scriptorium
`82b0f231b6ba71328f65f9a501143b2eedbe5d9c`. Stages 1–6 are complete; stages
7–13 are pending.
`82b0f231b6ba71328f65f9a501143b2eedbe5d9c`. Stages 1–7 are complete; stages
8–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
@@ -427,7 +427,13 @@ expectations, without legacy parsing or narrowed valid-definition support.
## Stage 7: Migrate HTTP And Report Fixtures Without Changing Their Contracts
Status: Pending. Depends on Stage 6.
Status: Complete. HTTP and report engine fixtures now use keyed prompt/profile
definitions and native ConfigKit underlays; backend tests use PromptKit's keyed
`BackendSource` while retaining explicit pointer-valued limits, including the
zero-capacity queue. Request/status and report assertions remain unchanged.
Focused HTTP/report tests, `go test ./...`, `go test -race ./...`, `go vet
./...`, the CLI build, `gofmt`, `git diff --check`, and a repository-wide search
for removed constructor APIs pass.
Files: `internal/adapter/http/handler_test.go`,
`internal/report/report_test.go`; other test constructors found by removed-API