@indigoai-us/hq-cli 5.103.9 → 5.103.10

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 ## [Unreleased]
 
+## [5.103.10] — 2026-08-20
+
+### Fixed
+
+- The checkpoint stop-gate's already-replied branch no longer leaves a dangling
+  filler line under the reply. "Add no further text" was being satisfied with a
+  meta-note (`(reply already delivered above - turn complete)`) instead of
+  silence, which is the same visible-noise defect as repeating the reply. Both
+  the gate reason and the `hq core checkpoint` reminder now rule out the
+  sign-off / acknowledgement / meta-comment class by name and state that
+  emitting nothing is the correct finished state.
+
 ## [5.103.9] — 2026-08-20
 
 ### Fixed

package/assets/scaffold/core/scripts/checkpoint-stop-gate.sh

@@ -390,7 +390,7 @@ set -uo pipefail
   # which case we are in, so say exactly one thing.
   flags_spec='  hq core checkpoint --session-id %s --trigger stop-gate --summary "<what changed, in one line>" [--file <path>] [--decision "<choice and why>"] [--learning "<reusable rule>"] [--next "<outstanding step>"]\n\nOnly --summary is required, and the repeatable flags are what the sibling uses to enrich the record, distil policies and update the indexes — a bare summary gives it almost nothing to work with. Write them as machine record, not prose for the user, and pass each one that genuinely applies:\n  --file      every path you created or modified this turn\n  --decision  a choice you made that a reader would otherwise have to reverse-engineer\n  --learning  a rule that changes how someone acts next time, not a restatement of what just happened\n  --next      work that is genuinely still outstanding\nOmit a flag rather than padding it: an empty or invented learning is worse than none.\n\nIf this turn only read or inspected things and changed no state, the correct call instead is:\n\n  hq core checkpoint --session-id %s --idle'
   if [ "$replied" = 1 ]; then
-    reason="$(printf 'This turn changed something, so it needs an end-of-turn checkpoint before it can end.\n\nYour user-facing reply is ALREADY delivered — the message you just wrote is visible to the user. Do NOT send it again, in full or summarized: repeating it double-messages the user, which is exactly the bug this gate guards against.\n\nTHE SIBLING (a background maintenance agent) reads only the checkpoint payload, never your chat reply — anything it needs must go into the flags.\n\nRun the checkpoint now as the FINAL action of the turn and end the turn immediately after it, adding no further text:\n\n'"$flags_spec" "$session_id" "$session_id")"
+    reason="$(printf 'This turn changed something, so it needs an end-of-turn checkpoint before it can end.\n\nYour user-facing reply is ALREADY delivered — the message you just wrote is visible to the user. Do NOT send it again, in full or summarized: repeating it double-messages the user, which is exactly the bug this gate guards against.\n\nTHE SIBLING (a background maintenance agent) reads only the checkpoint payload, never your chat reply — anything it needs must go into the flags.\n\nRun the checkpoint now as the FINAL action of the turn, then STOP - emit zero characters after the command. Ending a turn on a tool call with no trailing text is correct and expected here: it renders as the reply you already wrote followed by a collapsed checkpoint row. Do NOT append a sign-off, an acknowledgement, a status line, or any meta-note about the checkpoint itself - a dangling line such as "(reply already delivered above - turn complete)" is visible noise stuck under your reply, the same defect as repeating the reply. Silence is the finished state:\n\n'"$flags_spec" "$session_id" "$session_id")"
   else
     reason="$(printf 'This turn changed something, so it needs an end-of-turn checkpoint. Two different audiences are involved — do not conflate them:\n\n1. THE USER reads your normal chat reply. You have not sent one yet this turn — everything you owe them (results, links, answers, status, decisions) must go into it. The checkpoint is invisible to them and does NOT count as having replied.\n2. THE SIBLING (a background maintenance agent) reads the checkpoint payload. It never sees your chat reply, so anything it needs must go into the flags.\n\nORDER: run the checkpoint FIRST, then deliver your complete user-facing reply as the FINAL text of the turn — final-position text is the one placement every host renders in full. Every link, URL, instruction, command, and decision the user needs must appear in that final message.\n\n'"$flags_spec" "$session_id" "$session_id")"
   fi

package/dist/commands/core-checkpoint.js

@@ -60,8 +60,11 @@ export const CHECKPOINT_REPLY_REMINDER = "checkpoint: REMINDER — this checkpoi
     "and it does NOT count as your reply. If this turn's substance (results, findings, " +
     "decisions, state changes, anything awaiting their input) has NOT yet been delivered to " +
     "the user, write your user-facing reply now as the FINAL text of the turn. If you " +
-    "already delivered it earlier this turn, end the turn now WITHOUT repeating it — the " +
-    "user has already seen that message, and repeating it double-messages them.";
+    "already delivered it earlier this turn, end the turn now WITHOUT repeating it and " +
+    "WITHOUT any closing note — no sign-off, no acknowledgement, no meta-comment about " +
+    "this checkpoint. The user has already seen that message; both repeating it and " +
+    "appending a dangling note leave visible noise under it. Emitting no further text at " +
+    "all is the correct, finished state.";
 function printResult(line) {
     process.stdout.write(`${line}\n`);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@indigoai-us/hq-cli",
-  "version": "5.103.9",
+  "version": "5.103.10",
   "description": "HQ by Indigo management CLI — modules and cloud sync",
   "main": "dist/index.js",
   "bin": {