Add Blender forensic summary tools

[Ker102]

Summary

• Add focused Blender forensic summary commands inspired by the official Blender MCP summaries:
  • get_blendfile_summary_path_info
  • get_blendfile_summary_datablocks
  • get_blendfile_summary_missing_files
  • get_blendfile_summary_of_linked_libraries
  • get_blendfile_summary_usage_guess
• Wire the commands into the LangChain tool list, tool registry, tool filtering, system prompt, and blend-file health guide.
• Update capability inventory to mark blend-file forensic summaries as native ViperMesh coverage.
• Add focused regression coverage and guide coverage for the new tools.

Validation

• npx tsx scripts/test/test-blender-forensic-summary-tools.ts
• python -m py_compile desktop/assets/vipermesh-addon.py public/downloads/vipermesh-addon.py
• npx tsx scripts/test/test-blender-file-health-tool.ts
• npx tsx scripts/test/test-tool-guide-trigger-coverage.ts
• npx tsx scripts/test/test-blender-capability-inventory.ts
• npx tsc --noEmit --incremental false
• npm run lint (passes; existing baseline-browser-mapping age warning)
• git diff --check (passes; Windows line-ending warnings only)

[coderabbitai]

Warning

Review limit reached

@Ker102, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 31 minutes and 49 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 42850183-b826-4464-80cb-930d9a64b886

📥 Commits

Reviewing files that changed from the base of the PR and between d2d4d32 and 35aeb93.

📒 Files selected for processing (10)

• data/tool-guides/blend-file-health-guide.md
• desktop/assets/vipermesh-addon.py
• docs/blender-mcp-capability-inventory.md
• lib/ai/agents.ts
• lib/orchestration/prompts/blender-agent-system.md
• lib/orchestration/tool-filter.ts
• lib/orchestration/tool-registry.ts
• public/downloads/vipermesh-addon.py
• scripts/test/test-blender-forensic-summary-tools.ts
• scripts/test/test-tool-guide-trigger-coverage.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/blender-forensic-summary-tools

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}