sync-env-downlisted

# sync-env-down — pull sync folder → local Brings the unified environment onto this machine. The engine (`sync_engine.py`) lives in the sibling `sync-envs` skill folder. ## How to run the engine - **Windows:** `py -3 "<claudeSkillsDir>\sync-envs\sync_engine.py" <args>` - **macOS/Linux:** `python3 "<claudeSkillsDir>/sync-envs/sync_engine.py" <args>` **Always launch it in the background** (the Bash tool's `run_in_background: true`), for both previews and applies. The sync folder is usually a cloud drive, and when the drive client is unwell the engine blocks in a kernel filesystem read for minutes. A foreground run holds the whole turn hostage, so the user cannot ask you to investigate while it hangs — which is exactly when they most want to. Backgrounding costs nothing on a fast run (you are notified as soon as it exits) and keeps you reachable on a slow one. ## The 30-second check (do this every run) A healthy scan reaches its first output within a few seconds. So: **if the run has not finished at ~30 seconds, check on it — do not keep waiting.** The engine emits a heartbeat to **stderr** while scanning: ``` [scan] claude-memory (down): 1840 files ``` Read the background output at ~30s, then again ~10s later, and compare: - **Line count/counter advancing** → healthy, just large. Say so and keep waiting. - **Last `[scan]` line identical across both samples** → **stalled. Raise the alarm now** (see below). The last line also names the phase it wedged in. - **No `[sca