config-sync-target-adaptation

Config-sync target adaptation coordinates target-specific adapters to apply configuration rules uniformly across Droid, Qwen, Codex, OpenCode, and Amp CLI environments. It maps each target to its corresponding adapter, resolves directories via shared helpers, and enforces safety constraints to ensure consistent rule application.

Use adapter-driven config-sync to manage target-specific configuration, rules, and commands directories. The plan-driven workflow deterministically resolves each environment's paths through dedicated helpers rather than hard-coded paths, ensuring safe, repeatable synchronization across heterogeneous CLI tools.

Yes. Config-sync target adaptation automates adapter selection and directory resolution using shared helpers (get_target_config_dir, get_target_rules_dir, get_target_commands_dir), eliminating manual path configuration. Backups verify safety for all target file modifications.

Adapters invoke governance through documented safety constraints and backup verification for every modified target file. The workflow enforces strict use of helper functions to resolve permissions and commands directories, preventing unsafe direct path access.

The deterministic target resolution phase maps each target in the plan to its corresponding adapter. Only mapped target/component combinations are processed; unmapped targets are skipped, ensuring predictable behavior and preventing unexpected configuration changes.

No. Adding a new CLI environment requires only mapping it to its adapter in the config-sync plan. Directory paths are resolved dynamically through shared helpers, so environment-specific paths are automatically discovered without manual reconfiguration.