@paths.design/caws-cli 10.1.0 → 11.0.0

package/dist/templates/.cursor/hooks/naming-check.sh

@@ -1,64 +0,0 @@
-#!/bin/bash
-# Cursor Hook: Naming Conventions
-# 
-# Purpose: Enforce CAWS naming conventions (no enhanced-, -copy, etc.)
-# Event: afterFileEdit
-# 
-# @author @darianrosebrook
-
-set -euo pipefail
-
-# Read input from Cursor
-INPUT=$(cat)
-
-# Extract file path
-FILE_PATH=$(echo "$INPUT" | jq -r '.file_path // ""')
-
-# Get just the filename
-FILENAME=$(basename "$FILE_PATH")
-
-# Check for banned naming patterns
-BANNED_PATTERNS=(
-  "enhanced-"
-  "-enhanced"
-  "unified-"
-  "-unified"
-  "better-"
-  "-better"
-  "new-"
-  "-new"
-  "next-"
-  "-next"
-  "final-"
-  "-final"
-  "-copy"
-  "copy-"
-  "-revamp"
-  "revamp-"
-  "-improved"
-  "improved-"
-)
-
-for pattern in "${BANNED_PATTERNS[@]}"; do
-  if [[ "$FILENAME" == *"$pattern"* ]]; then
-    # Extract the pattern for the message
-    echo '{"userMessage":"⚠️ Naming violation: File contains banned pattern '"'$pattern'"'. Use purpose-driven names instead.","agentMessage":"This file uses a generic naming pattern ('"$pattern"'). Please rename with a specific, purpose-driven name that describes what the file does."}' 2>/dev/null
-    exit 0
-  fi
-done
-
-# Check for duplicate module patterns (e.g., both processor.ts and enhanced-processor.ts)
-if [[ "$FILENAME" =~ ^(enhanced|unified|better|new|next|final|improved)- ]]; then
-  BASE_NAME=$(echo "$FILENAME" | sed -E 's/^(enhanced|unified|better|new|next|final|improved)-//')
-  DIR_PATH=$(dirname "$FILE_PATH")
-  
-  # Check if base file exists
-  if [ -f "$DIR_PATH/$BASE_NAME" ]; then
-    echo '{"userMessage":"⚠️ Duplicate module detected: Both '"$FILENAME"' and '"$BASE_NAME"' exist. Merge into canonical name.","agentMessage":"Found duplicate modules. Please merge '"$FILENAME"' into '"$BASE_NAME"' and remove the duplicate."}' 2>/dev/null
-    exit 0
-  fi
-fi
-
-# Allow by default
-exit 0
-

package/dist/templates/.cursor/hooks/scan-secrets.sh

@@ -1,51 +0,0 @@
-#!/bin/bash
-# Cursor Hook: Secret & PII Scanner
-# 
-# Purpose: Prevent reading files with secrets or sensitive information
-# Event: beforeReadFile
-# 
-# @author @darianrosebrook
-
-set -euo pipefail
-
-# Read input from Cursor
-INPUT=$(cat)
-
-# Extract file path and content
-FILE_PATH=$(echo "$INPUT" | jq -r '.file_path // ""')
-CONTENT=$(echo "$INPUT" | jq -r '.content // ""')
-
-# Block reading of environment files
-if [[ "$FILE_PATH" =~ \.(env|env\.local|env\.development|env\.production|env\.test)$ ]]; then
-  echo '{"permission":"deny","userMessage":"⚠️ Blocked: Environment files contain secrets. Use placeholder values instead."}' 2>/dev/null
-  exit 0
-fi
-
-# Block reading of key files
-if [[ "$FILE_PATH" =~ \.(pem|key|p12|pfx|cert|crt)$ ]]; then
-  echo '{"permission":"deny","userMessage":"⚠️ Blocked: Certificate/key files should not be read by AI."}' 2>/dev/null
-  exit 0
-fi
-
-# Scan content for common secret patterns
-# bearer requires 20+ chars to avoid false positives on short tokens in docs
-# AKIA prefix is specific to AWS access keys
-if echo "$CONTENT" | grep -qiE "(api[_-]?key\s*[:=]\s*['\"]?[A-Za-z0-9_\-]{16,}|secret[_-]?key\s*[:=]\s*['\"]?[A-Za-z0-9_\-]{16,}|password\s*[:=]\s*['\"]?[^\s'\"]{8,}|private[_-]?key\s*[:=]|access[_-]?token\s*[:=]\s*['\"]?[A-Za-z0-9_\-]{16,}|[Bb]earer\s+[A-Za-z0-9_\-\.]{20,}|AKIA[0-9A-Z]{16})"; then
-  # Don't block, but warn
-  echo '{"permission":"allow","userMessage":"⚠️ Warning: Potential secrets detected in file. Ensure they are not committed.","agentMessage":"This file may contain secrets. Use placeholder values or environment variables."}' 2>/dev/null
-  exit 0
-fi
-
-# Check for common PII patterns (SSN, credit card)
-# SSN: exactly 3-2-4 digit pattern (not inside longer numbers)
-# Credit card: require at least a Luhn-plausible 13-19 digit sequence with separators
-if echo "$CONTENT" | grep -qE "(^|[^0-9])[0-9]{3}-[0-9]{2}-[0-9]{4}($|[^0-9])" || \
-   echo "$CONTENT" | grep -qE "(^|[^0-9])[0-9]{4}[- ][0-9]{4}[- ][0-9]{4}[- ][0-9]{4}($|[^0-9])"; then
-  echo '{"permission":"allow","userMessage":"⚠️ Warning: Potential PII detected. Ensure compliance with data protection policies.","agentMessage":"This file may contain PII (SSN, credit card). Use anonymized test data."}' 2>/dev/null
-  exit 0
-fi
-
-# Allow by default
-echo '{"permission":"allow"}' 2>/dev/null
-exit 0
-

package/dist/templates/.cursor/hooks/scope-guard.sh

@@ -1,52 +0,0 @@
-#!/bin/bash
-# Cursor Hook: Scope Guard
-# 
-# Purpose: Check if files being worked on are within working-spec scope
-# Event: beforeSubmitPrompt
-# 
-# @author @darianrosebrook
-
-set -euo pipefail
-
-# Read input from Cursor
-INPUT=$(cat)
-
-# Extract attachments
-ATTACHMENTS=$(echo "$INPUT" | jq -r '.attachments // []')
-
-# Only check if we have file attachments and a working spec
-if [ ! -f ".caws/working-spec.yaml" ] && [ ! -f ".caws/working-spec.yml" ]; then
-  # No spec file, allow by default
-  echo '{"continue":true}' 2>/dev/null
-  exit 0
-fi
-
-# Check if scope-guard tool exists
-if [ -f ".caws/tools/scope-guard.js" ]; then
-  # Extract file paths from attachments
-  FILE_PATHS=$(echo "$ATTACHMENTS" | jq -r '.[] | select(.type=="file") | .file_path' 2>/dev/null || echo "")
-  
-  if [ -n "$FILE_PATHS" ]; then
-    # Check each file against scope
-    OUT_OF_SCOPE=()
-    while IFS= read -r file; do
-      if [ -n "$file" ]; then
-        if ! node .caws/tools/scope-guard.js check "$file" 2>/dev/null; then
-          OUT_OF_SCOPE+=("$file")
-        fi
-      fi
-    done <<< "$FILE_PATHS"
-    
-    # If any files are out of scope, warn but don't block
-    if [ ${#OUT_OF_SCOPE[@]} -gt 0 ]; then
-      FILES_LIST=$(printf '%s\n' "${OUT_OF_SCOPE[@]}")
-      echo '{"continue":true,"userMessage":"⚠️ Warning: Some attached files may be outside working-spec scope:\n'"$FILES_LIST"'","agentMessage":"Some files are outside the defined scope in working-spec.yaml. Consider updating the scope or removing these files."}' 2>/dev/null
-      exit 0
-    fi
-  fi
-fi
-
-# Allow by default
-echo '{"continue":true}' 2>/dev/null
-exit 0
-