{"agent":"claude","input":"Review the open pull request in resources on our WordPress plugin. Read composer.json, phpcs.xml.dist, phpstan.dist.neon, the workflows under .github/workflows, the pull request template, AGENTS.md or CONTRIBUTING.md if present, and the main plugin file first. If php or composer is missing in your sandbox, install them, then run composer install. Run the project's PHPCS, PHP compatibility and PHPStan scripts on the pull request's branch and on the base branch, and report only what the pull request adds or fixes. Then read the diff. For every changed or new hook callback, admin form handler, AJAX action and REST route, state which capability check guards it and whether it checks the specific object being changed; flag any that has none or relies on a nonce alone. Flag request data used without wp_unslash and a sanitizing function, output without an escaping function, redirects that are not wp_safe_redirect, secrets compared without hash_equals, and SQL built without prepare. Question every phpcs:ignore, phpstan ignore and ruleset exclusion the pull request adds. Hold the diff to the repository's own rules for which files may be edited. Check the pull request against its template: tests for changed behaviour, docblocks for new hooks, a changelog entry and testing instructions. Do not run the PHPUnit suite if it needs Docker; say in the review that you did not run it and that the repository's test workflow covers it. Post one review with the command results first, then findings by file and line, each with the fix. Do not push commits.","resources":[{"url":"https://github.com/your-org/your-app/pull/42"}]}