config-sync-overview

Config-sync follows an eight-phase deterministic pipeline: collect, analyze, plan, prepare, adapt, execute, verify, and report. Backup strategy and verification occur at specific phases to ensure configuration integrity before and after synchronization across tool ecosystems.

Config-sync maps target tools to their specific configuration directories and key files. The .claude directory stores configuration state, plan files, and backup artifacts. Configuration precedence is determined by phase sequencing and target-tool mappings documented in the architecture.

The .claude directories store config-sync metadata including backup locations, execution plans, and configuration state. They define precedence rules and semantics for how configurations are collected, staged, and applied across different tool ecosystems during synchronization phases.

Backups are managed at specific phases within the config-sync pipeline. The collect and prepare phases handle backup creation and staging. Backup locations are consolidated within .claude directories and mapped to target tool configuration directories for recovery.

This overview consolidates phase pipelines, tool-to-directory mappings, backup locations, and .claude semantics in one reference. Use it to answer high-level architecture questions, resolve directory placement decisions, and understand configuration precedence without parsing complete documentation.