chore: add CodeRabbit review config

[chodeus]

Adds a .coderabbit.yaml tailored to folder.view3 (Unraid plugin: PHP emhttp + jQuery/vanilla JS + CSS + .plg). Targets beta.

• Profile chill; base_branches: [beta] so beta-targeted feature PRs auto-review (main always does).
• path_instructions: PHP (validate input, escape XSS in generated CSS/JS, fail-closed guards, realpath re-confine on theme delete, settings enums allowlisted in both lib.php tables, escapeshellarg on docker exec), JS (innerHTML drops bound handlers → prefer TreeWalker; CSRF token on every mutation; the customEvents bus is frozen; createFolders() order math is fragile; 0/"" falsy), CSS (theme-agnostic, docker/dashboard parity, frozen public-API selectors), and the .plg manifest.
• Tools: gitleaks + semgrep; phpstan/biome/eslint off (emhttp globals + config-less jQuery → false "undefined" noise). Note: CI here runs php -l/xmllint/actionlint, not prettier.

Note: once tuned it should also land on main. CodeRabbit reads config from the PR head branch, so this PR is itself reviewed under the new config.

Summary by CodeRabbit

• Chores
  • Added automated code review configuration with tailored guidance for PHP, JavaScript, CSS, and plugin manifest files.
  • Enabled security scanning for secrets and common code issues.
  • Configured review behavior, branch coverage, draft handling, and excluded generated or vendor content from reviews.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 21 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: CHILL

Plan: Pro

Run ID: ce628a5a-b8ea-43b0-ad70-5cf499a0f511

📥 Commits

Reviewing files that changed from the base of the PR and between 3156ddd and f414785.

📒 Files selected for processing (1)

• .coderabbit.yaml

📝 Walkthrough

Walkthrough

Adds a complete .coderabbit.yaml configuration for automated review behavior, excluded paths, path-specific PHP/JavaScript/CSS/manifest guidance, and security tooling selection.

Changes

CodeRabbit Configuration

Layer / File(s)	Summary
Review scope and automation .coderabbit.yaml	Sets the review language and profile, enables automatic reviews for main and beta, disables request changes and drafts, and excludes vendor, release, media, and generated artifacts.
Path-specific review guidance .coderabbit.yaml	Adds security and correctness rules for PHP sources, JavaScript behavior, CSS compatibility, and the Unraid plugin manifest.
Analysis tooling .coderabbit.yaml	Enables gitleaks and semgrep, while disabling PHPStan, Biome, ESLint, and markdownlint.

Estimated code review effort: 2 (Simple) | ~15 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 accurately summarizes the main change: adding a CodeRabbit review configuration file.
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/coderabbit-config

---

_{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 @.coderabbit.yaml:
- Around line 14-15: Update the base_branches configuration to use the anchored
regex ^beta$ instead of beta, ensuring only the exact beta branch matches and
branches containing beta elsewhere are excluded.

🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 52706253-d9b2-4f54-aa18-b5a6f426437c

📥 Commits

Reviewing files that changed from the base of the PR and between 76f4633 and 3156ddd.

📒 Files selected for processing (1)

• .coderabbit.yaml

[chodeus]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.