@pmelab/gtd 62.1.0 → 64.0.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "gtd",
-  "version": "62.1.0",
+  "version": "64.0.0",
   "description": "Drive the gtd loop inside Claude Code: agent turns run as subagents, gtd decides every beat",
   "author": {
     "name": "Philipp Melab"

package/README.md

@@ -641,7 +641,9 @@ writing `gtd bundle`'s output to `.gtd/process.gtdpin`, and its last, once the
 flow has ended, an unpin beat removing it — the commit that closes the process.
 Both are ordinary `script` beats a driver runs unattended; see
 [Pin and unpin beats](https://github.com/pmelab/gtd/blob/main/docs/driver.md#pin-and-unpin-beats).
-Histories with pin commits are history format 2, which an older gtd refuses.
+Histories with pin commits are history format 2 or later, which an older gtd
+refuses. The beats rest at `gtd:pin` and `gtd:unpin`; a workflow step may not
+take a name starting with `gtd:`.
 
 While a process is pinned, the `gtd` on your `PATH` hands every command over to
 the pin, so editing the workflow or upgrading gtd mid-process changes nothing;
@@ -650,8 +652,11 @@ gtd notes on stderr when the live config differs from the pinned one. `ui`,
 always run live, and `gtd --live <command>` runs the live engine for any other,
 at the risk of misreading the process. To fix a workflow mid-process, edit it
 and run `gtd repin`: its script commits a fresh pin from the live engine and
-config, and the process continues on it. A pin in a format your gtd does not
-know is refused: upgrade gtd. See
+config, and the process continues on it. Where the edited workflow no longer
+replays the process, the repin continues from the divergence: the commits it
+cannot replay stay as files, and the process rests at the step the edited
+workflow reached (history format 3 or later). A pin in a format your gtd does
+not know is refused: upgrade gtd. See
 [Pinned processes](https://github.com/pmelab/gtd/blob/main/docs/cli.md#pinned-processes).
 
 ## License

package/dist/chunks/{flows-DENt0uWV.mjs → flows-B7ZRCe-B.mjs}

@@ -1,4 +1,4 @@
-import { t as __exportAll } from "./rolldown-runtime-8H4AJuhK.mjs";
+import { t as __exportAll } from "./rolldown-runtime-D7D4PA-g.mjs";
 //#region src/flows/runtime.ts
 /**
 * Bump only when the installed `FlowContext` object changes shape or semantics;

package/dist/chunks/{rolldown-runtime-8H4AJuhK.mjs → rolldown-runtime-D7D4PA-g.mjs}

@@ -1,4 +1,3 @@
-import "node:module";
 //#region \0rolldown/runtime.js
 var __defProp = Object.defineProperty;
 var __exportAll = (all, no_symbols) => {

package/dist/chunks/{steering-DF_BMadH.mjs → steering-DkA51qDa.mjs}

@@ -1,4 +1,4 @@
-import { t as __exportAll } from "./rolldown-runtime-8H4AJuhK.mjs";
+import { t as __exportAll } from "./rolldown-runtime-D7D4PA-g.mjs";
 //#region src/steering/SteeringFormat.ts
 /** `file:line:col: message` — the shape editors and grep already jump on. Stored 0-based, printed 1-based. A finding with a `line` but no `range`, or none at all, degrades to the shorter forms. */
 const formatFinding = (file, finding) => {