Migrate prompt fixtures to direct definitions
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Dependency upgrades, discovery, and smoke testing implementation plan
|
||||
|
||||
Status: Stages 1–4 complete; Stage 5 is next.
|
||||
Status: Stages 1–5 complete; Stage 6 is next.
|
||||
|
||||
## Authority and baseline
|
||||
|
||||
@@ -343,6 +343,16 @@ presentation, and error identity, not upstream detection algorithms.
|
||||
**Complete when:** the previous delivered feature set works through v0.16.0
|
||||
without compatibility scaffolding or implicit catalogs.
|
||||
|
||||
**Completed:** 2026-10-17. PromptKit fixtures now use direct prompt definitions,
|
||||
explicit profiles/backends, and distinct IDs for multiple prompts. ckprompt
|
||||
tests use the ID-only inspection and validation requests and verify that the
|
||||
removed version flags are unavailable. Semantic YAML tests cover absent,
|
||||
present-empty, and nonempty versions in prompt inspection, requirements, and
|
||||
catalog reports; PromptKit-specific requirement classification assertions were
|
||||
removed from the affected adapter/consumer tests. The ckprompt suite passed,
|
||||
and composed named inspection, requirements show, and request validation all
|
||||
ran successfully against the migrated fixture.
|
||||
|
||||
## Stage 6: Extend catalog contracts and engine adapters
|
||||
|
||||
**Primary files:** ckprompt public request declarations, `Suite`, `FromEngine`,
|
||||
|
||||
Reference in New Issue
Block a user