Fix Claude plugin loading in v1.0.1
Merged
SH
3mo ago+80+80+01234567890123456789-44-44-01234567890123456789
What changed
- mark the Claude marketplace entry as strict so Claude Code loads one component source instead of reporting a manifest conflict
- add a release-readiness check that fails when strict manifest loading regresses
- accept GitHub CLI source-tracking metadata when validating an installed Skill copy
- bump all package, plugin, documentation, pinned runtime, and schema references to v1.0.1
Why
The v1.0.0 manifests passed static validation, but a clean Claude Code installation reported the plugin as installed and failed to load because marketplace and plugin component declarations were merged. A real post-publish install test exposed the discrepancy.
Validation
- clean Claude Code home: plugin reports
enabled - clean Codex home: plugin reports
installed, enabled - 43 automated tests pass
- generated v1.0.1 tarball installs in an empty directory and completes a dry-run
- official Skill, Codex plugin, Claude plugin, and GitHub Skill validations pass
- npm pack/publish dry-runs pass; production dependency audit reports 0 vulnerabilities
Summary by cubic
Fixes Claude Code plugin load failures on clean installs by enabling strict manifest loading. Rolls the release to v1.0.1 across manifests, schemas, and docs, and adds guardrails to prevent regressions.
-
Bug Fixes
- Claude marketplace entry now sets
strict: trueto avoid merged component declarations and ensure the plugin loads. - All manifests, docs, commands, and schema
$idURLs now pin tov1.0.1for consistent installs.
- Claude marketplace entry now sets
-
New Features
- Validator accepts GitHub CLI source-tracking metadata in
SKILL.mdfor installed copies. doctoradds a release check to assert strict Claude manifest loading and version parity.
- Validator accepts GitHub CLI source-tracking metadata in