Skip to content

Add boundary globs, hotspot norm/bot signals, real preset filtering, … - #20

Merged
Eilodon merged 1 commit into
mainfrom
claude/calm-mcp-connection-9tk1f4
Jul 6, 2026
Merged

Add boundary globs, hotspot norm/bot signals, real preset filtering, …#20
Eilodon merged 1 commit into
mainfrom
claude/calm-mcp-connection-9tk1f4

Conversation

@Eilodon

@Eilodon Eilodon commented Jul 6, 2026

Copy link
Copy Markdown
Owner

…coverage hot-reload, and FTS5 memory recall

  • Boundary rules now accept glob patterns (crates/*/src/indexer/**) alongside the existing prefix-style rules, via globset with a literal-prefix fallback on invalid syntax.
  • Fitness report surfaces a note when Tier-0.5 languages dominate the function/method population, since they always report complexity 1 and can silently understate high_complexity_pct.
  • Hotspots expose normalized churn/complexity shares and classify each file's git churn as human/mixed/bot_dominated/unknown, filtering bot-authored commits out of the signal.
  • MCP preset filtering (orient/trace/edit/compound) now actually scopes tools/list and tools/call, not just the suggested_next hint — previously every preset still received rmcp's full unfiltered tool_box.
  • Coverage data (lcov/cobertura/etc.) reloads live when the watcher sees the report file change, instead of staying frozen at server-startup content.
  • Memory recall's fuzzy query moves from unranked SQL LIKE to an FTS5 virtual table with BM25 relevance ranking and a recency tie-break, synced via insert/update/delete triggers with a backfill migration for existing notes.

Claude-Session: https://claude.ai/code/session_01KTYcoCty8v6v5e2GdoniPa

…coverage hot-reload, and FTS5 memory recall

- Boundary rules now accept glob patterns (crates/*/src/indexer/**) alongside
  the existing prefix-style rules, via globset with a literal-prefix fallback
  on invalid syntax.
- Fitness report surfaces a note when Tier-0.5 languages dominate the
  function/method population, since they always report complexity 1 and can
  silently understate high_complexity_pct.
- Hotspots expose normalized churn/complexity shares and classify each file's
  git churn as human/mixed/bot_dominated/unknown, filtering bot-authored
  commits out of the signal.
- MCP preset filtering (orient/trace/edit/compound) now actually scopes
  tools/list and tools/call, not just the suggested_next hint — previously
  every preset still received rmcp's full unfiltered tool_box.
- Coverage data (lcov/cobertura/etc.) reloads live when the watcher sees the
  report file change, instead of staying frozen at server-startup content.
- Memory recall's fuzzy query moves from unranked SQL LIKE to an FTS5 virtual
  table with BM25 relevance ranking and a recency tie-break, synced via
  insert/update/delete triggers with a backfill migration for existing notes.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KTYcoCty8v6v5e2GdoniPa
@Eilodon
Eilodon merged commit 6aaef45 into main Jul 6, 2026
1 of 3 checks passed
@Eilodon
Eilodon deleted the claude/calm-mcp-connection-9tk1f4 branch July 6, 2026 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants