Summary

Sam reported that WP Rocket permission notices were still visible on the WordPress Plugins screen. I verified the issue against authenticated wp-admin HTML, not just WP-CLI.

What shipped

• Reproduced the WP Rocket permission notices in /wp-admin/plugins.php.
• Found the original repair had targeted /var/www/html/public_html, while the live browser admin was using /home/1615235.cloudwaysapps.com/fctbkwwahp/public_html.
• On the live app path, wp-content was owned by the Cloudways master user and set to 755, which blocked WP Rocket from creating advanced-cache.php and its cache/config directories through the app runtime.
• Created rollback snapshot: /home/master/wp-rocket-livepath-repair-20260517-170315.
• Set live wp-content to 775, created the WP Rocket cache/config directories, set those directories to 2775, set generated files to 664, and regenerated advanced-cache.php and the WP Rocket config from the live /home/... path.
• Verified the authenticated Plugins page now has zero WP Rocket missing-writing-permission notices.
• Cleaned the earlier /var/www/html/public_html fallback path back down from permissive modes to 2775 directories and 664 files.
• Updated Skills/wp-site-health/SKILL.md to version 1.0.4, mirrored it to the Claude skill locations, and updated Skills/SKILL-INDEX.md.
• Logged the QA item in admin/_qa-queue/2026-05-17.md.

Evidence

• Authenticated Plugins fetch after repair: plugin_status=200|https://aguiarinjurylawyers.com/wp-admin/plugins.php?codex_qa=1779036273.
• WP Rocket permission notice count after repair: 0.
• Syntax check: No syntax errors detected in wp-content/advanced-cache.php.
• Final generated advanced-cache.php uses /home/1615235.cloudwaysapps.com/fctbkwwahp/public_html, matching the browser runtime.

Reason for ending

The live WP Rocket permission notice issue is fixed and verified. The remaining decision is git hygiene, because the repository already has broad unrelated dirty state from other work.

Suggested next steps