Fix Workflow Trigger Paths to Include Configuration Folders

[JeremyDev87]

Fix Workflow Trigger Paths to Include Configuration Folders

📋 Summary

Expands GitHub Actions workflow trigger paths to include core configuration folders (.ai-rules/, .antigravity/, .claude/, .codex/, .cursor/, scripts/). This ensures that canary and dev builds trigger when these critical project configuration files change.

Resolves #13

🎯 Problem

Before This Change

GitHub workflows (codebuddy-canary.yml, codebuddy-dev.yml) only triggered on changes within the mcp-server/ folder. However, several critical configuration folders were excluded:

• .ai-rules/ - AI rules definitions that are copied into mcp-server/ during prepublishOnly and included in the npm package
• .antigravity/ - Antigravity (Gemini) configuration
• .claude/ - Claude Code configuration
• .codex/ - GitHub Copilot configuration
• .cursor/ - Cursor AI configuration
• scripts/ - Build/deployment scripts

Impact

When changes were made to these folders (especially .ai-rules/), workflows did not trigger, requiring manual intervention or changes to mcp-server/ to trigger builds. This was problematic because:

1. .ai-rules/ changes are included in the npm package via prepublishOnly script
2. Configuration changes should trigger new builds to ensure consistency
3. Manual workflow triggers were needed, reducing automation

✨ Solution

Changes Made

Added 6 new path patterns to both workflow files:

paths:
  - 'mcp-server/**'
  - '.ai-rules/**'      # ← Added
  - '.antigravity/**'   # ← Added
  - '.claude/**'        # ← Added
  - '.codex/**'         # ← Added
  - '.cursor/**'        # ← Added
  - 'scripts/**'        # ← Added
  - .github/workflows/codebuddy-canary.yml  # or codebuddy-dev.yml

Files Modified

• .github/workflows/codebuddy-canary.yml (+6 lines)
• .github/workflows/codebuddy-dev.yml (+6 lines)

Total: 2 files changed, +12 insertions

✅ Benefits

1. Automated Builds: Configuration changes now automatically trigger canary/dev builds
2. Consistency: Ensures .ai-rules/ changes are properly packaged and deployed
3. Reduced Manual Work: No need to manually trigger workflows or make dummy changes
4. Better CI/CD: All critical project files are now monitored for changes

🧪 Testing

• Workflow files syntax validated
• Path patterns follow GitHub Actions conventions
• No impact on existing mcp-server/** trigger behavior
• Verify workflow triggers on .ai-rules/ changes (manual test after merge)
• Verify workflow triggers on .claude/ changes (manual test after merge)

Issues

resolve #13