@twobirds/microcomponents 0.4.1 → 0.5.0

package/README.md

@@ -40,17 +40,25 @@ The progress of coding is occasionally being streamed on [twitch](https://twitch
 
 ## MCP Server
 
-An MCP (Model Context Protocol) server ships with this repo so AI assistants can look the library up instead of answering from memory: `microcomponents-mcp-server.ts` at the repo root.
+An MCP (Model Context Protocol) server ships with the package so AI assistants can look the library up instead of answering from memory. The source is `src/mcp/index.ts`, compiled by `tsconfig.mcp.json` to `dist/mcp/index.js` and published with the package, so installing it gives you the executable bin:
 
 ```bash
-pnpm run mcp:run   # start the server on stdio
-pnpm run mcp:dev   # restart it whenever src/ changes
-pnpm run mcp:docs  # regenerate docs/api.json and report undocumented exports
+microcomponents-mcp   # stdio server, straight from the installed package
+```
+
+In a published package the server runs from `dist/mcp` and reads the prebuilt `api.json` and the concept essays that the build step emits next to it. During development it generates the index live from `src/` at startup, so it cannot drift away from the library it documents:
+
+```bash
+pnpm run mcp:dev    # restart it whenever src/ changes
+pnpm run mcp:run    # start it from source on stdio
+pnpm run mcp:docs   # regenerate dist/mcp/api.json and report undocumented exports
 ```
 
 Tools: `list-components`, `get-component-docs`, `search-components`, `get-core-concept`, `get-source-file`, `list-undocumented`.
 
-There is no hand-written API list in the server. The whole index is extracted at startup from the JSDoc blocks of the public exports (the names re-exported by each `src/*/index.ts`), so it can never drift away from the code it documents — and `list-undocumented` tells you when a source file still lacks a doc block. Concept essays are hand-authored markdown, one file per concept under `docs/concepts/`, which is also where the tool's list of available concepts comes from.
+There is no hand-written API list in the server. The whole index is extracted from the JSDoc blocks of the public exports (the names re-exported by each `src/*/index.ts`), so it can never drift away from the code it documents — and `list-undocumented` tells you when a source file still lacks a doc block. Concept essays are hand-authored markdown, one file per concept under `docs/concepts/`, copied into `dist/mcp/concepts` by the build, which is where the tool's list of available concepts comes from.
+
+`get-source-file` reads package-root relative paths (`dist/core/MC.d.ts`, `dist/mcp/concepts/event-system.md`) and refuses any path outside the package sources.
 
 ## CLI
 
@@ -110,7 +118,7 @@ mc clean
 mc check
 ```
 
-`clean` and `check` are thin wrappers around the package.json scripts of the same name, so the scripts remain the single source of truth for what they do — `mc check` type-checks every project context (lib, cli, test, demo, node) and exits with the script's exit code.
+`clean` and `check` are thin wrappers around the package.json scripts of the same name, so the scripts remain the single source of truth for what they do — `mc check` type-checks every project context (lib, cli, mcp, test, demo, node) and exits with the script's exit code.
 
 The scaffold derives the file path from the tag using the same rule the runtime autoload loader uses (`my-card` → `my/card.ts`), names companion assets after the runtime's asset descriptors (`targetHtml` → `card.target.html`), and wires them into a `static assets` declaration. `--js` emits a plain JavaScript file for the rapid-prototyping path.
 

package/dist/cli/create.js

@@ -81,7 +81,7 @@ function packageJson(namespace) {
             typecheck: 'tsc --noEmit -p tsconfig.json && tsc --noEmit -p tsconfig.vc.json',
         },
         dependencies: {
-            '@twobirds/microcomponents': '^0.4.1',
+            '@twobirds/microcomponents': '^0.5.0',
         },
         devDependencies: {
             vite: '^8.1.5',