cherry-works 0.1.0 → 0.2.1

package/README.md

@@ -8,7 +8,8 @@ files your coding agent actually reads.
 .cw/charter/guide/no-any.md   ──cw build──▶   CLAUDE.md
 .cw/charter/sensor/lint.md                    .claude/rules/…
 .cw/charter/posture/secrets.md                .claude/settings.json (hooks, permissions)
-…                                             .claude/skills/…, .claude/commands/…
+…                                             .claude/skills/…, .claude/agents/…
+                                              .mcp.json (cw mcp serve)
 ```
 
 ## Why
@@ -79,7 +80,7 @@ The link points at your checkout. After you change the sources, run
 Inside the git repository you want to govern:
 
 ```bash
-cw init                       # asks which agent to compile for, then scaffolds .cw/charter/
+cw init                       # asks which agent to compile for (claude, selected), scaffolds .cw/charter/ and builds
 cw kinds guide                # what a guide requires
 cw add guide no-any --header description="No any in TypeScript." --header globs="src/**/*.ts"
 cw edit guide:no-any          # write the body in $VISUAL or $EDITOR
@@ -113,23 +114,30 @@ Each kind comes up at a different time:
 |---|---|
 | `guide` | a touched file matches one of its `globs`, or on every turn when it has no globs |
 | `sensor` | the `signal` it names is raised, and the harness runs its `run` command |
-| `command` | it is asked for by name, or a request matches its description |
-| `skill` | one of its `triggers` matches the request |
-| `playbook` | one of its `triggers` matches; its body is a sequence of commands |
+| `skill` | one of its `triggers` matches the request, or it is called by name as `/skill-<id>` |
+| `playbook` | one of its `triggers` matches; its body is a sequence of skills |
 | `agent` | it is spawned by identity, with only the `tools` it lists |
 | `posture` | always, wherever the host can be told what to `allow` and `deny` |
 | `corpus` | a primitive's `rationale` cites it, to give the reasoning behind a rule |
 | `mixin` | never on its own; its body is lent to the primitives that pull it in |
+| `mcp` | a primitive's body names it as `mcp:<id>`: a place outside the repository, reached through `cw mcp serve` |
 
 `cw kinds <kind>` gives the exact fields each kind takes. An identity is
 `kind:id`, and it names exactly one primitive across the whole charter. If two
 files claim the same identity, the build is refused and both files are named.
+An id is at most 40 characters, and may be grouped with `/`: `mcp:mfbs/billing`
+is kept at `.cw/charter/mcp/mfbs/billing.md`.
+
+`cw build` compiles every primitive to `.cw/out/<kind>/<id>.md`: its headers,
+then the bodies of the mixins it pulls in, then its own. What your agent's host
+is given points to that document, so you can open any primitive exactly as the
+agent reads it.
 
 ## Commands
 
 | Command | What it does |
 |---|---|
-| `cw init [--agent]` | Set the repository up under a charter |
+| `cw init [--agent]` | Set the repository up under a charter, and build it |
 | `cw build [--preview]` | Compile the charter, or show what a build would write |
 | `cw list [--kind] [--min]` | List what the charter holds |
 | `cw kinds [kind]` | List the kinds, or the fields one of them requires |
@@ -142,6 +150,8 @@ files claim the same identity, the build is refused and both files are named.
 | `cw suite add \| edit \| remove` | Manage test files |
 | `cw vendor add <source> [--ref] \| remove \| list` | Install, update, remove or list vendor sources |
 | `cw portal [--port]` | Open the charter in a browser on this machine |
+| `cw mcp auth [identity] [--status]` | Sign in, as yourself, to every place the charter reaches, or to one again |
+| `cw mcp serve` | Serve every place the charter reaches to your agent, over stdio |
 
 `cw doctor` exits with a failure status when the charter has an error, when a
 vendored file was edited in this repository, or when the compiled output no
@@ -222,9 +232,52 @@ It is installed under `.cw/vendor/<name>/`, pinned to the ref you chose and
 committed. Vendored primitives are read-only. To differ from one, write your own
 primitive under a new identity.
 
+## Places outside the repository
+
+Much of what an agent needs to know is kept elsewhere: another service's code,
+an issue tracker, a wiki. An `mcp` primitive declares one such place, an MCP
+server, and the tools of it your agent may use:
+
+```markdown
+---
+kind: mcp
+id: mfbs/billing
+description: Billing service code and pull requests.
+endpoint: https://api.githubcopilot.com/mcp/
+path: moneyforward/billing-service
+auth: ["oauth", "token"]
+tools: ["get_file_contents", "search_code", "list_pull_requests"]
+---
+
+The billing service. Look here before changing anything that charges a customer.
+```
+
+A place is either an `endpoint` reached over HTTP, or a `command` with its
+`args` that `cw` starts as a local process; a local one takes a token only, in
+the environment variable its `tokenEnv` names. Any primitive points the agent
+at a place by naming it in its body as `mcp:mfbs/billing`.
+
+```bash
+cw build            # adds one entry, cw mcp serve, to your agent's .mcp.json
+cw mcp auth         # sign in to every place you are not signed in to yet
+cw mcp auth --status
+```
+
+Every developer signs in as themselves, by browser where the place offers OAuth
+or with a token typed at a hidden prompt. Credentials are kept in the operating
+system's credential store, never in the repository, and renewed without asking
+where the place allows it. `cw mcp serve` is the one MCP server your agent is
+given: it serves the tools each place declares and forwards every call under
+your own credential. A place that is down or not signed in to loses only its own
+tools.
+
+A subagent reaches only the places it lists under `tools`: `mcp:<id>` for every
+tool of a place, or `mcp:<id>:<tool>` for one of them.
+
 ## Your agent can write rules too
 
-Every governed repository gets a built-in skill, `skill:cw-author`. It teaches
+Every governed repository gets a built-in skill, `skill:cw-author`, in the
+agent's hands from the moment `cw init` finishes. It teaches
 the agent to ask `cw kinds` what a kind requires and to write primitives with
 `cw add`, instead of copying fields from memory.
 
@@ -247,7 +300,6 @@ every check and changes nothing. A plain `npm publish` is refused.
 The engine follows a hexagonal layout. `src/hexagon/` holds the domain, the
 application use cases and their ports. `src/driver/` holds the CLI and the
 portal that drive it. `src/zdriven/` holds the adapters for files, git and YAML.
-The design is written in [specs/spec.md](specs/spec.md) and
-[specs/plan.md](specs/plan.md).
+What it must do is written in [specs/spec.md](specs/spec.md).
 
 This repository is governed by its own charter under [.cw/charter/](.cw/charter/).

package/dist/cw.js

@@ -3,7 +3,7 @@
 // package.json
 var package_default = {
   name: "cherry-works",
-  version: "0.1.0",
+  version: "0.2.1",
   description: "The charter engine: resolves a charter and compiles it into what a coding agent reads.",
   keywords: [
     "claude-code",
@@ -90,6 +90,7 @@ var package_default = {
   dependencies: {
     "@hono/node-server": "^2.1.1",
     "@hono/zod-openapi": "^1.6.3",
+    "@modelcontextprotocol/sdk": "^1.31.0",
     hono: "^4.13.7",
     picomatch: "^4.0.7",
     prompts: "^2.4.2",