feat: full-stack MCP surface — client template, npm CI, 13 repos

- build.py: vendor templates/client into mcp/templates/client with
  client.json manifest (16 kinds); register drone-npm as a third CI shape
  (types: pypi/npm/docker); root *.py stale doc numbers fixed
- registry.py: registry://client resource + list_client_components /
  get_client_component / get_client_template tools; build prompt gains the
  client scaffold step (docs://modules/ui_admin); compliance prompt covers
  npm packages; drone docs describe all three shapes
- repos.json (+mcp): doc-weaver, react-auth, react-openapi (npm Type B,
  package.json version source), vet (app Type C, VERSION)
- docs: 90_drone_pipelines gains Type B npm section; 91_versioning covers
  package.json as a version source; 94_repository_inventory gains the npm
  package table and services/apps Type C; lib index updated

Verified: bundle regen (24 modules, client 16, drone 3, repos 13); registry
client readers exercised against the vendored bundle.

standards/lib/index.html

@@ -821,8 +821,8 @@ and an optional pipelines layer.</p>
 </ul>
 <h2 id="delivery-meta">Delivery &amp; Meta</h2>
 <ul>
-<li><strong>Drone Pipelines</strong> — the two CI shapes: a PyPI/npm package or a Docker
-  deployment.</li>
+<li><strong>Drone Pipelines</strong> — the three CI shapes: a PyPI package, an npm package,
+  or a Docker deployment.</li>
 <li><strong>Versioning &amp; Changelog</strong> — SemVer, the tag↔version contract, and the
   release changelog.</li>
 <li><strong>Repository Inventory</strong> — every covered repo, its type, version source, and