Remove unused legacy LLM error definitions

This commit is contained in:
2026-11-22 09:39:50 +00:00
parent dd25838589
commit 7ee7b997f0
3 changed files with 6 additions and 107 deletions

View File

@@ -288,16 +288,20 @@ contracts to work around the framework's own unbounded sample.
## Finding 5: Remove The Disconnected Legacy LLM Error Contract
**Status: Complete.** Removed the unused legacy error taxonomy and its self-test;
current execution retains native PromptKit errors and application assessment/
capture errors. Contracts, pipeline, CLI, and module integration tests pass.
Priority: P3. Relevant stages: 8, 24, 35, and 44.
### Evidence And Impact
[`contracts/errors.go`](../../internal/framework/contracts/errors.go) still
At the reviewed baseline, `internal/framework/contracts/errors.go` still
defines the pre-migration `ErrInvalidStructuredOutput`, `ErrLLMCapacityExceeded`,
`ErrLLMGeneration`, `LLMGenerationError`, constructors, and copied failure/attempt
metadata. Current producers and validators retain native PromptKit errors instead.
Graph/code searches find this old taxonomy only in that file and its
[self-test](../../internal/framework/contracts/errors_test.go), not in an active
self-test (`internal/framework/contracts/errors_test.go`), not in an active
application consumer.
This is leftover contract surface from the removed adapter, not a second active