Complete the test suite review documentation

This commit is contained in:
2026-07-19 00:32:17 +00:00
parent 4f96abf42c
commit 9d3175d36a
2 changed files with 14 additions and 7 deletions

View File

@@ -132,8 +132,8 @@ handling of debug data is defined in [Operations](../operations.md#debug).
## Tests To Inspect ## Tests To Inspect
- `internal/framework/llm/scriptorium_client_test.go` and - `internal/framework/llm/scriptorium_client_test.go`: adapter mapping and local
`scriptorium_api_test.go`: adapter mapping and local HTTP integration. HTTP integration.
- `internal/framework/llm/scheduler_test.go` and - `internal/framework/llm/scheduler_test.go` and
`scheduled_client_test.go`: permits, FIFO behavior, cancellation, and wrapper `scheduled_client_test.go`: permits, FIFO behavior, cancellation, and wrapper
release. release.

View File

@@ -1,12 +1,19 @@
# Test Suite Policy Review Implementation # Test Suite Policy Review Implementation
## Status
Completed on 2026-07-18 by the commit series ending with `4f96abf`. This
document is retained as the execution record for the completed test-suite
policy review; its stages are no longer active implementation instructions.
## Purpose ## Purpose
This document is the decision-complete execution plan for implementing the This document records the decision-complete execution plan used to implement
target revisions in [Test Suite Policy Review](tests.md). Follow the stages in the target revisions in [Test Suite Policy Review](tests.md). The stages were
order. The feature roadmap owns the review evidence, desired test ownership, followed in order. The feature roadmap owns the review evidence, desired test
required dispositions, and target state; this document owns sequencing, ownership, required dispositions, and target state; this document records the
file-level work, validation, and stop conditions. sequencing, file-level work, validation, and stop conditions used during
implementation.
This is test-suite harmonization, not a production feature change. Do not This is test-suite harmonization, not a production feature change. Do not
modify production behavior. If a new durable test exposes incorrect production modify production behavior. If a new durable test exposes incorrect production