chore: update WPCS to patch CVE-2026-45293

[pattonwebz]

Summary

• WPCS (wp-coding-standards/wpcs) versions >= 0.14.1, < 3.4.1 have an eval() arbitrary code execution vulnerability in the WordPress.WP.EnqueuedResourceParameters sniff (CVE-2026-45293). This repo was locked to 3.3.0, which is vulnerable.
• Ran composer update wp-coding-standards/wpcs automattic/vipwpcs --with-all-dependencies to bring in the patched 3.4.1 (and vipwpcs 3.1.0, which bumped its own wpcs requirement). composer.json constraints already allowed these versions, so only composer.lock changed.
• Re-ran phpcs; no new violations from the updated ruleset (one pre-existing, unrelated warning in a test file).

Linear: PRO-1246 (subtask of PRO-1245)

Test plan

• composer update wp-coding-standards/wpcs automattic/vipwpcs --with-all-dependencies
• composer check-cs — no new violations

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 14 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: 07769040-74e9-48f8-bdeb-54f0df250530

📥 Commits

Reviewing files that changed from the base of the PR and between ae5de11 and 4ee8398.

⛔ Files ignored due to path filters (1)

• composer.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• tests/phpunit/includes/OptionsPageSourceTest.php

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch william/pro-1246-update-phpcswpcs-accessibility-checker

---

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

[pattonwebz]

Pushed a follow-up commit: the one pre-existing warning noted in the PR description (WordPressVIPMinimum.Performance.FetchingRemoteData.FileGetContentsUnknown in OptionsPageSourceTest.php) was causing a CI failure. Confirmed it's a false positive — file_get_contents( EDAC_PLUGIN_DIR . 'includes/options-page.php' ) reads a local plugin file, not a remote URL; the sniff just can't tell that statically from the constant-concatenated path. Suppressed with phpcs:ignore + justification. composer check-cs is now fully clean (0 errors, 0 warnings).