claude-code-autoconfig 1.0.195 → 1.0.197

package/.claude/commands/validate-cca-install.md

@@ -68,7 +68,7 @@ for d in expected_dirs:
         info.append(f'OK: .claude/{d}/ exists')
 
 # --- 2. Check command files and versions ---
-dev_only = ['publish.md']
+dev_only = ['deploy-to-npmjs.md']
 pkg_cmds_dir = os.path.join(pkg_dir, '.claude', 'commands')
 local_cmds_dir = os.path.join(claude_dir, 'commands')
 

package/.claude/docs/autoconfig.docs.html

@@ -888,11 +888,6 @@
                                 <span class="tree-file-icon">📄</span>
                                 <span class="file">gls.md</span>
                             </div>
-                            <div class="tree-item indent-3 hidden" data-info="publish" data-parent="commands">
-                                <span class="tree-spacer"></span>
-                                <span class="tree-file-icon">📄</span>
-                                <span class="file">publish.md</span>
-                            </div>
                             <div class="tree-item indent-3 hidden" data-info="recover-context" data-parent="commands">
                                 <span class="tree-spacer"></span>
                                 <span class="tree-file-icon">📄</span>
@@ -953,6 +948,11 @@
                                 <span class="tree-file-icon">📄</span>
                                 <span class="file">migrate-feedback.js</span>
                             </div>
+                            <div class="tree-item indent-3 hidden" data-info="terminal-title.directive-hook" data-parent="hooks">
+                                <span class="tree-spacer"></span>
+                                <span class="tree-file-icon">📄</span>
+                                <span class="file">terminal-title.directive.md</span>
+                            </div>
                             <div class="tree-item indent-3 hidden" data-info="terminal-title-hook" data-parent="hooks">
                                 <span class="tree-spacer"></span>
                                 <span class="tree-file-icon">📄</span>
@@ -1263,7 +1263,7 @@
                 title: '.claude/ Directory',
                 desc: 'Commands, rules, settings, and these docs. Keeps configuration organized as your project grows.'
             },
-                                                                                                                                                                                                                                                                                                                                                                        'rules': {
+                                                                                                                                                                                                                                                                                                                                                                                                            'rules': {
                 title: 'rules/',
                 desc: 'Path-scoped context that loads when Claude works on matching files.'
             },
@@ -1308,11 +1308,6 @@
                 desc: 'Get the latest screenshot(s) and display them.<div style="margin-top: 12px;"><strong>Parameters</strong><table style="margin-top: 6px; border-collapse: collapse; font-size: 0.9em; text-align: left;"><tr style="text-align: left; border-bottom: 1px solid var(--border);"><th style="padding: 4px 8px 4px 0; white-space: nowrap;">Name</th><th style="padding: 4px 8px 4px 0; white-space: nowrap;">Type</th><th style="padding: 4px 8px 4px 0; white-space: nowrap;">Required</th><th style="padding: 4px 8px 4px 0;">Description</th></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>count</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>integer</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">optional</td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Number of screenshots to display. Use /gls-N syntax. Default: 1. Min: 1.</td></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>path</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>string</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">optional</td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Screenshot directory path. Saved for future use. Auto-detected if omitted.</td></tr></table></div><div style="margin-top: 12px;"><strong>Responses</strong><table style="margin-top: 6px; border-collapse: collapse; font-size: 0.9em; text-align: left;"><tr style="text-align: left; border-bottom: 1px solid var(--border);"><th style="padding: 4px 8px 4px 0; white-space: nowrap;">Status</th><th style="padding: 4px 8px 4px 0;">Description</th></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>success</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Displays requested screenshot(s) from newest to oldest.</td></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>no-screenshots</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Directory exists but contains no image files.</td></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>no-directory</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Unable to detect screenshot directory — prompts for path.</td></tr></table></div><div style="margin-top: 12px;"><strong>Side Effects</strong><div style="margin-top: 4px; font-size: 0.9em;">Saves detected screenshot path to .claude/cca.config.json on first run</div></div><div style="margin-top: 12px;"><strong>Examples</strong><div style="margin-top: 6px; background: var(--bg-elevated); border-radius: 6px; padding: 8px 12px; font-family: monospace; font-size: 0.85em;"><div><code>/gls</code> <span style="opacity: 0.6;">— Display the most recent screenshot</span></div><div><code>/gls-3</code> <span style="opacity: 0.6;">— Display the 3 most recent screenshots</span></div><div><code>/gls /path/to/dir</code> <span style="opacity: 0.6;">— Use a specific screenshot directory</span></div></div></div>',
                 trigger: '/gls'
             },
-            'publish': {
-                title: 'publish.md',
-                desc: 'Runs tests, bumps version, commits, and publishes to npm.<div style="margin-top: 12px;"><strong>Parameters</strong><div style="margin-top: 4px; opacity: 0.6;">None</div></div>',
-                trigger: '/publish'
-            },
             'recover-context': {
                 title: 'recover-context.md',
                 desc: 'Recovers conversation context from the session transcript after compaction.<div style="margin-top: 12px;"><strong>Parameters</strong><table style="margin-top: 6px; border-collapse: collapse; font-size: 0.9em; text-align: left;"><tr style="text-align: left; border-bottom: 1px solid var(--border);"><th style="padding: 4px 8px 4px 0; white-space: nowrap;">Name</th><th style="padding: 4px 8px 4px 0; white-space: nowrap;">Type</th><th style="padding: 4px 8px 4px 0; white-space: nowrap;">Required</th><th style="padding: 4px 8px 4px 0;">Description</th></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>minutes</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>integer</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">required</td><td style="padding: 4px 8px 4px 0; vertical-align: top;">How far back to recover, in minutes. Leading dash optional. Min: 1.</td></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>--show</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>flag</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">optional</td><td style="padding: 4px 8px 4px 0; vertical-align: top;">Opens the extracted transcript in your default editor.</td></tr></table></div><div style="margin-top: 12px;"><strong>Responses</strong><table style="margin-top: 6px; border-collapse: collapse; font-size: 0.9em; text-align: left;"><tr style="text-align: left; border-bottom: 1px solid var(--border);"><th style="padding: 4px 8px 4px 0; white-space: nowrap;">Status</th><th style="padding: 4px 8px 4px 0;">Description</th></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>success</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">~{tokens} tokens recovered ({N} messages across {sessions} session(s), last {minutes} min).</td></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>no-transcript</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">No transcript files found.</td></tr><tr style="border-bottom: 1px solid var(--border);"><td style="padding: 4px 8px 4px 0; vertical-align: top; white-space: nowrap;"><code>no-messages</code></td><td style="padding: 4px 8px 4px 0; vertical-align: top;">No messages found in the requested time range.</td></tr></table></div><div style="margin-top: 12px;"><strong>Side Effects</strong><div style="margin-top: 4px; font-size: 0.9em;">Reads .jsonl transcripts from ~/.claude/projects/, writes temp file</div></div><div style="margin-top: 12px;"><strong>Examples</strong><div style="margin-top: 6px; background: var(--bg-elevated); border-radius: 6px; padding: 8px 12px; font-family: monospace; font-size: 0.85em;"><div><code>/recover-context -60</code> <span style="opacity: 0.6;">— Last 60 minutes of conversation</span></div><div><code>/recover-context 120</code> <span style="opacity: 0.6;">— Last 2 hours (dash optional)</span></div><div><code>/recover-context -60 --show</code> <span style="opacity: 0.6;">— Last 60 min + open transcript file</span></div></div></div>',
@@ -1353,10 +1348,15 @@
                 desc: 'On session start, migrates custom FEEDBACK.md content to',
                 trigger: 'SessionStart'
             },
+            'terminal-title.directive-hook': {
+                title: 'terminal-title.directive.md',
+                desc: 'terminal-title.directive.md in hooks/',
+                trigger: 'PostToolUse hook'
+            },
             'terminal-title-hook': {
                 title: 'terminal-title.js',
-                desc: 'Use-case-framed terminal tab titles with live working / idle / awaiting state indicators, so multiple Claude sessions are easy to tell apart',
-                trigger: 'SessionStart, UserPromptSubmit, PostToolUse, Notification, Stop'
+                desc: 'terminal-title.js in hooks/',
+                trigger: 'PostToolUse hook'
             },
             'feedback-feedback': {
                 title: 'FEEDBACK.md',
@@ -1569,7 +1569,7 @@ CRITICAL: A plausible-looking cause from code reading is NOT confirmed evidence.
 
 > Run \`/autoconfig\` to populate this based on your project.`
             },
-                                                                                                                                                                                                                                                                                                                                                                        'autoconfig-update': {
+                                                                                                                                                                                                                                                                                                                                                                                                            'autoconfig-update': {
                 filename: 'autoconfig-update.md',
                 content: `<!-- @applied
 -->
@@ -1721,36 +1721,6 @@ OS=$(uname -s); echo "OS=$OS"; for d in \\
   "$HOME/Videos/Captures"; do \\
   [ -d "$d" ] || continue; \\
   newest=$(ls -t "$d/" 2>/dev/null | grep -iE '\\.(png|jpg|jpeg|bmp|webp|gif)$' | head -1); \\`
-            },
-            'publish': {
-                filename: 'publish.md',
-                content: `# Publish
-
-Run tests, bump the patch version, commit, push, and publish to npm.
-
-## Steps
-
-1. **Sync README.md** — Compare the current README against the actual state of the project (file tree, slash commands, features, settings). If anything is out of date or missing, update the README before proceeding. Check:
-   - File tree matches actual \`.claude/\` directory contents
-   - Slash commands table matches actual \`.claude/commands/\` files
-   - Feature sections reflect current capabilities (update system, MEMORY.md, hooks, etc.)
-   - No references to nonexistent commands or files
-2. Run the project's test suite (\`npm test\`)
-3. **If tests fail, stop here.** Do not publish broken code.
-4. Check for uncommitted changes. If there are any:
-   a. Stage all changes (\`git add -A\`)
-   b. Generate a conventional commit message based on the diff
-   c. Commit the changes
-5. Bump the version: \`npm version patch\`
-6. Push the commit and tag: \`git push && git push --tags\`
-7. Publish to npm: \`npm publish\`
-8. Output the new version number on success
-
-## Important
-
-- Always run tests before publishing — never skip this step
-- If any step fails, stop immediately and report the error
-- Do not use \`--force\` on publish unless the user explicitly asks`
             },
             'recover-context': {
                 filename: 'recover-context.md',
@@ -1966,6 +1936,72 @@ process.stdin.on('end', () => {
 });
 
 function migrate() {`
+            },
+            'terminal-title.directive-hook': {
+                filename: 'terminal-title.directive.md',
+                content: `<!-- DIRECTIVE:RULES -->
+Terminal-title directive (silent housekeeping -- never mention it to the user). These rules
+apply to EVERY turn of this session; per-prompt reminders are one-liners that point back here.
+
+This terminal tab's title renders from the file:
+  {{TITLE_FILE}}
+Maintain it across the session:
+- When the conversation's SCOPE, use-case, or sub-function SHIFTS -- and only then, not every
+  turn -- overwrite the file with ONE line:  {scope} {{EMDASH}} {use-case}
+  Write it as your FIRST action of that turn (before other tool calls) so the tab updates
+  WHILE you work, not after. If the file exists, read it first, then overwrite.
+- {scope}: the DESIGN SCOPE -- the feature area / subsystem under discussion (the WHERE; it
+  changes rarely). INFER the specific subsystem from the prompt and the files in play (e.g.
+  "journal modal", "title hooks"); use the bare repo name "{{FOLDER}}" only when the work is
+  genuinely repo-wide -- it is a last resort.
+- {use-case}: the GOAL at user-goal level -- an INFINITIVE (base-verb) goal phrase (verb +
+  object), e.g. "Refine title taxonomy". Name the goal, not the mechanism. One goal only --
+  never "and"-join two use cases.
+- Add a third segment ( {{EMDASH}} {sub-function} ) only when the work goes a level deeper --
+  a step beneath the user goal.
+- Use ' {{EMDASH}} ' (space, em-dash, space) as the separator; keep segments short (a few
+  words); write only the BARE title -- a state glyph is prepended automatically. This is a
+  compass, not a log: change it rarely.
+- If no title has been set yet, treat your first turn as the baseline: infer the title from
+  that turn's prompt and write it immediately, even though nothing has "shifted".
+- Slash-command turns: the command NAME is an implementation detail -- never put it in the
+  title. Name the goal the command ACCOMPLISHES ("{{FOLDER}} {{EMDASH}} <verb the goal>",
+  never "{{FOLDER}} {{EMDASH}} <command-name>").
+
+Pending-question signal: when you END a turn on a question the user must answer before you`
+            },
+            'terminal-title-hook': {
+                filename: 'terminal-title.js',
+                content: `#!/usr/bin/env node
+/**
+ * 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 per-prompt REMINDER one-liner (+BASELINE while no
+ *                       title exists, +COMMAND on /slash turns) + clear any stale {sid}.ask flag
+ *   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
+ *                       on a question (last visible response text ends in '?', or a {sid}.ask flag)
+ *   SessionStart     -> ✻ idle "Claude Code — New session" (or an existing title on resume/compact)
+ *                       + inject the FULL RULES block — once per session instead of every prompt
+ *                       (~90% less directive overhead); resume/compact re-inject so a squeezed
+ *                       context re-learns the rules.
+ *
+ * Dedupe: when this file is the USER-LEVEL copy (~/.claude/hooks) and the project ships its own
+ * managed copy (<cwd>/.claude/hooks/terminal-title.js), this copy stands down entirely — otherwise
+ * both hooks inject directives naming two different title files (double tokens, double Writes).
+ *
+ * The title is set TWO ways on every event: \`process.title\` (= SetConsoleTitleW on Windows — the ONLY
+ * mechanism that flips the tab on UserPromptSubmit, where Claude Code drops \`terminalSequence\`) AND
+ * \`terminalSequence\` (honored on the other events). node writes UTF-8 natively, so glyphs go out as-is.
+ *
+ * Title files are PROJECT-SCOPED at <cwd>/.claude/hooks/.titles/<session_id>.txt — the model authors
+ * them; the directive injected each prompt tells it the path + format. Optional forensic log (one line
+ * per paint, for tracing an out-of-sync tab) is gated behind CLAUDE_TITLE_DEBUG=1 — default OFF,
+ * ~512KB-capped, written to .titles/_debug.log — so it never ships a growing log.
+ *
+ * Requires \`env.CLAUDE_CODE_DISABLE_TERMINAL_TITLE = "1"\` (set by plugin.json), or CC's own writer races.
+ */`
             },
             'feedback-feedback': {
                 filename: 'FEEDBACK.md',
@@ -2002,93 +2038,145 @@ Claude reads this file but must never write to it. When Claude discovers project
             },
             'settings': {
                 filename: 'settings.json',
-                content: `{
-  "env": {
-    "CLAUDE_CODE_DISABLE_AUTO_MEMORY": "0"
-  },
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node .claude/hooks/migrate-feedback.js"
-          }
-        ]
-      }
-    ],
-    "PostToolUse": [
-      {
-        "matcher": "Edit|Write",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node .claude/hooks/feedback-rule-check.js"
-          }
-        ]
-      }
-    ]
-  },
-  "permissions": {
-    "allow": [
-      "Read(./**)",
-      "Edit(./**)",
-      "Write(./**)",
-      "Glob",
-      "Grep",
-      "WebSearch",
-      "WebFetch",
-      "Bash(npm test)",
-      "Bash(npm test *)",
-      "Bash(npm run dev)",
-      "Bash(npm run build)",
-      "Bash(npm run lint)",
-      "Bash(npm run lint:fix)",
-      "Bash(npm run typecheck)",
-      "Bash(npm run test)",
-      "Bash(npm run test:*)",
-      "Bash(npm run validate)",
-      "Bash(git status)",
-      "Bash(git status *)",
-      "Bash(git diff *)",
-      "Bash(git add *)",
-      "Bash(git commit *)",
-      "Bash(git push *)",
-      "Bash(git pull)",
-      "Bash(git pull *)",
-      "Bash(git checkout *)",
-      "Bash(git branch *)",
-      "Bash(node .claude/*)",
-      "Bash(python3 *)",
-      "Bash(npx claude-code-autoconfig*)",
-      "Bash(npm pack *)",
-      "Bash(tar *)",
-      "Bash(mktemp *)",
-      "Bash(find ./*)",
-      "Bash(ls *)",
-      "Bash(dir *)",
-      "Bash(mkdir *)",
-      "Bash(mkdir -p *)",
-      "Bash(start *)",
-      "Bash(start .claude *)",
-      "Bash(open *)",
-      "Bash(open .claude *)",
-      "Bash(xdg-open *)",
-      "Bash(xdg-open .claude *)"
-    ],
-    "deny": [
-      "Read(./.env)",
-      "Read(./.env.*)",
-      "Read(./secrets/**)",
-      "Read(./**/credentials.*)",
-      "Read(./**/*.pem)",
-      "Read(./**/*.key)",
-      "Bash(rm -rf *)",
-      "Bash(curl *)",
-      "Bash(wget *)"
-    ]
-  }
+                content: `{
+  "env": {
+    "CLAUDE_CODE_DISABLE_AUTO_MEMORY": "0",
+    "CLAUDE_CODE_DISABLE_TERMINAL_TITLE": "1"
+  },
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .claude/hooks/migrate-feedback.js"
+          }
+        ]
+      },
+      {
+        "matcher": "*",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .claude/hooks/terminal-title.js"
+          }
+        ]
+      }
+    ],
+    "UserPromptSubmit": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .claude/hooks/terminal-title.js"
+          }
+        ]
+      }
+    ],
+    "Stop": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .claude/hooks/terminal-title.js"
+          }
+        ]
+      }
+    ],
+    "Notification": [
+      {
+        "matcher": "permission_prompt",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .claude/hooks/terminal-title.js"
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .claude/hooks/feedback-rule-check.js"
+          }
+        ]
+      },
+      {
+        "matcher": "Bash|Write|Edit|MultiEdit|NotebookEdit|WebFetch|WebSearch|Task|AskUserQuestion",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node .claude/hooks/terminal-title.js"
+          }
+        ]
+      }
+    ]
+  },
+  "permissions": {
+    "allow": [
+      "Read(./**)",
+      "Edit(./**)",
+      "Write(./**)",
+      "Glob",
+      "Grep",
+      "WebSearch",
+      "WebFetch",
+      "Bash(npm test)",
+      "Bash(npm test *)",
+      "Bash(npm run dev)",
+      "Bash(npm run build)",
+      "Bash(npm run lint)",
+      "Bash(npm run lint:fix)",
+      "Bash(npm run typecheck)",
+      "Bash(npm run test)",
+      "Bash(npm run test:*)",
+      "Bash(npm run validate)",
+      "Bash(git status)",
+      "Bash(git status *)",
+      "Bash(git diff *)",
+      "Bash(git add *)",
+      "Bash(git commit *)",
+      "Bash(git push *)",
+      "Bash(git pull)",
+      "Bash(git pull *)",
+      "Bash(git checkout *)",
+      "Bash(git branch *)",
+      "Bash(node .claude/*)",
+      "Bash(python3 *)",
+      "Bash(npx claude-code-autoconfig*)",
+      "Bash(npm pack *)",
+      "Bash(tar *)",
+      "Bash(mktemp *)",
+      "Bash(find ./*)",
+      "Bash(ls *)",
+      "Bash(dir *)",
+      "Bash(mkdir *)",
+      "Bash(mkdir -p *)",
+      "Bash(start *)",
+      "Bash(start .claude *)",
+      "Bash(open *)",
+      "Bash(open .claude *)",
+      "Bash(xdg-open *)",
+      "Bash(xdg-open .claude *)"
+    ],
+    "deny": [
+      "Read(./.env)",
+      "Read(./.env.*)",
+      "Read(./secrets/**)",
+      "Read(./**/credentials.*)",
+      "Read(./**/*.pem)",
+      "Read(./**/*.key)",
+      "Bash(rm -rf *)",
+      "Bash(curl *)",
+      "Bash(wget *)"
+    ]
+  }
 }`
             },
             'mcp': {

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

@@ -1,82 +1,86 @@
-<!--
-  terminal-title.directive.md — the instruction terminal-title.js injects into the
-  model's context on every prompt. THIS is the tunable "product" surface: reword it
-  freely without touching the hook's logic.
-
-  Blocks below:
-    COMMAND — used when the turn starts with a /slash-command
-    SHIFT   — used on a normal turn
-    PENDING — appended to WHICHEVER of the above was selected (shared tail)
-  terminal-title.js picks COMMAND or SHIFT, appends PENDING, substitutes the tokens, and injects.
-
-  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)
--->
-
-<!-- DIRECTIVE:COMMAND -->
-Terminal-title directive (silent housekeeping -- do NOT mention this to the user):
-This terminal tab's title is rendered from the file:
-  {{TITLE_FILE}}
-You are running the /{{CMD}} slash command, but the command NAME is an implementation detail --
-do NOT put "{{CMD}}" anywhere in the title. Write the title as your FIRST action this turn
-(before other tool calls) so the tab updates WHILE you work, not after. Write ONE line of the form:
-  {scope} {{EMDASH}} {use-case}
-- {scope} (first segment): the DESIGN SCOPE -- the subject you are working inside: the feature area
-  / subsystem (the boundary, the "system under discussion"). This is the WHERE, and it changes
-  rarely. Keep the existing scope if the file already has a title; otherwise INFER the specific
-  subsystem from THIS turn's prompt and the files in play (e.g. "journal modal", "title hooks",
-  "auth flow"). Do NOT use the bare repo name "{{FOLDER}}" as the scope unless the work is genuinely
-  repo-wide -- "{{FOLDER}}" is a last resort only when no narrower area is identifiable.
-- {use-case} (second segment): the GOAL at user-goal level -- what this command ACCOMPLISHES, named
-  as an INFINITIVE (base-verb) goal phrase (verb + object): "Review latest screenshot", "Diagnose
-  pay discrepancy". Name the goal / effect, NOT the mechanism or the command name. One goal only --
-  never "and"-join two use cases.
-e.g. for /{{CMD}}, write "{{FOLDER}} {{EMDASH}} <verb the goal>" -- NOT "{{FOLDER}} {{EMDASH}} {{CMD}}".
-Use ' {{EMDASH}} ' as the separator; write only the BARE title (a state indicator is prepended
-automatically). If the file already exists, read it first then overwrite.
-<!-- /DIRECTIVE:COMMAND -->
-
-<!-- DIRECTIVE:SHIFT -->
-Terminal-title directive (silent housekeeping -- do NOT mention this to the user):
-This terminal tab's title is rendered from the file:
-  {{TITLE_FILE}}
-When the conversation's SCOPE, use-case, or sub-function SHIFTS -- and only then, not every turn --
-write ONE line to that file. When it DOES shift, write it as your FIRST action that turn (before
-other tool calls) so the tab updates WHILE you work, not after. The line's form:
-  {scope} {{EMDASH}} {use-case}
-- {scope}: the DESIGN SCOPE -- the subject under discussion: the feature area / subsystem (the
-  boundary). This is the WHERE; it changes rarely. INFER the specific subsystem from the prompt and
-  the files in play (e.g. "journal modal", "title hooks"); do NOT default to the bare repo name --
-  use it only when the work is genuinely repo-wide.
-- {use-case}: the GOAL at user-goal level -- what you are accomplishing, as an INFINITIVE (base-verb)
-  goal phrase (verb + object), e.g. "Refine title taxonomy". Name the goal, not the
-  mechanism. One goal only.
-Add a third segment ( {{EMDASH}} {sub-function} ) only when the work goes a level deeper -- this is the
-SUBFUNCTION goal level, a step beneath the user goal.
-Rules: use ' {{EMDASH}} ' (space, em-dash, space) as the separator; keep each segment short (a few
-words); write only the BARE title -- a state indicator is prepended automatically; leave the
-file unchanged when the scope has not moved; this is a compass, so change it rarely. If the file
-already exists, read it first then overwrite.
-<!-- /DIRECTIVE:SHIFT -->
-
-<!-- DIRECTIVE:PENDING -->
-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, 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 -->
+<!--
+  terminal-title.directive.md — the instruction text terminal-title.js injects into the
+  model's context. THIS is the tunable "product" surface: reword it freely without touching
+  the hook's logic.
+
+  Token-lean delivery (v2): the full rulebook is injected ONCE per session (SessionStart,
+  including resume/compact so a squeezed context re-learns it); every prompt gets only a
+  short reminder, plus state-specific addenda the hook selects when they apply.
+
+  Blocks below:
+    RULES    — the full directive, injected at SessionStart (all sources)
+    REMINDER — the per-prompt one-liner (every UserPromptSubmit)
+    BASELINE — appended to REMINDER while no title file exists yet (first turn)
+    COMMAND  — appended to REMINDER when the turn starts with a /slash-command
+  terminal-title.js picks REMINDER (+BASELINE/+COMMAND as applicable), substitutes the
+  tokens, and injects. SessionStart injects RULES.
+
+  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
+    {{FOLDER}}     — the working-directory folder name (scope fallback)
+    {{EMDASH}}     — the ' — ' segment separator
+    {{CMD}}        — the slash-command name (COMMAND block only)
+-->
+
+<!-- DIRECTIVE:RULES -->
+Terminal-title directive (silent housekeeping -- never mention it to the user). These rules
+apply to EVERY turn of this session; per-prompt reminders are one-liners that point back here.
+
+This terminal tab's title renders from the file:
+  {{TITLE_FILE}}
+Maintain it across the session:
+- When the conversation's SCOPE, use-case, or sub-function SHIFTS -- and only then, not every
+  turn -- overwrite the file with ONE line:  {scope} {{EMDASH}} {use-case}
+  Write it as your FIRST action of that turn (before other tool calls) so the tab updates
+  WHILE you work, not after. If the file exists, read it first, then overwrite.
+- {scope}: the DESIGN SCOPE -- the feature area / subsystem under discussion (the WHERE; it
+  changes rarely). INFER the specific subsystem from the prompt and the files in play (e.g.
+  "journal modal", "title hooks"); use the bare repo name "{{FOLDER}}" only when the work is
+  genuinely repo-wide -- it is a last resort.
+- {use-case}: the GOAL at user-goal level -- an INFINITIVE (base-verb) goal phrase (verb +
+  object), e.g. "Refine title taxonomy". Name the goal, not the mechanism. One goal only --
+  never "and"-join two use cases.
+- Add a third segment ( {{EMDASH}} {sub-function} ) only when the work goes a level deeper --
+  a step beneath the user goal.
+- Use ' {{EMDASH}} ' (space, em-dash, space) as the separator; keep segments short (a few
+  words); write only the BARE title -- a state glyph is prepended automatically. This is a
+  compass, not a log: change it rarely.
+- If no title has been set yet, treat your first turn as the baseline: infer the title from
+  that turn's prompt and write it immediately, even though nothing has "shifted".
+- Slash-command turns: the command NAME is an implementation detail -- never put it in the
+  title. Name the goal the command ACCOMPLISHES ("{{FOLDER}} {{EMDASH}} <verb the goal>",
+  never "{{FOLDER}} {{EMDASH}} <command-name>").
+
+Pending-question signal: when you END a turn on a question the user must answer before you
+can proceed, do BOTH 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 on phrasing or timing.
+     The flag is one-shot (consumed at turn end, auto-cleared next turn), so write it ONLY on
+     a turn genuinely blocked on an answer -- but ALWAYS then, even when the closing question
+     is wrapped in parens or is not the literal final character of the message.
+  2. Phrase your FINAL line to end with a question mark ('?') -- the backup signal, and good
+     UX. A single trailing parenthetical aside after the '?' is fine.
+Make the closing question self-contained: answerable without re-reading the response above
+it. Never signal for a rhetorical question or a recap.
+<!-- /DIRECTIVE:RULES -->
+
+<!-- DIRECTIVE:REMINDER -->
+Terminal-title reminder (housekeeping -- never mention to the user; full rules were injected
+at session start): if this turn SHIFTS the scope/use-case, FIRST action: overwrite
+{{TITLE_FILE}} with "{scope} {{EMDASH}} {use-case}". If you END this turn blocked on a
+question, write the flag file {{ASK_FILE}} and end your final line with '?'.
+<!-- /DIRECTIVE:REMINDER -->
+
+<!-- DIRECTIVE:BASELINE -->
+No title is set yet -- treat THIS turn as the baseline: infer {scope} {{EMDASH}} {use-case}
+from this prompt and the files in play, and write {{TITLE_FILE}} NOW (first action). Do not
+default to the bare folder name "{{FOLDER}}" unless the work is genuinely repo-wide.
+<!-- /DIRECTIVE:BASELINE -->
+
+<!-- DIRECTIVE:COMMAND -->
+This turn runs the /{{CMD}} slash command -- the command NAME is an implementation detail:
+never put "{{CMD}}" in the title. If the scope shifted, name the goal the command
+ACCOMPLISHES (e.g. "<area> {{EMDASH}} <verb the goal>").
+<!-- /DIRECTIVE:COMMAND -->

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

@@ -2,13 +2,20 @@
 /**
  * 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 (incl. the {sid}.ask path) +
- *                       clear any stale {sid}.ask flag so it reflects only the turn about to run
+ *   UserPromptSubmit -> ⬤ working  + inject the per-prompt REMINDER one-liner (+BASELINE while no
+ *                       title exists, +COMMAND on /slash turns) + clear any stale {sid}.ask flag
  *   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
  *                       on a question (last visible response text ends in '?', or a {sid}.ask flag)
  *   SessionStart     -> ✻ idle "Claude Code — New session" (or an existing title on resume/compact)
+ *                       + inject the FULL RULES block — once per session instead of every prompt
+ *                       (~90% less directive overhead); resume/compact re-inject so a squeezed
+ *                       context re-learns the rules.
+ *
+ * Dedupe: when this file is the USER-LEVEL copy (~/.claude/hooks) and the project ships its own
+ * managed copy (<cwd>/.claude/hooks/terminal-title.js), this copy stands down entirely — otherwise
+ * both hooks inject directives naming two different title files (double tokens, double Writes).
  *
  * The title is set TWO ways on every event: `process.title` (= SetConsoleTitleW on Windows — the ONLY
  * mechanism that flips the tab on UserPromptSubmit, where Claude Code drops `terminalSequence`) AND
@@ -23,6 +30,7 @@
  */
 const fs = require('fs');
 const path = require('path');
+const os = require('os');
 
 const ESC = '\x1b';
 const BEL = '\x07';
@@ -61,6 +69,10 @@ async function handle(data) {
   const event = data.hook_event_name || '';
   const sid = data.session_id || '';
   const cwd = data.cwd || process.cwd();
+  // User-level copy stands down when a project-level managed copy exists (see header).
+  if (shouldDefer(cwd, __dirname, __filename, path.join(os.homedir(), '.claude', 'hooks'))) {
+    process.exit(0);
+  }
   // PROJECT-SCOPED title dir (cwd-relative) — the plugin installs per-project. (The live ~/.claude
   // variant uses os.homedir() instead; that is the only difference between the two.)
   const dir = path.join(cwd, '.claude', 'hooks', '.titles');
@@ -96,7 +108,14 @@ async function handle(data) {
   if (event === 'SessionStart') {
     // Fresh-session placeholder; on resume/compact an existing model-authored title is preferred.
     const title = normalize(readTitle(file) || 'Claude Code - New session');
-    emit(setTitle(GLYPH.idle, title));
+    const out = setTitle(GLYPH.idle, title);
+    // Inject the FULL rulebook here — once per session — instead of on every prompt. All sources
+    // get it: startup/clear teach a fresh context, resume/compact re-teach a squeezed one.
+    const rules = buildBlocks(['RULES'], file, cwd, '');
+    if (rules) {
+      out.hookSpecificOutput = { hookEventName: 'SessionStart', additionalContext: rules };
+    }
+    emit(out);
     return;
   }
 
@@ -203,7 +222,15 @@ function inspectLastResponse(transcriptPath) {
     if (!line) continue;
     let obj;
     try { obj = JSON.parse(line); } catch (_) { continue; }
-    if (!obj || obj.type !== 'assistant' || !obj.message) continue;
+    if (!obj || !obj.message) continue;
+    // The current turn's response always sits AFTER the last real user prompt. Crossing one while
+    // scanning back for that response means it hasn't flushed to the JSONL yet (~200ms lag) — force a
+    // re-read (suspectRace) instead of falling through to the PRIOR turn's text, which may end in '?'
+    // and would wrongly paint the awaiting ◐ on what was really a statement turn.
+    if (obj.type === 'user' && isRealUserPrompt(obj)) {
+      return { ends: false, found: false, tail: '', suspectRace: true };
+    }
+    if (obj.type !== 'assistant') continue;
     const c = obj.message.content;
     let text = '';
     if (typeof c === 'string') {
@@ -234,6 +261,15 @@ function inspectLastResponse(transcriptPath) {
   return blank;
 }
 
+// A genuine human prompt (real text) vs a tool_result-carrier user message (content is only
+// tool_result blocks). Marks the boundary of the current turn's response while walking the transcript.
+function isRealUserPrompt(obj) {
+  const c = obj.message && obj.message.content;
+  if (typeof c === 'string') return c.trim().length > 0;
+  if (Array.isArray(c)) return c.some(b => b && b.type === 'text' && typeof b.text === 'string' && b.text.trim().length > 0);
+  return false;
+}
+
 // Event-loop-friendly sleep for the Stop flush-race re-read beat (handle awaits this; no busy-wait).
 function delay(ms) { return new Promise(resolve => setTimeout(resolve, ms)); }
 
@@ -264,28 +300,47 @@ function emit(obj) {
   process.exit(0);
 }
 
-// Build the injected directive from terminal-title.directive.md (COMMAND block for a /slash-command
-// turn, SHIFT otherwise; PENDING tail appended). Wording lives in the .md so it tunes without code edits.
+// Build the per-prompt injection: the REMINDER one-liner, plus BASELINE while no title file
+// exists yet (first turn), plus COMMAND on a /slash-command turn. The full rulebook (RULES) is
+// injected by SessionStart, not here. Wording lives in the .md so it tunes without code edits.
 function buildDirective(data, file, cwd) {
+  const prompt = typeof data.prompt === 'string' ? data.prompt : '';
+  const m = prompt.match(/^\s*\/([A-Za-z0-9][\w:.-]*)/);
+  const blocks = ['REMINDER'];
+  if (!fileExists(file)) blocks.push('BASELINE');
+  if (m) blocks.push('COMMAND');
+  return buildBlocks(blocks, file, cwd, m ? m[1] : '');
+}
+
+// Extract the named blocks from terminal-title.directive.md, join them, substitute the tokens.
+function buildBlocks(names, file, cwd, cmd) {
   let tpl = '';
   try {
     tpl = fs.readFileSync(path.join(__dirname, 'terminal-title.directive.md'), 'utf8');
   } catch (_) {
     return '';
   }
-  const prompt = typeof data.prompt === 'string' ? data.prompt : '';
-  const m = prompt.match(/^\s*\/([A-Za-z0-9][\w:.-]*)/);
-  const cmd = m ? m[1] : '';
-  const block = extractBlock(tpl, cmd ? 'COMMAND' : 'SHIFT');
-  if (!block) return '';
-  const pending = extractBlock(tpl, 'PENDING');
-  const combined = pending ? `${block}\n\n${pending}` : block;
-  return combined
+  const parts = names.map(n => extractBlock(tpl, n)).filter(Boolean);
+  if (!parts.length) return '';
+  return parts.join('\n')
     .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);
+    .split('{{CMD}}').join(cmd || '');
+}
+
+// Should THIS copy of the hook stand down? True only for the user-level copy (~/.claude/hooks)
+// running inside a project that ships its own managed copy — the project copy wins, so a session
+// gets ONE directive and ONE title file. Parameterized (no ambient __dirname/homedir) for tests.
+function shouldDefer(cwd, selfDir, selfFile, homeHooksDir) {
+  try {
+    if (path.resolve(selfDir) !== path.resolve(homeHooksDir)) return false; // we ARE the project copy
+    const projectCopy = path.join(cwd, '.claude', 'hooks', 'terminal-title.js');
+    return fs.existsSync(projectCopy) && path.resolve(projectCopy) !== path.resolve(selfFile);
+  } catch (_) {
+    return false;
+  }
 }
 
 function extractBlock(tpl, name) {
@@ -297,4 +352,4 @@ function extractBlock(tpl, name) {
 }
 
 // Exported for tests (require()'d when require.main !== module). The hook itself never reads these.
-module.exports = { inspectLastResponse, normalize, GLYPH };
+module.exports = { inspectLastResponse, normalize, GLYPH, shouldDefer };

package/.claude/scripts/sync-docs.js

@@ -32,6 +32,10 @@ const SKIP = new Set([
 // Folders we scan for files
 const SCAN_FOLDERS = ['commands', 'agents', 'hooks', 'feedback'];
 
+// Dev-only files that live in the maintainer repo but are never installed to
+// user projects (mirror of bin/cli.js DEV_ONLY_FILES) — never document them.
+const DEV_ONLY_FILES = new Set(['deploy-to-npmjs.md']);
+
 // Structural keys that are not file-backed (always preserved, never generated)
 const STRUCTURAL_KEYS = new Set([
   'memory-md', 'root', 'claude-md', 'claude-dir'
@@ -263,6 +267,7 @@ function scanFiles() {
     }).sort();
 
     for (const file of files) {
+      if (DEV_ONLY_FILES.has(file)) continue;
       const ext = path.extname(file);
       const filePath = path.join(folderPath, file);
       const content = fs.readFileSync(filePath, 'utf8');
@@ -541,7 +546,12 @@ function generateFileContents(entries) {
 // =============================================================================
 
 const entries = scanFiles();
-let html = fs.readFileSync(docsPath, 'utf8');
+// The docs HTML may be CRLF on Windows, but every marker below is authored with
+// `\n`. Normalize to LF for the string surgery, then restore the file's original
+// EOL on write so we don't churn every line.
+const rawHtml = fs.readFileSync(docsPath, 'utf8');
+const eol = rawHtml.includes('\r\n') ? '\r\n' : '\n';
+let html = rawHtml.replace(/\r\n/g, '\n');
 
 // 1. Replace the file tree (between claude-dir folder row and settings.json closing div)
 //    We find the marker after the claude-dir folder and replace up to the settings div
@@ -656,7 +666,7 @@ if (fcEnd === -1) {
 const newFileContents = generateFileContents(entries);
 html = html.slice(0, fcInsertPoint) + newFileContents + '\n        ' + html.slice(fcEnd);
 
-fs.writeFileSync(docsPath, html);
+fs.writeFileSync(docsPath, eol === '\r\n' ? html.replace(/\n/g, '\r\n') : html);
 
 const fileCount = entries.filter(e => !e.isEmptyFolder).length;
 console.log(`Synced ${fileCount} files to docs.`);

package/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## v1.0.197
+- perf(terminal-title): deliver the directive once per session; dedupe user/project hooks
+
+## v1.0.196
+- fix(terminal-title): stop at the turn boundary when grading the closing '?' (stale-awaiting race)
+- fix(cli): require non-TTY stdout for inside-Claude block (env var alone false-positives in inherited terminals)
+
 ## v1.0.195
 - fix(terminal-title): flip awaiting ◐ for a closing question with a trailing parenthetical aside
 
@@ -141,9 +148,3 @@
 ## v1.0.148
 - fix: refine inside-Claude error wording
 
-## v1.0.147
-- fix: make inside-Claude error message more specific
-
-## v1.0.146
-- style: improve inside-Claude block message formatting
-

package/CLAUDE.md

@@ -42,17 +42,13 @@ 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
+### Publishing to npm — bypass-2FA token flow (web-auth publish is a DEAD END)
 
-`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.)
+(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`.
+- **Primary flow (agent can do it end-to-end):** `npm test` + `npm version patch` (commit + tag) → `npm whoami` to verify the Bypass-2FA granular token in `~/.npmrc` still authenticates → plain `npm publish` (works headless, no OTP) → after the `+ claude-code-autoconfig@<version>` line, `git push origin main --follow-tags`. Never double-bump if the version is already bumped.
+- **If `npm whoami` returns E401**, the token is dead/expired (90-day cap). The human rotates it (npmjs.com → Access Tokens → Granular → "Bypass 2FA", read-write, scoped to this package only) and pastes it into `~/.npmrc` in an editor — never via a command. Stopgap without a token: `npm publish --otp=<recovery-code>` in the human's own terminal.
+- **Do NOT use `npm login --auth-type=web && npm publish`:** login succeeds but publish still dies `EOTP` — the npm CLI can't route publish-time 2FA to the browser on this webauthn-only account (confirmed 2026-07-03, npm 10.9.2). Don't retry it in-agent, and don't ask for a typed TOTP (none exists). Full procedure: `.claude/commands/deploy-to-npmjs.md` (`/deploy-to-npmjs`).
 
 ## Debugging Methodology — Evidence Before Solutions
 

package/bin/cli.js

@@ -435,8 +435,12 @@ if (process.argv[2] === 'plugin') {
 
 const forceMode = process.argv.includes('--force');
 
-// Detect if running inside Claude Code session
-const insideClaude = process.env.CLAUDECODE === '1';
+// Detect if running inside Claude Code session.
+// CLAUDECODE=1 alone is not reliable: env vars inherit into every descendant
+// process (e.g. VS Code launched from a Claude session, and any terminal it
+// spawns). A genuine in-agent run has piped stdio (isTTY falsy), while a human
+// terminal has a real TTY — so require both signals before blocking.
+const insideClaude = process.env.CLAUDECODE === '1' && !process.stdout.isTTY;
 
 console.log('\x1b[36m%s\x1b[0m', '🚀 Claude Code Autoconfig');
 console.log();
@@ -653,7 +657,7 @@ const hooksSrc = path.join(packageDir, '.claude', 'hooks');
 const scriptsSrc = path.join(packageDir, '.claude', 'scripts');
 
 // Files that exist in the dev repo but should never be installed to user projects
-const DEV_ONLY_FILES = ['publish.md'];
+const DEV_ONLY_FILES = ['deploy-to-npmjs.md'];
 
 function copyDir(src, dest) {
   fs.mkdirSync(dest, { recursive: true });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-autoconfig",
-  "version": "1.0.195",
+  "version": "1.0.197",
   "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",
@@ -23,13 +23,14 @@
   ],
   "scripts": {
     "test": "node test/box-alignment.test.js && node test/cli-install.test.js && node test/update-system.test.js && node test/plugin-system.test.js && node test/terminal-title.test.js",
+    "pub": "npm whoami && npm publish",
     "test:box": "node test/box-alignment.test.js",
     "test:install": "node test/cli-install.test.js",
     "test:update": "node test/update-system.test.js",
     "postversion": "node scripts/generate-changelog.js --postversion"
   },
   "bin": {
-    "claude-code-autoconfig": "./bin/cli.js"
+    "claude-code-autoconfig": "bin/cli.js"
   },
   "files": [
     "bin",
@@ -40,7 +41,7 @@
     "!.claude/cca.config.json",
     "!.claude/.autoconfig-version",
     "!.claude/.autoconfig-plugins.json",
-    "!.claude/commands/publish.md",
+    "!.claude/commands/deploy-to-npmjs.md",
     "!.claude/plans",
     "CLAUDE.md",
     "CHANGELOG.md"