feat(search): implement actual file search in search_docs tool

Replace the previous template-based response (which only returned
instructions on where to search) with a real streaming grep engine that
returns file path, line number, and matched content — just like ripgrep.

Key decisions:
- Pure Node.js streaming regex grep as primary search (no binary deps,
  cross-platform, supports full JS/ripgrep regex: auth|login, \s+\w+, etc.)
- MiniSearch (already a transitive dep) as optional pre-filter/ranker to
  limit candidate files on large docsets before line-level grep
- OR syntax satisfied by native RegExp — no extra tooling needed
- context_lines defaults to 0 (was 2); exposed as optional MCP param so
  callers can request 1–3 lines of surrounding context when needed

Changes:
- packages/core/src/search/searcher.ts  — new core search engine
  (buildFileIndex, searchDocset, formatSearchResult)
- packages/core/src/types.ts            — SearchMatch, SearchDocsResult,
  SearchOptions types
- packages/core/src/index.ts            — export new search symbols
- packages/mcp-server/src/server.ts     — replace template processing with
  actual search; add context_lines param to search_docs tool schema
- packages/core/src/__tests__/searcher.test.ts  — 25 new unit tests
- packages/mcp-server/src/__tests__/web-sources.test.ts — update 3 tests
  for new grep-style content[0].text response shape
- test/e2e/mcp-protocol-compliance.test.ts — update 4 stale E2E tests
  that asserted old structuredContent/instructions response shape
- docs/adr/001-search-engine-for-search-docs-tool.md — Nygard ADR with
  weighted Pugh matrix comparing ripgrep wrapper vs MiniSearch hybrid vs
  Node.js streaming grep (Option C wins, score +21 vs baseline)

Author: mrsimpson

.beads/README.md

@@ -0,0 +1,85 @@
+# Beads - AI-Native Issue Tracking
+
+Welcome to Beads! This repository uses **Beads** for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code.
+
+## What is Beads?
+
+Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.
+
+**Learn more:** [github.com/steveyegge/beads](https://github.com/steveyegge/beads)
+
+## Quick Start
+
+### Essential Commands
+
+```bash
+# Create new issues
+bd create "Add user authentication"
+
+# View all issues
+bd list
+
+# View issue details
+bd show <issue-id>
+
+# Update issue status
+bd update <issue-id> --status in_progress
+bd update <issue-id> --status done
+
+# Sync with git remote
+bd sync
+```
+
+### Working with Issues
+
+Issues in Beads are:
+
+- **Git-native**: Stored in `.beads/issues.jsonl` and synced like code
+- **AI-friendly**: CLI-first design works perfectly with AI coding agents
+- **Branch-aware**: Issues can follow your branch workflow
+- **Always in sync**: Auto-syncs with your commits
+
+## Why Beads?
+
+✨ **AI-Native Design**
+
+- Built specifically for AI-assisted development workflows
+- CLI-first interface works seamlessly with AI coding agents
+- No context switching to web UIs
+
+🚀 **Developer Focused**
+
+- Issues live in your repo, right next to your code
+- Works offline, syncs when you push
+- Fast, lightweight, and stays out of your way
+
+🔧 **Git Integration**
+
+- Automatic sync with git commits
+- Branch-aware issue tracking
+- Intelligent JSONL merge resolution
+
+## Get Started with Beads
+
+Try Beads in your own projects:
+
+```bash
+# Install Beads
+curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
+
+# Initialize in your repo
+bd init
+
+# Create your first issue
+bd create "Try out Beads"
+```
+
+## Learn More
+
+- **Documentation**: [github.com/steveyegge/beads/docs](https://github.com/steveyegge/beads/tree/main/docs)
+- **Quick Start Guide**: Run `bd quickstart`
+- **Examples**: [github.com/steveyegge/beads/examples](https://github.com/steveyegge/beads/tree/main/examples)
+
+---
+
+_Beads: Issue tracking that moves at the speed of thought_ ⚡

.beads/config.yaml

@@ -0,0 +1,62 @@
+# Beads Configuration File
+# This file configures default behavior for all bd commands in this repository
+# All settings can also be set via environment variables (BD_* prefix)
+# or overridden with command-line flags
+
+# Issue prefix for this repository (used by bd init)
+# If not set, bd init will auto-detect from directory name
+# Example: issue-prefix: "myproject" creates issues like "myproject-1", "myproject-2", etc.
+issue-prefix: "agentic-knowledge"
+
+# Use no-db mode: load from JSONL, no SQLite, write back after each command
+# When true, bd will use .beads/issues.jsonl as the source of truth
+# instead of SQLite database
+no-db: true # JSONL-only mode, no SQLite database
+
+# Disable daemon for RPC communication (forces direct database access)
+# no-daemon: false
+
+# Disable auto-flush of database to JSONL after mutations
+# no-auto-flush: false
+
+# Disable auto-import from JSONL when it's newer than database
+# no-auto-import: false
+
+# Enable JSON output by default
+# json: false
+
+# Default actor for audit trails (overridden by BD_ACTOR or --actor)
+# actor: ""
+
+# Path to database (overridden by BEADS_DB or --db)
+# db: ""
+
+# Auto-start daemon if not running (can also use BEADS_AUTO_START_DAEMON)
+# auto-start-daemon: true
+
+# Debounce interval for auto-flush (can also use BEADS_FLUSH_DEBOUNCE)
+# flush-debounce: "5s"
+
+# Git branch for beads commits (bd sync will commit to this branch)
+# IMPORTANT: Set this for team projects so all clones use the same sync branch.
+# This setting persists across clones (unlike database config which is gitignored).
+# Can also use BEADS_SYNC_BRANCH env var for local override.
+# If not set, bd sync will require you to run 'bd config set sync.branch <branch>'.
+# sync-branch: "beads-sync"
+
+# Multi-repo configuration (experimental - bd-307)
+# Allows hydrating from multiple repositories and routing writes to the correct JSONL
+# repos:
+#   primary: "."  # Primary repo (where this database lives)
+#   additional:   # Additional repos to hydrate from (read-only)
+#     - ~/beads-planning  # Personal planning repo
+#     - ~/work-planning   # Work planning repo
+
+# Integration settings (access with 'bd config get/set')
+# These are stored in the database, not in this file:
+# - jira.url
+# - jira.project
+# - linear.url
+# - linear.api-key
+# - github.org
+# - github.repo

.beads/interactions.jsonl

@@ -0,0 +1,5 @@
+{"id":"agentic-knowledge-1","title":"agentic-knowledge: epcc (development-plan-actually-search.md)","description":"Responsible vibe engineering session using epcc workflow for agentic-knowledge","status":"open","priority":2,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-10T09:55:15.223205+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-10T09:55:15.223205+01:00"}
+{"id":"agentic-knowledge-1.1","title":"Explore","description":"Research the codebase to understand existing patterns and gather context about the problem space.  - If uncertain about conventions or rules, ask the user about them - Read relevant files and documentation - If  exists: Understand and document requirements there - Otherwise: Document requirements in your task management system  Focus on understanding without writing code yet. Document your findings and create tasks as needed.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-10T09:55:15.37274+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-10T09:55:15.37274+01:00","dependencies":[{"issue_id":"agentic-knowledge-1.1","depends_on_id":"agentic-knowledge-1","type":"parent-child","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"agentic-knowledge-1.2","title":"Plan","description":"Create a detailed implementation strategy based on your exploration:  - If  exists: Base your strategy on requirements from it - Otherwise: Use existing task context  Break down the work into specific, actionable tasks. Consider edge cases, dependencies, and potential challenges.  - If architectural changes needed and  exists: Document in  - Otherwise: Create tasks to track architectural decisions  - If  exists: Adhere to the design in it - Otherwise: Elaborate design options and present them to the user  Document the planning work thoroughly and create implementation tasks as part of the code phase as needed.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-10T09:55:15.524416+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-10T09:55:15.524416+01:00","dependencies":[{"issue_id":"agentic-knowledge-1.2","depends_on_id":"agentic-knowledge-1","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"agentic-knowledge-1.2","depends_on_id":"agentic-knowledge-1.1","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"agentic-knowledge-1.3","title":"Code","description":"Follow your plan to build the solution:  - If  exists: Follow the design from it - Otherwise: Elaborate design options and present them to the user - If  exists: Build according to the architecture from it - Otherwise: Elaborate architectural options and present them to the user - If  exists: Ensure requirements from it are met - Otherwise: Ensure existing requirements are met based on your task context  Write clean, well-structured code with proper error handling. Prevent regression by building, linting, and executing existing tests. Stay flexible and adapt the plan as you learn more during implementation. Update task progress and create new tasks as needed.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-10T09:55:15.67957+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-10T09:55:15.67957+01:00","dependencies":[{"issue_id":"agentic-knowledge-1.3","depends_on_id":"agentic-knowledge-1","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"agentic-knowledge-1.3","depends_on_id":"agentic-knowledge-1.2","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}
+{"id":"agentic-knowledge-1.4","title":"Commit","description":"Ensure code quality and documentation accuracy through systematic cleanup and review. **STEP 1: Code Cleanup** Systematically clean up development artifacts: 1. **Remove Debug Output**: Search for and remove all temporary debug output statements used during development.    Look for language-specific debug output methods (console logging, print statements, debug output functions).    Remove any debugging statements that were added for development purposes.  2. **Review TODO/FIXME Comments**:    - Address each TODO/FIXME comment by either implementing the solution or documenting why it's deferred    - Remove completed TODOs    - Convert remaining TODOs to proper issue tracking if needed  3. **Remove Debugging Code Blocks**:    - Remove temporary debugging code, test code blocks, and commented-out code    - Clean up any experimental code that's no longer needed    - Ensure proper error handling replaces temporary debug logging  **STEP 2: Documentation Review** Review and update documentation to reflect final implementation: 1. **Update Long-Term Memory Documents**: Based on what was actually implemented:    - If  exists: Update it if requirements changed during development    - If  exists: Update it if architectural impacts were identified    - If  exists: Update it if design details were refined or changed    - Otherwise: Document any changes in the plan file 2. **Compare Against Implementation**: Review documentation against actual implemented functionality 3. **Update Changed Sections**: Only modify documentation sections that have functional changes 4. **Remove Development Progress**: Remove references to development iterations, progress notes, and temporary decisions 5. **Focus on Final State**: Ensure documentation describes the final implemented state, not the development process 6. **Ask User to Review Document Updates** **STEP 3: Final Validation** - Run existing tests to ensure cleanup didn't break functionality - Verify documentation accuracy with a final review - Ensure code is ready for production/delivery Update task progress and mark completed work as you finalize the feature.","status":"open","priority":3,"issue_type":"task","owner":"github@beimir.net","created_at":"2026-03-10T09:55:15.837066+01:00","created_by":"Oliver Jägle","updated_at":"2026-03-10T09:55:15.837066+01:00","dependencies":[{"issue_id":"agentic-knowledge-1.4","depends_on_id":"agentic-knowledge-1","type":"parent-child","created_at":"0001-01-01T00:00:00Z"},{"issue_id":"agentic-knowledge-1.4","depends_on_id":"agentic-knowledge-1.3","type":"blocks","created_at":"0001-01-01T00:00:00Z"}]}

.beads/issues.jsonl

@@ -0,0 +1 @@
+agentic-knowledge-1.4

.beads/last-touched

@@ -0,0 +1,4 @@
+{
+  "database": "beads.db",
+  "jsonl_export": "issues.jsonl"
+}

.beads/metadata.json

@@ -0,0 +1,29 @@
+{
+  "conversationId": "agentic-knowledge-actually-search-p423k1",
+  "projectPath": "/Users/oliverjaegle/projects/privat/mcp-server/agentic-knowledge",
+  "epicId": "agentic-knowledge-1",
+  "phaseTasks": [
+    {
+      "phaseId": "explore",
+      "phaseName": "Explore",
+      "taskId": "agentic-knowledge-1.1"
+    },
+    {
+      "phaseId": "plan",
+      "phaseName": "Plan",
+      "taskId": "agentic-knowledge-1.2"
+    },
+    {
+      "phaseId": "code",
+      "phaseName": "Code",
+      "taskId": "agentic-knowledge-1.3"
+    },
+    {
+      "phaseId": "commit",
+      "phaseName": "Commit",
+      "taskId": "agentic-knowledge-1.4"
+    }
+  ],
+  "createdAt": "2026-03-10T08:55:16.192Z",
+  "updatedAt": "2026-03-10T08:55:16.192Z"
+}