claude-code-autoconfig 1.0.194 → 1.0.195

package/.claude/hooks/terminal-title.directive.md

@@ -69,9 +69,14 @@ proceed, do BOTH of these as near-final actions so the tab flips to the AWAITING
 (instead of the idle asterisk):
   1. Write the flag file {{ASK_FILE}} (any short content, e.g. "1"). This is the RELIABLE trigger --
      it is on disk before the turn ends, so it never misses (the transcript-text check in 2 can race
-     the turn-end write and silently miss). The flag is one-shot: it is consumed at turn end and
-     auto-cleared next turn, so write it ONLY on a turn you are genuinely blocked on an answer.
-  2. Phrase your FINAL line so it ends with a question mark ('?') -- a backup signal, and good UX.
+     the turn-end write and silently miss, or miss on phrasing -- see below). The flag is one-shot: it
+     is consumed at turn end and auto-cleared next turn, so write it ONLY on a turn you are genuinely
+     blocked on an answer. Write it WHENEVER the turn genuinely needs the user's answer to proceed --
+     the flag doesn't parse your text, so it is correct even when your closing question is wrapped in
+     parens, phrased as a parenthetical aside, or is not the literal final character of the message.
+  2. Phrase your FINAL line so it ends with a question mark ('?') -- a backup signal, and good UX. A
+     single trailing parenthetical aside after the '?' is fine ("...option A or B? (I lean B.)"), but
+     do not rely on phrasing for the signal -- the flag in step 1 is what reliably flips the tab.
 Make the closing question self-contained: answerable from the question alone, without re-reading
 the response above it. Only do this for a genuine blocking question, never a rhetorical one or a recap.
 <!-- /DIRECTIVE:PENDING -->

package/.claude/hooks/terminal-title.js

@@ -177,7 +177,8 @@ function fileExists(file) {
 
 // Stop heuristic: did the turn end on a question? Read the JSONL transcript, find the most-recent
 // assistant message with VISIBLE text (skip pure tool_use turns so a final title/memory Write doesn't
-// mask the question), test whether it ends in '?' (allowing trailing whitespace / ) * _ "). Returns a
+// mask the question), test whether it ends in '?' (allowing trailing whitespace / ) * _ ", plus one
+// trailing parenthetical aside — see the endsOnQuestion regex below). Returns a
 // diagnostic record { ends, found, tail }: `ends` is the old boolean the caller branches on; `found`
 // and `tail` feed the debug log so a missing half-circle can be told apart — a transcript-flush race
 // shows found=0 (or a stale tail), a genuine regex miss shows a tail that's present but doesn't end
@@ -216,7 +217,15 @@ function inspectLastResponse(transcriptPath) {
     if (text.trim()) {
       // last ~60 chars, collapsed to one line and quote-stripped so it can't break the log framing
       const tail = text.trim().slice(-60).replace(/\s+/g, ' ').replace(/"/g, "'");
-      return { ends: /\?[\s)*_"]*$/.test(text), found: true, tail, suspectRace: sawTextlessAssistant };
+      // Ends on a question? A '?' at the end, tolerating trailing whitespace / ) * _ " — AND an optional
+      // SINGLE trailing parenthetical aside after it ("How should we handle it? (I lean option 2.)"), a
+      // common shape: ask, then a bracketed recommendation/clarifier. The aside is one level only
+      // (`[^()]`, no nesting) and must sit at the very end, so a mid-message rhetorical '?' or a plain
+      // statement ending in ')' still won't match — only a genuine closing question does. Belt to the
+      // {sid}.ask flag's suspenders: the flag is the primary, parse-free path; this only hardens the
+      // fallback for turns that ended on a parenthetical question without writing one.
+      const endsOnQuestion = /\?[\s)*_"]*(\([^()]*\)[\s.*_"]*)?$/.test(text);
+      return { ends: endsOnQuestion, found: true, tail, suspectRace: sawTextlessAssistant };
     }
     // assistant message with no visible text = a thinking-only or tool_use-only block sitting AFTER the
     // last text we'll grade — a strong hint the final text line hasn't flushed yet.

package/CHANGELOG.md

@@ -1,5 +1,8 @@
 # Changelog
 
+## v1.0.195
+- fix(terminal-title): flip awaiting ◐ for a closing question with a trailing parenthetical aside
+
 ## v1.0.194
 - fix(terminal-title): guard the Stop question-grade against the transcript-flush race
 
@@ -144,9 +147,3 @@
 ## v1.0.146
 - style: improve inside-Claude block message formatting
 
-## v1.0.145
-- fix: block npx install from inside Claude Code session
-
-## v1.0.144
-- feat: swagger-style docs, wider layout, better install UX
-

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-autoconfig",
-  "version": "1.0.194",
+  "version": "1.0.195",
   "description": "Intelligent, self-configuring setup for Claude Code. One command analyzes your project, configures Claude, and shows you what it did.",
   "author": "ADAC 1001 <info@adac1001.com>",
   "license": "MIT",