feat(claude): enable the full 65-plugin catalog at project scope

[kyle-sexton]

No linked issue

Summary

Enables all 65 plugins in this repo's marketplace at project scope, so the checkout dogfoods everything it publishes, while keeping the checkout-relative directory marketplace source that lets a session exercise in-flight plugin changes.

Fix

.claude/settings.json:

• Enabled 65 plugins under enabledPlugins — the exact plugin count in .claude-plugin/marketplace.json — sorted alphabetically, one per line, so a single entry can be flipped to false without disturbing the rest.
• That includes the 7 catalog entries marked defaultEnabled: false, which install as false and were enabled explicitly: ai-briefing, dometrain, firecrawl, kindle-dedrm, miro, songwriting, x.
• Added $schema pointing at json.schemastore.org/claude-code-settings.json for editor validation.
• extraKnownMarketplaces.melodic-software keeps the relative directory / ./ source. Existing env and worktree keys are unchanged.

Installs were driven from a parse of marketplace.json rather than a hand-transcribed list, so the enabled set cannot drift from the catalog.

An earlier revision of this branch switched the marketplace to a github source with autoUpdate. That was reverted in 7d574f3 and deliberately not reinstated: a relative directory source resolves against the repository checkout, so a session loads plugin code as changed on the current branch, whereas a github source installs from published main and makes it impossible to validate a plugin change before release. Catalog breadth and marketplace source are independent choices; only the breadth changed here.

docs/CLOUD-SESSIONS.md described a curated nine-plugin set and would otherwise have contradicted the shipped config. It now documents the full-catalog choice, states the per-turn context cost as the trade, points consumer repos at enabling only what they need, and records the two unset credentials below. The claude-code-plugins row in docs/CLOUD-FLEET-SETUP.md no longer lists enabledPlugins as undecided.

Verification

• enabledPlugins count is 65 and equals the plugin count in .claude-plugin/marketplace.json; every value is true; zero names missing and zero extra when diffed against the catalog programmatically.
• claude plugin list --json reported 65 plugins, all at scope: project, all enabled: true, ids matching the catalog exactly.
• .claude-plugin/marketplace.json on this branch was confirmed byte-identical to main before being parsed as the source of truth.
• Valid JSON; 2-space indent, LF, final newline, no trailing whitespace, per .editorconfig and .gitattributes.
• .claude/settings.local.json and the user-scope settings file were not modified.

Not verified: runtime plugin behavior. Hooks, MCP servers, and skills load in a subsequent session, and claude plugin list --json exposes no error field, so a clean load rests on all 65 installing and listing without error rather than on a positive error report. Two plugins bundle MCP servers whose required credentials are unset and which exit at startup until configured: miro (miro_api_token) and dometrain (dometrain_api_key). A further 30 plugins have optional-only userConfig options unset. The claude plugin list verification above was run against the earlier github-source revision; the enabled set is identical, but it was not re-run after the source reverted to directory.

Related

Refs the automated Codex review on this PR.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MifjAMa5pCvgBsdLWL64WQ

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[claude]

Claude finished @kyle-sexton's task in 1m 53s —— View job

---

Security review complete

• Gather context (diff, changed files)
• Apply skip gate / assess security-relevant surface
• Review changed file(s) for security issues
• Post final findings

Scope: .claude/settings.json only (75 additions / 6 deletions), per gh pr diff / git show d9a37cb.

Changes reviewed:

1. Added $schema for IDE validation — no security impact.
2. Enabled 65 plugins under enabledPlugins ("<plugin>@melodic-software": true). Verified every enabled plugin id corresponds to an existing directory under plugins/ in this repo — no typosquatted or unexpected plugin names introduced.
3. Changed extraKnownMarketplaces.melodic-software.source from a local directory (./) to a github source (melodic-software/claude-code-plugins) with autoUpdate: true, and no ref/commit pin.

Why #3 isn't flagged as a finding: on its face this looks like the supply-chain pattern the review criteria calls out (unpinned source + auto-update = code that can change without a new review). However, this is the repo's own documented, intentional convention, not something introduced by this PR:

• README.md and docs/CLOUD-FLEET-SETUP.md both recommend exactly this source: github + no-ref-pin configuration.
• plugins/claude-ops/skills/plugins/context/scope-semantics.md#L160-L168 documents autoUpdate as an expected/recommended background behavior, and the repo's own tooling suggests enabling it when off.
• The marketplace source is this same repository, so the trust boundary (who can merge to main) is unchanged by this PR — it doesn't grant execution rights to any new party.

No CRITICAL/IMPORTANT/SUGGESTION findings. Diff is a config-only change (no code, no workflow permissions:, no secrets/token handling) and matches established, documented project convention.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d9a37cb3fe

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[github-actions]

Last security-reviewed head: 2a5c689edfb460c87d49ea84ad129a9c87075102. On the next push, the relevance gate compares only the commits since this SHA; delete this comment to force a full re-review.

[claude]

Claude finished @kyle-sexton's task in 3m 14s —— View job

---

Security review complete

• Gather context (diff, changed files)
• Invoke /review:security-review for PR feat(claude): enable the full 65-plugin catalog at project scope #2631 at HEAD 2a5c689
• Review changed file(s) for security issues
• Post final findings

Scope: relevance gate compares against the last reviewed head d9a37cb. Two commits landed since then — 7d574f3 and 2a5c689edfb460c87d49ea84ad129a9c87075102 (current HEAD) — touching .claude/settings.json, docs/CLOUD-FLEET-SETUP.md, docs/CLOUD-SESSIONS.md.

Net change to .claude/settings.json since the last review: only the extraKnownMarketplaces.melodic-software.source block — d9a37cb → 2a5c689 diff shows 7d574f3 reverted it from {"source":"github","repo":"melodic-software/claude-code-plugins"} + autoUpdate: true back to the checkout-relative {"source":"directory","path":"./"}, and 2a5c689 made no further change to it. See .claude/settings.json#L76-L83. This is a security-positive change (removes the unpinned remote autoUpdate source flagged in the prior review) — no new concern here.

enabledPlugins is byte-identical to the already-reviewed d9a37cb state — all 65 plugins true, including miro (L48) and dometrain (L33), which the marketplace catalog marks defaultEnabled: false. I re-examined this independently (it's the subject of two Codex P1/P2 comments) since the prior review's writeup didn't explicitly reason about it:

• plugins/miro/.mcp.json sources its credential from ${user_config.miro_api_token} (explicit per-user/per-project config, not an ambient env var), and the docs added in this PR (docs/CLOUD-SESSIONS.md L184-190) disclose that both MCP servers exit at startup until that credential is configured, and document /plugin configure / flipping to false as the mitigation for sessions that shouldn't attempt it.
• The marketplace source is checkout-relative (directory/./), so no new code-execution trust boundary is crossed by enabling more of this same repo's own plugins.
• This is unchanged, previously-reviewed, and now further disclosed in-repo — I'm not raising it as a new security finding. (Whether the full 65-plugin default is the right project default vs. the curated 9 the PR description still claims is a config/scope judgment call, not a vulnerability — out of scope for this security-only lane.)

No CRITICAL/IMPORTANT/SUGGESTION findings. Nothing in the reviewed diff introduces an injection surface, auth/access-control gap, unsafe secret handling, or GitHub Actions permission-widening.
· branch claude/melodic-software-plugins-dts0df

[claude]

Claude finished @kyle-sexton's task in 34s —— View job

---

Code review skipped

• Gather context (diff, changed files)
• Invoke /review:code-review and apply its skip gate
• Post final summary

Per the /review:code-review skip gate, this stops before deep review: the PR is closed (merged), so there is no open pull request to post inline review comments against. No findings were produced and nothing further was posted.

For reference, the change itself (.claude/settings.json enabling the curated nine-plugin set plus $schema) already received:

• A security review from Claude (no findings; config-only change matching documented convention).
• Automated review from chatgpt-codex-connector flagging the marketplace source, credentialed-plugin, and plugin-set-scope points — those were addressed/superseded by the version that merged, per the PR's final diff.

[github-actions]

Claude has reviewed this PR 1 time. The lane skips further automatic reviews after 5; deleting this comment resets the count.