chore: add DeepSource configuration

[2233admin]

Summary

• Add repository-local DeepSource configuration.
• Enabled analyzers: python, javascript, shell.
• Exclude generated, dependency, and build output paths to keep first-run findings actionable.

Validation

• Parsed .deepsource.toml with Python tomllib.
• Existing CI/CodeQL/Dependabot configuration is unchanged.

Follow-up

• Enable 2233admin/obsidian-llm-wiki in the DeepSource Dashboard after this PR merges.
• Review first analysis and tune exclude_patterns if generated files dominate findings.

[coderabbitai]

Warning

Review limit reached

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

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

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ 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 rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9cd9aa6f-a71c-4608-9a86-eefae23329f8

📥 Commits

Reviewing files that changed from the base of the PR and between fae2cca and d0d8fb0.

📒 Files selected for processing (1)

• .deepsource.toml

---

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.}

[gemini-code-assist]

Code Review

This pull request adds a .deepsource.toml configuration file to enable DeepSource analyzers for Python, JavaScript, and Shell. Feedback suggests specifying the exact path to the dependency file (mcp-server/package.json) for the JavaScript analyzer and defining a specific Python runtime version (e.g., "3.11") instead of using a wildcard.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The dependency_file_paths option expects paths to the actual dependency files (e.g., package.json), not just the directory name. Since the package file is located at mcp-server/package.json, this should be updated to ensure DeepSource can resolve the dependencies correctly.

Suggested change

	dependency_file_paths = ["mcp-server"]
	dependency_file_paths = ["mcp-server/package.json"]

[gemini-code-assist]

DeepSource's Python analyzer expects a specific major.minor version for runtime_version (such as "3.11" or "3.12"). Since the project's compiler/pyproject.toml specifies requires-python = ">=3.11", setting this to "3.11" ensures the analyzer runs with the correct Python version features.

Suggested change

	runtime_version = "3.x.x"
	runtime_version = "3.11"