anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify ATVM systemOS command defaults

Browse Source
This commit is contained in:
anthony.wen
2026-04-14 15:37:53 -04:00
parent 72ef15f308
commit 893fe35524
3 changed files with 16 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
atvm/docs/automation/run-learnings.md
View File

@@ -526,3 +526,12 @@ This file stores run-specific examples only when a run produced a new learning r
- When extracting `TEST FLOW:` from a generated spec, include common steps plus only the runtime-gated plugin branch selected for that run.
- Use watcher metadata such as the approved integration/plugin path to decide whether to include FC steps, iSCSI steps, or both.
- Do not count every plugin-gated branch in the generated spec just because the text is present.
## Run Learning: 2026-04-14 (`cmc-systemOS` should not carry plugin or integration arguments)
- Observed operator requirement:
- `cmc-systemOS` runs should not be planned with `--use_specified_plugin`, `--integration_type`, or watcher integration/plugin metadata.
- Treating `cmc-systemOS` like a plugin-bearing template adds incorrect command arguments and misleading status metadata.
- Action for future runs:
- Plan `cmc-systemOS` template commands without plugin-selection or integration-type arguments.
- When watcher-backed execution is used for `cmc-systemOS`, omit watcher integration/plugin metadata too.
- Keep plugin defaults scoped to templates that actually use plugin selection.