miaodx/intuitive-flow/intuitive-tests

Intuitive Tests

Improve test-suite signal and maintainability. Keep proof of observable behavior, real failure modes, and supported contracts; consolidate duplicates and remove assertions that merely restate implementation shape. Keep at least one meaningful proof of every behavior. Runtime discovery and packaging checks can be valuable contracts even when they look structural.

For broad or ambiguous cleanup, audit then propose a decision-complete slice. For a precise implementation request, execute that slice and park unrelated ideas. Keep existing repo test conventions; pytest examples are not a required taxonomy.

Modes

Read value and pruning for test admission or deletion decisions; read suite structure only for markers, moves, fixtures, or parameterization. An audit may recommend a route without loading every implementation procedure.

Verify the changed behavior and affected runner/collection paths. Derive any external-service, hardware, or credential limits from current user/repo policy. Report kept/merged/deleted/reclassified tests, remaining proof, affected commands, and skipped checks with their actual reason.