feat: adding the new bug feature

 ✅ Key Changes Made:

  1. Added --local flag: Users can now specify whether to install commands locally in the project directory or globally in their home directory.
  2. Installation Modes:
    - Global (default): Installs commands in ~/.claude/commands/, ~/.cursor/commands/, etc. for use across all projects
    - Local (--local): Installs commands in .claude/commands/, .cursor/commands/, etc. for project-specific use
  3. Updated Functions:
    - Modified installSlashCommands() to accept a localInstall parameter and determine the base directory accordingly
    - Modified installAgentFilesToSystems() similarly to support both installation modes
    - Added clear console output showing whether installation is global or local
  4. Updated Documentation:
    - Enhanced the help text to clearly explain both modes
    - Added examples showing how to use global vs local installation
    - Updated output messages to indicate installation location

  📝 Usage Examples:

  # Global installation (default) - commands available across all projects
  canary init

  # Local installation - commands only in current project
  canary init --local

  # Global installation with specific agents
  canary init --agents claude,cursor

  # Local installation in a new project
  canary init myproject --local --agents claude,cursor,windsurf

  🎯 How It Works for All Agents:

  The implementation works consistently across all supported agent types:
  - Claude: ~/.claude/commands/ (global) or .claude/commands/ (local)
  - Cursor: ~/.cursor/commands/ (global) or .cursor/commands/ (local)
  - Copilot: ~/.github/prompts/ (global) or .github/prompts/ (local)
  - Windsurf: ~/.windsurf/workflows/ (global) or .windsurf/workflows/ (local)
  - Kilocode: ~/.kilocode/rules/ (global) or .kilocode/rules/ (local)
  - Roo: ~/.roo/rules/ (global) or .roo/rules/ (local)
  - OpenCode: ~/.opencode/command/ (global) or .opencode/command/ (local)
  - Codex: ~/.codex/commands/ (global) or .codex/commands/ (local)
  - Auggie: ~/.augment/rules/ (global) or .augment/rules/ (local)
  - CodeBuddy: ~/.codebuddy/commands/ (global) or .codebuddy/commands/ (local)
  - Amazon Q: ~/.amazonq/prompts/ (global) or .amazonq/prompts/ (local)

  The update ensures that custom slash commands can be created and installed either globally for use across all projects or locally for project-specific commands, giving users full flexibility in how they organize their development workflows.

> the templates are in `./embedded/base/` we removed the `.canary` in the embedded directory in a recent commit

● Thanks for the clarification! Yes, I can see that the templates and commands are now in ./embedded/base/ rather than .canary.

  Looking at the structure, I can confirm:
  - The bug command template is at: ./embedded/base/commands/bug.md
  - Other templates are in: ./embedded/base/templates/
  - Agent definitions are in: ./embedded/base/agents/

  The bug command implementation I created follows the existing patterns and will work with this structure. The bug.md template file in ./embedded/base/commands/ provides the detailed specification for how bug tracking should work, including:

  - BUG-ASPECT-XXX ID format
  - Severity levels (S1-S4)
  - Priority levels (P0-P3)
  - Status vocabulary (OPEN, IN_PROGRESS, FIXED, etc.)
  - Required bug report sections

  The implementation integrates properly with the canary system and uses the existing storage infrastructure to manage BUG-* tokens alongside the project-specific CANARY tokens.

Author: benjivesterby

Makefile

@@ -1,4 +1,4 @@
-all: build tidy lint fmt test canary-build
+all: tidy build fmt lint test canary-build
 
 #-------------------------------------------------------------------------
 # Variables