projecta-rrr 1.21.9 → 1.21.10

package/CHANGELOG.md

@@ -4,6 +4,51 @@ All notable changes to RRR will be documented in this file.
 
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
+## [1.21.10] - 2026-04-18
+
+**semantic_search injection waves 2 + 3.**
+
+Completes the token-saving rollout started in v1.21.9. Waves 2 and 3 target
+commands that auditor identified as MED priority but still carry significant
+token cost in practice — milestone audits, gap planning, roadmap creation,
+project research, and the planner agent itself.
+
+### Added
+
+- **semantic_search in `rrr-planner` agent.** Planner previously grepped
+  CONTEXT.md and ROADMAP sections during task breakdown — now prefers
+  ~500-token semantic_search for "existing implementations", "similar
+  patterns", "existing code shape" queries.
+
+- **semantic_search reference in 4 more commands:** `/rrr:audit-milestone`,
+  `/rrr:plan-milestone-gaps`, `/rrr:create-roadmap`, `/rrr:research-project`.
+  These don't run every session but they dominate milestone boundaries —
+  typical burn 12-22K each before this change.
+
+- **`semantic-search-preference.md` domain-query patterns (wave 3).**
+  10-row table: tech stack, architecture, similar implementation, error
+  root-cause, requirement coverage, auth/security, data model, test
+  coverage, API surface, config. With suggested k per query. Purpose:
+  stop Claude from grepping for "middleware" when a better-phrased
+  semantic_search would nail it in one call.
+
+### Status after waves 1-3
+
+Commands using semantic_search: **13 of 23** (was 5). The 10 remaining
+untouched commands do minimal code exploration (<5K tokens each) —
+diminishing returns beyond here.
+
+Agents using semantic_search: **5 of ~15** — the five highest-burn ones
+(rrr-codebase-mapper, rrr-phase-researcher, rrr-executor, rrr-debugger,
+rrr-planner). These carry ~80% of agent-side exploration cost.
+
+### Next (v1.22.0)
+
+Webhook-driven re-index infrastructure (GitHub App single-URL webhook +
+local post-commit hook → local MCP). Closes the "stale index" gap — today
+reindex only runs on cron or manual sync_repo. Needs a phase plan; not a
+patch.
+
 ## [1.21.9] - 2026-04-18
 
 **Token-efficient RRR: semantic_search injection wave 1 + hosted worker hardening.**

package/agents/rrr-planner.md

@@ -2,7 +2,7 @@
 name: rrr-planner
 description: Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /rrr:plan-phase orchestrator.
 model: sonnet
-tools: Read, Write, Bash, Glob, Grep, WebFetch, mcp__context7__*
+tools: Read, Write, Bash, Glob, Grep, WebFetch, mcp__context7__*, mcp__rrr-search-hosted__semantic_search, mcp__rrr-search__semantic_search
 color: green
 ---
 

package/commands/rrr/audit-milestone.md

@@ -19,6 +19,7 @@ Verify milestone achieved its definition of done. Check requirements coverage, c
 
 <execution_context>
 @~/.claude/rrr/references/principles.md
+@rrr/references/semantic-search-preference.md
 </execution_context>
 
 <context>

package/commands/rrr/create-roadmap.md

@@ -40,6 +40,7 @@ Roadmaps define what work happens in what order. Phases map to requirements.
 @~/.claude/rrr/templates/roadmap.md
 @~/.claude/rrr/templates/state.md
 @~/.claude/rrr/references/goal-backward.md
+@rrr/references/semantic-search-preference.md
 </execution_context>
 
 <context>

package/commands/rrr/plan-milestone-gaps.md

@@ -22,6 +22,7 @@ One command creates all fix phases — no manual `/rrr:add-phase` per gap.
 @~/.claude/rrr/references/principles.md
 @~/.claude/rrr/workflows/plan-phase.md
 @~/.claude/rrr/lib/phase-paths.md
+@rrr/references/semantic-search-preference.md
 </execution_context>
 
 <context>

package/commands/rrr/research-project.md

@@ -23,6 +23,10 @@ For new projects, use /rrr:new-project instead.
 Deprecated: 2026-01-16
 -->
 
+<execution_context>
+@rrr/references/semantic-search-preference.md
+</execution_context>
+
 <objective>
 Research domain ecosystem. Spawns 4 parallel rrr-project-researcher agents for comprehensive coverage.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projecta-rrr",
-  "version": "1.21.9",
+  "version": "1.21.10",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by Projecta.ai",
   "bin": {
     "projecta-rrr": "bin/install.js",

package/rrr/references/semantic-search-preference.md

@@ -23,6 +23,25 @@ When exploring the codebase to answer "what does X do?", "where is Y configured?
 - **Relevance:** semantic_search ranks by cosine similarity + RRF fusion with ripgrep; grep returns alphabetically.
 - **Cross-file synthesis:** top-K often spans multiple files — one call answers "how X works" that would otherwise need 3-5 greps.
 
+## Domain-Specific Queries
+
+Start with the right query phrasing — semantic_search ranks by meaning, not keywords. Pick the pattern closest to your intent:
+
+| Scenario | Query pattern | k |
+|---|---|---|
+| Tech stack discovery | `"technology stack" "frameworks" "dependencies" "build tools"` | 10 |
+| Architecture / module layout | `"system architecture" "module organization" "data flow"` | 10 |
+| Find similar implementation | `"implementation pattern for X" "existing code example"` | 5 |
+| Error root-cause (logs + code) | `"error pattern" "failure signature" "root cause indicators"` | 20 |
+| Requirement coverage | `"requirement implementation" "feature coverage" "missing pieces"` | 10 |
+| Auth / security surfaces | `"authentication flow" "token validation" "permission check"` | 10 |
+| Data model / schema | `"schema definition" "table design" "entity relationships"` | 10 |
+| Test coverage gaps | `"test cases" "validation" "edge case handling"` | 10 |
+| API surface | `"endpoints" "request handlers" "route definitions"` | 10 |
+| Config / environment | `"configuration" "environment variables" "settings"` | 5 |
+
+**Rule of thumb:** one semantic_search (k=5-10, ~500 tokens) before any Grep/Read chain on an unknown area. If the top hits answer the question, stop. If not, narrow with a second query — still cheaper than brute-force grep.
+
 ## Discovery
 
 Check availability once at workflow start: