Asset CleanUp Pro v1.2.8.5

* **New:** Manage plugin rules by page, directly from the front-end or the WordPress post editor, alongside the existing "By plugin" layout. * **New:** Added plugin unload rules and load exceptions for entries of a selected post type assigned to any term in selected taxonomies. * **New:** Pause and resume CSS/JS rules and Alternative Assets independently without deleting their saved configuration. * **Fix:** Preserve settings belonging to the inactive plugin edition when saving Settings or changing individual options through AJAX controls. Validate submitted form fields against the active edition's settings. * **Fix:** Validate submitted Plugins Manager rule statuses before preserving scoped taxonomy rules, avoiding PHP warnings for malformed values. * **Fix:** Guard Plugins Manager helpers during updates and open saved post-type taxonomy rules directly from "By plugin", without requiring an individual entry. * **Fix:** Keep Critical CSS preview cleanup confined to actual stylesheet tags, preserving marker-like text in other page content. * **Fix:** Preserve empty SCRIPT/STYLE markup in page content during cleanup, including STYLE literals used by JavaScript to create elements dynamically. * **Fix:** Remove temporary JS source markers from preload links, and handle whitespace consistently in CSS/JS unload query lists. * **Security:** Restrict asset diagnostic dumps to users with plugin access and escape their HTML output, including hardcoded asset data. * **Security:** Restrict credentialed front-end CORS responses to trusted origins while preserving requests from the primary Dashboard to WPML/Polylang language domains. Additional trusted origins can be configured with `wpacu_frontend_cors_allowed_origins`. * **Security:** Fix SQL injection in Plugins Manager author archive detection by parameterizing the author lookup and rejecting invalid input types. * **Security hardening:** Make temporary CSS/JS attribute cleanup safer by preserving inline JavaScript, quoted attribute values and text content. Ambiguous or unsupported HTML is left unchanged to avoid breaking the page, so some temporary markers may remain in the page source. Existing reflected-XSS and stored-XSS protections remain in place.