{"agent":"claude","input":"Audit this WordPress plugin for security problems and write the result to security-audit.md. Change no code, open no issue and no pull request, and post nothing publicly: read SECURITY.md first and follow its reporting route in your recommendations. Read the main plugin file, composer.json, phpcs.xml.dist, phpstan.dist.neon and any AGENTS.md or contributor notes. Install php and composer if your sandbox lacks them, run composer install, then run the project's PHPCS and PHPStan scripts and record the results as a baseline. Build a table of every entry point: REST routes with their permission_callback, AJAX actions, admin-post and form handlers, login hooks, shortcodes, WP-CLI commands and cron callbacks. For each give the handler, the capability check and whether it checks the specific object being changed, the nonce, and every request value it reads with how it is unslashed, sanitized and validated. Read every phpcs:ignore and ruleset exclusion in non-test code and judge whether its reason holds. Follow each secret or token from generation to storage to comparison: source of randomness, hashing, constant-time comparison, expiry, reuse and rate limiting. Check output escaping, redirects, file and remote requests, direct database queries, uninstall cleanup, and every filter that can weaken a check. Do not start a WordPress site. Mark each finding as confirmed by reading or needs a running site, with file and line, severity, the conditions an attacker needs, and the fix. End with the list of what you checked and found sound, so the report shows its coverage.","resources":[{"url":"https://github.com/your-org/your-app"}]}