Add PromptKit review follow-ups to the plan
This commit is contained in:
@@ -34,6 +34,21 @@ it must not recreate message replay, turn loops, or token aggregation locally.
|
||||
|
||||
## 1. Review Complete Native Conversations
|
||||
|
||||
Complete the PromptKit adoption review follow-ups before revising prompts.
|
||||
|
||||
- Extend the debug case of `TestSubprocessCorrectionRepairConversation` to
|
||||
compare the top-level `llm-execution.json` provider-attempt total with the
|
||||
provider fixture's request count. The total should include the initial proposal
|
||||
once and count each repair and validator request.
|
||||
[Subprocess fixture](../../cmd/audita/correction_repair_integration_test.go)
|
||||
- Decode each repair response once in the runner. Reuse the decoded value for
|
||||
proposal-reference and action checks and for debug output. Preserve the existing
|
||||
invalid-output disposition and raw response evidence.
|
||||
[Repair runner](../../internal/framework/runner/repair.go)
|
||||
- Compute each per-call execution summary once and reuse it for terminal coverage
|
||||
and usage in `llm-execution.json`.
|
||||
[Execution report](../../internal/framework/processreport/llm.go)
|
||||
|
||||
Use captured proposal exchanges and independent coordinator branches to inspect
|
||||
representative proposal-to-repair conversations, including a second revision and
|
||||
withdrawal. Review actual `OnPrepared` snapshots for instruction authority,
|
||||
|
||||
Reference in New Issue
Block a user