specflow-cc 1.18.1 → 1.18.3

package/CHANGELOG.md

@@ -5,6 +5,23 @@ All notable changes to SpecFlow will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.18.3] - 2026-04-11
+
+### Fixed
+
+- **Auto-heal for users upgrading from 1.18.0 / 1.18.1** — the installer now scans `hooks.PostToolUse` during every install and removes any flat `{ type, command }` entry that references `context-monitor`. These entries were written by the buggy `1.18.0`/`1.18.1` installer and would otherwise linger in `settings.json` next to the newly written correct matcher group, still tripping Claude Code's `"Expected array, but received undefined"` parse error. Foreign flat entries (belonging to other tools) are left untouched — only entries unambiguously written by prior SpecFlow versions are removed.
+- Three new smoke tests cover clean auto-heal, preservation of foreign flat entries, and the mixed state (pre-existing correct hook + flat broken duplicate).
+
+## [1.18.2] - 2026-04-11
+
+### Fixed
+
+- **Installer no longer corrupts `settings.json`** — the installer wrote the `context-monitor` PostToolUse hook as a flat `{ type, command }` object, but Claude Code expects every `PostToolUse` entry to be a matcher group of the shape `{ matcher?, hooks: [{ type, command }] }`. Claude Code failed to parse `settings.json` with `"Expected array, but received undefined"`, and permission rules in the affected file were silently disabled
+  - The hook is now written as a proper matcher group
+  - Broken duplicate-detection fixed: the installer previously checked `entry.command` on the top-level entry, but in the correct format the command lives inside `entry.hooks[i].command`. As a result, every repeat install pushed a new (broken) entry. Detection now walks `entry.hooks[]` and matches the existing hook correctly, so repeat installs are idempotent
+  - Smoke test extended with four new cases: format assertion, presence check, repeat-install idempotency, and preservation of a pre-existing correctly-formatted hook
+  - **Heads-up:** if you already ran `1.18.0` or `1.18.1` against a `settings.json` that had a pre-existing PostToolUse hook, you may have a duplicate flat entry. Remove any `PostToolUse` element that lacks a `hooks:` array (i.e. has `type`/`command` at the top level) and re-run the installer
+
 ## [1.18.1] - 2026-04-11
 
 ### Fixed

package/bin/install.js

@@ -289,13 +289,47 @@ function finishInstall(settingsPath, settings, statuslineCommand, shouldInstallS
   if (!settings.hooks) settings.hooks = {};
   if (!settings.hooks.PostToolUse) settings.hooks.PostToolUse = [];
 
-  const hasMonitor = settings.hooks.PostToolUse.some(h =>
-    h.command && h.command.includes('context-monitor')
+  // Auto-heal: remove flat, broken context-monitor entries written by
+  // installer versions 1.18.0 and 1.18.1. Those versions pushed
+  // { type: "command", command: "..." } directly into PostToolUse, but
+  // Claude Code requires every PostToolUse entry to be a matcher group
+  // of shape { matcher?, hooks: [{ type, command }, ...] }. A flat entry
+  // makes Claude Code fail to parse settings.json entirely. Only entries
+  // that are unambiguously ours (flat + command references context-monitor)
+  // are removed; everything else is left untouched.
+  {
+    const before = settings.hooks.PostToolUse.length;
+    settings.hooks.PostToolUse = settings.hooks.PostToolUse.filter(entry => {
+      const isFlatBrokenMonitor =
+        entry &&
+        !Array.isArray(entry.hooks) &&
+        entry.type === 'command' &&
+        typeof entry.command === 'string' &&
+        entry.command.includes('context-monitor');
+      return !isFlatBrokenMonitor;
+    });
+    const removed = before - settings.hooks.PostToolUse.length;
+    if (removed > 0) {
+      const plural = removed === 1 ? 'y' : 'ies';
+      console.log(`  ${green}✓${reset} Repaired settings.json (removed ${removed} broken hook entr${plural} from prior install)`);
+    }
+  }
+
+  // Claude Code expects each PostToolUse entry to be a matcher group:
+  //   { matcher?: string, hooks: [{ type, command }, ...] }
+  // Detect an existing context-monitor hook inside any matcher group.
+  const hasMonitor = settings.hooks.PostToolUse.some(entry =>
+    Array.isArray(entry && entry.hooks) &&
+    entry.hooks.some(h => h && h.command && h.command.includes('context-monitor'))
   );
   if (!hasMonitor) {
     settings.hooks.PostToolUse.push({
-      type: 'command',
-      command: monitorCommand
+      hooks: [
+        {
+          type: 'command',
+          command: monitorCommand
+        }
+      ]
     });
     console.log(`  ${green}✓${reset} Configured context monitor hook`);
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specflow-cc",
-  "version": "1.18.1",
+  "version": "1.18.3",
   "description": "Spec-driven development system for Claude Code — quality-first workflow with explicit audit cycles",
   "bin": {
     "specflow-cc": "bin/install.js"