CLI: unknown commands fall into the setup wizard, --dev leaks its argument, failures report success

[zantvoort]

• Unknown top-level commands fall through to the interactive wizard (storm-cli/storm.mjs:3036, :3081), so any typo launches setup. The db dispatcher already prints "Unknown db command" (:2316); do the same at top level.
• --dev's argument value leaks into positional slots (:2074, :3077), so storm db add --dev ./skills treats the path as the connection name.
• Skills are fetched from https://orm.st/skills with no timeout, no retry and no cache, so an outage bricks onboarding; and per-skill failures still end with "You're all set!" (:2683 vs :2819). Fail visibly, or summarize what did and did not install.
• Version literals disagree: storm.mjs:12 says 1.11.3, package.json says 1.11.4. The release sed that stamps the real version (release.yml:94) is anchored to one exact source line with no grep -q guard, so a refactor silently breaks stamping; add the guard.