feat(security): add Snyk scope baseline to generated projects

[williaby]

Summary

• Adds .snyk, .dcignore, and .vscode/settings.json to the generated project directory ({{cookiecutter.project_slug}}/) so every scaffolded repo scopes Snyk to project-owned code from day one.
• Snyk scans the on-disk working tree, not git or manifests, so it walks into .venv/, .worktrees/, node_modules/, and vendored site-packages/ and reports third-party vulnerabilities as if they belong to the project. .gitignore does not constrain Snyk's scan. A real team hit ~192 noise findings this way.
• Updates {{cookiecutter.project_slug}}/.gitignore with negation patterns so .vscode/settings.json is tracked despite the .vscode/ ignore rule.
• Updates CHANGELOG.md under [Unreleased].

Files changed

File	Purpose
.snyk	exclude: paths scope Snyk SCA scan
.dcignore	Same path set scopes Snyk Code scan
.vscode/settings.json	snyk.advanced.additionalParameters scopes VS Code extension
.gitignore	Negation patterns to track settings.json
CHANGELOG.md	Documents the addition

Test plan

• pre-commit run --all-files passes (confirmed locally: all 25 hooks pass)
• cookiecutter.json is untouched (verified: no diff)
• New files contain no unescaped {{ }} cookiecutter markers (verified)
• Generated .snyk exclude: block covers .venv, .worktrees, node_modules, site, htmlcov, out, **/site-packages/**
• Generated .dcignore uses gitignore-style path syntax
• .vscode/settings.json appears in git after generation (negation in .gitignore confirmed)

Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@williaby, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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

How do review limits work?

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

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, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 52562e1c-68d2-45aa-bed9-5679108895dd

📥 Commits

Reviewing files that changed from the base of the PR and between efcf21f and e5d340e.

📒 Files selected for processing (5)

• CHANGELOG.md
• {{cookiecutter.project_slug}}/.dcignore
• {{cookiecutter.project_slug}}/.gitignore
• {{cookiecutter.project_slug}}/.snyk
• {{cookiecutter.project_slug}}/.vscode/settings.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/snyk-scope-baseline

---

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