plumbbob 0.13.2 → 0.13.3

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "plumbbob",
   "displayName": "PlumbBob",
-  "version": "0.13.2",
+  "version": "0.13.3",
   "description": "Attention-first build process — driver skills + a CLI that keep you the decider: guidance on the work, a latch on the record.",
   "author": { "name": "Rob McLarty", "email": "hello@robmclarty.com", "url": "https://robmclarty.com" },
   "homepage": "https://github.com/robmclarty/plumbbob#readme",

package/README.md

@@ -49,7 +49,7 @@ PlumbBob itself, running its own loop.
 ## The loop in one picture
 
 <p align="center">
-  <img src="docs/media/loop-one-step.svg" alt="One step of the loop: /plumbbob:build implements step 1 and stops at the pause, the human says looks good, the step is checkpointed" width="760">
+  <img src="site/media/loop-one-step.svg" alt="One step of the loop, drawn as a wall going up course by course: on the scaffold a person reads a plumb line at the corner, and down the wall a mechanical arm holds the next stone and waits" width="760">
 </p>
 
 Everything the model must stay true to lives in one file, the build's `intent.md`
@@ -72,7 +72,8 @@ a decision the plan left open or after a stretch of steps worth reviewing.
 `/plumbbob:build` is the same loop a step at a time, stopping at every step's pause, for
 a plan without ranges or a stretch you want to walk slowly. Nothing is locked and nothing
 refuses you: the loop does the labor, pulls up to the line, and waits for you to advance
-it. **You are the clock.**
+it. **You are the clock.** [`docs/runs.md`](docs/runs.md) walks one plan through its runs
+and then drives it by hand, the two side by side.
 
 ## What a prompt can't replicate
 
@@ -183,7 +184,7 @@ In Claude Code, inside any git repo with a clean tree:
    **Recommendation**: Approve it, refilling on read. The gate is green and the seam held, and a bucket that refills when it is read needs no timer for the route to clean up.
    ````
 
-   ![The build pause as Claude Code renders it](docs/media/pause.svg)
+   ![The pause, drawn: a mechanical hand has set its stone on the line and hovers open and still, while a plumb bob in front comes to rest](site/media/pause.svg)
 
    (The check gate is [checkride](https://www.npmjs.com/package/checkride), one
    run across the tools your repo already configures: types, lint, tests, dead
@@ -203,7 +204,7 @@ In Claude Code, inside any git repo with a clean tree:
      · range 2 of 2: /plumbbob:run (steps 2-3)
    ```
 
-   ![The boundary after looks good](docs/media/checkpoint-boundary.svg)
+   ![The boundary, drawn: a bench mark freshly cut into the newest course of a stone wall, older marks below, and the red line raised one course over stones not yet laid](site/media/checkpoint-boundary.svg)
 
    Ask instead (`expand 2`, or any question) and it shows more of what is there and
    changes nothing. The answer closes on one line pointing back at the step, not on the
@@ -360,14 +361,16 @@ that matters.
 > under [`docs/evals/`](docs/evals/): the route the latch owns (*no checkpoint over a red
 > check under pressure*) went from **2/5 prose-only to 5/5 latched** on the first sweep
 > ([2026-07-11](docs/evals/2026-07-11.md)), every sweep since has held it and closed the
-> two gaps that one surfaced, and the latest ([2026-09-17](docs/evals/2026-09-17.md))
-> scores the shape of the turn itself.
+> two gaps that one surfaced, [2026-09-17](docs/evals/2026-09-17.md) began scoring the
+> shape of the turn itself, and the latest ([2026-10-19](docs/evals/2026-10-19.md)) holds a
+> run to its stop card, 5/5.
 
 ## Documentation
 
 Each doc answers one question (in rough reading order for a new user):
 
 - *What does a session actually look like?* → [`docs/happy-path.md`](docs/happy-path.md): one goal walked end to end; read this first.
+- *How do I drive a plan with runs, and what do they replace?* → [`docs/runs.md`](docs/runs.md): ranges, the build order, and the stop card's harvest, walked through three runs and set beside the manual build, harvest, and order moves.
 - *What do the words mean?* → [`docs/glossary.md`](docs/glossary.md): every term the loop mints, one line each, with where to read more.
 - *Show me the artifacts it leaves behind.* → [`examples/`](examples/): that same session's finished build folder, file by file.
 - *Should I / can I / what about…?* → [`docs/faq.md`](docs/faq.md): the adoption questions, answered straight.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "plumbbob",
-  "version": "0.13.2",
+  "version": "0.13.3",
   "description": "Attention-first build process: 15 skills + a CLI that keep you the decider — guidance on the work, a latch on the record.",
   "keywords": [
     "claude-code",