Add version field to 27 local-sourced plugins

[dicksontsai]

Problem

27 local-path plugins (where source is a string like "./plugins/foo" in marketplace.json) have no version field in their .claude-plugin/plugin.json. This causes claude-cli to cache them at ~/.claude/plugins/cache/{marketplace}/{plugin}/unknown/ forever.

The cache check in copyPluginToVersionedCache (pluginLoader.ts) sees pathExists(.../unknown/) → true → skips re-extraction, even after the marketplace content updates. Users are stuck with stale plugin files until they manually delete the cache. This is currently blocking the exec-bit preservation fix from reaching users with already-cached 644 hook scripts.

Fix

Add "version": "1.0.0" to all 27 affected manifests.

This works because calculatePluginVersion reads the manifest from the freshly-synced marketplace tree (not the stale cache), and manifest.version is priority #1 in version resolution. New version → new cache path → cache miss → re-extract.

Why this instead of anthropics/claude-cli-internal#24773 (GCS SHA fallback)

	GCS SHA fallback	This PR
Granularity	All 27 re-extract on every marketplace push	Only bumped plugins re-extract
Disk usage	Accumulates one cache dir per GCS SHA × 27 plugins (no cleanup logic)	One dir per actual plugin version
Coverage	Only fixes migrateFromEnabledPlugins; runtime calculatePluginVersion still returns 'unknown'	Fixes both paths (manifest.version is priority #1 everywhere)
claude-cli change	+43/-22	None

The marketplace updates far more often than any individual plugin — using the marketplace SHA as a per-plugin cache key is the wrong granularity.

Affected plugins

plugins/ (15): agent-sdk-dev, code-review, commit-commands, explanatory-output-style, feature-dev, frontend-design, hookify, learning-output-style, mcp-server-dev, playground, plugin-dev, pr-review-toolkit, ralph-loop, security-guidance, skill-creator

external_plugins/ (12): asana, context7, firebase, github, gitlab, greptile, laravel-boost, linear, playwright, serena, supabase, terraform

Remote-sourced plugins (github/git/url in marketplace.json) already get a git SHA version and are unaffected.

Follow-up (not in this PR)

• 12 LSP plugins + autofix-bot have no manifest at all — separate issue
• Consider a CI check that fails when a plugin's content changes but its version doesn't, to enforce the bump discipline going forward

[tobinsouth]

lgtm

[ekovshilovsky]

Hitting this in Claude Code 2.1.x: hookify and playwright both fail at runtime with

Plugin directory does not exist: .../<plugin>/unknown
(<plugin>@claude-plugins-official — run /plugin to reinstall)

because unknown/ is the install path the plugin manager picks when the manifest has no version field. /plugin reinstall doesn't help — the manifests on main still don't have a version, so the cycle repeats. The only working local workaround is to rename <plugin>/unknown/ → <plugin>/0.0.0/ in the cache and edit installed_plugins.json by hand, which gets clobbered on the next plugin update.

This PR is the actual fix. It was approved 2026-03-27 and has just been conflict-blocked since. Could someone with commit access pick it up and rebase against main?

(For visibility I tried opening a rebased external PR — #1705 — but the contribution bot auto-closed it as expected for non-Anthropic authors.)

[ekovshilovsky]

cc @tobinsouth — you approved this in March. Bumping in case the original author is unable to rebase; the conflicts look purely mechanical and this bug is actively biting Claude Code 2.1.x users (see prior comment for the failure mode and a real-world repro). Anyone on the team with commit access willing to pick it up?

[WoojinAhn]

+1, recently filed #1758 before discovering this PR. Posting the audit data from there in case it's useful here: in the current state, 8 of 14 plugins in this marketplace display as Version: unknown due to missing version field, and 1 plugin (session-report) lacks plugin.json entirely. Linking the issue for the per-plugin breakdown.