ux: npm global install gives no first-run guidance — 'supermodel' command is not in a project context

[greynewell]

Problem

Users who install via npm install -g @supermodeltools/cli get the binary but no post-install prompt. Unlike install.sh (which runs the wizard), the npm postinstall script doesn't guide the user to run supermodel in their project.

When the user eventually types supermodel from a random directory (not a project root), the wizard or watch runs against the wrong cwd — same issue as #158 but triggered by the user, not the installer.

Current npm postinstall behaviour

npm install -g @supermodeltools/cli
# installs binary, prints nothing

Expected

After install, print:

supermodel installed. Run 'supermodel' inside your project directory to get started.

Action

• Add a postinstall script to npm/package.json that echoes the getting-started message
• Do NOT run the wizard from postinstall — let the user invoke it from their project

[coderabbitai]

🔗 Related PRs

#49 - Add first-run detection and install-time setup wizard [merged]
#152 - feat: auto-launch setup wizard on first run of bare 'supermodel' [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!