@bugzy-ai/bugzy 1.19.2 → 1.20.0

package/package.json

@@ -1,95 +1,95 @@
-{
-  "name": "@bugzy-ai/bugzy",
-  "version": "1.19.2",
-  "description": "Open-source AI agent configuration for QA automation with Claude Code",
-  "publishConfig": {
-    "access": "public"
-  },
-  "keywords": [
-    "ai",
-    "testing",
-    "qa",
-    "automation",
-    "claude",
-    "mcp",
-    "agent",
-    "test-automation",
-    "claude-code"
-  ],
-  "homepage": "https://github.com/bugzy-ai/bugzy#readme",
-  "bugs": {
-    "url": "https://github.com/bugzy-ai/bugzy/issues"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/bugzy-ai/bugzy.git"
-  },
-  "license": "MIT",
-  "author": "Bugzy Team",
-  "type": "module",
-  "exports": {
-    ".": {
-      "types": "./dist/index.d.ts",
-      "import": "./dist/index.js",
-      "require": "./dist/index.cjs"
-    },
-    "./tasks": {
-      "types": "./dist/tasks/index.d.ts",
-      "import": "./dist/tasks/index.js"
-    },
-    "./subagents": {
-      "types": "./dist/subagents/index.d.ts",
-      "import": "./dist/subagents/index.js"
-    },
-    "./subagents/metadata": {
-      "types": "./dist/subagents/metadata.d.ts",
-      "import": "./dist/subagents/metadata.js"
-    }
-  },
-  "main": "./dist/index.cjs",
-  "module": "./dist/index.js",
-  "types": "./dist/index.d.ts",
-  "bin": {
-    "bugzy": "./dist/cli/index.js"
-  },
-  "files": [
-    "dist",
-    "templates",
-    "README.md",
-    "LICENSE"
-  ],
-  "scripts": {
-    "build": "tsup",
-    "dev": "tsup --watch",
-    "test": "vitest run",
-    "test:ci": "vitest run",
-    "type-check": "tsc --noEmit",
-    "lint": "eslint src",
-    "prepublishOnly": "pnpm run build && pnpm run test:ci"
-  },
-  "dependencies": {
-    "chalk": "^5.3.0",
-    "commander": "^11.1.0",
-    "dotenv": "^16.3.1",
-    "figlet": "^1.9.3",
-    "gradient-string": "^3.0.0",
-    "gray-matter": "^4.0.3",
-    "inquirer": "^9.2.12",
-    "ora": "^7.0.1"
-  },
-  "devDependencies": {
-    "@types/figlet": "^1.7.0",
-    "@types/gradient-string": "^1.1.6",
-    "@types/inquirer": "^9.0.7",
-    "@types/node": "^20.10.5",
-    "@typescript-eslint/eslint-plugin": "^6.15.0",
-    "@typescript-eslint/parser": "^6.15.0",
-    "eslint": "^8.56.0",
-    "tsup": "^8.0.1",
-    "typescript": "^5.3.3",
-    "vitest": "^1.1.0"
-  },
-  "engines": {
-    "node": ">=18.0.0"
-  }
-}
+{
+  "name": "@bugzy-ai/bugzy",
+  "version": "1.20.0",
+  "description": "Open-source AI agent configuration for QA automation with Claude Code",
+  "publishConfig": {
+    "access": "public"
+  },
+  "keywords": [
+    "ai",
+    "testing",
+    "qa",
+    "automation",
+    "claude",
+    "mcp",
+    "agent",
+    "test-automation",
+    "claude-code"
+  ],
+  "homepage": "https://github.com/bugzy-ai/bugzy#readme",
+  "bugs": {
+    "url": "https://github.com/bugzy-ai/bugzy/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/bugzy-ai/bugzy.git"
+  },
+  "license": "MIT",
+  "author": "Bugzy Team",
+  "type": "module",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "import": "./dist/index.js",
+      "require": "./dist/index.cjs"
+    },
+    "./tasks": {
+      "types": "./dist/tasks/index.d.ts",
+      "import": "./dist/tasks/index.js"
+    },
+    "./subagents": {
+      "types": "./dist/subagents/index.d.ts",
+      "import": "./dist/subagents/index.js"
+    },
+    "./subagents/metadata": {
+      "types": "./dist/subagents/metadata.d.ts",
+      "import": "./dist/subagents/metadata.js"
+    }
+  },
+  "main": "./dist/index.cjs",
+  "module": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "bin": {
+    "bugzy": "./dist/cli/index.js"
+  },
+  "files": [
+    "dist",
+    "templates",
+    "README.md",
+    "LICENSE"
+  ],
+  "scripts": {
+    "build": "tsup",
+    "dev": "tsup --watch",
+    "test": "vitest run",
+    "test:ci": "vitest run",
+    "type-check": "tsc --noEmit",
+    "lint": "eslint src",
+    "prepublishOnly": "pnpm run build && pnpm run test:ci"
+  },
+  "dependencies": {
+    "chalk": "^5.3.0",
+    "commander": "^11.1.0",
+    "dotenv": "^16.3.1",
+    "figlet": "^1.9.3",
+    "gradient-string": "^3.0.0",
+    "gray-matter": "^4.0.3",
+    "inquirer": "^9.2.12",
+    "ora": "^7.0.1"
+  },
+  "devDependencies": {
+    "@types/figlet": "^1.7.0",
+    "@types/gradient-string": "^1.1.6",
+    "@types/inquirer": "^9.0.7",
+    "@types/node": "^20.10.5",
+    "@typescript-eslint/eslint-plugin": "^6.15.0",
+    "@typescript-eslint/parser": "^6.15.0",
+    "eslint": "^8.56.0",
+    "tsup": "^8.0.1",
+    "typescript": "^5.3.3",
+    "vitest": "^1.1.0"
+  },
+  "engines": {
+    "node": ">=18.0.0"
+  }
+}

package/templates/init/.bugzy/runtime/hooks/pre-compact.sh

@@ -1,53 +1,53 @@
-#!/usr/bin/env bash
-# PreCompact Hook — Flush insights before context compaction
-# This script runs automatically before Claude Code compacts context.
-# Its stdout is injected into the conversation, instructing Claude to save learnings.
-
-set -euo pipefail
-
-RUNTIME_DIR=".bugzy/runtime"
-LOGS_DIR="$RUNTIME_DIR/logs"
-TODAY=$(date +%Y-%m-%d)
-LOG_FILE="$LOGS_DIR/$TODAY.md"
-
-# Ensure logs directory exists
-mkdir -p "$LOGS_DIR"
-
-cat <<'INSTRUCTIONS'
-=== PRE-COMPACTION: Save Your Learnings ===
-
-Context compaction is about to happen. Before your context is compressed, extract and save any knowledge from this session that matches the categories below.
-
-**Write entries to the daily log file** using the Write tool:
-INSTRUCTIONS
-
-echo "**Daily log path:** \`$LOG_FILE\`"
-
-cat <<'INSTRUCTIONS'
-
-**Format each entry as:**
-```markdown
-### HH:MM — {source-role-or-task}
-<!-- source: {task-or-subagent} -->
-- Insight or pattern learned
-- Another insight
-```
-
-**Extraction Categories (save only what applies):**
-- **Application patterns** — UI flows, navigation, API response patterns
-- **Test reliability** — Flaky selectors, timing issues, retry patterns
-- **Team preferences** — Communication style, workflow expectations
-- **Technical constraints** — Rate limits, auth lifetimes, deployment gotchas
-- **Environment facts** — URLs, test data patterns, feature flags
-
-**Include provenance** on each entry. Only save knowledge that would help in future sessions.
-INSTRUCTIONS
-
-# Inject the full maintenance guide for reference
-if [ -f "$RUNTIME_DIR/knowledge-maintenance-guide.md" ]; then
-  echo ""
-  echo "=== Knowledge Maintenance Guide (Reference) ==="
-  cat "$RUNTIME_DIR/knowledge-maintenance-guide.md"
-fi
-
-exit 0
+#!/usr/bin/env bash
+# PreCompact Hook — Flush insights before context compaction
+# This script runs automatically before Claude Code compacts context.
+# Its stdout is injected into the conversation, instructing Claude to save learnings.
+
+set -euo pipefail
+
+RUNTIME_DIR=".bugzy/runtime"
+LOGS_DIR="$RUNTIME_DIR/logs"
+TODAY=$(date +%Y-%m-%d)
+LOG_FILE="$LOGS_DIR/$TODAY.md"
+
+# Ensure logs directory exists
+mkdir -p "$LOGS_DIR"
+
+cat <<'INSTRUCTIONS'
+=== PRE-COMPACTION: Save Your Learnings ===
+
+Context compaction is about to happen. Before your context is compressed, extract and save any knowledge from this session that matches the categories below.
+
+**Write entries to the daily log file** using the Write tool:
+INSTRUCTIONS
+
+echo "**Daily log path:** \`$LOG_FILE\`"
+
+cat <<'INSTRUCTIONS'
+
+**Format each entry as:**
+```markdown
+### HH:MM — {source-role-or-task}
+<!-- source: {task-or-subagent} -->
+- Insight or pattern learned
+- Another insight
+```
+
+**Extraction Categories (save only what applies):**
+- **Application patterns** — UI flows, navigation, API response patterns
+- **Test reliability** — Flaky selectors, timing issues, retry patterns
+- **Team preferences** — Communication style, workflow expectations
+- **Technical constraints** — Rate limits, auth lifetimes, deployment gotchas
+- **Environment facts** — URLs, test data patterns, feature flags
+
+**Include provenance** on each entry. Only save knowledge that would help in future sessions.
+INSTRUCTIONS
+
+# Inject the full maintenance guide for reference
+if [ -f "$RUNTIME_DIR/knowledge-maintenance-guide.md" ]; then
+  echo ""
+  echo "=== Knowledge Maintenance Guide (Reference) ==="
+  cat "$RUNTIME_DIR/knowledge-maintenance-guide.md"
+fi
+
+exit 0

package/templates/init/.bugzy/runtime/hooks/session-start.sh

@@ -1,68 +1,68 @@
-#!/usr/bin/env bash
-# SessionStart Hook — Load knowledge base and recent daily logs into context
-# This script runs automatically at the start of each Claude Code session.
-# Its stdout is injected into the conversation context.
-
-set -euo pipefail
-
-RUNTIME_DIR=".bugzy/runtime"
-
-# Clean up any stale hook markers from previous sessions
-rm -rf "$RUNTIME_DIR/hooks/.markers" 2>/dev/null || true
-
-PROJECT_CONTEXT="$RUNTIME_DIR/project-context.md"
-KB_FILE="$RUNTIME_DIR/knowledge-base.md"
-LOGS_DIR="$RUNTIME_DIR/logs"
-
-# --- Memory System Overview ---
-cat <<'OVERVIEW'
-=== Memory System ===
-
-This project uses a hooks-based memory system with three layers:
-
-1. **Knowledge Base** (`.bugzy/runtime/knowledge-base.md`) — Curated, long-term knowledge. The source of truth.
-2. **Daily Log** (`.bugzy/runtime/logs/YYYY-MM-DD.md`) — Scratch buffer for the current day's insights.
-3. **Subagent Memory** (`.bugzy/runtime/memory/{role}.md`) — Role-specific knowledge per subagent.
-
-**Lifecycle:** During work, insights accumulate in context. Before context compaction (PreCompact hook), you flush insights to the daily log. At session end (SessionEnd hook), you consolidate the daily log into the knowledge base. Subagents manage their own memory via SubagentStart/SubagentStop hooks.
-
-Below is the current project context, knowledge base, and recent daily logs.
-OVERVIEW
-echo ""
-
-# --- Load Project Context ---
-if [ -f "$PROJECT_CONTEXT" ]; then
-  echo "=== Project Context ==="
-  cat "$PROJECT_CONTEXT"
-  echo ""
-fi
-
-# --- Load Knowledge Base ---
-if [ -f "$KB_FILE" ]; then
-  echo "=== Knowledge Base ==="
-  cat "$KB_FILE"
-  echo ""
-fi
-
-# --- Load Recent Daily Logs ---
-if [ -d "$LOGS_DIR" ]; then
-  TODAY=$(date +%Y-%m-%d)
-  YESTERDAY=$(date -v-1d +%Y-%m-%d 2>/dev/null || date -d "yesterday" +%Y-%m-%d 2>/dev/null || echo "")
-
-  if [ -f "$LOGS_DIR/$TODAY.md" ]; then
-    echo "=== Daily Log: $TODAY ==="
-    cat "$LOGS_DIR/$TODAY.md"
-    echo ""
-  fi
-
-  if [ -n "$YESTERDAY" ] && [ -f "$LOGS_DIR/$YESTERDAY.md" ]; then
-    echo "=== Daily Log: $YESTERDAY ==="
-    cat "$LOGS_DIR/$YESTERDAY.md"
-    echo ""
-  fi
-
-  # --- Prune logs older than 7 days ---
-  find "$LOGS_DIR" -name "*.md" -mtime +7 -delete 2>/dev/null || true
-fi
-
-exit 0
+#!/usr/bin/env bash
+# SessionStart Hook — Load knowledge base and recent daily logs into context
+# This script runs automatically at the start of each Claude Code session.
+# Its stdout is injected into the conversation context.
+
+set -euo pipefail
+
+RUNTIME_DIR=".bugzy/runtime"
+
+# Clean up any stale hook markers from previous sessions
+rm -rf "$RUNTIME_DIR/hooks/.markers" 2>/dev/null || true
+
+PROJECT_CONTEXT="$RUNTIME_DIR/project-context.md"
+KB_FILE="$RUNTIME_DIR/knowledge-base.md"
+LOGS_DIR="$RUNTIME_DIR/logs"
+
+# --- Memory System Overview ---
+cat <<'OVERVIEW'
+=== Memory System ===
+
+This project uses a hooks-based memory system with three layers:
+
+1. **Knowledge Base** (`.bugzy/runtime/knowledge-base.md`) — Curated, long-term knowledge. The source of truth.
+2. **Daily Log** (`.bugzy/runtime/logs/YYYY-MM-DD.md`) — Scratch buffer for the current day's insights.
+3. **Subagent Memory** (`.bugzy/runtime/memory/{role}.md`) — Role-specific knowledge per subagent.
+
+**Lifecycle:** During work, insights accumulate in context. Before context compaction (PreCompact hook), you flush insights to the daily log. At session end (SessionEnd hook), you consolidate the daily log into the knowledge base. Subagents manage their own memory via SubagentStart/SubagentStop hooks.
+
+Below is the current project context, knowledge base, and recent daily logs.
+OVERVIEW
+echo ""
+
+# --- Load Project Context ---
+if [ -f "$PROJECT_CONTEXT" ]; then
+  echo "=== Project Context ==="
+  cat "$PROJECT_CONTEXT"
+  echo ""
+fi
+
+# --- Load Knowledge Base ---
+if [ -f "$KB_FILE" ]; then
+  echo "=== Knowledge Base ==="
+  cat "$KB_FILE"
+  echo ""
+fi
+
+# --- Load Recent Daily Logs ---
+if [ -d "$LOGS_DIR" ]; then
+  TODAY=$(date +%Y-%m-%d)
+  YESTERDAY=$(date -v-1d +%Y-%m-%d 2>/dev/null || date -d "yesterday" +%Y-%m-%d 2>/dev/null || echo "")
+
+  if [ -f "$LOGS_DIR/$TODAY.md" ]; then
+    echo "=== Daily Log: $TODAY ==="
+    cat "$LOGS_DIR/$TODAY.md"
+    echo ""
+  fi
+
+  if [ -n "$YESTERDAY" ] && [ -f "$LOGS_DIR/$YESTERDAY.md" ]; then
+    echo "=== Daily Log: $YESTERDAY ==="
+    cat "$LOGS_DIR/$YESTERDAY.md"
+    echo ""
+  fi
+
+  # --- Prune logs older than 7 days ---
+  find "$LOGS_DIR" -name "*.md" -mtime +7 -delete 2>/dev/null || true
+fi
+
+exit 0

package/templates/init/.bugzy/runtime/knowledge-base.md

@@ -1,61 +1,61 @@
-# Knowledge Base
-
-> A curated collection of factual knowledge about this project - what we currently know and believe to be true. This is NOT a historical log, but a living reference that evolves as understanding improves.
-
-**Maintenance Guide**: See `knowledge-maintenance-guide.md` for instructions on how to maintain this knowledge base.
-
-**Core Principle**: This document represents current understanding, not a history. When knowledge evolves, update existing entries rather than appending new ones.
-
----
-
-## Project Knowledge
-
-_This knowledge base will be populated as you work. Add new discoveries, update existing understanding, and remove outdated information following the maintenance guide principles._
-
-### When to Update This File
-
-- **ADD**: New factual information discovered, new patterns emerge, new areas become relevant
-- **UPDATE**: Facts change, understanding deepens, multiple facts can be consolidated, language can be clarified
-- **REMOVE**: Information becomes irrelevant, facts proven incorrect, entries superseded by better content
-
-### Format Guidelines
-
-- Use clear, declarative statements in present tense
-- State facts confidently when known; flag uncertainty when it exists
-- Write for someone reading this 6 months from now
-- Keep entries relevant and actionable
-- Favor consolidation over accumulation
-
----
-
-## Example Structure
-
-Below is an example structure. Feel free to organize knowledge in the way that makes most sense for this project:
-
-### Architecture & Infrastructure
-
-_System architecture, deployment patterns, infrastructure details_
-
-### Testing Patterns
-
-_Test strategies, common test scenarios, testing conventions_
-
-### UI/UX Patterns
-
-_User interface conventions, interaction patterns, design system details_
-
-### Data & APIs
-
-_Data models, API behaviors, integration patterns_
-
-### Known Issues & Workarounds
-
-_Current limitations, known bugs, and their workarounds_
-
-### Domain Knowledge
-
-_Business domain facts, terminology, rules, and context_
-
----
-
-**Remember**: Every entry should answer "Will this help someone working on this project in 6 months?"
+# Knowledge Base
+
+> A curated collection of factual knowledge about this project - what we currently know and believe to be true. This is NOT a historical log, but a living reference that evolves as understanding improves.
+
+**Maintenance Guide**: See `knowledge-maintenance-guide.md` for instructions on how to maintain this knowledge base.
+
+**Core Principle**: This document represents current understanding, not a history. When knowledge evolves, update existing entries rather than appending new ones.
+
+---
+
+## Project Knowledge
+
+_This knowledge base will be populated as you work. Add new discoveries, update existing understanding, and remove outdated information following the maintenance guide principles._
+
+### When to Update This File
+
+- **ADD**: New factual information discovered, new patterns emerge, new areas become relevant
+- **UPDATE**: Facts change, understanding deepens, multiple facts can be consolidated, language can be clarified
+- **REMOVE**: Information becomes irrelevant, facts proven incorrect, entries superseded by better content
+
+### Format Guidelines
+
+- Use clear, declarative statements in present tense
+- State facts confidently when known; flag uncertainty when it exists
+- Write for someone reading this 6 months from now
+- Keep entries relevant and actionable
+- Favor consolidation over accumulation
+
+---
+
+## Example Structure
+
+Below is an example structure. Feel free to organize knowledge in the way that makes most sense for this project:
+
+### Architecture & Infrastructure
+
+_System architecture, deployment patterns, infrastructure details_
+
+### Testing Patterns
+
+_Test strategies, common test scenarios, testing conventions_
+
+### UI/UX Patterns
+
+_User interface conventions, interaction patterns, design system details_
+
+### Data & APIs
+
+_Data models, API behaviors, integration patterns_
+
+### Known Issues & Workarounds
+
+_Current limitations, known bugs, and their workarounds_
+
+### Domain Knowledge
+
+_Business domain facts, terminology, rules, and context_
+
+---
+
+**Remember**: Every entry should answer "Will this help someone working on this project in 6 months?"