ynh-troubleshootlisted

# Troubleshoot a broken setup The commands to diagnose almost anything here already exist. What is missing is knowing **which one to reach for**, so this skill is a routing table, not a tutorial. ## The rule that saves the most time **Establish where the truth diverges before changing anything.** There are four places a harness can be wrong, and the fix is different in each: ``` the manifest → what composition resolved → what the vendor received → what the vendor did ynd validate ynd compose ynd preview vendor's own logs ``` Walk it left to right and stop at the first surprise. Most sessions that go wrong start by editing the manifest when the manifest was fine. ## Start here, always ```bash ynh doctor ``` It checks the setup as a whole — vendor availability, installed-harness integrity, manifest validity of what is installed, symlink health, launcher and PATH, and anything sitting in quarantine — and reports findings with the command that fixes each. It is read-only: it will tell you what is wrong and never change it. If `ynh doctor` is clean and the problem persists, the fault is in the harness content rather than the installation, so go to the symptom table. (If its output covers only Claude hook wiring, you are on a build from before `doctor` was widened — go straight to the symptom table, which needs nothing from it.) ## Symptom → command | Symptom | Run this first | Why | |---|---|---| | **Install fails** | `ynd