using-sync

# Using LWC Sync Run Sync through the audited CLI only: ```text lwc sync HOST [ABS_DIRECTORY] --mode merge|pull|push ``` Every start, resume, resolve, abort, pull, push, or merge can publish or change durable data. Before the first execution in a bounded workflow, present a safety notice containing the exact command, target host, absolute directory, scope, mode, affected stores, impact, risks, recovery path, and reversibility. An explicit user instruction that already names or unambiguously accepts these facts is authorization; do not ask the human to repeat it. One authorization covers the bounded workflow while its host, directory, scope, mode, publication targets, and disclosed risks remain unchanged. It covers read-only preflight, prerequisite build and installation, the initial Sync, ordinary `--resume`, continuity or derived recovery, status checks, and an abort before publication. Equivalent command details that do not widen the target or risk do not require reconfirmation. Reconfirm only when a host, directory, scope, mode, or publication target changes; a new destructive, irreversible, privacy, or data-loss risk appears; or a candidate resolution would discard one side. Preserve-both and idempotent recovery within the same session remain covered. A Skill trigger alone is not authorization. Choose the scope explicitly before starting: - `--scope project` synchronizes only the active project Wiki. Supply the remote project's absolute directory when it cannot be ...