Summary of What Needs to be Done:
The CI test-selection guide (docs/ci-test-selection.md) documents how changed-file scoping works, but it lacks concrete examples of the fallback behavior when changed files cannot be detected.
Changes that Need to be Made:
Add a "Fallback Behavior" section to docs/ci-test-selection.md explaining:
- What happens when the changed-files list cannot be determined (e.g., shallow clone, missing Git history)
- How the script behaves when scripts/detect_changes.py returns an error or empty list
- Which test category is selected as the safe default in each scenario
- Example: shallow clone fallback → runs full test suite as safe default
Impact that it would Provide:
- Reduces confusion for contributors running CI in non-standard environments
- Documents the safety guarantees that prevent missed regressions
- Improves maintainability by making the fallback behavior explicit
Note: This task is being handled by tmdeveloper007 — please assign to that account when picking it up.
Summary of What Needs to be Done:
The CI test-selection guide (docs/ci-test-selection.md) documents how changed-file scoping works, but it lacks concrete examples of the fallback behavior when changed files cannot be detected.
Changes that Need to be Made:
Add a "Fallback Behavior" section to docs/ci-test-selection.md explaining:
Impact that it would Provide:
Note: This task is being handled by tmdeveloper007 — please assign to that account when picking it up.