specweave 1.0.39 → 1.0.40

package/CLAUDE.md

@@ -1,10 +1,10 @@
-<!-- SW:META template="claude" version="1.0.38" sections="header,start,autodetect,metarule,rules,workflow,structure,taskformat,secrets,syncing,mapping,testing,limits,troubleshooting,principles,linking,docs" -->
+<!-- SW:META template="claude" version="1.0.39" sections="header,start,autodetect,metarule,rules,workflow,structure,taskformat,secrets,syncing,mapping,testing,limits,troubleshooting,principles,linking,docs" -->
 
-<!-- SW:SECTION:header version="1.0.38" -->
+<!-- SW:SECTION:header version="1.0.39" -->
 **Framework**: SpecWeave | **Truth**: `spec.md` + `tasks.md`
 <!-- SW:END:header -->
 
-<!-- SW:SECTION:start version="1.0.38" -->
+<!-- SW:SECTION:start version="1.0.39" -->
 ## Getting Started
 
 **Initial increment**: `0001-project-setup` (auto-created by `specweave init`)
@@ -14,7 +14,7 @@
 2. **Customize**: Edit spec.md and use for setup tasks
 <!-- SW:END:start -->
 
-<!-- SW:SECTION:autodetect version="1.0.38" -->
+<!-- SW:SECTION:autodetect version="1.0.39" -->
 ## Auto-Detection
 
 SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
@@ -24,7 +24,7 @@ SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
 **Opt-out phrases**: "Just brainstorm first" | "Don't plan yet" | "Quick discussion" | "Let's explore ideas"
 <!-- SW:END:autodetect -->
 
-<!-- SW:SECTION:metarule version="1.0.38" -->
+<!-- SW:SECTION:metarule version="1.0.39" -->
 ## Meta-Rule: Think-Before-Act
 
 **Satisfy dependencies BEFORE dependent operations.**
@@ -35,7 +35,7 @@ SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
 ```
 <!-- SW:END:metarule -->
 
-<!-- SW:SECTION:rules version="1.0.38" -->
+<!-- SW:SECTION:rules version="1.0.39" -->
 ## Rules
 
 1. **Files** → `.specweave/increments/####-name/` (spec.md, plan.md, tasks.md at root; reports/, scripts/, logs/ subfolders)
@@ -45,7 +45,7 @@ SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
 5. **Root clean**: NEVER create .md/reports/scripts in project root → use increment folders
 <!-- SW:END:rules -->
 
-<!-- SW:SECTION:workflow version="1.0.38" -->
+<!-- SW:SECTION:workflow version="1.0.39" -->
 ## Workflow
 
 `/sw:increment "X"` → `/sw:do` → `/sw:progress` → `/sw:done 0001`
@@ -62,7 +62,7 @@ SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
 **Natural language**: "Let's build X" → `/sw:increment` | "What's status?" → `/sw:progress` | "We're done" → `/sw:done`
 <!-- SW:END:workflow -->
 
-<!-- SW:SECTION:structure version="1.0.38" -->
+<!-- SW:SECTION:structure version="1.0.39" -->
 ## Structure
 
 ```
@@ -78,7 +78,7 @@ SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
 **Multi-repo**: Clone to `/repositories`, not root → `repositories/backend/src/...`
 <!-- SW:END:structure -->
 
-<!-- SW:SECTION:taskformat version="1.0.38" -->
+<!-- SW:SECTION:taskformat version="1.0.39" -->
 ## Task Format
 
 ```markdown
@@ -88,7 +88,7 @@ SpecWeave auto-detects product descriptions and routes to `/sw:increment`:
 ```
 <!-- SW:END:taskformat -->
 
-<!-- SW:SECTION:secrets version="1.0.38" -->
+<!-- SW:SECTION:secrets version="1.0.39" -->
 ## Secrets Check
 
 **BEFORE CLI tools**: Check existing config first!
@@ -99,7 +99,7 @@ gh auth status
 ```
 <!-- SW:END:secrets -->
 
-<!-- SW:SECTION:syncing version="1.0.38" -->
+<!-- SW:SECTION:syncing version="1.0.39" -->
 ## Auto-Sync (Hooks)
 
 Post-task: updates tasks.md → living docs → external trackers (if configured)
@@ -107,7 +107,7 @@ Post-task: updates tasks.md → living docs → external trackers (if configured
 Config: `.specweave/config.json` → `hooks.post_task_completion`
 <!-- SW:END:syncing -->
 
-<!-- SW:SECTION:mapping version="1.0.38" -->
+<!-- SW:SECTION:mapping version="1.0.39" -->
 ## GitHub Mapping
 
 | SpecWeave | GitHub |
@@ -117,7 +117,7 @@ Config: `.specweave/config.json` → `hooks.post_task_completion`
 | Task T-XXX | Checkbox |
 <!-- SW:END:mapping -->
 
-<!-- SW:SECTION:testing version="1.0.38" -->
+<!-- SW:SECTION:testing version="1.0.39" -->
 ## Testing
 
 BDD in tasks.md | Unit >80% | `.test.ts` (Vitest)
@@ -129,13 +129,13 @@ vi.mock('fs', () => ({ readFile: vi.fn() }));
 ```
 <!-- SW:END:testing -->
 
-<!-- SW:SECTION:limits version="1.0.38" -->
+<!-- SW:SECTION:limits version="1.0.39" -->
 ## Limits
 
 **Max 1500 lines/file** — extract before adding
 <!-- SW:END:limits -->
 
-<!-- SW:SECTION:troubleshooting version="1.0.38" -->
+<!-- SW:SECTION:troubleshooting version="1.0.39" -->
 ## Troubleshooting
 
 | Issue | Fix |
@@ -149,7 +149,7 @@ vi.mock('fs', () => ({ readFile: vi.fn() }));
 | External not syncing | Check `config.json` → `external_tracker_sync: true` |
 <!-- SW:END:troubleshooting -->
 
-<!-- SW:SECTION:principles version="1.0.38" -->
+<!-- SW:SECTION:principles version="1.0.39" -->
 ## Principles
 
 1. **Spec-first**: `/sw:increment` before coding
@@ -159,7 +159,7 @@ vi.mock('fs', () => ({ readFile: vi.fn() }));
 5. **Clean**: All files in increment folders
 <!-- SW:END:principles -->
 
-<!-- SW:SECTION:linking version="1.0.38" -->
+<!-- SW:SECTION:linking version="1.0.39" -->
 ## Bidirectional Linking
 
 Tasks ↔ User Stories auto-linked via AC-IDs: `AC-US1-01` → `US-001`
@@ -167,7 +167,7 @@ Tasks ↔ User Stories auto-linked via AC-IDs: `AC-US1-01` → `US-001`
 Task format: `**AC**: AC-US1-01, AC-US1-02` (CRITICAL for linking)
 <!-- SW:END:linking -->
 
-<!-- SW:SECTION:docs version="1.0.38" -->
+<!-- SW:SECTION:docs version="1.0.39" -->
 ## Docs
 
 [spec-weave.com](https://spec-weave.com) | `.specweave/docs/internal/`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specweave",
-  "version": "1.0.39",
+  "version": "1.0.40",
   "description": "Spec-driven development framework for Claude Code. AI-native workflow with living documentation, intelligent agents, and multilingual support (9 languages). Enterprise-grade traceability with permanent specs and temporary increments.",
   "type": "module",
   "main": "dist/index.js",

package/plugins/specweave/commands/save.md

@@ -897,6 +897,34 @@ Summary:
   Saved: 1/1 repository
 ```
 
+### No Remote Configured (Single Repo or Parent Project)
+
+If operating in single-repo mode and no git remote is configured, prompt the user with the **EXACT project name** in the question:
+
+```markdown
+⚠️  No remote repository configured for 'sw-content-repurposer' (parent project).
+
+How would you like to proceed?
+  1. 📝 Enter URL manually - I'll provide the GitHub/GitLab URL for this repository
+  2. ⏭️  Skip push (commit only) - Just commit locally, I'll set up remote later
+  3. ❌ Cancel - Don't commit or push anything right now
+```
+
+**IMPORTANT**: Always include the project/repository name in the dialog so the user knows WHICH repository is missing the remote. For umbrella setups, this helps distinguish between:
+- Parent project (the umbrella root directory)
+- Child repositories (cloned into `repositories/` folder)
+
+**Check for pending clone jobs**: If `umbrella.childRepos` is empty but a clone job is running (check `/sw:jobs`), inform the user:
+
+```markdown
+ℹ️  Repository cloning is in progress (job: a84e4fe5).
+
+The child repositories are being cloned in the background. Options:
+  1. ⏳ Wait for cloning to complete (run `/sw:jobs` to check status)
+  2. 💾 Save parent project only (commit .specweave/ changes)
+  3. ❌ Cancel and retry later
+```
+
 ## Flags and Options
 
 | Flag | Description |

package/plugins/specweave/hooks/hooks.json

@@ -20,38 +20,6 @@
         ]
       }
     ],
-    "PreToolUse": [
-      {
-        "matcher": "Write",
-        "matcher_content": "\\.specweave/increments/\\d{3,4}E?-[^/]+/spec\\.md",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "bash -c 'W=\"${CLAUDE_PLUGIN_ROOT}/hooks/universal/fail-fast-wrapper.sh\"; S=\"${CLAUDE_PLUGIN_ROOT}/hooks/v2/guards/metadata-json-guard.sh\"; [[ -x \"$W\" ]] && exec \"$W\" \"$S\" || (cat >/dev/null && printf \"{\\\"decision\\\":\\\"allow\\\"}\")'"
-          }
-        ]
-      },
-      {
-        "matcher": "Write",
-        "matcher_content": "\\.specweave/increments/\\d{3,4}E?-[^/]+/",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "bash -c 'W=\"${CLAUDE_PLUGIN_ROOT}/hooks/universal/fail-fast-wrapper.sh\"; S=\"${CLAUDE_PLUGIN_ROOT}/hooks/v2/guards/increment-duplicate-guard.sh\"; [[ -x \"$W\" ]] && exec \"$W\" \"$S\" || (cat >/dev/null && printf \"{\\\"decision\\\":\\\"allow\\\"}\")'"
-          }
-        ]
-      },
-      {
-        "matcher": "Write",
-        "matcher_content": "\\.specweave/(increments/\\d{3,4}E?-[^/]+/spec\\.md|docs/internal/specs/)",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "bash -c 'W=\"${CLAUDE_PLUGIN_ROOT}/hooks/universal/fail-fast-wrapper.sh\"; S=\"${CLAUDE_PLUGIN_ROOT}/hooks/v2/guards/spec-validation-guard.sh\"; [[ -x \"$W\" ]] && exec \"$W\" \"$S\" || (cat >/dev/null && printf \"{\\\"decision\\\":\\\"allow\\\"}\")'"
-          }
-        ]
-      }
-    ],
     "PostToolUse": [
       {
         "matcher": "Edit|Write",

package/plugins/specweave/hooks/lib/common-setup.sh

@@ -77,24 +77,6 @@ guard_allow() {
   exit 0
 }
 
-# Block the tool call with reason (DEPRECATED v1.0.37 - use guard_warn instead)
-# NOTE: Blocking is discouraged. Use guard_warn for most cases.
-guard_block() {
-  local reason="$1"
-  reason=$(echo "$reason" | sed 's/"/\\"/g' | sed ':a;N;$!ba;s/\n/\\n/g')
-  printf '{"decision":"block","reason":"%s"}\n' "$reason"
-  exit 2
-}
-
-# Warn but ALLOW the tool call (v1.0.37+)
-# This is the PREFERRED approach - never block operations, always allow with warnings.
-guard_warn() {
-  local message="$1"
-  message=$(echo "$message" | sed 's/"/\\"/g' | sed ':a;N;$!ba;s/\n/\\n/g')
-  printf '{"decision":"allow","message":"%s"}\n' "$message"
-  exit 0
-}
-
 # ============================================================================
 # SIMPLE LOGGING (optional, writes to .specweave/logs/hooks.log)
 # ============================================================================

package/plugins/specweave/hooks/v2/guards/completion-guard.sh

@@ -1,76 +1,14 @@
 #!/bin/bash
-# completion-guard.sh - WARN (not block) on direct editing of metadata.json to "completed" status
+# completion-guard.sh - DISABLED (v1.0.38)
 #
-# v0.28.63+: Detects the auto-completion bug by warning on direct status changes to completed.
-# Status SHOULD go through ready_for_review first, and /sw:done marks completed with validation.
+# This guard was converted to WARNING-only in v1.0.37, and now completely
+# disabled in v1.0.38 per user feedback: "you MUST NEVER block such operations"
 #
-# v1.0.37+: CRITICAL CHANGE - Now WARNS instead of BLOCKING!
-# User feedback: "you MUST NEVER block such operations... do at least warning"
-# Business logic and validation should be in scripts/agents, not hard blocks.
+# Completion workflow should be handled by agents/scripts with proper business logic,
+# not by hooks that can interfere with file operations.
 #
-# PreToolUse hook - WARNS but ALLOWS the tool call
-#
-# IMPORTANT: This is a safety guard. Exit 0 allows (with warning if needed).
-# All exit paths MUST output JSON for proper Claude Code handling.
-set +e
-
-[[ "${SPECWEAVE_DISABLE_HOOKS:-0}" == "1" ]] && echo '{"decision":"allow"}' && exit 0
-
-# Read stdin for tool input
-INPUT=$(cat 2>/dev/null || echo '{}')
-
-# Check if this is editing metadata.json with status: completed
-# Pattern: file_path contains metadata.json AND (new_string OR content) contains "status"..."completed"
-
-# Extract file_path
-# Claude Code passes tool input in .tool_input.file_path format
-if command -v jq &> /dev/null; then
-  FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.file_path // .file_path // empty' 2>/dev/null)
-else
-  FILE_PATH=$(echo "$INPUT" | grep -o '"file_path"[[:space:]]*:[[:space:]]*"[^"]*"' | head -1 | sed 's/.*"\([^"]*\)".*/\1/')
-fi
+# This guard now does NOTHING - just allows all operations.
 
-# Only care about metadata.json files
-if [[ "$FILE_PATH" != *metadata.json ]]; then
-  echo '{"decision":"allow"}'
-  exit 0  # Allow
-fi
-
-# Extract the content being written (new_string for Edit, content for Write)
-# Claude Code passes tool input in .tool_input format
-if command -v jq &> /dev/null; then
-  NEW_CONTENT=$(echo "$INPUT" | jq -r '.tool_input.new_string // .tool_input.content // .new_string // .content // empty' 2>/dev/null)
-else
-  NEW_CONTENT=$(echo "$INPUT" | grep -o '"new_string"[[:space:]]*:[[:space:]]*"[^"]*"' | head -1)
-  if [[ -z "$NEW_CONTENT" ]]; then
-    NEW_CONTENT=$(echo "$INPUT" | grep -o '"content"[[:space:]]*:[[:space:]]*"[^"]*"' | head -1)
-  fi
-fi
-
-# Check if trying to set status to "completed" directly
-# This is a simple pattern match - if the edit/write contains status...completed
-if echo "$NEW_CONTENT" | grep -q '"status"[[:space:]]*:[[:space:]]*"completed"'; then
-  # Read current status from file to check if coming from ready_for_review
-  if [[ -f "$FILE_PATH" ]]; then
-    CURRENT_STATUS=$(grep -o '"status"[[:space:]]*:[[:space:]]*"[^"]*"' "$FILE_PATH" | head -1 | sed 's/.*"\([^"]*\)".*/\1/')
-
-    if [[ "$CURRENT_STATUS" == "ready_for_review" ]]; then
-      # This is a valid transition - allow
-      echo '{"decision":"allow"}'
-      exit 0
-    fi
-  fi
-
-  # WARN - trying to set completed without going through ready_for_review (v1.0.37)
-  cat << 'WARN_EOF'
-{
-  "decision": "allow",
-  "message": "⚠️ WARNING: Direct status change to \"completed\" detected!\n\n🚨 RECOMMENDED WORKFLOW:\n1. All tasks completed → status auto-transitions to \"ready_for_review\"\n2. Run /sw:done <increment-id> with explicit user confirmation\n3. Only then does status become \"completed\"\n\nWHY THIS MATTERS:\n• Ensures all ACs are checked in spec.md before closure\n• Requires explicit user approval\n• Maintains audit trail (approvedAt timestamp)\n\n💡 If implementing closure logic, use:\n  MetadataManager.updateStatus(incrementId, IncrementStatus.COMPLETED)\n\nOperation ALLOWED - proceeding with status change."
-}
-WARN_EOF
-  exit 0  # ALLOW with warning (v1.0.37)
-fi
-
-# Allow other edits to metadata.json
+set +e
 echo '{"decision":"allow"}'
 exit 0

package/plugins/specweave/hooks/v2/guards/increment-duplicate-guard.sh

@@ -1,149 +1,14 @@
 #!/bin/bash
-# increment-duplicate-guard.sh - WARN (not block) on duplicate increment IDs
+# increment-duplicate-guard.sh - DISABLED (v1.0.38)
 #
-# v0.33.0+: Detects duplicate increment numbers (0121 and 0121 both existing)
-# Also detects 0001 and 0001E collisions (they share the same base number)
+# This guard was converted to WARNING-only in v1.0.37, and now completely
+# disabled in v1.0.38 per user feedback: "you MUST NEVER block such operations"
 #
-# v1.0.37+: CRITICAL CHANGE - Now WARNS instead of BLOCKING!
-# User feedback: "you MUST NEVER block such operations... do at least warning"
-# Business logic and validation should be in scripts/agents, not hard blocks.
+# Duplicate detection should be handled by agents/scripts with proper business logic,
+# not by hooks that can interfere with file operations.
 #
-# PreToolUse hook for Write tool - WARNS but ALLOWS the tool call
-#
-# Exit 0 = allow (with JSON warning message if duplicate detected)
-set +e
-
-[[ "${SPECWEAVE_DISABLE_HOOKS:-0}" == "1" ]] && echo '{"decision":"allow"}' && exit 0
-
-# Read stdin for tool input
-INPUT=$(cat 2>/dev/null || echo '{}')
-
-# Extract file_path from the tool call
-# Claude Code passes tool input in .tool_input.file_path format
-if command -v jq &> /dev/null; then
-  FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.file_path // .file_path // empty' 2>/dev/null)
-else
-  FILE_PATH=$(echo "$INPUT" | grep -o '"file_path"[[:space:]]*:[[:space:]]*"[^"]*"' | head -1 | sed 's/.*"\([^"]*\)".*/\1/')
-fi
-
-# Only care about .specweave/increments/ paths
-if [[ "$FILE_PATH" != *.specweave/increments/* ]]; then
-  echo '{"decision":"allow"}'
-  exit 0  # Not an increment file - allow
-fi
-
-# CRITICAL FIX (v1.0.37): ALWAYS allow metadata.json writes!
-# metadata.json is the FIRST file created for any increment - it MUST succeed.
-# Duplicate detection only makes sense for the INCREMENT FOLDER, not individual files.
-# Once the folder exists, any file writes within it should be allowed.
-if [[ "$FILE_PATH" == *metadata.json ]]; then
-  echo '{"decision":"allow","message":"metadata.json write allowed (increment creation)"}'
-  exit 0
-fi
-
-# Extract the increment folder name from the path
-# Pattern: .specweave/increments/XXXX-name/file.md or .specweave/increments/XXXX-name/subfolder/file
-# We need to extract "XXXX-name" part
-
-# Remove the .specweave/increments/ prefix
-AFTER_INCREMENTS=${FILE_PATH#*.specweave/increments/}
-
-# Get the first path component (the increment folder)
-INCREMENT_FOLDER=$(echo "$AFTER_INCREMENTS" | cut -d'/' -f1)
-
-# Skip special folders
-if [[ "$INCREMENT_FOLDER" == "_archive" ]] || [[ "$INCREMENT_FOLDER" == "_abandoned" ]] || [[ "$INCREMENT_FOLDER" == "_paused" ]] || [[ "$INCREMENT_FOLDER" == "README.md" ]]; then
-  echo '{"decision":"allow"}'
-  exit 0
-fi
-
-# Extract the increment number from folder name (handles both 0121-name and 0121E-name)
-INCREMENT_NUM=$(echo "$INCREMENT_FOLDER" | grep -oE '^[0-9]{3,4}' | head -1)
-
-if [[ -z "$INCREMENT_NUM" ]]; then
-  echo '{"decision":"allow"}'
-  exit 0  # Not a standard increment folder pattern - allow
-fi
-
-# Normalize to 4 digits (strip leading zeros to avoid octal interpretation)
-INCREMENT_NUM=$(printf "%04d" "$((10#$INCREMENT_NUM))")
-
-# Find the increments root directory
-INCREMENTS_DIR=$(echo "$FILE_PATH" | grep -o '.*/\.specweave/increments' | head -1)
+# This guard now does NOTHING - just allows all operations.
 
-if [[ ! -d "$INCREMENTS_DIR" ]]; then
-  # Increments directory doesn't exist yet - first increment, allow creation
-  echo '{"decision":"allow"}'
-  exit 0
-fi
-
-# Scan ALL directories for existing increment with the same number
-DIRS_TO_CHECK=(
-  "$INCREMENTS_DIR"
-  "$INCREMENTS_DIR/_archive"
-  "$INCREMENTS_DIR/_abandoned"
-  "$INCREMENTS_DIR/_paused"
-)
-
-FOUND_DUPLICATES=()
-
-for DIR in "${DIRS_TO_CHECK[@]}"; do
-  if [[ ! -d "$DIR" ]]; then
-    continue
-  fi
-
-  # Find all folders matching this increment number (including E suffix variants)
-  while IFS= read -r -d '' EXISTING_FOLDER; do
-    EXISTING_NAME=$(basename "$EXISTING_FOLDER")
-
-    # Extract number from existing folder
-    EXISTING_NUM=$(echo "$EXISTING_NAME" | grep -oE '^[0-9]{3,4}' | head -1)
-
-    if [[ -z "$EXISTING_NUM" ]]; then
-      continue
-    fi
-
-    EXISTING_NUM=$(printf "%04d" "$((10#$EXISTING_NUM))")
-
-    # Check if same base number (0121 matches 0121, 0121E, etc.)
-    if [[ "$EXISTING_NUM" == "$INCREMENT_NUM" ]]; then
-      # Skip if it's the exact same folder we're creating
-      if [[ "$EXISTING_NAME" == "$INCREMENT_FOLDER" ]]; then
-        continue
-      fi
-
-      # Found a duplicate!
-      FOUND_DUPLICATES+=("$EXISTING_NAME (in $(basename "$DIR"))")
-    fi
-  done < <(find "$DIR" -maxdepth 1 -type d -name "${INCREMENT_NUM}*" -print0 2>/dev/null)
-done
-
-# If duplicates found, WARN but ALLOW the operation (v1.0.37+: no blocking!)
-if [[ ${#FOUND_DUPLICATES[@]} -gt 0 ]]; then
-  # Format duplicates for JSON
-  DUP_LIST=""
-  for DUP in "${FOUND_DUPLICATES[@]}"; do
-    DUP_LIST="${DUP_LIST}\\n  - ${DUP}"
-  done
-
-  # Calculate the next available number using gap-filling strategy
-  EXISTING_NUMS=$(find "$INCREMENTS_DIR" "$INCREMENTS_DIR/_archive" "$INCREMENTS_DIR/_abandoned" "$INCREMENTS_DIR/_paused" -maxdepth 1 -type d -name "[0-9]*-*" 2>/dev/null | xargs -I {} basename {} | grep -oE '^[0-9]{3,4}' | sort -n | uniq)
-  NEXT_NUM=1
-  while echo "$EXISTING_NUMS" | grep -q "^$(printf "%04d" $NEXT_NUM)$\|^$(printf "%03d" $NEXT_NUM)$"; do
-    NEXT_NUM=$((NEXT_NUM + 1))
-  done
-  NEXT_NUM_PADDED=$(printf "%04d" $NEXT_NUM)
-
-  # Extract the name part from the attempted folder
-  FOLDER_NAME_PART=$(echo "$INCREMENT_FOLDER" | sed 's/^[0-9]\{3,4\}E\?-//')
-  SUGGESTED_FOLDER="${NEXT_NUM_PADDED}-${FOLDER_NAME_PART}"
-
-  # v1.0.37: ALLOW with WARNING instead of blocking
-  # User can still proceed - the warning provides guidance
-  printf '{"decision":"allow","message":"⚠️ DUPLICATE INCREMENT ID DETECTED\\n\\n✅ SUGGESTED: %s\\n⚠️ CURRENT: %s\\n\\nNumber %s already exists:%s\\n\\n💡 RECOMMENDATION: Consider using .specweave/increments/%s/ instead.\\n\\nOperation ALLOWED - proceeding with current path."}\n' "$SUGGESTED_FOLDER" "$INCREMENT_FOLDER" "$INCREMENT_NUM" "$DUP_LIST" "$SUGGESTED_FOLDER"
-  exit 0  # ALLOW with warning (v1.0.37: no blocking!)
-fi
-
-# No duplicates - allow
+set +e
 echo '{"decision":"allow"}'
 exit 0

package/plugins/specweave/hooks/v2/guards/metadata-json-guard.sh

@@ -1,98 +1,14 @@
 #!/bin/bash
+# metadata-json-guard.sh - DISABLED (v1.0.38)
 #
-# metadata-json-guard.sh
+# This guard was converted to WARNING-only in v1.0.37, and now completely
+# disabled in v1.0.38 per user feedback: "you MUST NEVER block such operations"
 #
-# Pre-tool-use hook that WARNS (not blocks) if metadata.json is missing before spec.md creation.
-# This helps ensure proper increment creation workflow.
+# Metadata validation should be handled by agents/scripts with proper business logic,
+# not by hooks that can interfere with file operations.
 #
-# ROOT CAUSE: When Claude creates increments via user prompt (not /sw:increment),
-# metadata.json may be forgotten, causing:
-# - Status tracking broken
-# - WIP limits don't work
-# - External sync fails (GitHub/Jira/ADO)
-# - All increment commands fail
-#
-# v1.0.37+: CRITICAL CHANGE - Now WARNS instead of BLOCKING!
-# User feedback: "you MUST NEVER block such operations... do at least warning"
-# Business logic and validation should be in scripts/agents, not hard blocks.
-#
-# SOLUTION: WARN if spec.md is created without metadata.json, but ALLOW the operation.
-# The warning prompts Claude to create metadata.json immediately after.
-#
-# Activation:
-# - tool_name: Write
-# - file_path matches: .specweave/increments/*/spec.md
-#
-# Returns exit 0 (allow) with warning message if metadata.json missing
-#
-# Bypass: Set SPECWEAVE_FORCE_METADATA=1 to skip validation
-#
-# v0.34.0 - Initial implementation based on user project bug analysis
-# v1.0.37 - Changed from BLOCK to WARN (allow with warning message)
-
-set +e  # CRITICAL: Never use set -e in hooks (causes cascading failures)
-
-# Check for force bypass
-if [ "$SPECWEAVE_FORCE_METADATA" = "1" ]; then
-  echo '{"decision": "allow", "message": "metadata.json guard bypassed (SPECWEAVE_FORCE_METADATA=1)"}'
-  exit 0
-fi
-
-# Disable hooks bypass
-if [ "$SPECWEAVE_DISABLE_HOOKS" = "1" ]; then
-  echo '{"decision": "allow"}'
-  exit 0
-fi
-
-# Read tool input from stdin (safe handling)
-INPUT=$(cat 2>/dev/null || echo '{}')
-
-# Check jq availability - allow if not present
-if ! command -v jq >/dev/null 2>&1; then
-  echo '{"decision": "allow"}'
-  exit 0
-fi
-
-# Extract tool name - with jq fallback
-TOOL_NAME=$(echo "$INPUT" | jq -r '.tool_name // .tool_input.tool_name // ""' 2>/dev/null || echo "")
-
-# Only validate Write tool calls
-if [ "$TOOL_NAME" != "Write" ]; then
-  echo '{"decision": "allow"}'
-  exit 0
-fi
-
-# Extract file path - handle both formats
-FILE_PATH=$(echo "$INPUT" | jq -r '.tool_input.file_path // .file_path // ""' 2>/dev/null || echo "")
-
-# Only validate spec.md files in increments folder
-# Match: 3-4 digits, optional E suffix, kebab-case name, spec.md
-if [[ ! "$FILE_PATH" =~ \.specweave/increments/([0-9]{3,4}E?-[^/]+)/spec\.md$ ]]; then
-  echo '{"decision": "allow"}'
-  exit 0
-fi
-
-# Extract increment folder path
-INCREMENT_DIR=$(dirname "$FILE_PATH")
-INCREMENT_ID="${BASH_REMATCH[1]}"
-
-# Check if metadata.json exists in the same increment folder
-METADATA_PATH="${INCREMENT_DIR}/metadata.json"
-
-if [ -f "$METADATA_PATH" ]; then
-  # metadata.json exists, allow spec.md creation
-  echo '{"decision": "allow"}'
-  exit 0
-fi
-
-# metadata.json doesn't exist - WARN but ALLOW spec.md creation (v1.0.37)
-NOW=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
-
-cat << WARN_EOF
-{
-  "decision": "allow",
-  "message": "⚠️ WARNING: metadata.json MISSING - Creating spec.md without it!\n\n🚨 IMMEDIATE ACTION REQUIRED:\nCreate metadata.json NOW for this increment to work properly.\n\nWithout metadata.json:\n  - ❌ Status tracking broken\n  - ❌ WIP limits don't work\n  - ❌ External sync fails (GitHub/Jira/ADO)\n  - ❌ All increment commands fail\n\n📋 CREATE metadata.json:\n   Write({\n     file_path: \"${METADATA_PATH}\",\n     content: {\n       \"id\": \"${INCREMENT_ID}\",\n       \"status\": \"planned\",\n       \"type\": \"feature\",\n       \"priority\": \"P1\",\n       \"created\": \"${NOW}\",\n       \"lastActivity\": \"${NOW}\",\n       \"testMode\": \"TDD\",\n       \"coverageTarget\": 95,\n       \"feature_id\": null,\n       \"epic_id\": null,\n       \"externalLinks\": {}\n     }\n   })\n\nOperation ALLOWED - proceeding with spec.md write."
-}
-WARN_EOF
+# This guard now does NOTHING - just allows all operations.
 
+set +e
+echo '{"decision":"allow"}'
 exit 0

package/plugins/specweave/hooks/v2/guards/spec-validation-guard.sh

@@ -1,175 +1,14 @@
 #!/bin/bash
-# spec-validation-guard.sh - Consolidated spec.md and living docs validation
+# spec-validation-guard.sh - DISABLED (v1.0.38)
 #
-# COMBINES (v0.35.4+):
-# - per-us-project-validator.sh (deleted) - Per-US **Project**: validation
-# - spec-project-validator.sh (deleted) - Placeholder detection
-# - project-folder-guard.sh (deleted) - Living docs folder validation
+# This guard was converted to WARNING-only in v1.0.37, and now completely
+# disabled in v1.0.38 per user feedback: "you MUST NEVER block such operations"
 #
-# Activation:
-# - tool_name: Write
-# - file_path matches: .specweave/increments/*/spec.md OR .specweave/docs/internal/specs/*/
+# Spec validation should be handled by agents/scripts with proper business logic,
+# not by hooks that can interfere with file operations.
 #
-# v1.0.37+: CRITICAL CHANGE - All validations now WARN instead of BLOCK!
-# User feedback: "you MUST NEVER block such operations... do at least warning"
-# Business logic and validation should be in scripts/agents, not hard blocks.
-#
-# Exit 0 = allow (with JSON warning message if validation fails)
-#
-# Bypasses:
-# - SPECWEAVE_DISABLE_HOOKS=1 - Disable all hooks
-# - SPECWEAVE_FORCE_PROJECT=1 - Skip project validation
-# - SPECWEAVE_FORCE_METADATA=1 - Skip all spec validation
-
-set +e  # CRITICAL: Never use set -e in hooks
-
-# Source shared library if available
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-LIB_DIR="${SCRIPT_DIR}/../../lib"
-if [[ -f "$LIB_DIR/common-setup.sh" ]]; then
-  source "$LIB_DIR/common-setup.sh"
-  init_pretool_guard || exit 0
-else
-  # Fallback inline implementation
-  [[ "${SPECWEAVE_DISABLE_HOOKS:-0}" == "1" ]] && echo '{"decision":"allow"}' && exit 0
-  HOOK_INPUT=$(cat 2>/dev/null || echo '{}')
-  if ! command -v jq >/dev/null 2>&1; then
-    echo '{"decision":"allow"}'
-    exit 0
-  fi
-  HOOK_TOOL_NAME=$(echo "$HOOK_INPUT" | jq -r '.tool_name // ""' 2>/dev/null || echo "")
-  HOOK_FILE_PATH=$(echo "$HOOK_INPUT" | jq -r '.tool_input.file_path // .file_path // ""' 2>/dev/null || echo "")
-  HOOK_CONTENT=$(echo "$HOOK_INPUT" | jq -r '.tool_input.content // .tool_input.new_string // ""' 2>/dev/null || echo "")
-fi
-
-# Check bypass flags
-[[ "$SPECWEAVE_FORCE_PROJECT" == "1" ]] && echo '{"decision":"allow","message":"Project validation bypassed"}' && exit 0
-[[ "$SPECWEAVE_FORCE_METADATA" == "1" ]] && echo '{"decision":"allow","message":"Spec validation bypassed"}' && exit 0
-
-# Only validate Write tool
-[[ "$HOOK_TOOL_NAME" != "Write" ]] && echo '{"decision":"allow"}' && exit 0
-
-# No file path = allow
-[[ -z "$HOOK_FILE_PATH" ]] && echo '{"decision":"allow"}' && exit 0
-
-# ============================================================================
-# VALIDATION 1: spec.md placeholder detection
-# ============================================================================
-if [[ "$HOOK_FILE_PATH" =~ \.specweave/increments/[0-9]{3,4}E?-[^/]+/spec\.md$ ]]; then
-
-  # Check for unresolved {{...}} placeholders - WARN only (v1.0.37)
-  if echo "$HOOK_CONTENT" | grep -qE '\{\{[A-Z_]+\}\}'; then
-    PLACEHOLDERS=$(echo "$HOOK_CONTENT" | grep -oE '\{\{[A-Z_]+\}\}' | sort -u | tr '\n' ', ' | sed 's/,$//')
-    printf '{"decision":"allow","message":"⚠️ UNRESOLVED PLACEHOLDERS DETECTED\\n\\nFound: %s\\n\\n🔧 FIX: Replace placeholders with actual values.\\nRun: specweave context projects\\nThen use values from the JSON output.\\n\\nOperation ALLOWED - proceeding anyway."}\n' "$PLACEHOLDERS"
-    exit 0
-  fi
-
-  # Check for **Project**: field in User Stories (soft validation - warn, don't block)
-  # Pattern: ### US-XXX or #### US-XXX followed by **Project**:
-  US_COUNT=$(echo "$HOOK_CONTENT" | grep -cE '^#{3,4} US-' 2>/dev/null || echo "0")
-  PROJECT_COUNT=$(echo "$HOOK_CONTENT" | grep -cE '^\*\*Project\*\*:' 2>/dev/null || echo "0")
-
-  # Trim to just the number
-  US_COUNT="${US_COUNT//[^0-9]/}"
-  PROJECT_COUNT="${PROJECT_COUNT//[^0-9]/}"
-  [[ -z "$US_COUNT" ]] && US_COUNT=0
-  [[ -z "$PROJECT_COUNT" ]] && PROJECT_COUNT=0
-
-  # Only warn if there are User Stories but no Project fields
-  # Don't block - just allow with warning
-  if [[ "$US_COUNT" -gt 0 ]] && [[ "$PROJECT_COUNT" -eq 0 ]]; then
-    echo '{"decision":"allow","message":"⚠️ WARNING: No **Project**: fields found. Add **Project**: after each US heading for proper sync."}'
-    exit 0
-  fi
-
-  # Check for comma-separated projects (1:1 mapping required) - WARN only (v1.0.37)
-  if echo "$HOOK_CONTENT" | grep -qE '^\*\*Project\*\*:.*,'; then
-    printf '{"decision":"allow","message":"⚠️ MULTIPLE PROJECTS IN ONE US DETECTED\\n\\nEach User Story should map to exactly ONE project.\\n\\n💡 RECOMMENDATION: Split cross-project features into separate User Stories:\\n\\nWRONG:\\n### US-001: OAuth Implementation\\n**Project**: frontend, backend\\n\\nCORRECT:\\n### US-001: OAuth Login Form\\n**Project**: frontend\\n\\n### US-002: OAuth API\\n**Project**: backend\\n\\nOperation ALLOWED - proceeding anyway."}\n'
-    exit 0
-  fi
-
-  # Check structure level to validate **Board**: fields
-  # For 1-level structures (GitHub), **Board**: should NOT be present
-  # For 2-level structures (ADO/JIRA with boards), **Board**: is required
-  # NOTE: This is a WARNING only - do NOT block spec writes!
-  PROJECT_ROOT="${HOOK_FILE_PATH%%/.specweave/*}"
-  BOARD_COUNT=$(echo "$HOOK_CONTENT" | grep -cE '^\*\*Board\*\*:' 2>/dev/null || echo "0")
-  BOARD_COUNT="${BOARD_COUNT//[^0-9]/}"
-  [[ -z "$BOARD_COUNT" ]] && BOARD_COUNT=0
-
-  if [[ "$BOARD_COUNT" -gt 0 ]]; then
-    # Has **Board**: fields - check if this is a 2-level structure
-    CONFIG_FILE="$PROJECT_ROOT/.specweave/config.json"
-    IS_2LEVEL="false"
-
-    if [[ -f "$CONFIG_FILE" ]]; then
-      # 2-level indicators: ADO areaPathMapping, JIRA boardMapping with multiple boards
-      HAS_AREA_MAPPING=$(jq -r '.sync.profiles | to_entries[] | select(.value.provider == "ado") | .value.config.areaPathMapping.mappings | length > 0' "$CONFIG_FILE" 2>/dev/null | grep -c "true" || echo "0")
-      HAS_BOARD_MAPPING=$(jq -r '.sync.profiles | to_entries[] | select(.value.provider == "jira") | .value.config.boardMapping.boards | length > 1' "$CONFIG_FILE" 2>/dev/null | grep -c "true" || echo "0")
-      HAS_MULTI_TEAMS=$(jq -r '.umbrella.childRepos | map(.team) | unique | length > 1' "$CONFIG_FILE" 2>/dev/null || echo "false")
-
-      if [[ "$HAS_AREA_MAPPING" -gt 0 ]] || [[ "$HAS_BOARD_MAPPING" -gt 0 ]] || [[ "$HAS_MULTI_TEAMS" == "true" ]]; then
-        IS_2LEVEL="true"
-      fi
-    fi
-
-    # WARN only - never block spec.md writes (too disruptive)
-    if [[ "$IS_2LEVEL" != "true" ]]; then
-      echo '{"decision":"allow","message":"⚠️ WARNING: **Board**: fields found but this is a 1-level structure (GitHub). Board fields are only needed for ADO/JIRA with multiple boards. Consider removing **Board**: lines."}'
-      exit 0
-    fi
-  fi
-
-  echo '{"decision":"allow"}'
-  exit 0
-fi
-
-# ============================================================================
-# VALIDATION 2: Living docs folder validation
-# ============================================================================
-if [[ "$HOOK_FILE_PATH" =~ \.specweave/docs/internal/specs/([^/]+)/ ]]; then
-  PROJECT_NAME="${BASH_REMATCH[1]}"
-
-  # Skip README.md and _features/_archive special folders
-  [[ "$PROJECT_NAME" == "README.md" ]] && echo '{"decision":"allow"}' && exit 0
-  [[ "$PROJECT_NAME" == "_features" ]] && echo '{"decision":"allow"}' && exit 0
-  [[ "$PROJECT_NAME" == "_archive" ]] && echo '{"decision":"allow"}' && exit 0
-
-  # Check for template placeholders - WARN only (v1.0.37)
-  if [[ "$PROJECT_NAME" =~ \{\{.*\}\} ]]; then
-    printf '{"decision":"allow","message":"⚠️ UNRESOLVED PLACEHOLDER: %s\\n\\n🔧 FIX: Replace {{...}} with actual project name\\n\\nOperation ALLOWED - proceeding anyway."}\n' "$PROJECT_NAME"
-    exit 0
-  fi
-
-  # Check for comma-separated (invalid) - WARN only (v1.0.37)
-  if [[ "$PROJECT_NAME" =~ , ]]; then
-    printf '{"decision":"allow","message":"⚠️ COMMA-SEPARATED PROJECTS: %s\\n\\nEach User Story should have ONE project folder.\\n\\n💡 RECOMMENDATION: Split into separate specs\\n\\nOperation ALLOWED - proceeding anyway."}\n' "$PROJECT_NAME"
-    exit 0
-  fi
-
-  # Check for common example/placeholder names - WARN only (v1.0.37)
-  EXAMPLE_NAMES="frontend-app|backend-api|mobile-app|shared-lib|acme-corp|my-app|myapp|example-project|test-project"
-  if [[ "$PROJECT_NAME" =~ ^($EXAMPLE_NAMES)$ ]]; then
-    # Try to get valid projects from config
-    PROJECT_ROOT="${HOOK_FILE_PATH%%/.specweave/*}"
-    CONFIG_FILE="$PROJECT_ROOT/.specweave/config.json"
-
-    if [[ -f "$CONFIG_FILE" ]]; then
-      # Check if this example name is actually configured
-      IS_CONFIGURED=$(jq -r --arg name "$PROJECT_NAME" '.multiProject.projects[$name] // .project.name == $name' "$CONFIG_FILE" 2>/dev/null || echo "false")
-
-      if [[ "$IS_CONFIGURED" != "true" ]]; then
-        VALID_PROJECTS=$(jq -r '.multiProject.projects | keys | join(", ") // .project.name // "specweave"' "$CONFIG_FILE" 2>/dev/null || echo "specweave")
-        printf '{"decision":"allow","message":"⚠️ EXAMPLE PROJECT NAME DETECTED: %s\\n\\nThis looks like a placeholder/example name from documentation.\\n\\nConfigured projects: %s\\n\\n💡 RECOMMENDATION: Edit spec.md and use a real project name\\n\\nOperation ALLOWED - proceeding anyway."}\n' "$PROJECT_NAME" "$VALID_PROJECTS"
-        exit 0
-      fi
-    fi
-  fi
-
-  echo '{"decision":"allow"}'
-  exit 0
-fi
+# This guard now does NOTHING - just allows all operations.
 
-# Not a spec.md or living docs file - allow
+set +e
 echo '{"decision":"allow"}'
 exit 0

package/plugins/specweave/hooks/v2/guards/metadata-json-guard.test.sh

@@ -1,302 +0,0 @@
-#!/bin/bash
-# Comprehensive test suite for metadata-json-guard.sh
-# Tests that spec.md creation is blocked when metadata.json is missing
-#
-# Usage: bash metadata-json-guard.test.sh
-#
-# v0.34.0 - Initial test suite
-
-set -e
-
-GUARD="$(dirname "$0")/metadata-json-guard.sh"
-TEST_DIR=$(mktemp -d)
-PASS=0
-FAIL=0
-TOTAL=0
-
-# Colors for output
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-NC='\033[0m' # No Color
-
-cleanup() {
-  rm -rf "$TEST_DIR"
-}
-trap cleanup EXIT
-
-# Create test increment structure
-setup_test_increment() {
-  local with_metadata="$1"
-  local increment_name="${2:-0001-test-feature}"
-
-  mkdir -p "$TEST_DIR/.specweave/increments/$increment_name"
-
-  if [ "$with_metadata" = "true" ]; then
-    cat > "$TEST_DIR/.specweave/increments/$increment_name/metadata.json" << 'EOF'
-{
-  "id": "0001-test-feature",
-  "status": "planned",
-  "type": "feature",
-  "priority": "P1",
-  "created": "2025-12-10T00:00:00Z",
-  "lastActivity": "2025-12-10T00:00:00Z",
-  "testMode": "TDD",
-  "coverageTarget": 95,
-  "feature_id": null,
-  "epic_id": null,
-  "externalLinks": {}
-}
-EOF
-  fi
-}
-
-# Test helper: should block
-test_should_block() {
-  local name="$1"
-  local file_path="$2"
-  local content="$3"
-  TOTAL=$((TOTAL + 1))
-
-  # Build JSON input for the guard
-  local json_input
-  json_input=$(jq -n \
-    --arg tool_name "Write" \
-    --arg file_path "$file_path" \
-    --arg content "$content" \
-    '{tool_name: $tool_name, tool_input: {file_path: $file_path, content: $content}}')
-
-  result=$(echo "$json_input" | bash "$GUARD" 2>&1; echo "EXIT:$?")
-  exit_code=$(echo "$result" | grep -o 'EXIT:[0-9]*' | cut -d: -f2)
-
-  if [[ "$exit_code" == "2" ]]; then
-    echo -e "${GREEN}✓ BLOCKED${NC}: $name"
-    PASS=$((PASS + 1))
-  else
-    echo -e "${RED}✗ NOT BLOCKED${NC}: $name"
-    echo "  File: $file_path"
-    echo "  Exit code: $exit_code (expected 2)"
-    echo "  Output: $(echo "$result" | head -5)"
-    FAIL=$((FAIL + 1))
-  fi
-}
-
-# Test helper: should allow
-test_should_allow() {
-  local name="$1"
-  local file_path="$2"
-  local content="$3"
-  TOTAL=$((TOTAL + 1))
-
-  # Build JSON input for the guard
-  local json_input
-  json_input=$(jq -n \
-    --arg tool_name "Write" \
-    --arg file_path "$file_path" \
-    --arg content "$content" \
-    '{tool_name: $tool_name, tool_input: {file_path: $file_path, content: $content}}')
-
-  result=$(echo "$json_input" | bash "$GUARD" 2>&1; echo "EXIT:$?")
-  exit_code=$(echo "$result" | grep -o 'EXIT:[0-9]*' | cut -d: -f2)
-
-  if [[ "$exit_code" == "0" ]]; then
-    echo -e "${GREEN}✓ ALLOWED${NC}: $name"
-    PASS=$((PASS + 1))
-  else
-    echo -e "${RED}✗ WRONGLY BLOCKED${NC}: $name"
-    echo "  File: $file_path"
-    echo "  Exit code: $exit_code (expected 0)"
-    FAIL=$((FAIL + 1))
-  fi
-}
-
-# Test non-Write tools (should always allow)
-test_non_write_tool() {
-  local name="$1"
-  local tool_name="$2"
-  TOTAL=$((TOTAL + 1))
-
-  local json_input
-  json_input=$(jq -n \
-    --arg tool_name "$tool_name" \
-    --arg file_path "$TEST_DIR/.specweave/increments/0001-test/spec.md" \
-    '{tool_name: $tool_name, tool_input: {file_path: $file_path}}')
-
-  result=$(echo "$json_input" | bash "$GUARD" 2>&1; echo "EXIT:$?")
-  exit_code=$(echo "$result" | grep -o 'EXIT:[0-9]*' | cut -d: -f2)
-
-  if [[ "$exit_code" == "0" ]]; then
-    echo -e "${GREEN}✓ ALLOWED (non-Write)${NC}: $name"
-    PASS=$((PASS + 1))
-  else
-    echo -e "${RED}✗ WRONGLY BLOCKED${NC}: $name"
-    FAIL=$((FAIL + 1))
-  fi
-}
-
-echo "========================================"
-echo "  METADATA JSON GUARD - COMPREHENSIVE TESTS"
-echo "========================================"
-echo ""
-echo "Test directory: $TEST_DIR"
-echo ""
-
-echo -e "${YELLOW}=== CORE FUNCTIONALITY: BLOCK WHEN METADATA MISSING ===${NC}"
-
-# Setup without metadata
-setup_test_increment "false" "0001-no-metadata"
-test_should_block "spec.md without metadata.json (3-digit)" \
-  "$TEST_DIR/.specweave/increments/0001-no-metadata/spec.md" \
-  "---\nincrement: 0001-no-metadata\n---"
-
-setup_test_increment "false" "0012-no-metadata"
-test_should_block "spec.md without metadata.json (4-digit)" \
-  "$TEST_DIR/.specweave/increments/0012-no-metadata/spec.md" \
-  "---\nincrement: 0012-no-metadata\n---"
-
-setup_test_increment "false" "123-short"
-test_should_block "spec.md without metadata.json (3-digit short)" \
-  "$TEST_DIR/.specweave/increments/123-short/spec.md" \
-  "---\nincrement: 123-short\n---"
-
-setup_test_increment "false" "0001E-external"
-test_should_block "spec.md without metadata.json (external E suffix)" \
-  "$TEST_DIR/.specweave/increments/0001E-external/spec.md" \
-  "---\nincrement: 0001E-external\n---"
-
-echo ""
-echo -e "${YELLOW}=== CORE FUNCTIONALITY: ALLOW WHEN METADATA EXISTS ===${NC}"
-
-# Setup with metadata
-setup_test_increment "true" "0002-has-metadata"
-test_should_allow "spec.md WITH metadata.json present" \
-  "$TEST_DIR/.specweave/increments/0002-has-metadata/spec.md" \
-  "---\nincrement: 0002-has-metadata\n---"
-
-setup_test_increment "true" "0123E-external-with-meta"
-test_should_allow "spec.md WITH metadata.json (external E suffix)" \
-  "$TEST_DIR/.specweave/increments/0123E-external-with-meta/spec.md" \
-  "---\nincrement: 0123E-external-with-meta\n---"
-
-echo ""
-echo -e "${YELLOW}=== NON-SPEC FILES: SHOULD NOT VALIDATE ===${NC}"
-
-# Create increment without metadata for these tests
-setup_test_increment "false" "0003-other-files"
-test_should_allow "plan.md (not spec.md)" \
-  "$TEST_DIR/.specweave/increments/0003-other-files/plan.md" \
-  "# Plan"
-
-test_should_allow "tasks.md (not spec.md)" \
-  "$TEST_DIR/.specweave/increments/0003-other-files/tasks.md" \
-  "# Tasks"
-
-test_should_allow "metadata.json itself" \
-  "$TEST_DIR/.specweave/increments/0003-other-files/metadata.json" \
-  '{"id": "test"}'
-
-test_should_allow "report in subfolder" \
-  "$TEST_DIR/.specweave/increments/0003-other-files/reports/COMPLETION.md" \
-  "# Report"
-
-echo ""
-echo -e "${YELLOW}=== FILES OUTSIDE INCREMENTS: SHOULD NOT VALIDATE ===${NC}"
-
-test_should_allow "spec.md outside increments (docs)" \
-  "$TEST_DIR/.specweave/docs/internal/spec.md" \
-  "# Documentation"
-
-test_should_allow "spec.md in root" \
-  "$TEST_DIR/spec.md" \
-  "# Root spec"
-
-test_should_allow "Random file" \
-  "$TEST_DIR/random.txt" \
-  "Random content"
-
-echo ""
-echo -e "${YELLOW}=== NON-WRITE TOOLS: SHOULD ALWAYS ALLOW ===${NC}"
-
-test_non_write_tool "Read tool" "Read"
-test_non_write_tool "Edit tool" "Edit"
-test_non_write_tool "Glob tool" "Glob"
-test_non_write_tool "Grep tool" "Grep"
-test_non_write_tool "Bash tool" "Bash"
-
-echo ""
-echo -e "${YELLOW}=== BYPASS MODES ===${NC}"
-
-# Test SPECWEAVE_FORCE_METADATA bypass
-setup_test_increment "false" "0004-bypass"
-TOTAL=$((TOTAL + 1))
-json_input=$(jq -n \
-  --arg tool_name "Write" \
-  --arg file_path "$TEST_DIR/.specweave/increments/0004-bypass/spec.md" \
-  --arg content "---\nincrement: 0004-bypass\n---" \
-  '{tool_name: $tool_name, tool_input: {file_path: $file_path, content: $content}}')
-
-result=$(SPECWEAVE_FORCE_METADATA=1 bash -c "echo '$json_input' | bash '$GUARD'" 2>&1; echo "EXIT:$?")
-exit_code=$(echo "$result" | grep -o 'EXIT:[0-9]*' | cut -d: -f2)
-if [[ "$exit_code" == "0" ]] && echo "$result" | grep -q "bypassed"; then
-  echo -e "${GREEN}✓ ALLOWED (bypass)${NC}: SPECWEAVE_FORCE_METADATA=1 works"
-  PASS=$((PASS + 1))
-else
-  echo -e "${RED}✗ BYPASS FAILED${NC}: SPECWEAVE_FORCE_METADATA=1"
-  echo "  Exit code: $exit_code"
-  FAIL=$((FAIL + 1))
-fi
-
-# Test SPECWEAVE_DISABLE_HOOKS bypass
-TOTAL=$((TOTAL + 1))
-result=$(SPECWEAVE_DISABLE_HOOKS=1 bash -c "echo '$json_input' | bash '$GUARD'" 2>&1; echo "EXIT:$?")
-exit_code=$(echo "$result" | grep -o 'EXIT:[0-9]*' | cut -d: -f2)
-if [[ "$exit_code" == "0" ]]; then
-  echo -e "${GREEN}✓ ALLOWED (bypass)${NC}: SPECWEAVE_DISABLE_HOOKS=1 works"
-  PASS=$((PASS + 1))
-else
-  echo -e "${RED}✗ BYPASS FAILED${NC}: SPECWEAVE_DISABLE_HOOKS=1"
-  FAIL=$((FAIL + 1))
-fi
-
-echo ""
-echo -e "${YELLOW}=== EDGE CASES ===${NC}"
-
-# Test with empty file path
-TOTAL=$((TOTAL + 1))
-json_input='{"tool_name": "Write", "tool_input": {"file_path": "", "content": "test"}}'
-result=$(echo "$json_input" | bash "$GUARD" 2>&1; echo "EXIT:$?")
-exit_code=$(echo "$result" | grep -o 'EXIT:[0-9]*' | cut -d: -f2)
-if [[ "$exit_code" == "0" ]]; then
-  echo -e "${GREEN}✓ ALLOWED${NC}: Empty file path"
-  PASS=$((PASS + 1))
-else
-  echo -e "${RED}✗ FAILED${NC}: Empty file path should be allowed"
-  FAIL=$((FAIL + 1))
-fi
-
-# Test with malformed JSON (should fail gracefully)
-TOTAL=$((TOTAL + 1))
-result=$(echo "not json" | bash "$GUARD" 2>&1; echo "EXIT:$?")
-exit_code=$(echo "$result" | grep -o 'EXIT:[0-9]*' | cut -d: -f2)
-if [[ "$exit_code" == "0" ]]; then
-  echo -e "${GREEN}✓ ALLOWED${NC}: Malformed JSON handled gracefully"
-  PASS=$((PASS + 1))
-else
-  echo -e "${RED}✗ FAILED${NC}: Malformed JSON should be allowed (fail-safe)"
-  FAIL=$((FAIL + 1))
-fi
-
-echo ""
-echo "========================================"
-echo "  RESULTS"
-echo "========================================"
-echo -e "Total: $TOTAL"
-echo -e "${GREEN}Passed: $PASS${NC}"
-if [[ $FAIL -gt 0 ]]; then
-  echo -e "${RED}Failed: $FAIL${NC}"
-  exit 1
-else
-  echo -e "Failed: 0"
-  echo ""
-  echo -e "${GREEN}ALL TESTS PASSED!${NC}"
-fi