Fix: Correct template loading path in bash script

ISSUE:
- Script was looking for templates in repository root /TEMPLATES/
- Templates are actually stored in dist/TEMPLATES/
- --project flag was failing with 'Template not found' error

ROOT CAUSE:
- REPO_ROOT variable was set to $SCRIPT_DIR/../.. (repository root)
- Should have been $SCRIPT_DIR/.. (dist directory)

FIX:
- Changed REPO_ROOT from '../..' to '..' in check-performance.sh
- Added inline comments explaining the path structure
- Updated dist/TEMPLATES/_AI_INSTRUCTIONS.md to clarify templates
  must be in dist/TEMPLATES/ (not repository root)
- Updated CHANGELOG.md with detailed explanation

IMPACT:
- --project <name> flag now correctly loads from dist/TEMPLATES/<name>.txt
- Template feature is now fully functional

Author: noelsaw1

CHANGELOG.md

@@ -7,6 +7,15 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [1.0.59] - 2025-12-31
 
+### Fixed
+- **Template Loading Path** - Fixed `REPO_ROOT` variable in bash script to correctly load templates from `dist/TEMPLATES/`
+  - **Issue:** Script was looking for templates in repository root `/TEMPLATES/` instead of `dist/TEMPLATES/`
+  - **Root Cause:** `REPO_ROOT` was set to `$SCRIPT_DIR/../..` (repository root) instead of `$SCRIPT_DIR/..` (dist directory)
+  - **Fix:** Changed `REPO_ROOT` calculation from `../..` to `..` to point to `dist/` directory
+  - **Impact:** `--project <name>` flag now correctly loads templates from `dist/TEMPLATES/<name>.txt`
+  - Updated `dist/TEMPLATES/_AI_INSTRUCTIONS.md` to clarify templates must be in `dist/TEMPLATES/` (not repository root)
+  - Added inline comments in bash script explaining the path structure
+
 ### Added
 - **Contributor License Agreement (CLA)** - Added CLA requirement for contributors
   - Created `CLA.md` - Individual Contributor License Agreement

dist/TEMPLATES/_AI_INSTRUCTIONS.md

@@ -4,13 +4,15 @@
 Help users complete WP Code Check project configuration templates.
 
 ## Context
-Users create template files in `/TEMPLATES/` to store project configurations. This allows them to run performance checks with a simple command like `run acme` instead of typing long paths every time.
+Users create template files in `dist/TEMPLATES/` to store project configurations. This allows them to run performance checks with a simple command like `--project acme` instead of typing long paths every time.
+
+**IMPORTANT:** Templates must be stored in `dist/TEMPLATES/` (not repository root `/TEMPLATES/`). The bash script's `REPO_ROOT` variable was updated on 2025-12-31 to point to the `dist/` directory to ensure templates load correctly from `dist/TEMPLATES/`.
 
 ## Workflow
-1. User creates a new `.txt` file in `/TEMPLATES/` (e.g., `acme.txt`)
+1. User creates a new `.txt` file in `dist/TEMPLATES/` (e.g., `acme.txt`)
 2. User pastes an absolute path to a WordPress plugin/theme directory
 3. User asks you to complete the template
-4. You extract metadata and fill in the template using the structure from `_TEMPLATE.txt`
+4. You extract metadata and fill in the template using the structure from `dist/TEMPLATES/_TEMPLATE.txt`
 
 ---
 
@@ -42,10 +44,10 @@ Users create template files in `/TEMPLATES/` to store project configurations. Th
 - Example: `acme.txt` → `PROJECT_NAME=acme`
 
 ### 4. Generate the Full Template
-- Use the structure from `/TEMPLATES/_TEMPLATE.txt`
+- Use the structure from `dist/TEMPLATES/_TEMPLATE.txt`
 - Fill in the **BASIC CONFIGURATION** section:
   - `PROJECT_NAME` (from filename)
-  - `PATH` (from user's pasted path)
+  - `PROJECT_PATH` (from user's pasted path)
   - `NAME` (from plugin header)
   - `VERSION` (from plugin header)
 - Leave all **COMMON OPTIONS** and **ADVANCED OPTIONS** commented out (user can enable as needed)
@@ -69,7 +71,7 @@ If you can't find the plugin file or extract metadata:
 
 ## Example Interaction
 
-**User creates `/TEMPLATES/acme.txt` with:**
+**User creates `dist/TEMPLATES/acme.txt` with:**
 ```
 /Users/noelsaw/Local Sites/bloomzhemp-10-24-25/app/public/wp-content/plugins/acme-plugin
 ```

dist/bin/check-performance.sh

@@ -31,7 +31,10 @@
 # Directories and shared libraries
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 LIB_DIR="$SCRIPT_DIR/lib"
-REPO_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
+# REPO_ROOT points to dist/ directory (not repository root)
+# This ensures templates are loaded from dist/TEMPLATES/ where they belong
+# Changed from ../.. to .. on 2025-12-31 to fix template loading
+REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
 
 # shellcheck source=dist/bin/lib/colors.sh
 source "$LIB_DIR/colors.sh"