[feature] init should detect when npx cache serves stale CLI version (no @latest pin)

[BaseInfinity]

Feedback Type

Feature request

Description

Running npx agentic-sdlc-wizard init (without @latest) will serve whatever version is in the user's npx cache. If they ran the wizard once a month ago, they get the month-old CLI — silently. No warning, no version compare against the registry.

In my case, fresh init ran against cached 1.73.0 while npm registry latest was 1.77.0. The wizard files written to .claude/ were from 1.73.0. I only caught it because I ran /update and Step 1.5 surfaced the gap.

This is a quiet onboarding bug — first-time users won't know about npx caching and will install stale wizard files without realizing it.

Suggested Fixes (any one, or combination)

1. CLI-side registry check at init time. Have init hit https://registry.npmjs.org/agentic-sdlc-wizard/latest (same call /update Step 1.5 makes), compare to installed CLI version, and print a one-line nudge before doing any work:

   agentic-sdlc-wizard CLI 1.73.0 in use; latest is 1.77.0. Run \npx -y agentic-sdlc-wizard@latest init` to install the newest hooks/skills.`

   Non-blocking by default. Maybe a --check-version opt-in could make it hard-fail.

2. Docs change. The README install command should be npx -y agentic-sdlc-wizard@latest init (with -y to silence the npx prompt and @latest to force registry hit). Less invasive, less defensive — just steers users to the right one-liner.

3. Both. Recommend @latest in docs, plus a CLI nudge for users who copy the older npx agentic-sdlc-wizard init command from old blog posts / tutorials.

Context

• Wizard version installed: 1.73.0 (out of npx cache)
• npm registry latest at install time: 1.77.0
• Setup type: not yet run /setup — caught at first /update invocation
• Caught by: /update Step 1.5 (CLI version check) — that step works as designed, this request is about catching the gap one step earlier so users never need to discover it via /update

Why It Matters

The wizard's whole value prop is "follow the latest battle-tested SDLC". If onboarding silently installs a 4-version-old CLI, every downstream step (hooks, skills, templates) is stale by default. /update does catch it, but users don't always think to run /update immediately after install — most assume init gave them latest.

---

Submitted via /feedback skill