Plugin update command fails to detect newer version (0.1.0 → 0.1.1)

Description

The claude plugin update command incorrectly reports that a plugin is at the latest version when a newer version is available in the marketplace.

Steps to Reproduce

1. Have plugin git-workflow@xabierlaiseca installed at version 0.1.0
2. Marketplace has version 0.1.1 available (confirmed in marketplace cache)
3. Run: claude plugin update git-workflow@xabierlaiseca -s user

Expected Behavior

Should detect that 0.1.1 > 0.1.0 and update the plugin.

Actual Behavior

$ claude plugin update git-workflow@xabierlaiseca -s user
Checking for updates for plugin "git-workflow@xabierlaiseca" at user scope…
✔ git-workflow is already at the latest version (0.1.0).

Environment

• Platform: macOS (Darwin 24.6.0)
• Model: claude-sonnet-4-5@20250929

Additional Context

Installed version (from ~/.claude/plugins/installed_plugins.json):

"git-workflow@xabierlaiseca": [
  {
    "scope": "user",
    "version": "0.1.0",
    "installedAt": "2026-02-24T15:57:34.023Z",
    "gitCommitSha": "ef11c002d91c65289c0b2d607254a2a5d106fdbf"
  }
]

Available version (from marketplace cache ~/.claude/.claude/plugins/marketplaces/xabierlaiseca/.claude-plugin/marketplace.json):

{
  "name": "git-workflow",
  "version": "0.1.1",
  ...
}

The marketplace cache is up-to-date (latest commit: be9c537), confirmed by checking ~/.claude/plugins/known_marketplaces.json which shows lastUpdated: "2026-02-25T18:05:58.799Z".

Workaround

The plugin can be updated by uninstalling and reinstalling:

claude plugin uninstall git-workflow@xabierlaiseca -s user
claude plugin install git-workflow@xabierlaiseca -s user

Suspected Cause

Version comparison logic in the update command may not be correctly parsing semantic versions or comparing them properly.