@pmelab/gtd 7.4.0 → 7.4.1

package/README.md

@@ -196,7 +196,7 @@ Both halves are enforced by `gtd validate` and the `gtd step` gate.
 
 Herdr integration: a workflow state can declare an optional `label:` — a
 human-readable display name surfaced in `gtd next --json`/`gtd status`. The
-reference `bin/gtd-loop` driver uses it to report its lifecycle
+reference `bin/gtd` driver uses it to report its lifecycle
 (working/blocked/idle) to a [Herdr](https://herdr.dev) pane sidebar via the
 `herdr` CLI when running under Herdr (`HERDR_ENV=1`, a pane ID, and `herdr` on
 `$PATH`); outside Herdr this is a complete no-op. See

package/bin/gtd

@@ -67,20 +67,38 @@ fi
 # `--resume`/`--session-id`. An adapter that ignores them keeps working.
 herdr_ok() { [ "${HERDR_ENV:-}" = 1 ] && [ -n "${HERDR_PANE_ID:-}" ] && command -v herdr >/dev/null 2>&1; }
 
+# Run a `herdr` invocation best-effort. Normally output is discarded and a
+# failure is swallowed (`|| true`) so a missing/incompatible herdr never blocks
+# the loop. Set GTD_HERDR_DEBUG=1 to instead surface every call and its exit
+# code on stderr — the escape hatch that makes a silent CLI-signature mismatch
+# (e.g. an arg herdr rejects) visible again.
+herdr_run() {
+  if [ "${GTD_HERDR_DEBUG:-}" = 1 ]; then
+    printf 'gtd/herdr: %s\n' "$*" >&2
+    herdr "$@" >&2
+    printf 'gtd/herdr: exit=%s\n' "$?" >&2
+  else
+    herdr "$@" >/dev/null 2>&1 || true
+  fi
+}
+
+# NOTE: herdr requires the positional <PANE_ID> BEFORE the options for
+# `pane` subcommands — passing it last makes herdr reject the first option as
+# `unknown option` (exit 2). Keep the pane id first here.
 herdr_report() {  # $1=state (working|blocked|idle)  $2=message
   herdr_ok || return 0
-  herdr pane report-agent --source herdr:gtd --agent gtd \
-    --state "$1" --message "$2" "$HERDR_PANE_ID" >/dev/null 2>&1 || true
+  herdr_run pane report-agent "$HERDR_PANE_ID" \
+    --source herdr:gtd --agent gtd --state "$1" --message "$2"
 }
 
 herdr_notify() {  # $1=title  $2=body
   herdr_ok || return 0
-  herdr notification show "$1" --body "$2" --sound request >/dev/null 2>&1 || true
+  herdr_run notification show "$1" --body "$2" --sound request
 }
 
 herdr_release() {  # hand the pane back to Herdr's normal detection
   herdr_ok || return 0
-  herdr pane release-agent --source herdr:gtd --agent gtd "$HERDR_PANE_ID" >/dev/null 2>&1 || true
+  herdr_run pane release-agent "$HERDR_PANE_ID" --source herdr:gtd --agent gtd
 }
 
 trap 'code=$?; if [ "$code" -ne 0 ]; then

package/docs/loop.md

@@ -183,18 +183,21 @@ GTD_LOOP_AGENT_CMD='my-agent-cli --prompt "$GTD_LOOP_PROMPT"' gtd
 
 ## Herdr integration (optional)
 
-`bin/gtd-loop` optionally reports its lifecycle to [Herdr](https://herdr.dev) (a
+`bin/gtd` optionally reports its lifecycle to [Herdr](https://herdr.dev) (a
 terminal multiplexer for coding agents) via a `herdr` CLI binary, entirely at
 the driver's edge — gtd core never talks to Herdr. Every call is best-effort
 (guarded, output discarded, `|| true`), so a missing/failing `herdr` binary
-never blocks, slows, or fails the loop.
+never blocks, slows, or fails the loop. Because that guard also hides a herdr
+CLI-signature mismatch, set `GTD_HERDR_DEBUG=1` to surface every `herdr` call
+and its exit code on stderr instead.
 
 The reporting is a no-op unless all three guard conditions hold: `HERDR_ENV=1`,
-a non-empty `$HERDR_PANE_ID`, and `herdr` on `$PATH`. When they do, `gtd-loop`
-makes three kinds of calls:
+a non-empty `$HERDR_PANE_ID`, and `herdr` on `$PATH`. When they do, `gtd` makes
+three kinds of calls (note the positional `<PANE_ID>` comes BEFORE the options —
+herdr's `pane` subcommands reject a trailing pane id):
 
-- `herdr pane report-agent --source herdr:gtd --agent gtd --state <state> --message <label> "$HERDR_PANE_ID"`
-- `herdr pane release-agent --source herdr:gtd --agent gtd "$HERDR_PANE_ID"`
+- `herdr pane report-agent "$HERDR_PANE_ID" --source herdr:gtd --agent gtd --state <state> --message <label>`
+- `herdr pane release-agent "$HERDR_PANE_ID" --source herdr:gtd --agent gtd`
 - `herdr notification show <title> --body <label> --sound request`
 
 mapped onto the loop's states like this:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pmelab/gtd",
-  "version": "7.4.0",
+  "version": "7.4.1",
   "private": false,
   "description": "Git-aware CLI that emits the next prompt for an autonomous coding agent based on the current repository state",
   "bin": {