wiki: a Plugins page, and the reference pages regenerated Plugins, marketplaces and libraries get a page of their own; Sources keeps its name and becomes the backends page. Configuration, Tools and Endpoints are regenerated from the new config models and /health body. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
pack becomes library Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The Configuration note, and a diagram whose columns line up notes/Configuration.notes.md is the first use of the notes mechanism: the generated Include table lists `instructions` and `agents` with no sign that nothing is harvested from them, and the reference page somebody looks a field up in is where that belongs. Sources.md already said it; Configuration.md now does too, without editing a generated page. Configuration.md, Tools.md and Endpoints.md are regenerated: the banner now only promises a notes file when there is one, and Endpoints.md carries the corrected `fingerprint` type. Home.md's diagram had its box and its arrows in different columns, so the branch did not bracket the mcp-kb box it came out of. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The manual: generated reference and hand-written guides Thirteen pages and the notes directory. Configuration, Tools and Endpoints are rendered by scripts/generate_wiki.py from config.schema(), a live server's tool list and spec.build_spec(), so they cannot describe a server that never shipped; edit wiki/notes/<page>.notes.md to add prose to one. The rest — Home, Installing, Deployment, Sources, Skills, Prompts, Scoping, Operations — are hand-written and the generator never touches them. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>