Align systemOS watcher output with template behavior
This commit is contained in:
@@ -225,6 +225,18 @@ This file stores run-specific examples only when a run produced a new learning r
|
||||
- `21. Clean up iSCSI targets`
|
||||
- `22. Power off`
|
||||
|
||||
## Run Learning: 2026-03-27 (Template-specific coverage fields and systemOS flow)
|
||||
- Observed requirement:
|
||||
- `COVERAGE:` should only show fields that were actually present in the `cmc-templates.py` command for that template.
|
||||
- Showing an empty integration/plugin path on a template that does not use one adds noise and misleads the reader.
|
||||
- `cmc-systemOS` needs its own full numbered `TEST FLOW:` list rather than falling back to the generic short placeholder flow.
|
||||
- `NOTES:` should stay consistent across templates and should not include internal parent-summary recovery notes for `cmc-systemOS`.
|
||||
- Action for future runs:
|
||||
- Render `COVERAGE:` from the actual template command inputs used for that run.
|
||||
- Omit integration/plugin coverage lines when the template command did not use them.
|
||||
- Use the 21-step `cmc-systemOS` flow from `status-template.md`.
|
||||
- Keep `NOTES:` template-consistent and operator-facing, without parent-log-summary recovery notes.
|
||||
|
||||
## Run Learning: 2026-03-27 (Start watcher before runner when watcher is requested)
|
||||
- Observed failure mode:
|
||||
- Starting `run-sorry-cypress.py` before the watcher can race with the watcher helper's stale-log cleanup.
|
||||
|
||||
Reference in New Issue
Block a user