plugins: replace enable-first profiles with a native all-true manifest

[yulonglin]

What

Replaces the enable-first claude-tools context plugin system with the platform-native model: a single user-scope install manifest, and no per-project plugin state.

Previously every repo needed a .claude/context.yaml before its plugins worked, and claude-tools context wrote project-scope true/false maps for all 33 installed plugins — the source of the △ "project settings override your user setting" warnings in /plugin.

Now enabledPlugins in claude/settings.json lists the 24 kept plugins with an explicit true. An explicit true wins at every scope, so the setup does not rely on the platform's undocumented no-entry default.

Changes

• Removed SessionStart hooks context_auto_apply.sh and check_things_mcp.sh
• deploy.sh: dropped the claude-tools context --sync step (marketplaces were already declared natively in extraKnownMarketplaces, so it was redundant) and the context-templates deploy block
• Deleted .claude/context.yaml and claude/templates/contexts/profiles.yaml
• statusline.sh: removed the now-dead context.yaml reader
• extraKnownMarketplaces 7 → 6: dropped dev-browser-marketplace; kept productivity-tools, which still ships the macOS-only bear-mcp
• Pruned 9 unused plugins: dev-browser, figma, gopls-lsp, huggingface-skills, imessage, plugin-dev, ralph-loop, swift-lsp, things-mcp
• Rewrote claude/docs/plugin-management.md; fixed the CLAUDE.md reference, which pointed at a path that did not resolve

Also done outside the repo (live runtime): the 9 uninstalls, deregistering rust-skills and dev-browser-marketplace, and trashing 9 temp_git_* cache dirs.

Findings worth reading

• Every plugin on this machine was installed at project scope, bound to the unrelated quiet-hooks worktree via projectPath. Install records pinned to a worktree die with it. Plugins should be installed at user scope; claude plugin list shows the Scope column.
• claude plugin uninstall resolves scope to the owning project, not the CWD — run from this worktree with the default --scope user, it edited quiet-hooks/.claude/settings.json. It also leaves install records behind, so "uninstalled" ≠ "absent from installed_plugins.json".
• The "no entry means enabled" premise is unverified. defaultEnabled is absent for all 276 official plugins, and every installed plugin already carries an explicit entry, so there was no clean case to observe. This is the strongest argument for the all-true manifest over an empty map.
• Open risk: deploy.sh runs no installs, and it is unconfirmed whether a user-scope true entry installs a missing plugin or only enables a present one. Treat the cross-machine claim as unproven until a second machine deploys.

Verification

• statusLine/hooks/permissions gate passes on claude/settings.json (per .claude/rules/dotfiles-settings.md); 24 entries, all true
• zsh -n deploy.sh and bash -n claude/statusline.sh pass
• Runtime marketplaces now exactly match extraKnownMarketplaces (6)
• Not yet verified: the /plugin warning/error count, which needs a fresh session

https://claude.ai/code/session_01WoJYQoyUNVUn56h87MHDQ7

---

Status, split three ways (updated after the follow-up sweep, 9588dbc)

1. Landed in the repo — verified. The all-true 24-entry manifest, hook removals, marketplace list 7 -> 6, deploy.sh and statusline.sh cleanup, docs rewrite. Plus 9588dbc, which swept seven stale references the first pass missed: a CLAUDE.md row and a README section documenting the retired CLI, an edit-profiles alias opening a deleted file, a claude-plugin-reset step calling a nonexistent claude-context binary, and two orphaned hook scripts. stale-claims.sh now asserts the manifest is all-true instead of running a permanently-skipped profiles check.

2. Changed in the live runtime, outside the repo. 9 plugins uninstalled; rust-skills and dev-browser-marketplace deregistered; temp_git_* cache dirs trashed. None of this is captured by the diff — a fresh machine gets the repo state, not this.

3. Changed in another worktree — unintended. Running claude plugin uninstall resolved scope to the owning project, which was the live quiet-hooks worktree, not the CWD. Net uncommitted delta there is one line: dev-browser@dev-browser-marketplace: false removed. Low harm (that plugin is uninstalled and its marketplace deregistered), and I deliberately did not touch the file again — it belongs to a running session.

Acceptance criteria that do NOT pass

• "Every pruned plugin is absent from installed_plugins.json" — fails. All 9 records persist; claude plugin uninstall edits enabledPlugins but leaves the install record. Not satisfiable by the CLI alone.
• "/plugin reports zero override warnings and zero hard errors" — unverified; needs a fresh session to observe.
• "No file references claude-tools context" — passed only after 9588dbc. It did not pass at f89b1f4.

Pre-existing, not caused by this PR

quiet-hooks/.claude/settings.json carries 32 entries with 10 set false, including telegram, playwright, research and writing. Project scope beats the user-scope true manifest, so those stay off in that worktree. It dies with the worktree, so no action taken.

Recommended follow-up

Every plugin on this machine is recorded as "scope": "project" bound to quiet-hooks — install records pinned to a worktree die with it. Reinstall the 24 at --scope user once no session is using that worktree.