Prefer generated specs for ATVM test flow

This commit is contained in:
2026-03-30 20:31:14 -04:00
parent b1b7e89449
commit c64a64ca14
3 changed files with 16 additions and 1 deletions

View File

@@ -443,3 +443,11 @@ This file stores run-specific examples only when a run produced a new learning r
- Action for future runs:
- Add `--test_partition` to `cmc-templates.py` commands by default.
- Omit it only when the operator explicitly asks not to use it.
## Run Learning: 2026-03-30 (Use generated spec as the source of truth for `TEST FLOW:`)
- Observed operator requirement:
- The operator wants the current full workflow steps for the actual test template/run, not a stale hand-maintained flow list.
- Action for future runs:
- Resolve `TEST FLOW:` from the generated `.ts` spec for the actual run whenever that spec exists.
- Extract the numbered `it(...)` steps from the generated spec referenced by the run's `specPattern`.
- Only use template-level or static fallback flow definitions when the generated spec cannot be found or parsed.