claude-code-autoconfig 1.0.192 → 1.0.193

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

@@ -11,6 +11,7 @@
 
   Tokens (substituted at runtime):
     {{TITLE_FILE}} — absolute path to this session's title file the model writes
+    {{ASK_FILE}}   — absolute path to this session's one-shot {sid}.ask flag (PENDING block)
     {{FOLDER}}     — the working-directory folder name (scope fallback)
     {{EMDASH}}     — the ' — ' segment separator
     {{CMD}}        — the slash-command name (COMMAND block only)
@@ -63,9 +64,14 @@ already exists, read it first then overwrite.
 <!-- /DIRECTIVE:SHIFT -->
 
 <!-- DIRECTIVE:PENDING -->
-Pending-question signal: if you END this turn by asking the user a question they must answer
-before you can proceed, phrase it so your FINAL line ends with a question mark ('?') -- the tab
-indicator then flips to the AWAITING half-circle automatically (instead of the idle asterisk).
+Pending-question signal: when you END this turn on a question the user must answer before you can
+proceed, do BOTH of these as near-final actions so the tab flips to the AWAITING half-circle
+(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.
 Make the closing question self-contained: answerable from the question alone, without re-reading
-the response above it. Only end on a '?' for a genuine blocking question, never a rhetorical one.
+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

@@ -2,7 +2,8 @@
 /**
  * Terminal Title — distributable plugin hook (installed to <project>/.claude/hooks/terminal-title.js).
  * ONE self-dispatching hook for five events (keyed on hook_event_name):
- *   UserPromptSubmit -> ⬤ working  + inject the title directive into the model's context
+ *   UserPromptSubmit -> ⬤ working  + inject the title directive (incl. the {sid}.ask path) +
+ *                       clear any stale {sid}.ask flag so it reflects only the turn about to run
  *   PostToolUse      -> ⬤ working  (refresh, so a mid-turn title flip shows live + clears a stale ◐)
  *   Notification     -> ◐ awaiting your approval (permission_prompt matcher only)
  *   Stop             -> ✻ idle / done — OR ◐ awaiting (+ a 2nd BEL = gold tab) when the turn ended
@@ -65,6 +66,10 @@ function handle(data) {
     // Ensure the state dir exists, but NOT the file — the model's Write tool refuses to overwrite a
     // file it hasn't read, so a pre-created empty file would make its first title write fail.
     try { fs.mkdirSync(dir, { recursive: true }); } catch (_) { /* ignore */ }
+    // Clear any stale {sid}.ask left by an interrupted prior turn (Stop never ran to consume it), so a
+    // leftover flag can't paint a false ◐ on this turn's end. The flag must reflect ONLY this turn.
+    const askFile = path.join(dir, `${sid}.ask`);
+    if (fileExists(askFile)) { try { fs.unlinkSync(askFile); } catch (_) { /* ignore */ } }
     const title = normalize(readTitle(file) || folderName(cwd));
     const out = setTitle(GLYPH.working, title);
     out.hookSpecificOutput = {
@@ -221,6 +226,7 @@ function buildDirective(data, file, cwd) {
   const combined = pending ? `${block}\n\n${pending}` : block;
   return combined
     .split('{{TITLE_FILE}}').join(file)
+    .split('{{ASK_FILE}}').join(file.replace(/\.txt$/, '.ask'))
     .split('{{FOLDER}}').join(folderName(cwd))
     .split('{{EMDASH}}').join(EMDASH)
     .split('{{CMD}}').join(cmd);

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## v1.0.193
+- fix(installer): always refresh cca-managed title hooks on upgrade
+- fix(terminal-title): arm the {sid}.ask flag so awaiting ◐ is race-free
+- docs(publish): document web-auth/passkey publish flow in Discoveries
+
 ## v1.0.192
 - fix(pkg): exclude runtime .titles/ from published tarball
 
@@ -142,6 +147,3 @@
 ## v1.0.144
 - feat: swagger-style docs, wider layout, better install UX
 
-## v1.0.143
-- feat: add /validate-cca-install command
-

package/CLAUDE.md

@@ -42,6 +42,18 @@ See `.claude/feedback/` for corrections and guidance from the team.
 ## Discoveries
 <!-- Claude: append project-specific learnings, gotchas, and context below. This section persists across /autoconfig runs. -->
 
+### Publishing to npm — web-auth (passkey) flow, run by the human
+
+`npm publish` for this package is a **two-actor** flow; a bare in-agent `npm publish` will FAIL. (Supersedes the auto-generated "## Publishing" one-liner above.)
+
+- The npm account has **2FA**. A sandboxed/agent shell can't open a browser, so `npm publish` there dies with `npm error code EOTP`. Don't retry it in-agent; don't default to asking for a typed OTP.
+- **Working flow:** the agent runs `npm test` + `npm version patch` (commit + tag), then the **human runs the publish in their own terminal** (needs a browser):
+  ```
+  cd C:\CODE\claude-code-autoconfig && npm login --auth-type=web && npm publish
+  ```
+  → browser opens → pick the Google passkey → close it → `+ claude-code-autoconfig@<version>`.
+- **After** the success line, the agent pushes: `git push origin main --follow-tags`. Never double-bump if the version is already bumped. Full procedure: `.claude/commands/publish.md`.
+
 ## Debugging Methodology — Evidence Before Solutions
 
 **NEVER jump to a fix based on assumptions.** When investigating a bug:

package/bin/cli.js

@@ -767,10 +767,21 @@ if (fs.existsSync(feedbackSrc)) {
   copyFn(feedbackSrc, path.join(claudeDest, 'feedback'));
 }
 
-// Copy hooks directory (preserve user customizations unless --force)
+// Copy hooks directory. Genuinely user-authorable hooks are preserved on upgrade
+// (copyDirIfMissing), BUT the cca-managed title-hook files are ALWAYS refreshed so bug-fixes
+// reach existing installs — without this, copyDirIfMissing leaves stale hooks in place forever
+// (same always-overwrite rationale as scripts/ below). --force already overwrites everything.
+const MANAGED_HOOKS = ['terminal-title.js', 'terminal-title.directive.md'];
 if (fs.existsSync(hooksSrc)) {
   const copyFn = forceMode ? copyDir : copyDirIfMissing;
   copyFn(hooksSrc, path.join(claudeDest, 'hooks'));
+  if (!forceMode) {
+    const hooksDestDir = path.join(claudeDest, 'hooks');
+    for (const name of MANAGED_HOOKS) {
+      const src = path.join(hooksSrc, name);
+      if (fs.existsSync(src)) fs.copyFileSync(src, path.join(hooksDestDir, name));
+    }
+  }
 }
 
 // Copy scripts directory (always overwrite — these are utility scripts, not user-customizable)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-autoconfig",
-  "version": "1.0.192",
+  "version": "1.0.193",
   "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",