feat(agents): add learnings-researcher for institutional knowledge (#106)

* fix(compound-docs): correct severity enum in validation example

The example error message referenced [critical, moderate, minor] but
the yaml-schema.md defines severity as [critical, high, medium, low].

* refactor(agents): standardize search tool recommendations

- Update repo-research-analyst to recommend built-in Grep tool instead
  of CLI rg (Grep uses ripgrep under the hood)
- Add TypeScript example for ast-grep alongside Ruby
- Update pattern-recognition-specialist to use built-in Grep tool
- Keep ast-grep for AST-based structural matching (language-specific)

* feat(agents): add learnings-researcher for institutional knowledge

Add new research agent that efficiently searches docs/solutions/ for
relevant past solutions before implementing features or fixing bugs.

Key features:
- Grep-first filtering strategy for efficiency with 100+ files
- Category-based narrowing to reduce search scope
- Parallel Grep calls with synonym support (OR patterns)
- Frontmatter-only reads before full document reads
- Always checks critical patterns file
- Uses haiku model for speed (structured task, recipe-based)

Integrates with /workflows:plan to run in parallel with
repo-research-analyst during local research phase.

Closes the loop on compound engineering: solutions documented via
/workflows:compound are now discoverable during planning.

plugins/compound-engineering/agents/review/pattern-recognition-specialist.md

@@ -34,7 +34,7 @@ Your primary responsibilities:
 
 Your workflow:
 
-1. Start with a broad pattern search using grep or ast-grep for structural matching
+1. Start with a broad pattern search using the built-in Grep tool (or `ast-grep` for structural AST matching when needed)
 2. Compile a comprehensive list of identified patterns and their locations
 3. Search for common anti-pattern indicators (TODO, FIXME, HACK, XXX)
 4. Analyze naming conventions by sampling representative files