feat(claude): nudge to update plugin version if a newer one exists

[OisinKyne]

feat(claude): nudge to update the Obol skills plugin when a newer version is released

obol stack up already tips Claude Code users toward installing the Obol skills plugin, but went permanently silent once it was installed — and its nudges mixed CLI and in-REPL syntax. This PR fixes the wording and adds a staleness check.

What's here

• Consistent CLI nudges: both the "marketplace not registered" and "plugin not installed" tips now use claude plugin marketplace add ObolNetwork/skills / claude plugin install obol@<marketplace> (previously one line was the in-REPL /plugin install … form).

• Update nudge: when the plugin is installed, the installed version (from ~/.claude/plugins/installed_plugins.json — v2 maps each plugin@marketplace key to an array of per-scope install records; the legacy single-object shape and the literal "unknown" version are tolerated) is compared against the released version (.claude-plugin/plugin.json on ObolNetwork/skills' default branch, fetched with a 2-second timeout and capped body read). A newer release prints:

  Tip: Obol skills plugin 1.4.0 is available (you have 1.3.0). Update with:
      claude plugin marketplace update obol
      claude plugin update obol@obol
  

• Never blocks, never nags on guesswork: any failure — no claude in PATH, malformed config, unreachable GitHub, unknowable local version — stays silent. Timing unchanged: the tip remains the final output of a successful stack up.

Testing

Unit tests with fixtures mirroring the real Claude Code file shapes (marketplace lookup incl. a renamed marketplace resolving by repo, both installed-plugins formats, "unknown" handling), a local test server for the manifest fetch (including 404-stays-silent), and a numeric version-compare table (1.9.0 < 1.10.0).

🤖 Generated with Claude Code