chore(claude): register the forest plugin marketplace

[hercemer42]

Installing the Forest Claude Code toolkit in this repo currently takes two commands, the first of which nobody can guess:

/plugin marketplace add ForestAdmin/claudine
/plugin install forest@forest

This commits the marketplace source so only the second one is needed.

What the entry does, and does not do

.claude/settings.json registers ForestAdmin/claudine as a marketplace named forest and marks the forest plugin enabled for this project. It installs nothing: a developer who has not run /plugin install forest@forest has no plugin fetched, loaded or run for them — verified by putting an equivalent entry in a scratch repo for a plugin absent from this machine, opening a session there, and finding the plugin still absent from both claude plugin list and the install ledger.

Access to the private ForestAdmin/claudine comes from the developer's own git credentials. There is no field for it here, and someone without access gets a resolution failure.

Why .gitignore changes

Line 23 was .claude/, which excludes the directory itself — git never descends into it, so a !.claude/settings.json negation would be dead text. .claude/* excludes the entries instead, so the negation applies and only the shared settings file becomes trackable. Every personal file (settings.local.json, and every subdirectory) stays ignored.

Refs: PRD-713

🤖 Generated with Claude Code

Note

Register forest Claude plugin marketplace and track .claude/settings.json

• Adds .claude/settings.json with extraKnownMarketplaces pointing to ForestAdmin/claudine and forest@forest enabled in enabledPlugins
• Updates .gitignore to ignore .claude/* but negate .claude/settings.json so the config stays tracked

^{Macroscope summarized 177bba2.}

[linear-code]

PRD-713

[qltysh]

Coverage Impact

This PR will not change total coverage.

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.

[hercemer42]

Closing — the premise doesn't hold up.

A user-scope /plugin install forest@forest makes the toolkit available in every repo, not just the four. So a committed per-repo marketplace entry only helps somebody who has not installed yet, in one of four specific repos, and becomes dead weight the moment they install once anywhere. Verified the plain way: ForestAdmin/claudine itself commits no .claude/settings.json, and a session opened there still loads all seven forest skills, off a scope=user install.

Two further findings from measuring the mechanism rather than reasoning about it:

• extraKnownMarketplaces is lazy. A session never clones from it, so it changes nothing until somebody types /plugin install — naming forest@forest, which is exactly as unguessable as the repo name the entry was meant to spare them. Someone without access to the private repo sees nothing at all, rather than the per-session resolution failure this PR's description claimed.
• The "forest@forest": true pre-enable key installs at project scope, silently, at session start, with nobody running /plugin install. That is the narrower install shape, obtained without asking.

So the friction this targeted — /plugin marketplace add ForestAdmin/claudine — was not the real barrier. Not knowing the toolkit exists is, and no committed file fixes that, as PRD-713 concedes in its own value section. The demo does: two commands, once per person, at user scope, covering every repo forever.

PRD-713 goes back to that. Nothing here is worth the review and maintenance it would carry.