ynh-troubleshoot

Topics in the source

• Troubleshoot a broken setup
• The rule that saves the most time
• Start here, always
• Symptom → command
• When ynh check gates
• Reading the four layers
• How to answer

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. Establish where the truth diverges before changing anything. There are four places a harness can be wrong, and the fix is different in each: 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. It checks the setup as a whole — vendor availability, installed-harness integrity, manifest validity of what is installed, symlink health, launcher and PATH, whether each harness's delegates still resolve (a delegate that is on disk but not committed fails every run while the harness still loads), 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. | Symptom | Run this first | Why | |---|---|---| | Install fails | ynd validate | Almost always a manifest or frontmatter error. Validation names the file

This is an excerpt. Refer to the complete source and its current requirements.