Purpose
Drive the multi-target config-sync CLI workflow using the defined phase pipeline with consistent backup and audit behavior.
IO Semantics
Input: CLI arguments, settings.json parameters, existing plan files, target tool configuration directories.
Output: Execution plans, phase execution metadata, run logs, and backup records.
Side Effects: Writes plan files, creates backups under backup directories, updates target configuration files when write phases execute.
Deterministic Steps
Parameter Normalization
- Read CLI arguments and merge with settings.json.
- Resolve target list and component selection.
Plan Creation or Loading
- Create a new plan describing collect, analyze, plan, prepare, adapt, execute, verify, cleanup, report phases; or load an existing plan file.
Phase Execution
- Run collect and analyze to discover current configuration state.
- Run plan and prepare to build and validate the execution plan, including backup locations.
- Run adapt and execute to apply changes for selected targets and components.
- Run verify, cleanup, and report to validate results, manage temporary artifacts, and emit summaries.
Result Persistence
- Persist plan updates, run metadata, and logs into backup directories.
1---2name: config-sync-cli-workflow3description: Orchestrate multi-target CLI configuration synchronization using config-sync phase runners and planners.4---5
6## Purpose
7
8Drive the multi-target config-sync CLI workflow using the defined phase pipeline with consistent backup and audit behavior.
9
10## IO Semantics
11
12Input: CLI arguments, settings.json parameters, existing plan files, target tool configuration directories.
13Output: Execution plans, phase execution metadata, run logs, and backup records.
14Side Effects: Writes plan files, creates backups under backup directories, updates target configuration files when write phases execute.
15
16## Deterministic Steps
17
181. Parameter Normalization
19 - Read CLI arguments and merge with settings.json.
20 - Resolve target list and component selection.
21
222. Plan Creation or Loading
23 - Create a new plan describing collect, analyze, plan, prepare, adapt, execute, verify, cleanup, report phases; or load an existing plan file.
24
253. Phase Execution
26 - Run collect and analyze to discover current configuration state.
27 - Run plan and prepare to build and validate the execution plan, including backup locations.
28 - Run adapt and execute to apply changes for selected targets and components.
29 - Run verify, cleanup, and report to validate results, manage temporary artifacts, and emit summaries.
30
314. Result Persistence
32 - Persist plan updates, run metadata, and logs into backup directories.
majiayu000