Merge pull request #113 from Hypercart-Dev-Tools/development

Development to Main

Author: noelsaw1

CHANGELOG.md

@@ -5,6 +5,113 @@ All notable changes to this project 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).
 
+## [Unreleased]
+
+---
+
+## [2.2.5] - 2026-02-07
+
+### Added
+
+#### .wpcignore Support - Exclude Directories from Scans
+
+- **Added .wpcignore file support** (similar to .gitignore) to exclude directories and files from scans
+  - Automatically loads exclusions from `.wpcignore` in scan path, current directory, or repository root
+  - Supports directory patterns (e.g., `tools/`, `.git/`, `node_modules/`)
+  - Supports file patterns with wildcards (e.g., `*.min.js`, `*.log`)
+  - Comments (lines starting with `#`) and empty lines are ignored
+  - **Impact:** Prevents scanning embedded dependencies, version control files, and build artifacts
+  - **Use case:** Prevents recursive scanning when AI-DDTK scans itself (WPCC embedded at `tools/wp-code-check/`)
+
+- **Created .wpcignore template** at `dist/templates/.wpcignore.template`
+  - Sensible defaults: `tools/`, `.git/`, `node_modules/`, `vendor/`, `dist/logs/`, `dist/reports/`
+  - Minified files: `*.min.js`, `*.min.css`, `*bundle*.js`
+  - Organized by category with comments explaining each exclusion
+  - Ready to copy to project root and customize
+
+- **Created .wpcignore for AI-DDTK** at `/Users/noelsaw/Documents/GH Repos/AI-DDTK/.wpcignore`
+  - Excludes `tools/` directory to prevent WPCC from scanning its own embedded copy
+  - Prevents timeout/stalling issues when scanning AI-DDTK repository
+
+#### Progress Indicators for Magic String Detector
+
+- **Added progress indicators to Magic String Detector aggregation loops**
+  - Shows "Processing match X of Y..." every 10 seconds during string extraction (lines 2582-2619)
+  - Shows "Analyzing string X of Y..." every 10 seconds during string aggregation (lines 2631-2687)
+  - Follows same pattern as clone detection progress indicators (added in v1.0.85)
+  - **Impact:** Users can see progress during long scans, reducing perceived wait time
+  - **Fixes:** Stalling/timeout issues reported when scanning large codebases (10K+ files)
+
+#### --skip-magic-strings Flag - Last Resort for Timeout Issues
+
+- **Added `--skip-magic-strings` command-line flag** to completely skip Magic String Detector phase
+  - **Alias:** `--disable-magic-strings` (both flags work identically)
+  - **Use case:** Last resort option when scans timeout during Magic String Detector aggregation
+  - **Behavior:** Shows warning message "⚠ Skipped (--skip-magic-strings flag enabled)" and bypasses entire phase
+  - **Pattern:** Follows same approach as existing `--skip-clone-detection` flag
+  - **Impact:** Allows scans to complete even when Magic String Detector would timeout
+  - **Trade-off:** Skips detection of duplicate option names, transient keys, and capability strings
+  - **Examples:**
+    - `wpcc --paths . --skip-magic-strings --format json`
+    - `wpcc --paths . --disable-magic-strings --format json` (alias)
+
+### Changed
+
+- **Improved exclusion handling in clone detection and file caching**
+  - Clone detection now uses dynamic `GREP_EXCLUSIONS` from `EXCLUDE_DIRS` (includes .wpcignore entries)
+  - File caching now applies .wpcignore exclusions instead of hardcoded `vendor/` and `node_modules/`
+  - Added `build_grep_exclusions()` helper function to convert `EXCLUDE_DIRS` to grep -v commands
+  - **Impact:** Consistent exclusion behavior across all scan phases
+
+### Technical Details
+
+- **Files Modified:**
+  - `dist/bin/check-performance.sh`:
+    - Added `SKIP_MAGIC_STRINGS=false` variable (line 150)
+    - Added `--skip-magic-strings` and `--disable-magic-strings` to help text (lines 471-472)
+    - Added argument parsing for both flags (line 834: `--skip-magic-strings|--disable-magic-strings`)
+    - Added skip logic for Magic String Detector (lines 6201-6218, closing fi at line 6272)
+    - Added `load_wpcignore()` function (lines 900-941)
+    - Added `build_grep_exclusions()` helper (lines 960-970)
+    - Updated `process_aggregated_pattern()` with progress indicators (lines 2579-2687)
+    - Updated `process_clone_detection()` to use dynamic exclusions (lines 2815-2834)
+    - Updated file caching to use dynamic exclusions (lines 3337-3347)
+  - `dist/templates/.wpcignore.template` - Created
+  - `/Users/noelsaw/Documents/GH Repos/AI-DDTK/.wpcignore` - Created
+
+- **Version:** Bumped to 2.2.5
+
+### Documentation
+
+- **TODO:** Update README.md with .wpcignore documentation
+- **TODO:** Update SHELL-QUICKSTART.md with .wpcignore usage
+- **TODO:** Update dist/TEMPLATES/_AI_INSTRUCTIONS.md with .wpcignore troubleshooting
+
+---
+
+### Changed
+
+#### Documentation: AI-DDTK Integration
+
+- **Added AI-DDTK as installation option** in README.md with comprehensive value proposition
+  - New "Option 2: Via AI-DDTK" section in Quick Start → Installation
+  - Detailed comparison table showing all tools included with AI-DDTK
+  - Key benefits: centralized toolkit, AI-optimized workflows, global access, automatic updates
+  - Clear guidance on when to choose AI-DDTK vs standalone installation
+- **Added "Related Projects" section** explaining AI-DDTK's git subtree relationship with WPCC
+  - Documents how AI-DDTK embeds WPCC at `tools/wp-code-check/`
+  - Explains update mechanism (`./install.sh update-wpcc`)
+  - Clarifies that both options provide identical WPCC features
+- **Created strategic analysis document** at `PROJECT/1-INBOX/STRATEGIC-ANALYSIS-WPCC-VS-AI-DDTK.md`
+  - Analyzed whether Claude Code Integration features should be ported to AI-DDTK
+  - Conclusion: Keep all features in WPCC (MCP, AI Triage, GitHub Issues)
+  - Rationale: AI-DDTK embeds WPCC via git subtree; porting would create circular dependency
+  - Documents actual AI-DDTK architecture (v1.0.5) vs initial assumptions
+
+**Context:** AI-DDTK (AI Driven Development ToolKit) is a centralized toolkit that includes WP Code Check plus additional WordPress development tools (local-wp, WP AJAX Test, Playwright, PHPStan recipes, AI agent guidelines). It provides a global `wpcc` command and is optimized for AI-driven workflows with Claude Code, Cursor, Augment, etc.
+
+---
+
 ## [2.2.4] - 2026-02-07
 
 ### Fixed

PROJECT/1-INBOX/AI-DDTK-DOCUMENTATION-UPDATE.md

@@ -0,0 +1,173 @@
+# AI-DDTK Documentation Update
+
+**Created:** 2026-02-07  
+**Status:** Complete  
+**Type:** Documentation Enhancement
+
+---
+
+## 🎯 Summary
+
+Updated WP Code Check documentation to inform users about AI-DDTK as an alternative installation option with detailed value propositions.
+
+---
+
+## 📝 Changes Made
+
+### 1. README.md - Installation Section
+
+**Location:** Lines 85-195
+
+**Added:**
+- **Option 1: Standalone Installation** - Renamed existing installation instructions
+- **Option 2: Via AI-DDTK** - New comprehensive section with:
+  - What is AI-DDTK explanation
+  - Installation instructions
+  - Complete tools table (9 tools/features)
+  - Key benefits list (6 benefits)
+  - How it works explanation (git subtree)
+  - Example workflow
+  - Decision guide (when to choose each option)
+
+**Value Propositions Highlighted:**
+- ✅ Centralized toolkit (one installation, multiple tools)
+- ✅ AI-optimized (built for Claude Code, Cursor, Augment, etc.)
+- ✅ Global access (`wpcc` command from any directory)
+- ✅ Automatic updates (`./install.sh update-wpcc`)
+- ✅ Workflow automation (pre-built patterns)
+- ✅ Zero conflicts (isolated tools)
+
+---
+
+### 2. README.md - Related Projects Section
+
+**Location:** Lines 690-743 (new section before "About")
+
+**Added:**
+- AI-DDTK repository link and description
+- Git subtree relationship explanation
+- How it works (technical details)
+- When to use AI-DDTK vs standalone (decision guide)
+- Clarification that both options provide identical WPCC features
+
+---
+
+### 3. CHANGELOG.md
+
+**Location:** Lines 8-35 (new Unreleased section)
+
+**Added:**
+- Documentation: AI-DDTK Integration section
+- Summary of README changes
+- Reference to strategic analysis document
+- Context about AI-DDTK's purpose and architecture
+
+---
+
+### 4. Strategic Analysis Document
+
+**File:** `PROJECT/1-INBOX/STRATEGIC-ANALYSIS-WPCC-VS-AI-DDTK.md`
+
+**Content:**
+- Analysis of whether to port Claude Code Integration features to AI-DDTK
+- Actual AI-DDTK architecture (v1.0.5) vs initial assumptions
+- Git subtree integration explanation
+- Architecture diagrams
+- Recommendation: Keep all features in WPCC
+- Action items for documentation updates
+
+---
+
+## 🎯 Key Messages to Users
+
+### For New Users
+
+**"You have two ways to install WP Code Check:"**
+
+1. **Standalone** - Just the scanner, minimal installation
+2. **AI-DDTK** - Scanner + toolkit with 8 additional tools, optimized for AI workflows
+
+**Both give you the same WP Code Check features** - the difference is in how you access them.
+
+---
+
+### For AI-Driven Teams
+
+**"AI-DDTK is built for you:"**
+
+- Global `wpcc` command (no path memorization)
+- AI Agent Guidelines (AGENTS.md v2.4.0) with Phase 1-4 workflows
+- Additional tools: local-wp, WP AJAX Test, Playwright, PHPStan recipes
+- One-command updates for all tools
+- Fix-Iterate Loop pattern for autonomous debugging
+
+---
+
+### For CI/CD Users
+
+**"Standalone is probably better for you:"**
+
+- Minimal installation footprint
+- Direct control over repository
+- No extra tools you don't need
+- Standard git clone workflow
+
+---
+
+## 📊 Documentation Quality
+
+**Strengths:**
+- ✅ Clear decision guidance (when to choose each option)
+- ✅ Comprehensive value propositions (9 tools listed)
+- ✅ Technical accuracy (git subtree explained)
+- ✅ User-focused benefits (not just features)
+- ✅ Multiple entry points (Quick Start, Related Projects)
+
+**Coverage:**
+- ✅ Installation instructions for both options
+- ✅ Feature comparison table
+- ✅ Example workflows
+- ✅ Decision trees
+- ✅ Links to AI-DDTK repository
+
+---
+
+## ✅ Completion Checklist
+
+- [x] Added AI-DDTK installation option to README.md
+- [x] Created comprehensive value proposition with tools table
+- [x] Added decision guidance (when to choose each option)
+- [x] Created "Related Projects" section
+- [x] Explained git subtree relationship
+- [x] Updated CHANGELOG.md
+- [x] Created strategic analysis document
+- [x] Verified all links and references
+
+---
+
+## 🔗 Related Files
+
+- `README.md` - Main documentation (updated)
+- `CHANGELOG.md` - Version history (updated)
+- `PROJECT/1-INBOX/STRATEGIC-ANALYSIS-WPCC-VS-AI-DDTK.md` - Strategic analysis
+- `PROJECT/1-INBOX/CLAUDE-CODE-INTEGRATION-REVIEW.md` - Feature audit
+
+---
+
+## 📈 Impact
+
+**For Users:**
+- Better informed installation decisions
+- Awareness of AI-DDTK as an option
+- Clear understanding of benefits for each approach
+
+**For AI-DDTK:**
+- Increased visibility
+- Clear value proposition
+- Proper attribution and relationship documentation
+
+**For WPCC:**
+- Maintains standalone viability
+- Documents ecosystem relationships
+- Provides multiple installation paths
+