bluera-knowledge 0.13.3 → 0.14.1

package/dist/index.js

@@ -7,10 +7,10 @@ import {
   isWebStoreDefinition,
   runMCPServer,
   spawnBackgroundWorker
-} from "./chunk-XL2UHMBL.js";
+} from "./chunk-UAWKTJWN.js";
 import {
   IntelligentCrawler
-} from "./chunk-AOSDVRRH.js";
+} from "./chunk-AIS5S77C.js";
 import {
   ASTParser,
   AdapterRegistry,
@@ -24,7 +24,7 @@ import {
   err,
   extractRepoName,
   ok
-} from "./chunk-AJI5DCKY.js";
+} from "./chunk-Y24ZJRZP.js";
 import "./chunk-HRQD3MPH.js";
 
 // src/index.ts

package/dist/mcp/server.js

@@ -1,8 +1,8 @@
 import {
   createMCPServer,
   runMCPServer
-} from "../chunk-XL2UHMBL.js";
-import "../chunk-AJI5DCKY.js";
+} from "../chunk-UAWKTJWN.js";
+import "../chunk-Y24ZJRZP.js";
 import "../chunk-HRQD3MPH.js";
 export {
   createMCPServer,

package/dist/workers/background-worker-cli.js

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import {
   IntelligentCrawler
-} from "../chunk-AOSDVRRH.js";
+} from "../chunk-AIS5S77C.js";
 import {
   JobService,
   createDocumentId,
@@ -10,7 +10,7 @@ import {
   createStoreId,
   destroyServices,
   shutdownLogger
-} from "../chunk-AJI5DCKY.js";
+} from "../chunk-Y24ZJRZP.js";
 import "../chunk-HRQD3MPH.js";
 
 // src/workers/background-worker-cli.ts

package/hooks/check-dependencies.sh

@@ -3,12 +3,12 @@
 # Automatically checks and installs dependencies for the plugin
 #
 # Environment variables:
-#   BK_SKIP_AUTO_INSTALL=1  - Skip automatic pip installation of crawl4ai
+#   BK_SKIP_AUTO_INSTALL=1  - Skip automatic installation of crawl4ai
 #                             Set this if you prefer to manage Python packages manually
 #
 # What this script auto-installs (if missing):
 #   - Node.js dependencies (via bun or npm, from package.json)
-#   - crawl4ai Python package (via pip, for web crawling)
+#   - Python virtual environment with crawl4ai (isolated from system Python)
 #   - Playwright Chromium browser (via playwright CLI, for headless crawling)
 
 set -e
@@ -16,6 +16,11 @@ set -e
 # Get the plugin root directory
 PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$(dirname "$(dirname "$0")")}"
 
+# Venv location within plugin (isolated from system Python)
+VENV_DIR="$PLUGIN_ROOT/.venv"
+VENV_PYTHON="$VENV_DIR/bin/python3"
+VENV_PIP="$VENV_DIR/bin/pip"
+
 # Colors for output
 RED='\033[0;31m'
 GREEN='\033[0;32m'
@@ -26,21 +31,24 @@ NC='\033[0m' # No Color
 # Helper Functions
 # =====================
 
-# Install Playwright browser (called after crawl4ai is confirmed installed)
+# Install Playwright browser using specified python
+# Args: $1 = python path to use
 install_playwright_browser() {
+    local PYTHON_CMD="${1:-python3}"
+
     # Check if Playwright Chromium is already installed by testing if browser can be launched
-    if python3 -c "from playwright.sync_api import sync_playwright; p = sync_playwright().start(); b = p.chromium.launch(); b.close(); p.stop()" 2>/dev/null; then
+    if "$PYTHON_CMD" -c "from playwright.sync_api import sync_playwright; p = sync_playwright().start(); b = p.chromium.launch(); b.close(); p.stop()" 2>/dev/null; then
         echo -e "${GREEN}[bluera-knowledge] Playwright Chromium ready ✓${NC}"
         return 0
     fi
 
     echo -e "${YELLOW}[bluera-knowledge] Installing Playwright browser (one-time setup)...${NC}"
-    if python3 -m playwright install chromium 2>/dev/null; then
+    if "$PYTHON_CMD" -m playwright install chromium 2>/dev/null; then
         echo -e "${GREEN}[bluera-knowledge] Playwright Chromium installed ✓${NC}"
         return 0
     else
         echo -e "${YELLOW}[bluera-knowledge] Playwright browser install failed.${NC}"
-        echo -e "${YELLOW}Manual fix: python3 -m playwright install chromium${NC}"
+        echo -e "${YELLOW}Manual fix: $PYTHON_CMD -m playwright install chromium${NC}"
         return 1
     fi
 }
@@ -68,7 +76,7 @@ if [ ! -d "$PLUGIN_ROOT/node_modules" ]; then
 fi
 
 # =====================
-# Python Dependencies
+# Python Dependencies (using venv)
 # =====================
 
 # Check if Python3 is installed
@@ -81,75 +89,56 @@ fi
 
 # Check Python version (require 3.8+)
 python_version=$(python3 -c 'import sys; print(".".join(map(str, sys.version_info[:2])))')
-required_version="3.8"
 
 if ! python3 -c "import sys; exit(0 if sys.version_info >= (3, 8) else 1)"; then
     echo -e "${YELLOW}[bluera-knowledge] Python ${python_version} detected. Python 3.8+ recommended for crawl4ai${NC}"
 fi
 
-# Check if crawl4ai is installed
-if python3 -c "import crawl4ai" 2>/dev/null; then
-    # Already installed - get version
-    crawl4ai_version=$(python3 -c "import crawl4ai; print(crawl4ai.__version__)" 2>/dev/null || echo "unknown")
-    echo -e "${GREEN}[bluera-knowledge] crawl4ai ${crawl4ai_version} is installed ✓${NC}"
+# Check if venv exists and has crawl4ai installed
+if [ -f "$VENV_PYTHON" ] && "$VENV_PYTHON" -c "import crawl4ai" 2>/dev/null; then
+    crawl4ai_version=$("$VENV_PYTHON" -c "import crawl4ai; print(crawl4ai.__version__)" 2>/dev/null || echo "unknown")
+    echo -e "${GREEN}[bluera-knowledge] crawl4ai ${crawl4ai_version} ready (venv) ✓${NC}"
     # Ensure Playwright browser is installed for headless crawling
-    install_playwright_browser
+    install_playwright_browser "$VENV_PYTHON"
     exit 0
 fi
 
-# crawl4ai not installed - attempt installation
-echo -e "${YELLOW}[bluera-knowledge] crawl4ai not found. Web crawling features will be unavailable.${NC}"
-echo ""
-echo -e "${YELLOW}To enable web crawling, install crawl4ai:${NC}"
-echo -e "  ${GREEN}pip install crawl4ai${NC}"
-echo ""
-
 # Check if auto-install is disabled
 if [ "${BK_SKIP_AUTO_INSTALL:-}" = "1" ]; then
     echo -e "${YELLOW}[bluera-knowledge] Auto-install disabled (BK_SKIP_AUTO_INSTALL=1)${NC}"
-    echo -e "${YELLOW}Install manually: pip install crawl4ai && python3 -m playwright install chromium${NC}"
+    echo -e "${YELLOW}To enable web crawling, create venv manually:${NC}"
+    echo -e "  ${GREEN}python3 -m venv $VENV_DIR${NC}"
+    echo -e "  ${GREEN}$VENV_PIP install crawl4ai${NC}"
+    echo -e "  ${GREEN}$VENV_PYTHON -m playwright install chromium${NC}"
     exit 0
 fi
 
-# Check if we should auto-install
-if command -v pip3 &> /dev/null || command -v pip &> /dev/null; then
-    echo -e "${YELLOW}[bluera-knowledge] Auto-installing crawl4ai via pip...${NC}"
-    echo -e "${YELLOW}(Set BK_SKIP_AUTO_INSTALL=1 to disable auto-install)${NC}"
-
-    # Try to install using pip3 or pip
-    if command -v pip3 &> /dev/null; then
-        PIP_CMD="pip3"
+# Create venv if it doesn't exist
+if [ ! -d "$VENV_DIR" ]; then
+    echo -e "${YELLOW}[bluera-knowledge] Creating Python virtual environment...${NC}"
+    if python3 -m venv "$VENV_DIR" 2>/dev/null; then
+        echo -e "${GREEN}[bluera-knowledge] Virtual environment created ✓${NC}"
     else
-        PIP_CMD="pip"
+        echo -e "${RED}[bluera-knowledge] Failed to create virtual environment${NC}"
+        echo -e "${YELLOW}Manual fix: python3 -m venv $VENV_DIR${NC}"
+        exit 0
     fi
+fi
 
-    # Try with --break-system-packages for PEP 668 environments (Python 3.11+)
-    # This is needed on modern Python versions (macOS Homebrew, some Linux distros)
-    if $PIP_CMD install --quiet --break-system-packages crawl4ai 2>/dev/null; then
-        echo -e "${GREEN}[bluera-knowledge] Successfully installed crawl4ai ✓${NC}"
-        crawl4ai_version=$(python3 -c "import crawl4ai; print(crawl4ai.__version__)" 2>/dev/null || echo "installed")
-        echo -e "${GREEN}[bluera-knowledge] crawl4ai ${crawl4ai_version} ready${NC}"
-        # Install Playwright browser for headless crawling
-        install_playwright_browser
-    else
-        # Fallback: try without --break-system-packages for older Python
-        if $PIP_CMD install --quiet --user crawl4ai 2>/dev/null; then
-            echo -e "${GREEN}[bluera-knowledge] Successfully installed crawl4ai ✓${NC}"
-            crawl4ai_version=$(python3 -c "import crawl4ai; print(crawl4ai.__version__)" 2>/dev/null || echo "installed")
-            echo -e "${GREEN}[bluera-knowledge] crawl4ai ${crawl4ai_version} ready${NC}"
-            # Install Playwright browser for headless crawling
-            install_playwright_browser
-        else
-            echo -e "${RED}[bluera-knowledge] Auto-installation failed${NC}"
-            echo ""
-            echo -e "${YELLOW}For Python 3.11+ (externally-managed), install manually:${NC}"
-            echo -e "  ${GREEN}pip install --break-system-packages crawl4ai${NC}"
-            echo -e "${YELLOW}Or use a virtual environment:${NC}"
-            echo -e "  ${GREEN}python3 -m venv venv && source venv/bin/activate && pip install crawl4ai${NC}"
-        fi
-    fi
+# Install crawl4ai into venv
+echo -e "${YELLOW}[bluera-knowledge] Installing crawl4ai into virtual environment...${NC}"
+echo -e "${YELLOW}(Set BK_SKIP_AUTO_INSTALL=1 to disable auto-install)${NC}"
+
+if "$VENV_PIP" install --quiet crawl4ai 2>/dev/null; then
+    crawl4ai_version=$("$VENV_PYTHON" -c "import crawl4ai; print(crawl4ai.__version__)" 2>/dev/null || echo "installed")
+    echo -e "${GREEN}[bluera-knowledge] crawl4ai ${crawl4ai_version} installed (venv) ✓${NC}"
+    # Install Playwright browser for headless crawling
+    install_playwright_browser "$VENV_PYTHON"
 else
-    echo -e "${YELLOW}pip not found. Please install crawl4ai manually.${NC}"
+    echo -e "${RED}[bluera-knowledge] Failed to install crawl4ai${NC}"
+    echo -e "${YELLOW}Manual fix:${NC}"
+    echo -e "  ${GREEN}$VENV_PIP install crawl4ai${NC}"
+    echo -e "  ${GREEN}$VENV_PYTHON -m playwright install chromium${NC}"
 fi
 
 # Always exit 0 to not block the session

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bluera-knowledge",
-  "version": "0.13.3",
+  "version": "0.14.1",
   "description": "CLI tool for managing knowledge stores with semantic search",
   "type": "module",
   "bin": {
@@ -64,6 +64,17 @@
   "publishConfig": {
     "access": "public"
   },
+  "files": [
+    "dist/",
+    "python/",
+    "hooks/",
+    "commands/",
+    "skills/",
+    ".claude-plugin/",
+    "README.md",
+    "CHANGELOG.md",
+    "LICENSE"
+  ],
   "devDependencies": {
     "@eslint/js": "^9.39.2",
     "@types/babel__core": "^7.20.5",

package/.claude/commands/code-review.md

@@ -1,15 +0,0 @@
-# Code Review
-
-Review the local codebase using multi-agent analysis. See @.claude/skills/code-review-repo/skill.md for process details.
-
-## Context
-
-!`echo "---PROJECT---" && ls -la && echo "---CLAUDE.md FILES---" && find . -name CLAUDE.md 2>/dev/null`
-
-## Workflow
-
-1. **Gather context**: Find all CLAUDE.md files and source files
-2. **Multi-agent review**: Launch 5 parallel agents (CLAUDE.md compliance, bug scan, git history, PR comments, code comments)
-3. **Score issues**: Haiku agents score each issue 0-100 for confidence
-4. **Filter**: Only report issues with confidence >= 80
-5. **Output**: Print formatted results to console

package/.claude/commands/commit.md

@@ -1,34 +0,0 @@
-# Commit
-
-Create atomic, well-organized commits. See @.claude/skills/atomic-commits/SKILL.md for documentation check criteria.
-
-## Context
-
-!`git status && echo "---STAGED---" && git diff --cached --stat && echo "---UNSTAGED---" && git diff --stat && echo "---UNTRACKED---" && git ls-files --others --exclude-standard && echo "---HISTORY---" && git log --oneline -10`
-
-## Workflow
-
-1. **Analyze**: Run `git diff HEAD` to see all changes
-2. **Documentation Check**: Check if README.md or CLAUDE.md need updates (see skill)
-3. **Group**: Identify logical features (see skill for grouping rules)
-4. **Commit each group**:
-   ```bash
-   git add <files>
-   git commit -m "<type>(<scope>): <description>"
-   ```
-5. **Handle untracked**: Categorize as commit/ignore/intentional
-6. **Report**: Show commits created and final `git status --short`
-
-## Validation
-
-Pre-commit hooks run automatically:
-- **Doc-only changes**: Skips all validation (instant)
-- **Code changes**: Runs lint + typecheck per language
-
-If hooks fail, fix issues and retry. Never use `--no-verify`.
-
-## Safety
-
-- Never force push
-- Never amend commits from other sessions
-- Ask if unsure about grouping

package/.claude/council-cache/1a43ed5977b8f29afc79a9bf5c4082ee5ad8338c42ab991a4241a48f80c1e46d.json

@@ -1,7 +0,0 @@
-{
-  "provider": "openai",
-  "model": "codex-mini-latest",
-  "prompt": "What are the best trigger keywords and patterns for a skill auto-activation system in a Claude Code plugin? Context: We're building a UserPromptSubmit hook for the bluera-knowledge plugin that detects when users would benefit from learning about specific skills. The 5 skills are: (1) knowledge-search - how to query indexed library sources, (2) when-to-query - deciding between BK vs Grep/Read, (3) search-optimization - optimizing search parameters, (4) advanced-workflows - multi-tool orchestration, (5) store-lifecycle - managing knowledge stores. Key insight: if a user already uses BK terminology, they don't need the skill suggested. We want to catch users who SHOULD be using BK but don't know it exists.",
-  "response": "Below is a bite‑sized “pattern cookbook” you can drop into your `UserPromptSubmit` hook in the bluera‑knowledge Claude Code plugin. The idea is simple:\n\n1. **Look for “natural” signals** that a user is trying to do something Blue‑Knowledge (BK) was built for, but  \n2. **Exclude** anyone already using BK lingo (e.g. “knowledge‑search,” “index,” “store,” “workflow”) so you don’t remind the experienced.\n\n---\n\n## 1. Skill → Trigger‑patterns matrix\n\n| Skill                | What it is                                                                                   | Trigger patterns (if user text _contains_)                                                                                                     | Exclude if user text _contains_                        |\n|:---------------------|:---------------------------------------------------------------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------|:--------------------------------------------------------|\n| **knowledge‑search** | How to query an indexed library of docs/sources.                                             | `\\b(find|lookup|search|get me|show me|where can i find)\\b.*\\b(docs|documentation|references?|articles?)\\b`                                       | `\\bknowledge[- ]search\\b|\\bindex(ed)?\\b|\\bstore\\b`       |\n| **when‑to‑query**    | Deciding whether to use BK vs. grep/`read()` etc.                                             | `\\b(grep|read\\(\\)|scan files|open files manually|search local files)\\b|\\b(is there a better way)\\b`                                             | `\\bwhen[- ]to[- ]query\\b|\\bblue[- ]knowledge\\b`          |\n| **search‑optimization** | Tuning filters, relevance, context windows, metadata to get better hits.                   | `\\b(narrow|filter|refine|limit|boost|prioritize|sort)\\b.*\\b(results|hits|matches)\\b`                                                           | `\\bsearch[- ]optimization\\b|\\brelevance\\b|\\bcontext window\\b` |\n| **advanced‑workflows** | Chaining multiple tools/APIs, branching, retrieval‑then‑generation, tool orchestration.      | `\\b(chain|pipeline|orchestrate|automate|workflow|multi[- ]step|multi[- ]tool)\\b`                                                               | `\\badvanced[- ]workflows\\b|\\btool orchestration\\b`       |\n| **store‑lifecycle**   | Setting up/updating/archiving knowledge stores, versioning, pruning old info.               | `\\b(create|update|delete|archive|prune|version)\\b.*\\b(store|index|database|repository)\\b`                                                       | `\\bstore[- ]lifecycle\\b|\\bknowledge[- ]store\\b`          |\n\n---\n\n### 1.1. Example Regex snippets\n\n```js\n// snippet for knowledge-search\nconst KNOWLEDGE_SEARCH_RE = /\\b(?:find|lookup|search|get me|show me|where can i find)\\b.*\\b(?:docs|documentation|references?|articles?)\\b/i;\n\n// snippet for when-to-query\nconst WHEN_TO_QUERY_RE = /\\b(?:grep|read\\(\\)|scan files|open files manually|search local files)\\b|\\b(?:is there a better way)\\b/i;\n\n// snippet for store-lifecycle\nconst STORE_LIFECYCLE_RE = /\\b(?:create|update|delete|archive|prune|version)\\b.*\\b(?:store|index|database|repository)\\b/i;\n```\n\n---\n\n## 2. Putting it together in your hook\n\nBelow is a simplified example of how you might wire these patterns into a Claude Code `UserPromptSubmit` hook. You’ll want to adjust the messaging and localization to taste.\n\n```js\n/**\n * bluera-knowledge UserPromptSubmit hook\n * Detect users who could benefit from Blue‑Knowledge skills.\n */\nexport async function onUserPromptSubmit(event, ctx) {\n  const text = event.prompt.text;\n\n  // quick bailout: if they already speak BK\n  const hasBKTerm = /\\bknowledge[- ]search\\b|\\bwhen[- ]to[- ]query\\b|\\bsearch[- ]optimization\\b|\\badvanced[- ]workflows\\b|\\bstore[- ]lifecycle\\b|\\bblue[- ]knowledge\\b/i.test(text);\n  if (hasBKTerm) return;\n\n  // mapping skill → [pattern, user‐facing hint]\n  const SKILLS = [\n    {\n      name: \"knowledge-search\",\n      re: /\\b(?:find|lookup|search|get me|show me|where can i find)\\b.*\\b(?:docs|documentation|references?|articles?)\\b/i,\n      hint: \"🔍 You can try using our **knowledge‑search** feature to query indexed docs—no manual grepping needed!\"\n    },\n    {\n      name: \"when-to-query\",\n      re: /\\b(?:grep|read\\(\\)|scan files|open files manually|search local files)\\b|\\b(?:is there a better way)\\b/i,\n      hint: \"💡 Noticed you're grepping or opening files one by one. Our **when‑to‑query** guide helps decide BK vs. direct file search.\"\n    },\n    {\n      name: \"search-optimization\",\n      re: /\\b(?:narrow|filter|refine|limit|boost|prioritize|sort)\\b.*\\b(?:results|hits|matches)\\b/i,\n      hint: \"⚙️ Want more relevant hits? See our **search‑optimization** tips for tuning relevance and filters.\"\n    },\n    {\n      name: \"advanced-workflows\",\n      re: /\\b(?:chain|pipeline|orchestrate|automate|workflow|multi[- ]step|multi[- ]tool)\\b/i,\n      hint: \"🔗 Looking to chain tools or build pipelines? Check out **advanced‑workflows** for multi‑tool orchestration.\"\n    },\n    {\n      name: \"store-lifecycle\",\n      re: /\\b(?:create|update|delete|archive|prune|version)\\b.*\\b(?:store|index|database|repository)\\b/i,\n      hint: \"🗄️ Managing indexes or archiving old data? Our **store‑lifecycle** guide covers store setup, pruning, and versioning.\"\n    }\n  ];\n\n  // find the first match\n  for (const skill of SKILLS) {\n    if (skill.re.test(text)) {\n      await ctx.reply({\n        type: \"skill-suggestion\",\n        skill: skill.name,\n        message: skill.hint\n      });\n      break;\n    }\n  }\n}\n```\n\n---\n\n## 3. Tuning tips\n\n1. **Balance precision/recall**:  \n   - Start _wide_: shorter patterns catch more but risk noise.  \n   - Refine as you gather real prompts: update regex to avoid false positives.\n\n2. **Avoid overlap**:  \n   If two patterns both match, pick the one that feels _most_ immediately helpful. (Above example picks the first.)\n\n3. **User‑facing copy**:  \n   Keep hints crisp, emoji‑tagged, and link directly to your docs or `@help` commands.\n\n4. **Metrics & feedback loop**:  \n   Log suggestions shown vs. accepted. Tune patterns around low‑acceptance hits.\n\n---\n\n### Summary\n\nBy combining simple regex‑based detectors with an exclusion of existing BK terminology, you’ll catch “hidden” use cases where users are laboring manually and would love a BK shortcut. Tweak patterns over time against your live traffic, and you’ll have a reliable auto‑activation layer that boosts discoverability _without_ nagging your power users.",
-  "timestamp": 1768432278
-}

package/.claude/hooks/post-edit-check.sh

@@ -1,40 +0,0 @@
-#!/bin/bash
-# Smart post-edit auto-fix hook
-# Auto-fixes lint issues and validates types on modified files
-
-cd "$CLAUDE_PROJECT_DIR" || exit 0
-
-# Get modified TS/JS files (uncommitted changes)
-MODIFIED_TS_FILES=$(git diff --name-only HEAD 2>/dev/null | grep -E '\.(ts|tsx|js|jsx)$' || true)
-
-# If no TS/JS changes, skip
-if [ -z "$MODIFIED_TS_FILES" ]; then
-  exit 0
-fi
-
-# Auto-fix lint issues on modified files only (fast)
-echo "$MODIFIED_TS_FILES" | xargs npx eslint --fix --quiet 2>/dev/null || true
-
-# Check for remaining lint errors (exit 2 to block and show to Claude)
-LINT_OUTPUT=$(echo "$MODIFIED_TS_FILES" | xargs npx eslint --quiet 2>&1)
-if [ -n "$LINT_OUTPUT" ]; then
-  echo "$LINT_OUTPUT" >&2
-  exit 2
-fi
-
-# Run typecheck (exit 2 to block and show to Claude)
-TYPE_OUTPUT=$(npx tsc --noEmit --pretty false 2>&1)
-if [ -n "$TYPE_OUTPUT" ]; then
-  echo "$TYPE_OUTPUT" | head -20 >&2
-  exit 2
-fi
-
-# Check for anti-patterns in code files only (not docs/markdown)
-ANTI_PATTERN=$(git diff -- '*.ts' '*.tsx' '*.js' '*.jsx' ':!dist/' | grep -E '\b(fallback|deprecated|backward compatibility|legacy)\b' | grep -v '^-' | grep -E '^\+' || true)
-if [ -n "$ANTI_PATTERN" ]; then
-  echo 'Anti-pattern detected (fallback/deprecated/backward compatibility/legacy). Review CLAUDE.md.' >&2
-  echo "$ANTI_PATTERN" >&2
-  exit 2
-fi
-
-exit 0

package/.claude/rules/code-quality.md

@@ -1,12 +0,0 @@
-# Code Quality Rules
-
-## Fail Early and Fast
-
-Our code is expected to *work* as-designed:
-- Use `throw` when state is unexpected or for any error condition
-- Use 100% strict typing; no `any` no `as`, unless completely unavoidable and considered best practice
-
-## Never
-
-- Write "fallback code" or "graceful degradation" code or implement "defaults" *unless* it's part of the specification
-- Leave commented code, nor reference outdated/deprecated implementations

package/.claude/rules/git.md

@@ -1,5 +0,0 @@
-# Git Rules
-
-## Never
-
-- Use `--no-verify` on Git commits; this anti-pattern completely circumvents the code protections we have in place

package/.claude/rules/versioning.md

@@ -1,7 +0,0 @@
-# Versioning Rules
-
-## Always
-
-- Use the `bun run version:*` commands after changes
-  - Without this, the changes would not be detected by Claude Code
-- Push to main after version bump - releases happen automatically (no manual tagging needed)

package/.claude/settings.local.json.example

@@ -1,45 +0,0 @@
-{
-  "permissions": {
-    "allow": [
-      "Bash(osascript:*)",
-      "Bash(bun run lint:*)",
-      "Bash(bun run typecheck:*)",
-      "Bash(npm run lint:*)",
-      "Bash(npm run typecheck:*)",
-      "Bash(bun run precommit:*)"
-    ],
-    "deny": [
-      "Bash(*validate-npm-release*)",
-      "Bash(bun run validate:*)",
-      "Bash(npm run validate:*)"
-    ]
-  },
-  "hooks": {
-    "PostToolUse": [
-      {
-        "matcher": "Write|Edit",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "\"$CLAUDE_PROJECT_DIR/.claude/hooks/post-edit-check.sh\"",
-            "statusMessage": "Validating changes..."
-          }
-        ]
-      }
-    ],
-    "Notification": [
-      {
-        "matcher": "permission_prompt|idle_prompt|elicitation_dialog",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "osascript -e 'display notification \"Claude needs your input\" with title \"Claude Code\" sound name \"Glass\"' 2>/dev/null || true"
-          }
-        ]
-      }
-    ]
-  },
-  "enabledPlugins": {
-    "bluera-knowledge@bluera": true
-  }
-}

package/.claude/skills/atomic-commits/SKILL.md

@@ -1,61 +0,0 @@
----
-name: atomic-commits
-description: Create atomic commits grouped by logical features with README.md and CLAUDE.md awareness.
-version: 1.0.0
----
-
-# Atomic Commits with Documentation Awareness
-
-Guidelines for creating well-organized commits with README.md and CLAUDE.md awareness.
-
-## Documentation Check
-
-Before committing, evaluate if changes need documentation updates.
-
-### README.md (User-facing documentation)
-
-| Change Type | README Section to Update |
-|-------------|-------------------------|
-| MCP tools added/removed/renamed | MCP Tools table, MCP Integration section |
-| New commands or skills | Commands/Skills documentation |
-| CLI interface changes | Usage examples |
-| Configuration changes | Configuration/Environment sections |
-| Breaking API changes | Upgrade/migration notes |
-| New features | Feature documentation |
-| Installation changes | Installation section |
-
-**Trigger files → check README.md:**
-- `src/mcp/server.ts` - MCP tool surface
-- `.claude-plugin/plugin.json` - Plugin metadata
-- `commands/*.md` - Command documentation
-
-### CLAUDE.md (Claude Code memory - hierarchical)
-
-CLAUDE.md stores context that helps future sessions "do the right thing". Update when:
-- You struggled with something and the insight would prevent future mistakes
-- Important patterns or conventions that aren't obvious from code alone
-- Workflows or commands that are non-trivial to discover
-
-CLAUDE.md is hierarchical - use the directory level matching the changed files. Use `@path/to/file` includes to stay DRY.
-
-| Change Scope | Which CLAUDE.md |
-|--------------|-----------------|
-| Project-wide (scripts, CI/CD, build) | Root CLAUDE.md |
-| Directory-specific patterns | Subdirectory CLAUDE.md (create if needed) |
-
-## Grouping Rules
-
-Identify logical features by grouping related files:
-- Same feature = same commit
-- Infrastructure/config = separate commit
-- Tests = with their implementation OR separate if test-only
-
-## Commit Message Format
-
-```
-<type>(<scope>): <description>
-```
-
-Types: `feat`, `fix`, `docs`, `chore`, `refactor`, `test`, `style`, `build`, `ci`, `perf`
-
-**Note:** Commit messages are validated by commitlint (conventional commits format).

package/.claude/skills/code-review-repo/skill.md

@@ -1,62 +0,0 @@
----
-name: code-review-repo
-description: Review local codebase for bugs and CLAUDE.md compliance using multi-agent analysis
-version: 1.0.0
----
-
-# Local Code Review
-
-Review the entire local codebase for bugs, issues, and CLAUDE.md compliance.
-
-## Process
-
-1. **Gather CLAUDE.md files**: Use a Haiku agent to find all CLAUDE.md files in the repository (root and subdirectories)
-
-2. **Identify source files**: Determine which files to review:
-   - Include: `.ts`, `.tsx`, `.js`, `.jsx`, `.py`, `.rs`, `.go` and similar source files
-   - Exclude: `node_modules/`, `dist/`, `.git/`, vendor directories, generated files
-
-3. **Multi-agent review**: Launch 5 parallel Sonnet agents to independently review the codebase. Each agent returns a list of issues with reasons:
-   - **Agent #1**: Audit for CLAUDE.md compliance. Check that code follows guidelines in all relevant CLAUDE.md files.
-   - **Agent #2**: Shallow bug scan. Look for obvious bugs, error handling issues, and logic errors. Focus on significant bugs, not nitpicks.
-   - **Agent #3**: Git history context. Use git blame and history to identify patterns, recent changes, and potential issues in light of historical context.
-   - **Agent #4**: Previous PR comments. Check closed PRs that touched these files for any feedback that might apply.
-   - **Agent #5**: Code comment compliance. Ensure code follows any guidance in TODO, FIXME, NOTE, or other code comments.
-
-4. **Confidence scoring**: For each issue found, launch a parallel Haiku agent to score confidence (0-100):
-   - **0**: False positive, doesn't hold up to scrutiny
-   - **25**: Might be real, but unverified. Stylistic issues not in CLAUDE.md
-   - **50**: Real but minor, rarely hit in practice
-   - **75**: Verified real issue, important, directly impacts functionality or mentioned in CLAUDE.md
-   - **100**: Definitely real, frequently hit, evidence confirms
-
-5. **Filter**: Only report issues with score >= 80
-
-## False Positive Examples
-
-Avoid flagging:
-- Issues that linters/typecheckers catch (imports, types, formatting)
-- General quality issues unless in CLAUDE.md
-- Code with lint-ignore comments for that specific issue
-- Pre-existing issues unrelated to recent changes
-- Pedantic nitpicks a senior engineer wouldn't mention
-
-## Output Format
-
-### Code review
-
-Found N issues:
-
-1. Brief description (CLAUDE.md says "...")
-   `file/path.ts:42`
-
-2. Brief description (bug due to missing error handling)
-   `file/path.ts:88-95`
-
----
-
-Or if no issues:
-
-### Code review
-
-No issues found. Checked for bugs and CLAUDE.md compliance.

package/.editorconfig

@@ -1,15 +0,0 @@
-root = true
-
-[*]
-charset = utf-8
-end_of_line = lf
-insert_final_newline = true
-trim_trailing_whitespace = true
-indent_style = space
-indent_size = 2
-
-[*.md]
-trim_trailing_whitespace = false
-
-[*.ts]
-indent_size = 2

package/.env.example

@@ -1,21 +0,0 @@
-# Required Configuration
-# Copy this file to .env and set all values
-
-# Logging Configuration
-# Valid values: trace, debug, info, warn, error, fatal
-LOG_LEVEL=info
-
-# Search Quality Configuration
-# Test file boost multiplier (lower values penalize test files more)
-SEARCH_TEST_FILE_BOOST=0.5
-
-# Confidence thresholds for raw vector similarity scoring
-# Results with maxRawScore >= high threshold are "high" confidence
-# Results with maxRawScore >= medium threshold are "medium" confidence
-# Results below medium threshold are "low" confidence
-SEARCH_CONFIDENCE_HIGH=0.5
-SEARCH_CONFIDENCE_MEDIUM=0.3
-
-# MCP Server Configuration
-# Project root directory for MCP server
-PROJECT_ROOT=/path/to/project