plumbbob 0.13.5 → 0.13.7

package/skills/run/SKILL.md

@@ -122,7 +122,7 @@ walk before it, since the checkpoint would refuse it. The halt list is the build
 red check, a self-review mismatch, a bound agent's `blocked` or `drift`, or a new decision
 ends at that step's pause card. `plumbbob build` names the top step as the top of the range
 you granted when it enters it. Once that step lands, its checkpoint prints the boundary
-with the Stop row (`| Stop | Range 3 of 5 landed - <its stop> |`); relay none of it, and end
+with the Stop row (`| Stop | **Range 3** landed - <its stop> |`); relay none of it, and end
 the run on the stop card, below, in the same turn.
 
 **A bare range.** `grant: none, as a bare range builds to its pause`: build the range's one
@@ -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
@@ -204,6 +207,15 @@ it, and record nothing in this turn: `plumbbob harvest` refuses in the turn the
 because the human has not read it yet. If the turn is held with a reason saying the stop card
 is still owed, do exactly what the reason says.
 
+*After a halt the human approved, the card comes short.* When the step that completed the
+range halted at its pause and `looks good` landed it, the human read that step's Summary,
+Readout, and recommendation a moment ago, so `plumbbob handoff --stop` prints only the
+Harvested table, the moves, the state table with its Stop row, and the link
+([D119 (short-stop-after-a-halt)](https://github.com/robmclarty/plumbbob/blob/main/docs/decisions.md#d119)).
+Write the range's detail file all the same, in full: the stop's record reads it, and
+`show the stop` prints the card whole from it. Paste the short card exactly as it printed;
+never add back the parts it left out.
+
 ## 6. The reply at a stop
 
 The card's proposals are settled in one reply
@@ -221,14 +233,18 @@ and the Your Call block names the replies. Read the human's message as one of th
 - **A change** (`make P7 a tangent`, or a change to the review) is direction, and the turn
   that makes it is your reply
   ([D110 (reply-after-the-card)](https://github.com/robmclarty/plumbbob/blob/main/docs/decisions.md#d110)).
-  Rewrite the detail file's line or section, say in your own words what moved, then run
-  `plumbbob handoff --stop` and paste the one-line reminder it prints beneath your reply.
+  Rewrite the detail file's line or section, run `plumbbob handoff --stop` last among your
+  tool calls and keep the one-line reminder it prints, then say in your own words what
+  moved and end the turn on that line, with no tool call after your reply
+  ([D121 (reply-after-the-tools)](https://github.com/robmclarty/plumbbob/blob/main/docs/decisions.md#d121)).
   The card does not come back for a change; nothing is recorded until `looks good`, which
   records every lean as the detail file then reads.
 - **A question**, or `expand 2`, is answered from the detail file, the range's commits, or
-  the Log, never from recall; then run `plumbbob handoff --stop` and paste the one-line
-  reminder it prints beneath your answer. Only `show the stop`, or any wording of it, takes
-  `plumbbob handoff --stop --full`, and never to read the card for yourself.
+  the Log, never from recall: read what you need and run `plumbbob handoff --stop` first,
+  then write the answer, and end the turn on the one-line reminder it printed, with no tool
+  call after the answer. Only `show the stop`, or any wording of it, takes
+  `plumbbob handoff --stop --full`, which prints the card whole after a short one too, and
+  never to read the card for yourself.
 - **`/plumbbob:run`** typed at the card confirms everything the way `looks good` does, and
   runs the next range. Record first: fold the blockers and run `plumbbob harvest`, then read
   `plumbbob status --run "<the same argument>"` again. When its grant line says

package/skills/status/SKILL.md

@@ -39,3 +39,10 @@ annotate it.
    the `next →` names the run to type, `/plumbbob:run` with the steps it will land beside
    it. You relay the block with the rest; a `⚠` row is `/plumbbob:refine`'s to fix.
 4. If it reads `NO ACTIVE SESSION`, tell the human to `/plumbbob:plan` to frame a goal.
+5. If the human asks what is still open, run `plumbbob status --questions` and relay its
+   output whole: a table row per question that waits on the human, linked to its entry in
+   `intent.md`, with why it matters and the lean, and a `Deferred` line beneath it naming
+   the questions left to the work and what settles each
+   ([D120 (deferred-questions)](https://github.com/robmclarty/plumbbob/blob/main/docs/decisions.md#d120)).
+   Never list the questions in your own words
+   ([D118 (questions-table)](https://github.com/robmclarty/plumbbob/blob/main/docs/decisions.md#d118)).

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
@@ -143,7 +146,7 @@ this skill verifies it the same way: **it reads the diff, not the author**
    one, the write-versus-relay line of
    [D78 (em-dash-ban)](https://github.com/robmclarty/plumbbob/blob/main/docs/decisions.md#d78).
 
-   *Then answer the reply in your own words.* The card shows once
+   *Then answer the reply in your own words, after every tool call.* The card shows once
    ([D110 (reply-after-the-card)](https://github.com/robmclarty/plumbbob/blob/main/docs/decisions.md#d110)):
    every later turn at this pause is your reply, closed by one line. A message that
    **asks** ("expand 2", "what does that mean?", "why did the seam row flag that?") is an
@@ -151,12 +154,17 @@ this skill verifies it the same way: **it reads the diff, not the author**
    `## Log` for an older step, never from recall. A message that **directs** is needs-work:
    make the change, run the check, and say what moved and what the check found; when the
    change moves what the card said, write the detail file again so the record matches what
-   lands. Nothing lands until the human says `looks good`. Either way, then run
-   `plumbbob handoff <n>` and paste its output beneath your reply, whole and verbatim: at a
-   pause whose card has shown it prints one line,
-   `**Next Up**: Back to Step <N> of <M> - <title>`, whatever changed since, so your reply
-   stays on screen. The turn is your reply, then that line, and nothing after it. The CLI
-   picks the form, never you: paste whichever one it prints, and never retype the card.
+   lands. Nothing lands until the human says `looks good`. Either way, every tool call
+   comes before your reply and none after it
+   ([D121 (reply-after-the-tools)](https://github.com/robmclarty/plumbbob/blob/main/docs/decisions.md#d121)):
+   read, edit, run the check, write the detail file, and run `plumbbob handoff <n>` last
+   among them. At a pause whose card has shown it prints one line,
+   `**Next Up**: Back to **Step N** on <Model> - <title>`, whatever changed since. Keep
+   that line, then write your reply, and end the turn on the line, whole and verbatim. The
+   turn is your tool calls, then your reply, then that line, and nothing after it: a
+   client that folds text written before a tool call (Zed, through the agent bridge) shows
+   the line and hides a reply written above the call. The CLI picks the form, never you:
+   paste whichever one it prints, and never retype the card.
 
    The card comes back one way: the human asks to see it (`show the pause`, or any wording
    of it). Then run `plumbbob handoff <n> --full` and paste its output whole, with nothing

package/templates/intent.md

@@ -129,7 +129,9 @@ Three lines:
   · *lean:* the model's proposed resolution: one answer to react to, not a menu
 
 The human reads *plain* to understand, then *lean* to approve or redirect: one
-pass, no round-trip.
+pass, no round-trip. The plan card tables the open questions a row each, and a cell
+shows only the first sentence of its line, so open the question, *plain*, and *lean*
+each on a sentence that stands alone: the question, why it matters, the answer.
 
 When a question resolves, swap *resolve by:* for *resolved:* <date, the call> ON THE
 OPENER LINE, e.g.
@@ -146,6 +148,17 @@ build reports zero open questions
 ([D77 (placeholder-uncounted)](https://github.com/robmclarty/plumbbob/blob/main/docs/decisions.md#d77));
 fill it in and it counts.
 
+When the human would rather let the work answer a question, it is deferred, not
+resolved: keep the question and swap *resolve by:* for *deferred:* <date>, until
+<what settles it> ON THE OPENER LINE, so the opener reads
+
+  **Q4 (latency-budget)**: What latency budget do we hold?, *deferred:* 2026-10-31, until step 4's latency numbers
+
+It stays open and still counts, but the card lists it on a line beneath the table
+rather than in it, so `yes to all leans` leaves it alone. Once the work answers it,
+swap the marker for *resolved:* as above
+([D120 (deferred-questions)](https://github.com/robmclarty/plumbbob/blob/main/docs/decisions.md#d120)).
+
 Size to the work: a tiny build's single, obvious question may stay one bare line;
 the *plain:*/*lean:* pair earns its keep only when a human decision genuinely waits
 on it.