chore: Greptile deep-label repo config (plan 028)

[zen-agents]

Adds .greptile/config.json so Greptile only runs on review:deep App-authored PRs.

• labels: review:deep only
• includeAuthors: org App bots
• excludeAuthors: non-implementation bots
• triggerOnUpdates: false
• commentTypes: logic, syntax
• ignorePatterns: lockfiles/dist/.next/node_modules
• autoApprove: off
• statusCheck: on

Org Flex Usage Limit is $0. CodeRabbit remains the standard path (labels review:standard + review:deep via central coderabbit config).

Summary by CodeRabbit

• Chores
  • Added project review configuration to control automated code review behavior.
  • Enabled status checks and deep review labeling.
  • Limited review comments to logic and syntax issues.
  • Excluded generated files, lockfiles, and selected automation accounts from review.
  • Disabled automatic description updates and approvals.

[greptile-apps]

Required label not found on this PR.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds .greptile/config.json with repository review policies, author filters, trigger and approval settings, status checks, file limits, and ignored paths.

Changes

Greptile Review Policy

Layer / File(s)	Summary
Greptile configuration .greptile/config.json	Sets review strictness, comment categories, labels, included and excluded authors, update triggers, status checks, file limits, ignored paths, description updates, and auto-approval behavior.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly reflects the main change: adding Greptile repo configuration for deep-label review routing.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/greptile-config-20260724T062650Z

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.greptile/config.json:
- Line 25: Update the ignorePatterns configuration in .greptile/config.json so
dist, .next, and node_modules patterns use recursive directory matching with
**/, ensuring these directories are ignored at every nesting depth while
preserving the existing lockfile exclusions.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository: ZenSystemAI/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: f90a4456-a0fa-438e-8407-26d016d980d1

📥 Commits

Reviewing files that changed from the base of the PR and between ba690fb and 9cac430.

📒 Files selected for processing (1)

• .greptile/config.json

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Match ignored build and dependency directories at every depth.

Because these patterns contain /, dist/**, .next/**, and node_modules/** only target root-level directories under .greptile/’s governed root; nested paths such as packages/web/dist/** can still be reviewed. Greptile applies .gitignore-style matching, where **/ is needed for all directory levels. (greptile.com)

Proposed fix

-  "ignorePatterns": "**/package-lock.json\n**/pnpm-lock.yaml\ndist/**\n.next/**\nnode_modules/**",
+  "ignorePatterns": "**/package-lock.json\n**/pnpm-lock.yaml\n**/dist/**\n**/.next/**\n**/node_modules/**",

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	"ignorePatterns": "**/package-lock.json\n**/pnpm-lock.yaml\ndist/**\n.next/**\nnode_modules/**",
	"ignorePatterns": "**/package-lock.json\n**/pnpm-lock.yaml\n**/dist/**\n**/.next/**\n**/node_modules/**",

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.greptile/config.json at line 25, Update the ignorePatterns configuration in
.greptile/config.json so dist, .next, and node_modules patterns use recursive
directory matching with **/, ensuring these directories are ignored at every
nesting depth while preserving the existing lockfile exclusions.