plumbbob 0.13.5 → 0.13.6

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "plumbbob",
   "displayName": "PlumbBob",
-  "version": "0.13.5",
+  "version": "0.13.6",
   "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/dist/lib/orient.js

@@ -2029,13 +2029,64 @@ function sectionProse(detail, heading) {
     if (text.length === 0) {
         return null;
     }
-    return text
-        .split(/\n{2,}/)
-        .map((paragraph) => paragraph
-        .split('\n')
-        .map((l) => l.trim())
-        .join(' '))
-        .join('\n\n');
+    return proseBlocks(text).join('\n\n');
+}
+/**
+ * Prose's blocks, in order: each paragraph unwrapped onto one line, and each
+ * fenced block kept line for line with its fences trimmed flush.
+ *
+ * A command the human is meant to copy rides a fence of its own
+ * (D114 (command-fences)), and joining its lines would run two commands into
+ * one. A fence opened straight under a sentence still ends that paragraph, so
+ * it always stands between blank lines and renders as a block, never as
+ * backticks inside the sentence. A fence left unclosed keeps everything after
+ * it and is closed here, so it cannot swallow the `more details` link the
+ * card prints beneath it.
+ */
+function proseBlocks(text) {
+    const blocks = [];
+    let paragraph = [];
+    let fence = null;
+    let fenced = [];
+    for (const line of text.split('\n')) {
+        if (fence !== null) {
+            const closed = closesFence(line, fence);
+            fenced.push(closed ? line.trim() : line.trimEnd());
+            if (closed) {
+                blocks.push(fenced.join('\n'));
+                fence = null;
+            }
+            continue;
+        }
+        const opened = fenceOpening(line);
+        if (opened !== null || line.trim() === '') {
+            if (paragraph.length > 0)
+                blocks.push(paragraph.join(' '));
+            paragraph = [];
+        }
+        if (opened !== null) {
+            fence = opened;
+            fenced = [line.trim()];
+        }
+        else if (line.trim() !== '') {
+            paragraph.push(line.trim());
+        }
+    }
+    if (fence !== null)
+        blocks.push([...fenced, fence.char.repeat(fence.length)].join('\n'));
+    if (paragraph.length > 0)
+        blocks.push(paragraph.join(' '));
+    return blocks;
+}
+/** The fence a line opens: three or more backticks or tildes, indented three spaces at most. Null when it opens none. */
+function fenceOpening(line) {
+    const marker = /^ {0,3}(`{3,}|~{3,})/.exec(line)?.[1];
+    return marker === undefined ? null : { char: marker.charAt(0), length: marker.length };
+}
+/** Whether a line closes an open fence: the same character, at least as many of it, and nothing after. */
+function closesFence(line, fence) {
+    const marker = /^ {0,3}(`{3,}|~{3,})\s*$/.exec(line)?.[1];
+    return marker !== undefined && marker.startsWith(fence.char) && marker.length >= fence.length;
 }
 /**
  * The `## Summary` section of `.plumbbob/detail.md` and the numbered detail
@@ -2079,8 +2130,7 @@ export function normalizeDetailHeadings(detail) {
     let afterHeading = false;
     for (const line of detail.split('\n')) {
         if (fence !== null) {
-            const close = /^ {0,3}(`{3,}|~{3,})\s*$/.exec(line)?.[1];
-            if (close !== undefined && close.startsWith(fence.char) && close.length >= fence.length) {
+            if (closesFence(line, fence)) {
                 fence = null;
             }
             out.push(line);
@@ -2091,10 +2141,7 @@ export function normalizeDetailHeadings(detail) {
         if ((heading || afterHeading) && line.trim() !== '' && prior !== undefined && prior.trim() !== '') {
             out.push('');
         }
-        const open = /^ {0,3}(`{3,}|~{3,})/.exec(line)?.[1];
-        if (open !== undefined) {
-            fence = { char: open.charAt(0), length: open.length };
-        }
+        fence = fenceOpening(line);
         out.push(line);
         afterHeading = heading;
     }
@@ -2132,8 +2179,9 @@ export function parseSections(detail) {
 }
 /**
  * The `## Recommendation` section of `.plumbbob/detail.md`: the one or two
- * plain sentences a decision turn ends on, or null when the model wrote none.
- * `handoff` emits it after the card, unfenced; the eye lands on the last text,
+ * plain sentences a decision turn ends on, each shell command they name in a
+ * `sh` fence of its own, or null when the model wrote none. `handoff` emits it
+ * after the card, the prose itself unfenced; the eye lands on the last text,
  * and the last text should say which move the model would take.
  */
 export function parseRecommendation(detail) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "plumbbob",
-  "version": "0.13.5",
+  "version": "0.13.6",
   "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",

package/skills/build/SKILL.md

@@ -181,7 +181,10 @@ switch with `/model` and rerun to honor it, or wave you on. Advisory, never a ga
    sentence, closed by a period, then the reason as a capitalized sentence or two. The lead
    and the recommendation are flowing prose and handoff unwraps both to the renderer's
    width, so never hard-wrap them; handoff also prepends the bold `**Recommendation**:`
-   label, which you never type. `checkpoint` records this file beneath the step's dated
+   label, which you never type. A shell command you want the human to run never rides
+   inside a sentence: end the sentence on a colon and give the command a fenced `sh` block
+   of its own, one command to a line, which handoff keeps line for line. A slash command
+   or a path stays in backticks in the sentence. `checkpoint` records this file beneath the step's dated
    line in the build-log's `## Log` and then truncates it, so the detail lands in the
    tracked ledger rather than piling up on disk.
 

package/skills/plan/SKILL.md

@@ -283,7 +283,10 @@ read checked and found sound. A plan with a hole gets `Sharpen <the one worst ho
 and why it matters; when the read found more than one, say how many sit behind `expand`
 and name `/plumbbob:refine` as the move that writes them up as Open questions, with their
 plain and lean sub-lines, for the human to settle. Three findings at most; the rest is
-refine's. `plumbbob handoff --plan` prints the label and your recommendation beneath the
+refine's. A shell command you want the human to run never rides inside a sentence: end the
+sentence on a colon and give the command a fenced `sh` block of its own, one command to a
+line, which handoff keeps line for line; `/plumbbob:refine` stays in backticks in the
+sentence. `plumbbob handoff --plan` prints the label and your recommendation beneath the
 state table, then the `more details` link to the file, "expand 2" opens `## 2`, and `checkpoint --plan` records the read beneath the
 plan's line in the build-log's `## Log`, the build's first entry. The cold read is the tip of refine: it makes the
 full attack discoverable at the moment it would pay, and lets a sound plan skip it. Refine

package/skills/run/SKILL.md

@@ -196,7 +196,10 @@ A park you leave out reads `no lean proposed` on the card and stays open, and a
 reads `not given`. The section vanishes when no park is open, and so does the card's Harvested part
 ([D100 (stop-card)](https://github.com/robmclarty/plumbbob/blob/main/docs/decisions.md#d100)).
 The recommendation speaks to the plan's stop, the header's `stop:` line, and to the
-proposals: the move you would take on both, then why.
+proposals: the move you would take on both, then why. A shell command you want the human to
+run never rides inside a sentence: end the sentence on a colon and give the command a fenced
+`sh` block of its own, one command to a line, which handoff keeps line for line. A slash
+command or a path stays in backticks in the sentence.
 
 *Render it and stop.* Run `plumbbob handoff --stop` and paste its output whole, verbatim, at
 top level, trailing blank line included, then end the turn. Write nothing before it or after

package/skills/verify/SKILL.md

@@ -114,7 +114,10 @@ this skill verifies it the same way: **it reads the diff, not the author**
    sentence, closed by a period, then the reason as a capitalized sentence or two. The lead
    and the recommendation are flowing prose and handoff unwraps both to the renderer's
    width, so never hard-wrap them; handoff also prepends the bold `**Recommendation**:`
-   label, which you never type. This is the **one** file `/plumbbob:verify` writes, and it
+   label, which you never type. A shell command you want the human to run never rides
+   inside a sentence: end the sentence on a colon and give the command a fenced `sh` block
+   of its own, one command to a line, which handoff keeps line for line. A slash command
+   or a path stays in backticks in the sentence. This is the **one** file `/plumbbob:verify` writes, and it
    is turn presentation, never the diff under review; the author-blind contract below still
    holds. `checkpoint` records this file beneath the step's dated line in the build-log's
    `## Log` and then truncates it (the detail plane in the