cherry-works 0.2.0 → 0.3.0

package/README.md

@@ -5,11 +5,11 @@ markdown files, and `cw` checks them, tests them and compiles them into the
 files your coding agent actually reads.
 
 ```text
-.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/agents/…
-                                              .mcp.json (cw mcp serve)
+.cw/charter/guide/no-any/index.md   ──cw build──▶   CLAUDE.md
+.cw/charter/sensor/lint/index.md                    .claude/rules/…
+.cw/charter/posture/secrets/index.md                .claude/settings.json (hooks, permissions)
+…                                                   .claude/skills/…, .claude/agents/…
+                                                    .mcp.json (cw mcp serve)
 ```
 
 ## Why
@@ -80,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
@@ -125,10 +125,13 @@ Each kind comes up at a different time:
 `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`.
+Every primitive is a folder holding its `index.md`, and any other file in that
+folder is one of its assets, reached from the body as `./<file>`. An id is at
+most 40 characters, and may be grouped with `/`: `mcp:mfbs/billing` is kept at
+`.cw/charter/mcp/mfbs/billing/index.md`.
 
-`cw build` compiles every primitive to `.cw/out/<kind>/<id>.md`: its headers,
+`cw build` compiles every primitive to `.cw/out/<kind>/<id>/index.md`, with its
+assets copied beside it: 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.
@@ -137,7 +140,7 @@ agent reads it.
 
 | 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 |
@@ -276,7 +279,8 @@ 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.
 

package/dist/cw.js

@@ -3,7 +3,7 @@
 // package.json
 var package_default = {
   name: "cherry-works",
-  version: "0.2.0",
+  version: "0.3.0",
   description: "The charter engine: resolves a charter and compiles it into what a coding agent reads.",
   keywords: [
     "claude-code",