Summary
Review tests/harness and remove or reduce it unless its ongoing value can be demonstrated.
Problem
The code under tests/harness currently appears to provide little or no practical value. Until that value is established, it should not be treated as a source of test conventions, implementation guidance, or reusable patterns.
The folder adds maintenance and discovery cost without a clear corresponding benefit. We should determine whether it has any active consumers or supported purpose, then remove obsolete code rather than preserving it by default.
Scope
- Inventory the intended responsibilities and current consumers of
tests/harness.
- Verify whether CI, workflows, documentation, or supported test scenarios depend on it.
- Identify any functionality with a concrete, current use case.
- Remove code, dependencies, and references that do not have demonstrated value.
- Retain or rebuild only the minimum needed for confirmed use cases.
Acceptance criteria
- Every retained component has a documented purpose and active consumer.
- Code without demonstrated value is removed.
- CI and supported test flows continue to work.
- Documentation and repository guidance are updated to reflect the final state.
Summary
Review
tests/harnessand remove or reduce it unless its ongoing value can be demonstrated.Problem
The code under
tests/harnesscurrently appears to provide little or no practical value. Until that value is established, it should not be treated as a source of test conventions, implementation guidance, or reusable patterns.The folder adds maintenance and discovery cost without a clear corresponding benefit. We should determine whether it has any active consumers or supported purpose, then remove obsolete code rather than preserving it by default.
Scope
tests/harness.Acceptance criteria