= 2.59.12.44 =
* Separate Varnish capability observation from control transport: create and verify canaries through the canonical public WordPress route while sending PURGE or BAN only to the configured control endpoint.
* Restore HTTP exact-invalidation discovery for control-only listeners such as the Hetzner endpoint without requiring those listeners to serve ordinary frontend GET requests.
* Preserve independent Exact PURGE and Exact BAN behavior probes and derive broader capability tests from the method verified during the current run.
* Preserve terminal topology outcomes such as entire-host `not-applicable` instead of reclassifying them through generic supported/unsupported aggregation.
* Persist endpoint, basic-test, HTML-variant, ESI, and aggregate capability diagnostics in existing revisioned UltraCache state records, with one-time migration from superseded diagnostic options.
* Invalidate the incorrect 2.59.12.43 capability proofs through revised capability fingerprints so they cannot authorize runtime behavior before a fresh Test Varnish run.
* Keep capability-probe operations isolated from production recent-operation reporting and require a specific reason for every non-executed or inconclusive capability result.

= 2.59.12.43 =
* Independently behavior-test HTTP Exact PURGE and Exact BAN on every configured endpoint instead of limiting probes from the configured method or adapter classification.
* Derive the common production hard-invalidation method from current endpoint proofs and use the same verified method for targeted, HTML-only, and entire-host runtime operations.
* Probe Batch BAN, HTML-only flush, entire-host flush, soft purge, stale refresh, and origin revalidation independently without executing known-URL or TTL production fallbacks.
* Persist explicit per-endpoint capability states, reason codes, messages, applicability, conclusiveness, timestamps, and proof expiry in the existing UltraCache state table.
* Distinguish supported, not supported, not applicable, observation incomplete, configuration changed, proof expired, and not tested outcomes; every untested UI result includes its specific persisted reason.
* Migrate the legacy endpoint capability option into the existing UltraCache state record and remove the legacy option after successful persistence; no transient state is added.

= 2.59.12.42 =
* Make Automatic Varnish site flushing choose from the observed static-object route and verified production capabilities instead of preferring HTML-only flush unconditionally.
* Select verified entire-host flush when public static objects pass through Varnish, and select verified HTML-only flush when public static objects bypass Varnish.
* Report a verified HTML-only operation as degraded when static ownership is inconclusive or static objects pass through Varnish without verified entire-host invalidation.
* Display the actual site runtime strategy in the Varnish summary: HTML-only flush, entire-host flush, known site pages, or automatic expiry.
* Preserve the existing capability persistence, production transports, VCL contracts, and explicit manual scope behavior.

= 2.59.12.41 =
* Use one bounded post-invalidation observation contract for exact invalidation, batch BAN, HTML-only flush, entire-host flush, and static preservation proofs.
* Retry transient public DNS/HTTP observation failures while still requiring two successful responses that match the expected canary generation or exact written artifact.
* Fail immediately on any successful stale or mismatched observation so retries cannot manufacture a capability the production runtime does not support.
* Report exhausted transport-only observations as `observation-incomplete` instead of incorrectly classifying the server capability as unsupported.
* Preserve the existing production planner, control operations, capability tables, and persistent diagnostic contracts without adding transient state.

= 2.59.12.40 =
* Preserve the complete Varnish basic-test contract instead of truncating associative payloads by key count, recursion budget, insertion order, or string length.
* Persist the full ESI capability proof and endpoint/test evidence through the existing sanitization contract.
* Add an independent contract-bound HTML variant capability record and use it as the authoritative public-path registry source.
* Restore the HTML variant capability into the basic diagnostic response from its dedicated record and remove the redundant capability-list slice.

= 2.59.12.39 =
* Classify public static delivery as Varnish bypass when the origin generation changes immediately without Varnish response evidence.
* Prove the existing production HTML-only BAN with two independent cached WordPress HTML canaries instead of requiring a cacheable static object.
* Persist static-bypass topology through the endpoint registry, runtime planner, and diagnostics so Automatic site flush selects direct `html-flush` rather than known-URL fallback.
* Report entire-host invalidation as not applicable when static assets bypass Varnish, while retaining the original through-Varnish HTML/static proof path.

= 2.59.12.38 =
* Replace the per-bucket page-cache variant cap with one bounded cap over complete normalized-URL hash families.
* Allow missing orig/WebP/AVIF members to complete an existing family even when another bucket already reached the path limit.
* Rotate the oldest complete families under a path-level database lock, removing all bucket files, compressed/freshness/ESI sidecars, matching static aliases, and cache-asset references.
* Record exact cached and failed HTML buckets plus cache-write error codes; an unsatisfied family rotation is terminal instead of retrying three times.

= 2.59.12.37 =
* Finalize the zero-transient regression candidate with plugin-wide enforcement that production transient reads and writes remain absent.
* Verify that direct transient deletion is restricted to the final legacy migration and uninstall allowlists, with no runtime fallback to legacy values.
* Validate the integrated persistent-state, lock, capability, diagnostics, queue, media, warm-up, Varnish, font-map, runtime-JS, and admin-notice contracts without adding new behavior.

= 2.59.12.36 =
* Replaced transient-backed admin notices with user-scoped, delete-on-read revisioned state records.
* Consolidated all legacy transient cleanup into one final migration and removed superseded per-version transient migration hooks.
* Enforced zero production transient reads/writes; direct deletion remains only in the named legacy cleanup and uninstall allowlists.

= 2.59.12.35 =
* Replace the runtime font CSS transient map with authoritative `ultracache_css_rewrite_map` reads and request-local memoization; stale generated targets are marked inactive in the same table.
* Persist interim and final browser runtime JS reports in the existing `ultracache_js_diagnostic_jobs` table, merge reports under an atomic database lock, and bind standalone reports to the durable queue job when available.
* Remove the runtime JS scan transient report path and the legacy media conversion-test transient fallback; existing persistent option/table contracts remain authoritative.
* Add one-time cleanup for superseded font-map, runtime JS report, and media conversion-test transient keys without importing their values.

= 2.59.12.34 =
* Replaced transient-backed dashboard stats, storage diagnostics, page-cache activity, and last cache-event state with persistent UltraCache-owned state records.
* Made normal and periodic dashboard reads DB-only; analytics counters and lightweight backend metrics refresh without scanning page-cache or object-cache storage.
* Persist full object-cache measurements only from the existing explicit Count Object Cache action; capped filesystem scans run only during explicit diagnostics/count actions.
* Added persistent snapshot age, stale, configuration-changed, dirty, partial, and persistence status fields without deleting historical evidence.
* Added one-time legacy transient cleanup without importing transient values as authoritative state.

= 2.59.12.33 =
* Replace media encoder support, AVIF self-test, and GD WebP probe transients/options with fingerprinted revisioned capability state.
* Replace the media library work-summary transient with a persistent dirty-aware summary rebuilt from authoritative attachment/source data after media mutations.
* Replace per-format optimized-storage health transients with persistent diagnostic snapshots that retain evidence and fail closed when stale, dirty, or configuration-changed.
* Remove production transient readers and writers for these media paths and add one-time cleanup without importing legacy values as capability proof.

= 2.59.12.32 =
* Replace the frontend compression result transient with fingerprinted revisioned state that survives object-cache eviction and reports stale or configuration-changed evidence explicitly.
* Replace stored compression challenge transients with short-lived HMAC-signed tokens and atomic database replay claims; expired, modified, and repeated challenges fail closed.
* Replace loopback SSL fallback history and object-cache support snapshots with persistent runtime capability state.
* Remove production transient readers and writers for the three runtime/server capability paths and add one-time cleanup for superseded fixed and dynamic keys.

= 2.59.12.31 =
* Replaced LCP observation cleanup transients with an atomic database cooldown lease.
* Replaced media affected-page cleanup, on-demand queue deduplication, and queue-init maintenance transients with database locks.
* Removed the transient fallback from signed LiteSpeed control replay protection; verification now fails closed when the lock contract is unavailable.
* Replaced Google Fonts cache-write retry transients with short database leases.
* Added one-time cleanup for superseded fixed and dynamic coordination transient keys.

= 2.59.12.30 =
* Remove the legacy cron warm execution-lock transient mirror; the existing token-guarded `ultracache_locks` mutex and revisioned warm-decision fence are now the only authoritative ownership records.
* Replace the cron worker-recovery throttle transient with an expiring atomic database lock while retaining the separate short-lived recovery execution mutex.
* Replace per-post save warm cooldown transients with expiring atomic database locks, preserving filter-controlled cooldown duration and cross-request deduplication.
* Delete the fixed legacy warm coordination transients once during upgrade and remove residual database option rows for dynamic post-save warm transient keys without migrating their values.

= 2.59.12.29 =
* Replaces the Varnish performance snapshot transient with revisioned persistent state, retaining measurements across object-cache flushes and marking them stale or configuration-changed instead of deleting them.
* Replaces the reverse-proxy detection transient with explicit, fingerprinted persistent diagnostic state; ordinary status reads no longer issue network probes.
* Refreshes reverse-proxy evidence only during explicit Detect Varnish, Test Varnish, or Measure Varnish Performance actions.
* Adds one-time cleanup for the superseded Varnish diagnostic transients without migrating transient values into authoritative state.

= 2.59.12.28 =
* Remove the HTML/host flush, two-stage origin refill, and soft-purge capability transient readers and writers; the persistent per-endpoint capability registry is now the only source that can authorize Varnish runtime behavior.
* Persist bounded aggregate topology, soft-purge, and origin-revalidation diagnostic details in the existing revisioned UltraCache state table without allowing those diagnostic records to grant a capability.
* Preserve tested, unsupported, expired, and configuration-changed capability history through explicit registry timestamps and proof-expiry fields instead of deleting the state when a transient expires.
* Delete the four superseded Varnish capability transient keys once during upgrade, including the already-obsolete refresh-ahead capability key.

= 2.59.12.27 =
* Move the latest production Varnish operation result from `ultracache_varnish_last_result` transient storage to the existing revisioned `ultracache_locks` state table under `ultracache_state:varnish.last_operation`.
* Make Varnish diagnostics, REST status, and WP-CLI consume the same persistent operation-state record, so object-cache eviction or transient expiration cannot erase the latest result.
* Link completed `varnish_flush_all` dashboard actions to the persistent operation result with the durable action-job ID and timestamps after the action-job row is saved.
* Delete the superseded transient once through a persistent migration marker; no production reader or writer falls back to it.

= 2.59.12.26 =
* Verify each post-BAN canary refill against the exact generation 2 artifact written by UltraCache, using the deterministic body marker, body hash, or canary ETag as equivalent object-identity evidence.
* Preserve the production capability contract: a successful two-URL Batch BAN proof now activates bounded runtime and queued batching, while failed, expired, or unavailable proof continues to use exact BAN per URL.
* Record per-canary post-BAN verification evidence without changing the Varnish transport, planner policy, UI layout, Detect flow, or fallback behavior.

= 2.59.12.25 =
* Align durable queued Admin/HTTP BAN execution with the same current Batch BAN capability used by the direct targeted runtime and request estimator; unverified batching now produces one exact BAN operation per URL and endpoint.
* Downgrade a failed verified batch expression to exact-per-URL fallback first, preserving independent Exact BAN proof until that fallback itself fails.
* Complete capability-driven regression coverage for targeted, queued, site-wide, soft-purge, known-URL, and TTL strategies, including planner, registry, queue accounting, UI truth states, and production Flush All delegation.
* Assert that Varnish capability probes use production execution paths and that no diagnostic-only Batch BAN, HTML/host flush, or soft-PURGE transport remains.

= 2.59.12.24 =
* Route the HTTP soft-purge capability proof through the production targeted invalidator, including production URL normalization, scoped planner authorization, endpoint selection, transport, and runtime result accounting.
* Remove the diagnostic-only soft-PURGE request executor; canaries now provide observation only and pre-transport failures remain Not tested.
* Permit the internal soft strategy override only for an exact matching endpoint-and-URL capability probe; outside that probe UltraCache retains its current verified strategy or hard exact fallback.
* Run authenticated origin-revalidation proof only after at least one configured endpoint accepts the production soft-PURGE operation, and bind endpoint origin evidence only to endpoints that completed that transport step.

= 2.59.12.23 =
* Route HTML-only and entire-host capability proof through the production site-flush planner, scope executor, adapter, transport, and endpoint accounting used by Flush All.
* Remove the diagnostic-only scope-expression executor and its HTML/host test wrappers; canaries now provide observation only and never send a separate invalidation command.
* Test HTTP data-plane endpoints independently, while treating multiple Admin sockets as one configured production endpoint set whose aggregate behavior is observed on the canonical public path.
* Preserve Not tested for unavailable canaries or non-executed runtime plans, and persist broad-scope support only after the production operation is accepted and the required HTML/static behavior is observed.

= 2.59.12.22 =
* Route the two-URL Batch BAN capability proof through the production targeted invalidator instead of a diagnostic-only BAN executor.
* Use current Batch BAN proof to choose one bounded shared BAN expression; when only exact BAN is verified, send one exact BAN expression per URL through the same production path.
* Treat production normalization, deduplication, or transport precondition failures as Not tested when no request was sent, without adding canary URL bypasses.
* Persist Admin exact and batch behavior only when the complete configured control-endpoint set accepts the production operation and the public canary exposes the expected refill; align queue request estimates with the same batch-or-exact runtime decision.

= 2.59.12.21 =
* Replace the general Varnish test-run authorization bypass with a request-local capability probe bound to one operation, strategy, scope, endpoint set, and target-URL fingerprint.
* Require matching scoped authorization before the targeted runtime planner, authenticated exact-PURGE contract, direct diagnostic BAN transport, soft-PURGE diagnostic, or diagnostic refill may exercise an unverified path.
* Keep the existing test-depth state only for production metric/result suppression and bounded runtime side-effect deferral; a test run by itself no longer grants any invalidation capability.
* Preserve the canonical HTML-variant warm pipeline by opening a nested exact-URL probe only for its production pre-refill invalidation of the same URL and configured endpoints.

= 2.59.12.20 =
* Prevent cache-plugin signature labels from invoking the UltraCache text domain during early drop-in reconciliation before WordPress init.
* Preserve translated labels from init onward through the existing lifecycle-aware translation helper, without suppressing WordPress diagnostics or changing reconciliation timing.

= 2.59.12.19 =
* Preserve independently verified Batch BAN, HTML-only, entire-host, soft-purge, origin-revalidation, and SWR evidence when another capability is skipped or retested; runtime failures now downgrade only the affected topology scope.
* Bind HTML-variant and ESI evidence to public-path contracts instead of the Admin/HTTP control-plane identity, while retaining independent expiry and configuration-change truth.
* Report Not tested, Not supported, Proof expired, partial, and verified states consistently through the capability registry, runtime planner, stored diagnostics, and Varnish dashboard.
* Complete executable regression coverage for Admin/HTTP exact invalidation, contract-only advertisements, multi-endpoint intersection, proof expiry, configuration changes, soft-purge state, public-path scope, performance fingerprinting, and UI presentation.

= 2.59.12.18 =
* Connect Test Varnish in HTTP Soft or Automatic mode to a per-endpoint soft-PURGE canary that requires cached generation 1, a high-confidence STALE response after origin changes to generation 2, and a stable generation-2 HIT after bounded revalidation polling.
* Execute the existing authenticated origin-revalidation contract during the same diagnostic and require WordPress origin proof for every active HTML variant before runtime soft purge is enabled.
* Persist independent soft-purge, origin-revalidation, and SWR tested state bound to the current soft/refill configuration; skipped preconditions preserve current proof, while real behavior failures fail closed without downgrading independent exact invalidation.
* Expand the performance snapshot fingerprint to include Varnish mode, endpoints, PURGE/BAN method, a non-reversible secret fingerprint, endpoint VCL contract identity/capabilities, public-path capabilities, and HTML-variant policy.

= 2.59.12.17 =
* Separate control-endpoint invalidation capabilities from site/public-path ESI and HTML-variant behavior without changing the Varnish settings or Detect workflow.
* Verify Batch BAN with two isolated WordPress-served canaries and one real batched expression instead of deriving it from exact BAN support.
* Verify HTML-only and entire-host invalidation independently with cached HTML and opaque static canaries, bypassing only the existing behavior-proof gate during the diagnostic command.
* Keep HTTP contract advertisements as metadata until their matching behavior proof succeeds, report per-capability Not tested/Not supported/verified truth, and fail closed when multiple Admin sockets cannot be mapped to individual public data paths.

= 2.59.12.16 =
* Distinguish an authenticated Varnish control connection from command acceptance and exact cache invalidation proof in Admin mode.
* Report connected generic VCL setups accurately while leaving exact BAN, batch BAN, HTML-only flush, and host flush unavailable until their existing behavior proofs succeed.
* Remove contradictory connection warnings and non-expiring Admin proof labels, and show bounded proof expiry plus exact per-endpoint status from the capability registry.
* Preserve the 2.59.12.15 fail-closed runtime planner and existing HTTP PURGE/BAN behavior without adding automatic tests or changing the Varnish settings workflow.

= 2.59.12.15 =
* Stop deriving exact BAN, batch BAN, HTML-only flush, and entire-host flush runtime capabilities from Admin mode or endpoint reachability alone.
* Require current isolated-canary proof and bounded expiry for Admin exact BAN behavior, while preserving the existing HTTP PURGE/BAN proof path.
* Keep public canary reachability separate from authenticated admin control acceptance and fail closed after a newer behavior test contradicts an older proof.
* Downgrade affected endpoint capabilities after failed runtime invalidation so the planner selects the next verified fallback instead of repeating a stale strategy.

= 2.59.12.14 =
* Discard the disposable cron warm queue and coordination runtime during the supported SVN/private upgrade reset instead of migrating pending, processing, or legacy job rows.
* Remove the self-referencing legacy warm-row consolidation and metadata-compaction upgrade path that could issue ambiguous `source_context` SQL.
* Recreate any outdated warm queue schema as an empty current queue, gate non-owner requests while the reset is incomplete, and preserve all user configuration.
* Serialize the shared locks-table dbDelta prerequisite with a narrow expiring bootstrap option lock and verify the required columns and indexes before marking schema version 2 complete.

= 2.59.12.13 =
* Complete the Media Library Replacement publication regression pass across block, reuse, overwrite, rollback, restart, verification, and cleanup paths.
* Preserve a pre-existing or externally changed destination when a failed publication cannot prove that the current file is the exact UltraCache output from that attempt.
* Remove partial replacement temporary files and overwrite backups when a filesystem copy reports failure, and align release documentation/version metadata.

= 2.59.12.12 =
* Publish Media Library Replacement AVIF/WebP destinations through verified same-directory temporary files and atomic commits instead of direct overwrite copies.
* Stop and report different existing destination files by default, while allowing an explicit Overwrite with verified backup policy that remains rollback-capable until Delete Originals completes.
* Persist previous and published destination fingerprints in the existing replacement registry, restore backups during rollback or Prepare restart, and block cleanup when ownership can no longer be proven.
* Prevent overwrite policy from resolving two same-job registry rows that require different bytes at the same Media Library destination.

= 2.59.12.11 =
* Restore atomic upload-conversion commits for AVIF/WebP destinations beside normal Media Library attachments instead of limiting the guarded commit path to uploads/ultracache.
* Restrict the upload-tree write allowance to exact same-directory `.uc-tmp-*` AVIF/WebP commit pairs plus the converter's final-output cleanup and freshness contexts.
* Preserve all generic filesystem guards and reject cross-directory, cross-format, non-image, and outside-uploads operations.

= 2.59.12.10 =
* Ensure the media queue schema upgrade completes before stale-worker recovery can read or update the persistent `stale_recoveries` counter.
* Prevent upgrades from older queue schemas from issuing recovery SQL against a column that has not yet been added.

= 2.59.12.09 =
* Consolidate the independent Upload, Rewrite, Rewrite Fallback, and Media Library Replacement format policies into the full media regression candidate without adding a second queue, encoder framework, replacement workflow, or browser detector.
* Clarify Original file fallback throughout the dashboard and Help because the current attachment may be JPEG, PNG, AVIF, or WebP after upload conversion or Media Library Replacement.
* Complete the release-wide media matrix, migration, explicit replacement generation, AVIF-source capability, queue, rewrite, warm-up, syntax, translation, and package regression gates.

= 2.59.12.08 =
* Admit AVIF Media Library and upload sources to the existing WebP pipeline only when the same Imagick or GD engine passes the AVIF decode and WebP encode self-test.
* Extend the established generated-path, queue rebuild, on-demand, HTML/CSS rewrite, upload-conversion, and conversion-test contracts to support AVIF-to-WebP without a second pipeline.
* Treat an AVIF source as the existing AVIF result, preserve animated AVIF sources, and keep browser selection on the existing Accept-based orig/WebP/AVIF cache buckets.

= 2.59.12.07 =
* Extend the existing AVIF self-test with an independent bundled AVIF source fixture so decode capability no longer depends on AVIF encode support.
* Report verified Imagick and GD AVIF decode plus AVIF-to-WebP capability separately while keeping the established AVIF encoder support contract unchanged.
* Expose the new codec capability results in media diagnostics without enabling AVIF production source admission yet.

= 2.59.12.06 =
* Queue missing, stale, or invalid Media Library Replacement targets as exact AVIF or WebP rows in the existing media queue.
* Process only the candidate attachment IDs discovered by each bounded readiness chunk while preserving queue locks, pause controls, stale recovery, and the existing three-attempt failure limit.
* Repeat the readiness verification pass until every generated target is valid and current before Prepare can unlock.

= 2.59.12.05 =
* Connected Media Library Replacement to the independent Image replacement format instead of Image Rewrite Format.
* Reused the existing readiness and Prepare policy guards so pre-Do plans are rebuilt when the replacement target changes.
* Locked replacement-format changes after destructive Do work begins while preserving the existing completion and recovery paths.

= 2.59.12.04 =
* Connected Convert new uploads to the independent Upload image format setting instead of the frontend rewrite policy.
* Renamed Image Output Format and Fallback Format to Image Rewrite Format and Image Rewrite Fallback Format without changing queue, rewrite, cache-variant, or warm-up behavior.
* Kept shared image quality, color-profile policy, and conversion-test controls available when Media Rewrite is disabled.

= 2.59.12.03 =
* Added canonical Upload Image Format and Image Replacement Format settings.
* Existing installations inherit both new formats from the saved Image Output Format.
* Added runtime, REST, and settings import/export support without changing media execution behavior.

= 2.59.12.02 =
* Treat color-profile policy outcomes as semantic media skips instead of retryable encoder failures, preserving the exact skip reason and detail.
* Continue AVIF-with-WebP queue work to the WebP unit in the same request when AVIF is skipped, and complete the attachment without three failed retries.
* Add the default-off Ignore color profile preservation media setting so generated AVIF/WebP variants may discard unverifiable ICC/ICM metadata while original images remain unchanged.

= 2.59.12.01 =
* Restore native parse_url() in every early-bootstrap advanced-cache URL parsing path because wp_parse_url() is not defined when WordPress loads the drop-in.
* Document each unavoidable native parser call precisely for Plugin Check without changing host, request, LiteSpeed, ESI, or cache-key validation behavior.
* Add an early-bootstrap regression gate that executes the generated advanced-cache drop-in with no wp_parse_url() function available.

= 2.59.12.00 =
* Detect the WordPress login request before frontend hook registration, using the native login predicate with bounded script-path fallbacks.
* Keep JavaScript defer/delay, stylesheet rewriting, resource hints, frontend helpers, and HTML output transforms completely detached from wp-login.php.
* Preserve cache invalidation hooks and normal public frontend optimization behavior without adding script-specific CAPTCHA or Clipboard exclusions.

= 2.59.11.99 =
* Route advanced-cache request headers and signed query controls through the existing normalized server/query helpers and use WordPress URL parsing.
* Reuse the existing object-cache lock acquisition and release paths, retaining narrowly documented native primitives only where flock handles are required.
* Resolve the remaining runtime translation, filesystem-probe, and iframe request-input Plugin Check findings without changing cache policy or backend behavior.

= 2.59.11.98 =
* Exclude the entire development tests directory from the installable production ZIP.
* Keep the complete parity and live validation suites in the development source tree and run them before packaging.
* Add a package-level regression check that rejects tests, test harnesses, and development-only PHP files in the production archive.

= 2.59.11.97 =
* Render Per-endpoint proofs with the same horizontal label/value rows used by the upper Varnish diagnostics cards.
* Render Recent operation and failures with that same horizontal row contract instead of vertical DetailRow blocks inside a nested grid.
* Add a regression gate that verifies both lower diagnostics cards use the shared horizontal renderer and contain no vertical label-above-value rows.

= 2.59.11.96 =
* Keep Automation-owned stale-while-revalidate response grace active in Admin/BAN mode instead of incorrectly requiring HTTP soft-purge capability.
* Replace the ambiguous HTML variants boolean with explicit supported, not-applicable, expired, configuration-changed, incomplete, or failed states plus active-bucket and per-bucket evidence.
* Place Per-endpoint proofs and Recent operation and failures in one deterministic responsive diagnostics row.

= 2.59.11.95 =
* Let Varnish 5.2 derive object grace from the dynamic Cache-Control stale-while-revalidate value produced by Automation & Scheduling instead of overriding every object with a fixed 10-minute grace.
* Emit stale-while-revalidate explicitly for cacheable shared responses, including 0 when SWR is disabled or Max stale equals Fresh TTL, so Varnish does not fall back to its default grace.
* Keep the independent 5-minute Varnish keep window and all existing TTL, invalidation, refill, ESI, endpoint, and template-selection contracts unchanged.

= 2.59.11.94 =
* Replace the two bundled Control Web Panel Varnish alternatives with one canonical fail-closed WordPress/WooCommerce/ESI template.
* Expose one dashboard Help download and preserve the existing CWP placeholders, local exact PURGE, object metadata, Accept variants, ESI transport, and request/response approval handshake.
* Remove obsolete template files, runtime data, documentation, and translation strings without changing Varnish settings, invalidation behavior, grace, or keep.

= 2.59.11.93 =
* Convert native Varnish Admin exact, batched, HTML-only, and entire-host BAN commands from portable request predicates to the bundled CWP object metadata contract before socket transport.
* Reuse the same bounded object-expression converter as the authenticated HTTP BAN contract and reject unsupported request predicates before opening the admin connection.
* Keep generic HTTP PURGE/BAN expressions, endpoint settings, capability policy, direct thresholds, queue scheduling, and CWP templates unchanged.

= 2.59.11.92 =
* Run persistent Varnish invalidation independently from Background warm pages per minute, using only the dedicated Varnish operations-per-minute budget.
* Keep refill, refresh-ahead, LiteSpeed auxiliary work, and ordinary page warming paused when the page rate is 0.
* Preserve UI/WP-CLI foreground priority, automatic retry/minute-window scheduling, and explicit worker status for independent invalidation.

= 2.59.11.91 =
* Connect queued Varnish invalidations to the dedicated atomic real-minute operation budget instead of charging URL rows to the page warm-rate budget.
* Count one operation for each exact PURGE or bounded BAN batch sent to one configured endpoint, including endpoint-specific retry work.
* Persist successful endpoint progress across limited budgets, leave unattempted endpoints immediately pending without increasing retry attempts, and increment retries only for actual transport failures.

= 2.59.11.90 =
* Add a dedicated revisioned Varnish invalidation-rate state with atomic compare-and-swap operation claims.
* Preserve the current real-minute allowance when the setting increases, apply lower ceilings immediately, and reset claims only at a new real-minute window.
* Synchronize the dedicated state after settings saves while leaving Varnish queue dispatch, scheduling, and direct invalidation behavior unchanged.

= 2.59.11.89 =
* Add Varnish invalidations per minute to the canonical dashboard, REST, CLI, import/export, and runtime settings contracts.
* Default the bounded setting to 10 operations per minute with an accepted range of 1–600, independently from page warm-up speed.
* Preserve the setting across performance-profile changes and leave all Varnish queue, scheduling, and direct-invalidation behavior unchanged for this version.

= 2.59.11.88 =
* Connect `jQuery(...).METHOD is not a function` diagnostics to the existing bounded active plugin/theme JavaScript filesystem scan.
* Resolve exact jQuery plugin provider definitions and consumer calls even when the provider script is absent from the page inventory.
* Return the exact consumer with an explicit provider-not-found result instead of producing zero suggestions.

= 2.59.11.87 =
* Register `lazyLoadThirdPartyIframesEnabled` in the existing REST settings schema so the Media Optimization switch persists through normal settings save and response synchronization.
* Keep the iframe eligibility, exclusions, viewport activation, runtime, UI, defaults, and storage structure unchanged.
* Add an executable REST save round-trip regression covering `false -> true -> false` persistence and returned patch/settings values.

= 2.59.11.86 =
* Add a Media Optimization switch for strict viewport-based lazy loading of eligible third-party iframes such as Google Maps and video embeds.
* Keep payment, authentication, CAPTCHA, hidden or zero-dimension functional frames, explicit eager/opt-out frames, and critical cart/checkout/account requests unchanged.
* Replace eligible iframe sources with inert placeholders, restore them 400 pixels before the viewport or on interaction through an external runtime, and preserve a no-JavaScript fallback without adding a timer or permanent provider exclusion UI.

= 2.59.11.85 =
* Decouple CSS Bundle Exclusions from local stylesheet media rewriting so excluded Elementor, theme, and plugin stylesheets remain separate but can still use generated AVIF/WebP background URLs.
* Create one-to-one `optimized-css/css-media-*.css` mirrors only when at least one local background image URL is actually rewritten, preserving stylesheet order, media attributes, imports, and all non-rewritten relative URLs.
* Keep the media stylesheet pass independent from font settings and bundling decisions, with atomic output writes and a dedicated `css-media-rewrite` source map.

= 2.59.11.84 =
* Add a false-by-default `needs_main_query` ESI fragment contract and opt only the built-in private WooCommerce classic mini-cart out of the WordPress main posts query.
* Short-circuit `posts_pre_query` only for GET/HEAD main queries carrying a valid signed token for an enabled fragment whose registered definition explicitly declares that main-query state is unnecessary.
* Preserve WordPress and WooCommerce bootstrap, cart/session initialization, private cookie transport, renderer output, no-store headers, public ESI, and all custom fragments unless they explicitly opt out.

= 2.59.11.83 =
* Display the existing rolling 24-hour ESI metrics inside Varnish Diagnostics for all ESI fragments and the WooCommerce mini-cart adapter.
* Show sampled and estimated request volume, estimated request rate and public/private mix, render duration, output size, and contained errors without changing the metrics backend.
* Keep zero-sample states neutral, surface contained errors even without sampled renders, and warn on the existing Woo mini-cart meaningful-traffic and 100 ms render-cost threshold.

= 2.59.11.82 =
* Add a query-string caching guidance step between the Delay non-critical/local JS and selective-options steps in the Help popup performance section.
* Direct administrators to enable Query-string args caching, populate and save the Query-string args whitelist, with `/YourProductURL?color=red` as the example.
* Keep the Help action informational only; no setting is changed automatically.

= 2.59.11.81 =
* Restore the public stem-based generated image identity, mapping `photo.jpg` and `photo.png` to `photo.avif`/`photo.webp` so existing optimized files remain immediately reusable.
* Extend WordPress unique filename selection across JPG, JPEG, PNG, and WebP source stems inside uploads, using `-2`, `-3`, and later suffixes to prevent new generated-variant collisions.
* Keep the correction free of automatic scans, regeneration, legacy detectors, cleanup UI, settings migrations, and frontend fallback lookups.

= 2.59.11.80 =
* Consolidate the verified strict-CSP async CSS, profiler input limits, quote-aware tag discovery, exact WordPress provider resolution, and LCP/SR7 winner contracts into one regression candidate.
* Add one executable release gate proving the 2.59.11.72-2.59.11.79 contracts coexist without a settings, schema, or warm-runtime migration change.
* Keep production runtime behavior identical to 2.59.11.79; this version adds package identity, integration evidence, and final release validation only.

= 2.59.11.79 =
* Use score, then rendered area, then DOM offset for whole-document generic LCP heuristic selection, matching the existing frontend optimization path.
* Order mixed Slider Revolution fallback candidates by explicit semantic origin before area, preserving area-first ordering inside each origin class.
* Add executable expected-winner fixtures for logo, hidden, navigation, featured-image, verified first-slide, static-slide, explicit-tag, and raw-fallback cases.

= 2.59.11.78 =
* Keep the bare `wp` namespace unresolved instead of treating `wp-util` as its provider.
* Resolve explicitly named WordPress packages through exact registered handles or exact `wp-includes` core paths, including `wp.element` and `wp.data`.
* Add final profiler-response fixtures for bare `wp`, `wp.template`, `wp.i18n`, `wp.hooks`, `wp.apiFetch`, `wp.domReady`, `wp.element`, and `wp.data`.

= 2.59.11.77 =
* Move confirmed module-background, marked SR7 image, static-context, generic SR7 image, generated image-list mapping, and manual SR7 tag discovery to the shared quote-aware raw tag scanner.
* Replace the 480-character URL proximity classifier with actual opening-tag and enclosing SR7 container context, including explicit candidate origins and structural first-slide markers.
* Preserve existing score constants, area-first comparators, first/static-slide paths, and browser-observed LCP contracts.

= 2.59.11.76 =
* Move generic WordPress featured-image LCP fallback discovery from the unsafe `<img\b[^>]*>` boundary regex to the shared quote-aware raw tag scanner.
* Preserve original tag bytes and exact byte offsets so navigation exclusion, article context, scoring, candidate hydration, and winner behavior remain unchanged for ordinary markup.
* Correct the JSON-LD primary-image pattern escaping found by the new executable fixture, eliminating the invalid-regex warning while retaining the existing metadata identity contract.
* Keep manual selector, manual URL-equivalence, SR7 discovery, browser observations, viewport policy, and comparator behavior unchanged.

= 2.59.11.75 =
* Add one dependency-free quote-aware raw HTML tag scanner that preserves original bytes, exact start/end offsets, allowed custom tag names, and fail-closed handling for unterminated quoted attributes.
* Migrate browser-observed LCP preload duplicate detection and empty external-script boundary collection away from `[^>]*` opening-tag regexes, preserving attributes that follow quoted `>` characters.
* Keep generic LCP/SR7 candidate discovery, HTML tree semantics, and script inner-content extraction unchanged for their dedicated later roadmap gates.

= 2.59.11.74 =
* Add a dependency-free quote-aware reference scanner and fixture matrix for `>` inside single- and double-quoted image, link, script, and SR7 attributes.
* Map each active regex caller to its actual impact, separating diagnostic-only count errors, duplicate-preload risk, optimization omissions, fallback LCP/SR7 candidate omissions, and script inner-content contracts.
* Keep production runtime behavior unchanged while making raw-tag bytes, start/end offsets, context policy, and fail-closed requirements executable gates for the next parser-hardening version.

= 2.59.11.73 =
* Bound pasted profiler console input to 256 KiB and 2,000 lines before sanitization, parsing, queue storage, and diagnostic processing.
* Preserve valid UTF-8 and complete lines where possible, while keeping accepted console content beyond the previous hidden parser slice available to the diagnostic engine.
* Return explicit truncation state, byte and line counts, reasons, and active limits in direct and queued profiler results without changing matching rules.

= 2.59.11.72 =
* Replace inline async-stylesheet `onload` handlers with one external WordPress-enqueued activation runtime compatible with strict Content Security Policy.
* Preserve each managed stylesheet's intended media target while retaining the existing DOM position, eligibility decisions, and noscript fallbacks.
* Cover general Async CSS, Critical Request Chain delayed stylesheets, and delayed icon-font CSS with executable PHP and JavaScript regression fixtures.

= 2.59.11.71 =
* Correct live AVIF engine classification when GD exposes imageavif() but has no runtime encoder codec.
* Validate failed-regeneration atomic preservation against the selected encoder directly instead of the sample conversion wrapper.

= 2.59.11.70 =
* Add a packaged WP-CLI live-runtime validation gate for actual host AVIF/WebP encoders, color management, EXIF orientation, animation policy, decoder admission, atomic replacement, freshness, semantic HTML/srcset behavior, and balanced font CSS parsing.
* Bundle deterministic EXIF orientation 1-8, animated/static WebP, and pixel-expectation fixtures used by the live gate without touching Media Library originals or persistent settings.
* Keep production runtime behavior, settings, and database schemas unchanged from 2.59.11.69; this build adds the final host-validation candidate and executable package contract only.
* Require the live JSON report to contain zero failures before the roadmap may be declared complete; unavailable encoder engines are reported separately as skips.

= 2.59.11.69 =
* Add one integrated UC-032 through UC-045 regression-candidate matrix that executes every dedicated media conversion, generated-variant, responsive-image, semantic HTML, and font-parser fixture.
* Audit all active media writer, generated-path, srcset, HTML rewrite, and `@font-face` call sites, with package-wide assertions that reject superseded direct writers, ambiguous filenames, global URL maps, and unsafe structural parsers.
* Route browser-observed LCP `srcset` matching through the shared comma-safe tokenizer, closing the remaining Cloudinary/imgix candidate-matching gap found by the integrated call-site inventory.
* Keep settings and database schemas unchanged; this release adds regression evidence plus the bounded LCP observation integration correction.

= 2.59.11.68 =
* Replace every active regex-based `@font-face` structural parser with one bounded scanner that respects comments, quoted strings, escapes, and balanced braces.
* Rewrite only exact block and declaration byte ranges, preserving untouched CSS and explicit `font-display: optional`, `fallback`, or `swap` values while normalizing only missing, `auto`, or `block` declarations.
* Fail closed on unclosed comments, strings, parentheses, or blocks, leaving malformed third-party CSS byte-for-byte unchanged instead of attempting repair.
* Share the scanner across font discovery/storage, inline and linked font rewriting, delayed icon-font splitting, REST font-pattern analysis, and diagnostics, with executable malformed and punctuation-heavy fixtures.

= 2.59.11.67 =
* Replace the full-document upload URL `str_replace` map with the same tag-aware media policy used for filtered fragments, so identical URLs keep their semantics in images, downloads, metadata, and JSON.
* Rewrite `src`, lazy-source, and srcset attributes only on explicit image surfaces, while preserving generic anchor `href`, `data-href`, iframe/link sources, and non-image inputs.
* Keep `data-lg-src`, `data-mfp-src`, explicit background attributes, and inline background URLs supported without rewriting Open Graph or Twitter image metadata.
* Add executable full-document and fragment fixtures proving image replacement, download preservation, format-stable social metadata, lightbox compatibility, JSON preservation, and removal of obsolete rewrite-map state.

= 2.59.11.66 =
* Replace raw comma splitting with one shared srcset parser used by media HTML rewriting, LCP candidate discovery, and both protocol-relative engine normalization paths.
* Treat commas inside Cloudinary/imgix-style URLs, query strings, and data URIs as URL content while retaining top-level candidate separators and descriptors.
* Rewrite only URL byte ranges, preserving untouched candidates, delimiters, and whitespace exactly; return the original srcset byte-for-byte when no URL changes.
* Add executable fixtures for width/density descriptors, URL-only candidates, mixed local/CDN values, data URIs, protocol-relative URLs, regex fallback, and WP HTML Tag Processor execution.

= 2.59.11.65 =
* Verify generated AVIF/WebP freshness against the exact source file before frontend rewrite, serving a variant only when both mtimes are valid and the output is at least as new as the source.
* Fall back to the original image for missing, stale, orphaned, or unverifiable variants, without deleting or rewriting files inside the frontend request.
* Reuse the bounded on-demand media queue with source mtime/size dedupe for stale and indeterminate discoveries, while memoizing source fingerprints and freshness states per request.
* Align newly committed output timestamps to future-dated sources when required, and add executable regressions for replacements, missing sources, unknown mtimes, queue dedupe, non-destructive lookup, and timestamp alignment.

= 2.59.11.64 =
* Retain the complete source filename in every generated AVIF/WebP path, mapping `photo.jpg` to `photo.jpg.avif` or `photo.jpg.webp` instead of removing the source extension.
* Add one canonical generated-path builder and exact reverse mapper shared by media generation, frontend lookup, LCP preference, Slider Revolution handling, and converted-image source recovery.
* Stop guessing source extensions and intentionally reject legacy ambiguous optimized names that cannot distinguish sources such as `photo.jpg` and `photo.png`.
* Apply the same collision-free identity to Media Library Replacement plans and add executable regressions for generation, serving, reverse mapping, Slider Revolution, and replacement destinations.

= 2.59.11.63 =
* Detect embedded JPEG APP2 ICC, PNG iCCP, and WebP ICCP metadata through bounded guarded reads before selecting an encoder.
* Route profiled or indeterminate sources exclusively through color-managed Imagick paths, including upload max-side resize inside the same bounded decode, while preserving the original upload when color management is unavailable.
* Preserve ICC/ICM bytes across metadata stripping, verify the real temporary AVIF/WebP output before atomic publication, and convert decoded pixels through a bundled sRGB profile when the delegate drops the original profile.
* Extend the AVIF runtime self-test with a valid profiled JPEG fixture, separate color-profile capability, and decoded-output RGB sample comparison against a runtime-generated sRGB reference.

= 2.59.11.62 =
* Parse JPEG APP1/Exif orientation through bounded guarded reads without depending on the optional PHP EXIF extension.
* Normalize the complete EXIF orientation matrix 1–8 before encoding, including mirrored cases 2, 4, 5, and 7, through native or manual Imagick operations and explicit GD pixel transforms.
* Reset Imagick output to top-left before metadata stripping and route oriented WebP sources away from the non-portable WordPress image-editor path into the shared normalized encoder paths.
* Add executable fixtures for little- and big-endian EXIF metadata, malformed/truncated tags, all eight GD pixel matrices, native/manual Imagick operations, alpha handling, and decode-normalize-encode ordering.

= 2.59.11.61 =
* Detect animated WebP sources before pixel decode through bounded RIFF chunk inspection and resource-limited Imagick metadata frame counting.
* Complete queue, direct, bulk, forced-regeneration, and conversion-test work as an explicit `animated_webp_unsupported` skip instead of recording an encoder failure or retrying the item.
* Preserve animated WebP uploads before any WordPress image-editor resize, return the original upload without an error, and never delete or replace the source.
* Add executable fixtures for VP8X, `ANIM`, `ANMF`, malformed containers, Imagick inspection order, queue completion, direct calls, upload preservation, and sample conversion reporting.

= 2.59.11.60 =
* Route WordPress image-editor, direct Imagick, and GD AVIF/WebP encodes through same-directory temporary files that retain the real output extension.
* Validate temporary media output before publication, atomically rename it into place, verify the final state, harden permissions, and remove temporary files on every failure path.
* Preserve any previously valid optimized destination when an encoder or commit fails, and prevent the guarded rename fallback from deleting an existing target before replacement succeeds.
* Add executable atomic-output fixtures covering successful replacement, invalid temporary output, failed commit preservation, cross-directory rejection, writer call-site coverage, and guarded rename semantics.

= 2.59.11.59 =
* Inspect source dimensions with `wp_getimagesize()` before constructing WordPress, Imagick, or GD pixel decoders, with bounded dimension and total-pixel ceilings and overflow-safe arithmetic.
* Estimate GD decoded bitmap memory as width × height × 4 × 1.8 plus allocator overhead, reserve current PHP headroom, and reject unsafe GD or unknown WordPress image-editor attempts before decode.
* Construct Imagick empty, apply bounded MEMORY and MAP resource limits before `readImage()`, restore prior process limits in `finally`, and report typed preflight/decode failures.
* Add executable decoder-admission fixtures covering geometry memoization, invalid/excessive sources, bounded filters, GD and WordPress memory rejection, resource-backed Imagick admission, and real conversion call ordering.

= 2.59.11.58 =
* Add a dedicated persistent `stale_recoveries` counter to media queue schema version 4 instead of treating work-unit attempts or ordinary conversion failures as worker crashes.
* Recover expired processing claims atomically, preserve `attempts` and `consecutive_failures`, and quarantine an item after the bounded stale-recovery limit so the next pending attachment can continue.
* Report stale-worker quarantine separately from normal conversion retry exhaustion, while explicit Retry Failed, regeneration, repair, and queue rebuild operations reset the appropriate failure state.
* Add executable stale-worker recovery fixtures covering three consecutive abandoned claims, terminal quarantine, next-item progress, and explicit manual retry reset.

= 2.59.11.57 =
* Complete the full audit regression candidate with one executable UC-001 through UC-031 source-contract matrix registered in the permanent parity harness.
* Require release identity parity across the plugin header, runtime constant, WordPress stable tag, README, translation template, and changelog before the candidate can pass.
* Re-run the complete page-cache, object-cache, ESI, Media Queue, Media Replacement, delayed JavaScript, CSS, LCP, Varnish, REST, lifecycle, and package-hardening regression matrix as one release gate.
* Keep production runtime behavior, settings schemas, and upgrade behavior unchanged from 2.59.11.56; this version adds only regression evidence and release metadata.

= 2.59.11.56 =
* Remove the unused object-cache `_exists()` helper after confirming that no runtime or generated-drop-in path calls it, while retaining the public WordPress-compatible key-validation contract.
* Replace the ambiguous REST `format_batch_response()` helper with `paginate_complete_item_set()`, deriving `total` from the complete input set so pagination metadata cannot describe a different dataset.
* Clamp past-end offsets to the actual global total, normalize item keys and page-size bounds in one canonical helper, and update both crawl-URL fallback callers to declare the complete-set contract explicitly.
* Add executable fixtures for first, middle, final, empty, exact-boundary, past-end, normalized-key, and 500-item-cap pagination together with source assertions for the removed dead code and superseded helper.

= 2.59.11.55 =
* Store the advanced-cache and object-cache PHP source templates as guarded `.php` files so ordinary web-server configurations execute the direct-access guard instead of returning the template source as plain text.
* Update both authoritative drop-in builders and all parity fixtures to consume the new template paths while preserving the generated drop-in source contract and placeholders.
* Keep the CWP Varnish configuration resources as downloadable `.tpl` files and add permanent package fixtures for template filenames, direct execution, source references, placeholders, and readme sections.
* Add WordPress.org Frequently Asked Questions and Upgrade Notice sections with the installed drop-in filename and upgrade behavior documented explicitly.

= 2.59.11.54 =
* Require every destructive Media Replacement confirmation token to match the current job, generation, action, WordPress user, and shared ten-minute TTL; expired or mismatched tokens are omitted from workflow responses.
* Consume database and Theme CSS start-confirmation tokens exactly once, persist action-specific server-side authorization for later chunks, pause/resume, and WP-CLI runs, and reject raw-token replay.
* Rotate the matching token and invalidate prior authorization whenever a new preview is requested, clear authorization after successful action completion, and keep a generation or user change fail-closed.
* Pause Do for recoverable confirmation refresh instead of marking the replacement plan failed, and add executable fixtures for expiry boundaries, wrong job/action/user/generation, replay, preview rotation, pause/resume, completion cleanup, Delete Originals parity, and WP-CLI user zero.

= 2.59.11.53 =
* Replace magic zero-expiry capability handling with a data-driven fail-closed registry that reports contract support, current transport reachability, behavior verification, expiry, and effective runtime availability separately.
* Keep native admin BAN, batch BAN, HTML-only, and entire-host contracts configured but unavailable until each admin endpoint accepts a real Test Varnish control request; a later failed recheck immediately removes runtime availability without erasing the historical contract record.
* Preserve historical HTTP capability proof after a failed canary for diagnostics while gating runtime use through explicit per-capability availability fields; semantic VCL contract downgrade remains the authoritative path that removes superseded contract evidence.
* Remove `SERVER_NAME` from discovery and enforce configured endpoint, loopback, server/local IP, local hostname, then reverse-DNS priority with executable registry, runtime-planner, recheck, unknown-capability, expiry, and candidate-order fixtures.

= 2.59.11.52 =
* Replace the broad refresh-ahead queue-busy check with a typed scanner gate that yields only to an active foreground warm-up owner, pending or processing Varnish invalidation, or a paused shared background rate.
* Allow bounded refresh-ahead discovery while unrelated shared page-refill rows exist, while retaining the exact per-URL pending-refill guard so the same page is never probed or queued twice.
* Preserve the timestamp of the last completed scan when a priority or capacity gate skips discovery, instead of treating a skipped attempt as a completed scan.
* Reuse one capped retry-backoff contract for transient public-probe failures and durable enqueue failures, with executable scheduling, same-URL pending, and escalating-backoff fixtures.

= 2.59.11.51 =
* Replace the ambiguous `array|null` Varnish invalidation queue return with explicit direct, queued, unavailable, and failed decision modes and typed reasons.
* Bound queue-failure fallback to at most 20 canonical URLs and 20 estimated endpoint requests when durable storage is unavailable or accepts zero rows, leaving the remainder to the declared TTL fallback instead of blocking the WordPress request.
* Refill only URLs that were actually invalidated, expose queue-failure and TTL-deferred accounting in production results, and keep partially persisted batches on the durable queue without duplicate direct execution.
* Add executable fixtures for URL and endpoint thresholds, duplicate canonicalization, partial persistence, foreground ownership, zero background rate, queue storage failures, and both targeted and site-known-URL callers.

= 2.59.11.50 =
* Add versioned page-lifecycle proof fields to persistent LCP mappings and verify a bounded set of old locked page URLs through the existing scheduled cleanup job.
* Remove exact LCP rows and manual-selector state before a post is trashed or permanently deleted, while resetting orphan evidence after saves, restores, and real locked browser observations.
* Delete URL-only mappings only after two consecutive `404`/`410` responses, stale mappings after repeated permanent `301`/`308` redirects, and treat temporary redirects, transport failures, and server failures as non-destructive evidence.
* Use no-follow HEAD probes with a one-byte GET fallback, compare-and-swap lifecycle updates, and executable fixtures for missing pages, redirects, races, hook timing, bounded selection, and terminal row accounting.

= 2.59.11.49 =
* Classify browser-observed LCP winners through one canonical viewport policy as universal, viewport-specific, or ambiguous.
* Apply `fetchpriority="high"`, eager image loading, and video preload promotion only when all three viewports confirm the same resource and one specific element identity.
* Match universal image, video, and poster candidates by their stored selector so duplicate elements using the same URL are not promoted together.
* Preserve one unscoped image preload for universal winners and media-scoped preloads for viewport-specific or incomplete mappings, with executable image, srcset, video, poster, background, and duplicate-winner fixtures.

= 2.59.11.48 =
* Preserve link-level media conditions on hoisted `@import` rules, including imports qualified by `layer()` and `supports()`.
* Reject a CSS source run when link media and import media require an intersection that cannot be represented without changing semantics, instead of emitting an unconditional import.
* Canonicalize compatible UTF-8 `@charset` declarations once and reject non-UTF-8 or conflicting charset declarations before any bundle file is committed.
* Carry link media through the leftover bundle path and add executable fixtures for media qualifiers, conflicts, unsafe media, comments, UTF-8 aliases, and incompatible charsets.

= 2.59.11.47 =
* Consolidate leftover and generated font-mix stylesheets only inside maximal contiguous runs of eligible stylesheet links, preserving every skipped stylesheet boundary.
* Replace global URL-based source removal with ordinal link-position plans so duplicate URLs and disjoint runs retain their original document identity and cascade position.
* Generate one bundle per eligible run, assign unique bundle and delayed-font element IDs, and keep isolated eligible stylesheets unchanged when no adjacent partner exists.
* Add executable run-planning and HTML rewrite fixtures for nonlocal, media, non-stylesheet, duplicate-URL, multiple-run, and delayed font-mix cases.

= 2.59.11.46 =
* Store a deterministic per-source CSS bundle fingerprint using the source URL, hashed canonical filesystem identity, modification time, and byte size.
* Reject CSS manifest entries when a source changes, disappears, resolves to a different local file, or predates the fingerprint contract.
* Invalidate the CSS bundle manifest on theme switches and Customizer saves before the affected frontend URLs are purged.
* Add executable freshness fixtures for unchanged, modified, missing, and legacy source states without exposing server filesystem paths or adding upgrade migrations.

= 2.59.11.45 =
* Keep inline scripts that call `document.write()` or `document.writeln()` on the synchronous HTML execution path, including direct, optional-chaining, and quoted bracket-property variants.
* Extend the first-party delayed-loader ready hold to `jQuery.ready.then()` while preserving its returned Deferred chain and restoring both jQuery ready registration surfaces after the lane flush.
* Preserve ordinary inline-script delay eligibility, first-party execution order, CSP attributes, and the existing automatic trigger policy.
* Add permanent PHP and executable JavaScript regression fixtures for document-stream-write exclusions, jQuery ready ordering, promise continuation, exact hook restoration, and one-time flushing.

= 2.59.11.44 =
* Complete the full roadmap regression candidate with release-identity, Media Replacement schema-parity, package-directory, REST/UI, and generated-artifact assertions.
* Align the public Media Converter replacement schema constant with the active schema version 11 used by the dedicated replacement manager.
* Refresh the translation-template project version, add the WordPress readme changelog section, and add direct-access guards to the remaining package directories.
* Clear the pending Media Conversion background cron hook during normal plugin deactivation, matching uninstall and full-cleanup behavior.
* Re-run the permanent cache, object-cache, warm-up, ESI, Media Replacement, LiteSpeed, and JavaScript regression suites without changing their accepted runtime contracts.

= 2.59.11.43 =
* Register the ESI and live Google Fonts template-enhancement callbacks only immediately before template inclusion and only when the current request can use them, instead of forcing WordPress full-output buffering on every frontend response.
* Force ESI buffering only when at least one fragment is registered, when another feature already requires the same buffer, or when an integration explicitly opts into late-registration compatibility.
* Preserve page-cache STORE, Runtime JavaScript scan, Google Fonts, upstream-filter, WooCommerce, and registered-fragment transformation paths while allowing no-fragment bypass requests to stream.
* Return the registered inline fallback when the expected WordPress template buffer did not start, and extend the permanent parity harness with selective callback, late-registration, upstream-buffer, and no-buffer fixtures.

= 2.59.11.42 =
* Add a deterministic ESI registry has_fragments/count contract and snapshot registered fragment state at the first template-enhancement buffer decision.
* Record the effective buffering reason for Runtime JavaScript scans, page-cache STORE, Google Fonts cleanup, ESI, upstream filters, and no-buffer decisions.
* Track bounded registration hooks, init timing, and fragments registered after the first buffer decision, and expose current/late counts in request-profile checkpoints.
* Preserve the existing ESI-enabled full-buffer behavior and verify byte-identical fragment definitions, rendering, fallbacks, and signed tokens while extending the permanent parity harness.

= 2.59.11.41 =
* Enforce a versioned LiteSpeed query-URL operation contract: native retrieval bypass, no native storage, no exact query purge, no query refill, and no base-URL aliasing.
* Reject non-empty query strings before LiteSpeed URL normalization so `/product?filter=red` can no longer purge or refill `/product`.
* Partition targeted invalidation inputs, report skipped query/invalid URLs, and enqueue only exact local queryless URLs into the LiteSpeed refill pipeline.
* Skip query URLs as not applicable in site-warm and targeted refill paths, expose the operation contract in diagnostics/UI, and extend the parity harness with executable query-operation fixtures.

= 2.59.11.40 =
* Add a versioned LiteSpeed query cache-key proof bound to the canonical query-policy fingerprint.
* Prove with executable fixtures that preserving native query order fragments equivalent URLs, while dropping allowed keys aliases distinct values; native key modifiers therefore cannot represent UltraCache canonical key ordering, structured-value ordering, and RFC3986 encoding.
* Recompute the proof in runtime and advanced-cache configuration, project its fingerprint/status into managed LiteSpeed rules, diagnostics, and exact-invalidation results, and ignore forged embedded proof state.
* Keep the blanket LiteSpeed query-string bypass active and do not install CacheKeyModify or cache-key-mod directives.

= 2.59.11.39 =
* Add a versioned canonical query-string cache policy with normalized effective allowlist, immutable/configured hard-blocked keys, and a stable behavior fingerprint.
* Make the page-cache engine and embedded advanced-cache runtime consume the same policy projection while preserving the existing query cacheability behavior.
* Project the same policy fingerprint into managed LiteSpeed rules, diagnostics, and exact-invalidation results without enabling LiteSpeed query-string retrieval yet.
* Extend the parity harness with engine/drop-in policy fixtures, order-independent fingerprint checks, hard-blocked allowlist filtering, and projection-only LiteSpeed assertions.

= 2.59.11.38 =
* Add a dependency-free CLI parity harness that executes the real engine helpers and extracts the real advanced-cache query and Accept implementations instead of duplicating their logic in tests.
* Cover host directory normalization, query canonicalization, HTML image buckets, private ESI cookies, manual warm-up REST/UI actions, Media Queue wait metadata, and Media Replacement live encoding/compare-and-swap invariants.
* Add a generated runtime object-cache conformance fixture for forced reads, add/replace, numeric operations, non-persistent groups, suspended additions, multiple-key APIs, cloning, deletion, and runtime flush semantics.
* Add executable dashboard job-runner fixtures for bounded queue-build backoff, progress-token reset, resumable stalls, and exactly-once exclusive lease pause behavior.

= 2.59.11.37 =
* Add a bounded, deduplicated in-memory admin error history with debug-only console reporting for non-fatal JavaScript failures.
* Surface exclusive job pause, failure, and release lease errors with actionable warning notices while ensuring release exceptions cannot leave the dashboard busy state stuck.
* Record job persistence, lifecycle refresh, Media Library Replacement status, and cache/dashboard refresh failures without interrupting successful primary operations.
* Classify harmless browser storage, focus, and scrolling failures explicitly and remove every empty catch block from the administrator JavaScript modules.

= 2.59.11.36 =
* Bind Delete Originals start-confirmation tokens to the active job, verified generation, WordPress user, and creation time, with a ten-minute lifetime.
* Consume the confirmation token once when the first destructive chunk starts, then require the recorded generation authorization and current replacement lease for pause, resume, and retry.
* Omit expired or wrong-user Delete Originals tokens from status responses and reject token replay, generation drift, and exact-expiry-boundary use before any original file is touched.
* Allow WP-CLI Delete Originals resume invocations to continue without a consumed start token while retaining the existing resumable database and Theme CSS confirmation behavior.

= 2.59.11.35 =
* Added SHA-256 fingerprints to Media Library replacement registry rows so Delete Originals detects same-size content changes.
* Centralized cleanup row validation across Preview, failed-row recovery, and the active Delete Originals runner.
* Replaced string-prefix uploads checks with canonical filesystem containment.
* Removed the superseded Cleanup Apply REST, facade, manager, API, and admin UI deletion path.

= 2.59.11.34 =
* Resolve serialized, JSON, or raw database encoding from the value read immediately before Media Library replacement apply, verification, and rollback instead of trusting only the earlier Preview flags.
* Preserve valid serialized string lengths and JSON structure when a database row changes format between Preview and Apply.
* Use byte-exact compare-and-swap database updates so a concurrent writer cannot be overwritten between the UltraCache read and write.
* Apply the same compare-and-swap protection to post-write recovery, rollback, and serialized-value repair operations.

= 2.59.11.33 =
* Return explicit media queue-building wait state, retry timing, build metadata, and a stable progress token when the queue has no ready items but its rebuild is incomplete.
* Prevent the dashboard job runner from immediately repeating empty unchanged batches by using cancellable bounded exponential backoff, cursor/progress-token checks, a no-progress timeout, and a hard iteration cap.
* Pause stalled media jobs in a resumable state instead of generating an unbounded REST polling loop while another rebuild worker holds the lock or the rebuild cannot advance.
* Preserve compatibility with older batch payloads by inferring queue-building waits from the existing queue status.

= 2.59.11.32 =
* Keep the filtered private ESI HTTP Cookie header in raw wire format while populating $_COOKIE with one-pass raw URL-decoded values that match PHP request semantics.
* Reject encoded control characters after decoding, preserve literal plus signs, and keep the first duplicate cookie value as PHP does.
* Reuse the same bounded cookie parser for production private fragments and the Varnish private-transport probe.
* Correct the private-fragment documentation so WordPress login-dependent renderers explicitly declare and transport the wordpress_logged_in_ cookie prefix.

= 2.59.11.31 =
* Allow the implemented dashboard manual warm-up cancel action through REST schema validation so the UI request reaches the ownership-checked cancellation handler and releases foreground priority.

= 2.59.11.30 =
* Scope Redis, APCu, and Disk request-local fallback markers by the actual runtime cache scope so one multisite blog cannot affect the same group/key in another blog.
* Route runtime flush and deprecated reset operations through the active backend so request-local fallback tracking is cleared with the values it describes while global reset state remains preserved.
* Keep group-level fallback cleanup limited to the current blog/global scope instead of clearing unrelated scoped state.
* Make the Runtime backend ignore forced persistent refreshes and return its request-local value because it has no persistent storage layer.
* Complete the object-cache conformance matrix across Runtime, Redis, APCu, SQLite, and Disk, including single-site, multisite, multiple APIs, non-persistent groups, expiry, fallback recovery, and concurrency regressions.

= 2.59.11.29 =
* Serialize Disk add, replace, delete, and numeric mutations with global, group, and striped per-key file locks while retaining atomic temporary-file rename writes.
* Prevent concurrent Disk add winners, replace/delete resurrection, and lost numeric updates; preserve the original absolute expiry during numeric mutations.
* Keep Disk reads concurrent through shared locks, make group/full flushes wait for active operations, and preserve the internal lock directory across flushes.
* Give Disk cache groups collision-resistant slug-plus-hash directories so distinct names such as a/b and a-b no longer share one file namespace.
* Treat unsupported Disk values as request-local cache entries without fatal serialization errors or stale persistent files, and synchronize dirty numeric fallback state after storage recovers.
* Enforce Disk payload and signed-envelope size limits before writing unreadable cache files.
* Extend the Disk backend diagnostic to verify file locking, atomic rename, readback, and cleanup rather than raw read/write alone.

= 2.59.11.28 =
* Make APCu add() use atomic apcu_add() so concurrent requests cannot both add the same persistent key.
* Serialize APCu set, replace, delete, and signed numeric mutations with bounded token-owned per-key locks, stale-lock expiry, and ownership-safe release.
* Preserve APCu numeric TTLs, prevent replace/delete resurrection and lost numeric updates, and keep in-flight writes bound to the namespace/group generation they locked.
* Track request-local APCu fallback values until a later successful mutation synchronizes them, while removing stale persistent envelopes after failed or unsupported replacement writes.
* Require and probe APCu atomic primitives, including apcu_cas(), before reporting the backend as available.

= 2.59.11.27 =
* Make Redis incr() and decr() use bounded WATCH/MULTI/EXEC transactions so concurrent numeric mutations accumulate instead of overwriting each other.
* Preserve the existing Redis expiry window during numeric updates instead of silently removing the key TTL.
* Retry transaction conflicts against the latest signed Redis payload and return false after a bounded five-attempt limit without overwriting the committed value.
* Track request-local Redis fallback values as authoritative until a later successful transaction synchronizes the accumulated value back to Redis.
* Reuse one signed Redis payload decoder for normal reads and transactional numeric mutations.

= 2.59.11.26 =
* Make Redis add() use an atomic conditional SET NX write so concurrent requests cannot both add the same persistent key.
* Make cold Redis replace() use SET XX so a key deleted concurrently is not recreated by an unconditional write.
* Preserve request-local fallback semantics when Redis is unavailable or a value cannot be serialized, and remove stale persistent values for unsupported replacements.
* Centralize signed Redis payload encoding and keep conditional TTL writes aligned with the existing Redis envelope and expiry contract.

= 2.59.11.25 =
* Reject invalid cache keys consistently across the public object-cache API while preserving integer zero as a valid key.
* Return false when delete() targets a missing key and keep delete-multiple results aligned with actual cache existence.
* Keep single-site cache scope unchanged during switch_to_blog(), preserve global runtime groups during reset(), and retain multisite isolation.
* Treat entries expiring at the current second as expired across shared payload checks and SQLite cleanup, add, read, and replace paths.
* Keep failed SQLite add() calls from creating request-local values when no authoritative existing row can be recovered.
* Preserve SQLite expiry during request-local numeric synchronization while matching WordPress zero-coercion and floor-at-zero behavior.

= 2.59.11.24 =
* Make incr() and decr() use an existing request-local numeric value before forcing a persistent read.
* Keep numeric mutations operational in the runtime backend and after Redis/APCu persistent-write fallback.
* Preserve non-persistent-group numeric behavior and the existing decrement floor at zero.
* Retain SQLite atomic numeric mutation for synchronized/cold persistent values while recovering runtime-only or divergent request-local counters through the normal write path.

= 2.59.11.23 =
* Read forced gets from the request-local store for non-persistent groups instead of reporting a false miss.
* Preserve existing request-local keys when add() or replace() checks persistent storage, including runtime-only fallback values.
* Limit wp_suspend_cache_addition() to add() and return false without writing while additions are suspended; keep set() and replace() operational.
* Make SQLite replace runtime-only values through the normal write path while retaining its conditional persistent replace for uncached keys.

= 2.59.11.22 =
* Use one canonical page-cache host-directory normalization contract in the engine and the generated advanced-cache drop-in.
* Preserve valid short and multi-label hostnames and punycode labels without WordPress filename-extension rewriting or hyphen collapsing.
* Normalize trailing-dot hosts consistently and preserve explicit request ports in the early drop-in cache key.
* Restore pre-WordPress page-cache hits for affected host and authority forms.

= 2.59.11.21 =
* Reused ultracache_server_value() for Varnish canary and ESI cookie server inputs.
* Made the LCP manual-selector upsert and bounded warm-queue hash query expose every prepared-statement argument explicitly.
* Replaced the discouraged mt_rand() fallback with wp_rand().
* Applied the existing controlled diagnostic HTML output contract to the Varnish canary response.
* Shortened the WordPress.org short description to remain within the 150-character limit.

= 2.59.11.20 =
* Fix integration-card headings, including Varnish Cache, using the active dashboard text token instead of a hard-coded white color.
* Preserve the existing light heading in dark mode while rendering a readable dark heading on the WordPress-native white card background.

= 2.59.11.19 =
* Removed the pre-run CSS/font directory inventory from `warm_html_all_css`; optional filesystem reporting now runs only after the canonical warm-up has completed.
* Added an immediate preparation message before the progress bar so WP-CLI execution is visible from command entry.
* Made generated asset traversal exception-safe, including unreadable nested directories.
* Reported final inventory limitations explicitly without replacing or aborting the per-URL HTML/CSS warm-up result.

= 2.59.11.18 =
* Replace the misleading final homepage-only CSS message with a site-wide WP-CLI report built from the canonical per-URL warm pipeline results.
* Report completed, skipped, and failed HTML URLs separately; report per-page CSS bundles built, reused, skipped, and failed, plus stylesheet and byte totals for newly built bundles.
* Inspect the generated cached HTML variants for main page bundles, leftover bundles, font-mix bundles, font-css, optimized-css, and localized Google Fonts references, including a dedicated homepage verification line.
* Report post-run manifest validity and generated asset inventory with new-file deltas for main, leftover, font-mix, delayed-font, font-css, optimized-css, Google Fonts CSS, and Google Fonts WOFF2 assets.
* Remove the redundant second homepage CSS rebuild after the full-site crawl; the homepage is now verified from the same canonical crawl result as every other URL.
* Raise foreground UI/WP-CLI HTML and CSS-source loopback timeouts from 10 to 60 seconds for heavy pages while keeping cron, visit, and other background profiles at 10 seconds.

= 2.59.11.17 =
* Restore Flush All Cache when Varnish inclusion is enabled by calling the authoritative Ultra_Cache_WP Varnish runtime helper from the REST permission callback.
* Keep the existing infrastructure capability requirement for active Varnish flushes without duplicating Varnish configuration logic inside the REST API class.

= 2.59.11.16 =
* Normalize Varnish capability rows to Supported, Not supported, or a mode-specific Unavailable state; remove ambiguous Not verified and Not tested capability labels.
* Show HTTP PURGE, VCL contract, soft purge, origin revalidation, and stale-while-revalidating as unavailable in Admin/BAN mode while preserving supported Admin BAN, flush, and ESI capabilities.
* Derive Flush scope and ESI capability status directly from effective runtime support instead of displaying raw unavailable registry states.
* Extend Test Varnish with an HTML-variant proof that runs the existing canonical page warm pipeline, including its existing Varnish invalidation and refill stages, then verifies the active orig, WebP, and AVIF public objects.

= 2.59.11.15 =
* Clarify Varnish diagnostics by showing HTTP PURGE and VCL contract rows as not used or not applicable in Admin mode instead of implying missing capability.
* Show Admin endpoint verification, non-expiring Admin proofs, unverified capabilities, and untested HTML variants with mode-appropriate labels.
* Add Help FAQ guidance that recommends Admin/BAN when available and verified, with HTTP PURGE as the practical fallback when the host exposes no admin endpoint.
* Add the verified generic full-site WP-CLI warm-up command using the existing HTML, Separate CSS Bundle, Varnish/LiteSpeed, and orig/WebP/AVIF pipeline.

= 2.59.11.14 =
* Fixed authenticated WP-CLI and dashboard warm loopbacks being rejected as `invalid-internal-control` when they carried the valid warm runtime token without a force-revalidate flag.
* Fixed authenticated internal CSS bundle source requests using the same runtime-control contract.

= 2.59.11.13 =
* Refactor both bundled CWP templates into ready-to-install per-domain templates with no embedded secret, token placeholder, disabled contract, or manual post-download edit.
* Retain exact normalized host matching, local-direct exact PURGE, canonical AVIF/WebP/original HTML variants, public ESI, the recommended private/WooCommerce ESI handshake, object host/URL metadata for Varnish admin BAN, separate grace/keep windows, and cache observability.
* Keep advanced exact, batch, HTML-only, and entire-host invalidation on UltraCache's existing Varnish admin transport instead of duplicating authentication inside each domain template.

= 2.59.11.12 =
* Emit an explicit per-endpoint result from the single-endpoint Varnish canary and persist that result directly into the authoritative capability registry.
* Make endpoint-registry status reads side-effect free so diagnostics, planners, runtime enablement checks, and configuration projections cannot rewrite or erase a verified proof.
* Keep capability proofs attached to configured endpoints while runtime enablement remains a separate execution gate, and preserve valid proofs across temporary disable/read cycles.
* Treat configuration fingerprint mismatches as read-only projections until a new explicit test or capability writer replaces the stored proof.

= 2.59.11.11 =
* Pass the exact normalized Varnish settings snapshot used by Test Varnish through behavior execution, endpoint-registry synchronization, profile sanitization, and persistence.
* Remove the 2.59.11.10 reader-side proof backfill and restore the registry reader to validation-only behavior.
* Prevent post-test settings re-reads from dropping or invalidating a successful endpoint proof before it reaches the authoritative capability registry.

= 2.59.11.09 =
* Fixed the public upgrade reset to recreate the disposable warm-up queue without running legacy row consolidation.
* Preserved the existing one-time Flush All flow and user settings while preventing MariaDB ambiguous-column errors during upgrade.

= 2.59.11.08 =
* Promote the integration-hardened warm-up architecture to the final validation candidate without changing runtime behavior from 2.59.11.07.
* Re-run the complete atomic coordination, ownership, stale-worker fencing, full-site plan, shared rate, read-only status, public upgrade reset, canonical queue, targeted-work, frontend-visit, Varnish, LiteSpeed, CSS, and LCP regression suite against the release tree.
* Verify release identity, unchanged schemas and public API, prepared-SQL compliance, plugin-root ZIP packaging, extracted-tree equality, and deterministic validation evidence before controlled live-server testing.

= 2.59.11.07 =
* Persist every configured Varnish and LiteSpeed refill requirement in the same canonical page_warm row as HTML, for both targeted work and newly discovered full-site URLs.
* Keep frontend HIT satisfaction limited to the HTML stage so CSS, LCP, Varnish, and LiteSpeed requirements remain pending until their canonical stages complete.
* Replace the targeted Varnish sibling upsert and redirect stage loop with one normalized required_stages upsert, preventing duplicate coalesced/upgraded metrics and preserving LiteSpeed stages across canonical redirects.
* Make Varnish and LiteSpeed refresh-ahead declare only their own external-cache stage, while ordinary affected-page work adds each enabled targeted refill policy to the shared URL row.
* Make background execution follow the canonical required_stages contract instead of silently enabling external-cache work from a generic targeted context, without changing ownership, plan, rate, queue schema, or scheduling architecture.

= 2.59.11.06 =
* Add one version-gated public upgrade reset from the WordPress.org/SVN 2.59.10.01 baseline while treating later private development warm runtime as disposable.
* Preserve the complete UltraCache settings option, discard legacy warm queues, owners, leases, cursors, retries, generations, and private warm decision/plan/rate payloads, then recreate the canonical queue and clean atomic coordination records.
* Run exactly one canonical Flush All Cache with the plugin_update reason, suppress automatic warm scheduling during the purge, and coalesce one fresh after-flush full-site plan only when the saved setting and background rate enable it.
* Make the transition resumable and idempotent with a dedicated upgrade lock, flushed/initialized phases, and a completed target marker; fresh installations are marked complete without an unnecessary cache flush.
* Avoid migrating transient queue rows through private development schemas by recreating the disposable warm queue directly at schema 17.

= 2.59.11.05 =
* Consolidate dashboard, REST, and WP-CLI warm-up status through one read-only snapshot built from warm_decision, warm_plan, warm_rate, legacy lifecycle compatibility fields, and bounded canonical queue aggregates.
* Add read-only lock and state readers that never create or upgrade schema, and display expired foreground or cron leases in memory without recovery writes.
* Derive pending and processing totals from the existing aggregate queue query, use at most one LIMIT 1 current-activity lookup, and avoid loading URL result sets regardless of queue size.
* Preserve the complete 2.59.11.04 status contract while adding the authoritative warmRate projection and reusing already-read decision, rate, lifecycle, and schedule data for worker diagnostics.
* Keep Varnish refill-worker diagnostics read-only by accepting the consolidated status context instead of re-reading or recovering warm runtime state.

= 2.59.11.04 =
* Move the persisted real-minute background URL allowance into one revisioned atomic warm_rate record with window, claimed, configured, and effective limits.
* Make WP-Cron, kickoff, WP-CLI/server-cron ticks, REST ticks, canonical page stages, persistent Varnish work, and LiteSpeed refill share the same remaining minute budget.
* Claim only executable URL slots through compare-and-swap so concurrent invocations cannot exceed the configured rate while interrupted workers may conservatively under-use a minute.
* Keep enqueue, Flush All, warm start, settings synchronization, and repeated same-minute invocations from resetting consumed slots or granting a second allowance.
* Keep rate 0 as a true paused state that leaves queued work pending and removes recurring or kickoff warm events instead of creating a reschedule storm.

= 2.59.11.03 =
* Move full-site plan identity, discovery cursor, source batch, scheduled selection limit, and mixed-workload fairness pointer into the revisioned atomic warm_plan record.
* Derive full-site selected, processed, outcome, and remaining counts from canonical queue membership instead of persisting duplicate counters.
* Guard discovery-batch commits and cursor advancement with exact compare-and-swap revisions so stale writers cannot move discovery backward.
* Complete and release the full-site plan independently of unrelated targeted work or retries, allowing targeted automation to continue.
* Reattach a paused active plan when the background rate is re-enabled, preserving the same plan ID, committed cursor, batch, limit, and fairness state.

= 2.59.11.02 =
* Bind UI, WP-CLI, and cron worker heartbeats to the exact authoritative source, token, and generation, with every explicit start or resume rotating to a fresh execution token.
* Revalidate ownership before per-URL claims, before HTML/CSS/LCP/Varnish/LiteSpeed work, after network/cache operations, and immediately before canonical queue result commits.
* Release stale cron and persistent Varnish row claims back to pending work instead of recording completed stages after foreground preemption or lease loss.
* Fence CSS bundle file and manifest writes, suppress stale Varnish/LiteSpeed result persistence, and preserve the existing atomic frontend-visit stage merge.

= 2.59.11.01 =
* Moved UI, WP-CLI, and cron warm-up ownership to one revisioned atomic warm_decision state record.
* Made the newest successful UI or WP-CLI start/resume the authoritative foreground owner while cron always yields to a valid foreground lease.
* Routed foreground and cron acquire, heartbeat, pause, release, expiry, and recovery through the shared decision record.
* Kept full-site plan and background-rate persistence on the existing legacy backend for their dedicated roadmap versions.

= 2.59.11.00 =
* Upgrade the shared UltraCache locks table to schema version 2 with explicit lock/state record types, revisions, update timestamps, and a type/expiry index.
* Add generic persistent state helpers for named reads, atomic creation, revision-guarded compare-and-swap updates, bounded mutation retries, named deletion, and explicitly requested record reads.
* Restrict every existing lock acquire, read, renew, release, and expired-row cleanup query to lock records so persistent state rows cannot be mistaken for or deleted as leases.
* Preserve the existing option-backed warm runtime and ownership behavior; the new atomic backend is foundation only in this version.

= 2.59.10.99 =
* Add a dedicated warm coordination access trait as the only persistence boundary for legacy cron, dashboard, WP-CLI, and cache-flush generation state.
* Separate legacy state normalization into explicit decision, full-site plan, and shared-rate helpers while preserving the existing option-backed runtime behavior.
* Add an executable field-ownership inventory for cron and foreground state so the later atomic storage migration has a verified, bounded contract.
* Keep queue schema, ownership semantics, UI and WP-CLI behavior, cron scheduling, targeted warm-up, frontend visits, Varnish, and LiteSpeed integration unchanged.

= 2.59.10.98 =
* Enforce Background warm pages per minute as one persisted real-minute URL ceiling instead of granting the full configured rate to every cron tick invocation.
* Serialize minute-window claims across kickoff events, WP-Cron, real server cron, and explicit background tick calls so overlapping invocations cannot multiply the allowed Varnish and page-pipeline work.
* Preserve the shared Varnish/page budget from 2.59.10.97 inside the single claimed minute window, including explicit pages-per-minute overrides.
* Defer duplicate same-minute invocations to the next minute boundary without clearing queue rows, full-site discovery, mixed-workload fairness, retries, or ownership state.
* Prefer conservative under-use after an interrupted tick over allowing a second invocation to overload the server in the same minute.

= 2.59.10.97 =
* Enforce one shared background URL budget per cron tick across persistent Varnish invalidation and canonical page automation.
* Subtract Varnish URLs already processed in the tick from the remaining page-warm selection budget instead of allowing both workers to consume the full configured rate independently.
* Keep the configured Background warm pages per minute value unchanged in worker state and diagnostics while using only the remaining per-tick budget for full-site discovery and mixed full-site/targeted queue selection.
* Apply an explicit cron-tick pages-per-minute override consistently to auxiliary Varnish work and targeted/full-site page selection for that same tick.
* When queued Varnish invalidation consumes the complete tick budget, preserve all page/full-site state and continue it on the next scheduled tick instead of treating the worker as configuration-paused.

= 2.59.10.96 =
* Apply Background warm pages per minute to the persistent Varnish invalidation worker instead of processing a fixed batch of up to 100 URLs on every cron tick.
* Keep queued Varnish invalidation paused when the shared background rate is 0, without repeatedly scheduling a worker that cannot execute page automation.
* Recheck UI/WP-CLI foreground ownership before auxiliary invalidation work, after acquiring the shared lock, and between bounded Varnish network groups.
* Release unprocessed Varnish queue claims immediately when a newer foreground owner appears, preserving retry state and allowing the dashboard or WP-CLI warm-up to take priority without waiting for lease expiry.

= 2.59.10.95 =
* Recheck the authoritative warm-worker state after acquiring the shared start lock, preventing concurrent after-flush or after-cleanup requests from replacing the full-site plan created by the first request.
* Preserve the first plan's membership, discovery cursor, Scheduled / Cron warm limit, source ordering, and progress when a second start request passed the earlier advisory state check.
* Recheck UI/WP-CLI foreground ownership inside the same lock before resetting full-site state, so a foreground warm-up that starts during the pre-lock window still retains priority over background automation.
* Keep the existing pre-lock checks as a low-cost fast path while making the locked checks authoritative for all state-changing start operations.

= 2.59.10.94 =
* Preserve `scheduled-full-site-complete` when a terminal canonical URL starts a later targeted update, import, LCP, CSS, or external-cache lifecycle during the same active full-site plan.
* Prevent terminal-row reuse from demoting an already processed full-site member back to `scheduled-full-site`, reducing processed progress, or counting the URL a second time when the targeted rerun completes.
* Keep the persisted full-site success/skipped/error outcome unchanged while resetting only the independent targeted lifecycle stages, claims, retries, position, and source context.
* Strip an incoming unprocessed full-site marker before restoring completed membership, keeping the canonical context set mutually consistent even under defensive duplicate enqueue paths.

= 2.59.10.93 =
* Alternate full-site and targeted canonical URLs across background ticks when Background warm pages per minute is 1, preventing either workload from starving behind the other.
* Start each new mixed full-site plan with its highest-priority selected URL, preserving homepage-first source ordering before alternating to targeted work.
* Persist the next mixed-workload class in the shared worker state so real cron invocations, restarts, and ownership handoffs retain deterministic fairness.
* Continue processing the only available workload immediately when the other class has no executable URL; background rates of 2 or more retain the existing bounded split.

= 2.59.10.92 =
* Advance full-site URL discovery while targeted update/import work remains pending instead of waiting for the complete shared queue to become empty.
* Reserve a bounded share of each background tick for selected full-site members while continuing targeted canonical work in the same gentle worker.
* Advance the full-site cursor when the current selected batch is accounted for, even when unrelated targeted URLs remain queued.
* Complete and release full-site membership independently once discovery and selected URLs finish, then continue remaining targeted automation without resetting or deleting it.

= 2.59.10.91 =
* Allow a new full-site background warm-up plan to start when the shared automation state is currently active with targeted update, import, LCP, CSS, or external-cache work.
* Treat only an already active and fresh `full_site` workload as an existing full-site plan; a targeted workload no longer suppresses Warm full site after Flush All Cache or scheduled cleanup.
* Preserve all existing canonical targeted rows while resetting only the full-site discovery cursor, selected-URL limit, and plan progress for the new full-site workload.
* Keep mixed targeted and full-site work on the same shared queue and background execution rate without expanding the Scheduled / Cron warm limit.

= 2.59.10.90 =
* Preserve full-site membership during targeted enqueue from the authoritative current canonical row instead of injecting a marker captured by an earlier membership lookup.
* Prevent a targeted enqueue that overlaps full-site plan completion or replacement from resurrecting `scheduled-full-site` or `scheduled-full-site-complete` after membership cleanup has removed it.
* Continue preserving selected or completed membership when it still exists in the database, including visit/worker completion races handled by version 2.59.10.89.
* Avoid loading the complete active full-site membership lookup for ordinary targeted enqueue requests; cross-batch discovery still uses the lookup for actual full-site planning.

= 2.59.10.89 =
* Preserve an already completed full-site membership when a targeted enqueue races with frontend-visit or worker completion of the same canonical URL.
* Resolve the terminal-row membership transition atomically inside the canonical upsert instead of trusting an earlier full-site membership snapshot.
* Prevent a stale `scheduled-full-site` snapshot from replacing `scheduled-full-site-complete`, reverting processed progress, or causing the URL to be counted again by the active plan.
* Keep targeted lifecycle reset, stages, priority, retries, and persisted full-site outcome unchanged.

= 2.59.10.88 =
* Preserve stages satisfied by a real frontend visit after a newer request marks an actively processing canonical URL for rerun.
* Track pending-rerun stage satisfaction separately from the outgoing worker lifecycle, then promote only that authoritative set when the claim is released, completed, or recovered after lease expiry.
* Prevent the outgoing worker from clearing valid HTML, CSS, LCP, Varnish, or LiteSpeed progress that belongs to the pending rerun while still discarding completion inherited from the older lifecycle.
* Upgrade queue metadata to version 17 and compact the new fixed-stage set without deleting URLs, claims, retries, full-site membership, or targeted work.

= 2.59.10.87 =
* Merge frontend-visit stage satisfaction directly against the current canonical `completed_stages` value through an atomic fixed-set union, preventing a stale pre-read from overwriting stages completed concurrently by the active worker.
* Evaluate pending-row completion from the current database `required_stages` and merged `completed_stages`, so a concurrently added CSS, LCP, Varnish, or LiteSpeed requirement prevents premature terminal success.
* Preserve active processing claims when a visit satisfies another stage, allowing the owning worker to continue from the authoritative merged stage set.
* Reconcile the persistent pending-URL hint against the post-update queue state, including a URL immediately reopened by a concurrent enqueue.

= 2.59.10.86 =
* Always reconcile persistent pending-URL hints against the bounded set affected by queue cleanup instead of inferring per-URL removal from an aggregate deleted-row count.
* Prevent duplicate legacy rows from offsetting a concurrent pending-to-processing transition and causing the surviving canonical URL to lose its active object-cache hint.
* Keep reconciliation limited to fixed 50-hash batches, preserving bounded memory and database work without scanning the complete warm queue.
* Remove the deleted-count shortcut whose equality with unique candidate URLs could not prove that the same URLs were actually removed.
* Preserve existing hints when the bounded reconciliation read fails, preferring one later queue lookup over hiding an active canonical URL from visit/worker coalescing.

= 2.59.10.85 =
* Reconcile persistent canonical pending-URL hints only against the URLs affected by queue cleanup instead of reading every active queue row.
* Process candidate URL hashes in fixed 50-item SQL batches so cleanup memory and database work remain bounded on large WooCommerce and WP All Import queues.
* Preserve active pending/processing hints when duplicate legacy rows or concurrent status transitions make deleted-row counts differ from unique cleanup URLs.
* Keep the zero-query normal path when deleted rows exactly match the captured unique cleanup candidates.

= 2.59.10.84 =
* Synchronize persistent canonical pending-URL hints whenever full-site membership cleanup or ordinary queue cleanup deletes database rows.
* Prevent deleted full-site lifecycle rows from leaving one-week object-cache hints that forced the next PHP-served cache hit to perform an unnecessary queue-table lookup.
* Preserve or restore hints for pending/processing rows that survive a concurrent status transition while cleanup runs.
* Avoid the reconciliation read on the normal path when the number of deleted rows exactly matches the captured cleanup candidates.

= 2.59.10.83 =
* Release finished full-site membership from canonical rows even when a targeted reuse of the same URL is actively processing at plan completion or replacement.
* Preserve the active processing claim, targeted source contexts, required/completed stages, retry state, and queue position while removing only stale full-site markers and the persisted plan outcome.
* Prevent a processing targeted row from carrying `scheduled-full-site` or `scheduled-full-site-complete` into the next full-site plan and suppressing that URL as an apparent duplicate.
* Apply the same cleanup when a new full-site plan replaces prior membership, so stale markers cannot survive across plan boundaries.

= 2.59.10.82 =
* Persist the original full-site terminal outcome independently from the reusable canonical row status, so later targeted update/import lifecycles cannot rewrite historical full-site success, skipped, or error accounting.
* Keep processed full-site membership stable while the same URL returns to pending, processing, done, skipped, or error for unrelated targeted work.
* Clear the persisted full-site outcome only when the active full-site plan releases membership from a mixed canonical row.
* Upgrade queue metadata to version 16 and infer exact outcomes for existing terminal full-site members; already-reused legacy members remain processed with an explicit unknown historical outcome instead of inventing a result.

= 2.59.10.81 =
* Merge worker-completed canonical stages with stages satisfied concurrently by a real frontend visit through an atomic fixed-set union instead of appending raw CSV strings.
* Prevent repeated retries, visit/worker races, and processing-row handoffs from duplicating `html`, `css_bundle`, `lcp_refresh`, `varnish`, or `litespeed` tokens in `completed_stages`.
* Preserve every stage already recorded by the active processing claim while keeping terminal and retry state transitions unchanged.
* Upgrade queue metadata to version 15 so existing duplicate completed-stage tokens are compacted without deleting URLs, claims, retries, progress, or full-site membership.

= 2.59.10.80 =
* Treat persisted full-site membership markers as the authoritative selected, processed, success, skipped, and error counters while an active plan is open.
* Mark a full-site member processed when a real frontend visit completes every required canonical stage before the background worker claims the URL.
* Synchronize full-site progress from canonical membership at status reads and at the beginning of each cron tick without turning dashboard status into a schema-mutating path.
* Release completed full-site membership and ordinary plan rows when the empty-queue early completion path finishes a plan, preventing stale members from suppressing URLs in the next full-site warm-up.

= 2.59.10.79 =
* Merge canonical source contexts token by token when targeted work reuses a pending or processing full-site member, instead of treating a multi-context value as one FIND_IN_SET token.
* Prevent repeated updates/imports from duplicating `scheduled-full-site`, `scheduled-full-site-complete`, or targeted source markers on the same active canonical row.
* Preserve active pending/processing lifecycle state, stage union, queue position, claims, retries, and full-site membership while applying the bounded context set union.
* Upgrade queue metadata to version 14 and compact source-context duplicates already written by earlier multi-context upserts without deleting queue work.

= 2.59.10.78 =
* Deduplicate full-site warm URLs across the complete cursor plan instead of only inside each discovery batch, so homepage, menu, page, post, and taxonomy sources cannot select the same canonical URL twice.
* Keep completed full-site membership rows until the plan finishes, allowing later discovery sources to recognize URLs already selected without storing thousands of hashes in the cursor option.
* Count `fullSitePlanned` from exact canonical membership so duplicate source URLs do not consume additional `Scheduled / Cron warm limit` capacity.
* Preserve pending or completed full-site membership when targeted update/import work reuses the same canonical URL row during an active plan.
* Track completed membership separately so a later targeted lifecycle can rerun the URL without increasing full-site success, skipped, error, or processed counters a second time.
* Upgrade canonical queue metadata to version 13 and normalize terminal membership markers without deleting URLs, stages, claims, retries, or targeted contexts.

= 2.59.10.77 =
* Persist explicit full-site membership on canonical queue rows so later targeted, LCP, CSS, or external-cache coalescing cannot erase their full-site progress identity.
* Track full-site selected, processed, success, skipped, error, and remaining counters independently from the shared queue's overall targeted workload counters.
* Keep targeted enqueue paths from inflating the active full-site plan's total/progress or overwriting its invocation provenance, including paused LCP work at a background rate of 0.
* Upgrade queue metadata to version 12 and mark eligible pending/processing rows from earlier releases without deleting URLs, stages, claims, retries, or progress.
* Show full-site processed progress separately from selected URLs and the Scheduled / Cron warm limit in Automation Worker status.

= 2.59.10.76 =
* Keep `Scheduled / Cron warm limit` immutable when targeted update/import URLs join an active full-site background warm plan.
* Preserve the active full-site plan's invocation provenance while canonical targeted rows retain their own source contexts for diagnostics and priority.
* Continue counting mixed pending URLs for worker progress without converting targeted work into additional full-site discovery budget.
* Complete the limit-ownership separation introduced in 2.59.10.62 for mixed full-site and targeted workloads.

= 2.59.10.75 =
* Preserve large queued Varnish invalidation work while dashboard or WP-CLI foreground warm-up owns execution, without scheduling a competing background kickoff.
* Preserve Varnish and LiteSpeed refresh-ahead stages in the canonical queue while foreground ownership is active; normal foreground-release recovery remains the single handoff path.
* Respect Background warm pages per minute for external-cache queue scheduling, so a configured value of 0 stores pending work without repeatedly scheduling an ineligible worker.
* Keep external-cache discovery and durable enqueue independent from execution ownership, matching the CSS and LCP foreground-deferral behavior introduced in 2.59.10.73 and 2.59.10.74.

= 2.59.10.74 =
* Preserve frontend-triggered LCP refresh work when dashboard or WP-CLI foreground warm-up owns execution, instead of replacing the interrupted background worker state with an LCP-only state.
* Keep foreground priority limited to execution: the LCP stage is coalesced into the canonical URL row immediately and resumes through the existing full-site or targeted worker after ownership is released.
* Preserve full-site discovery cursor, Scheduled / Cron warm limit, selected URL progress, and targeted worker metadata while foreground warm-up is active.
* Avoid unscheduling or creating a competing background worker from the LCP observation request; normal foreground-release recovery remains the single handoff path.

= 2.59.10.73 =
* Preserve frontend-triggered async CSS bundle work when a dashboard or WP-CLI foreground warm-up owns execution, instead of dropping the request before it reaches the canonical queue.
* Keep foreground priority limited to execution: the CSS stage is coalesced immediately, remains pending, and resumes through the shared background worker after ownership is released.
* Avoid overwriting an interrupted full-site plan or scheduling a competing cron worker while UI/WP-CLI ownership is active.
* Keep the existing Background warm pages per minute pause behavior and canonical URL/stage deduplication unchanged.

= 2.59.10.72 =
* Reset queue position from the incoming request whenever a terminal canonical row (`done`, `skipped`, or `error`) starts a new lifecycle.
* Keep pending rows on the earliest coalesced position and preserve an actively processing row's claimed position until its current worker releases ownership.
* Prevent a previous targeted terminal error at position 0 from jumping ahead when the URL is later selected by a full-site plan.
* Prevent a previous full-site terminal error from delaying a later targeted update that must return to position 0.
* Complete the terminal lifecycle reset introduced in 2.59.10.71 so context, stages, retries, claims, results, timestamps, and scheduling priority all belong to the new request.

= 2.59.10.71 =
* Reset `source_context` from the incoming request when a terminal canonical queue row is reused, so a later full-site warm plan cannot inherit stale targeted/import/LCP priority from an earlier lifecycle.
* Preserve existing source context and stage unions while a row is pending or processing, allowing active full-site and targeted requests to continue coalescing without losing ownership or diagnostics.
* Keep terminal-row reuse internally consistent by resetting `source_context`, `source_contexts`, stages, retries, claims, and result state as one new queue lifecycle.
* Prevent reused full-site rows from being retained by targeted-row preservation rules or reported as targeted Automation Worker work after their previous request already completed.

= 2.59.10.70 =
* Make canonical warm-queue stage and source-context merges idempotent so repeated updates/import hooks do not append duplicate metadata to the same URL row.
* Keep `required_stages` in one bounded canonical set during atomic queue upserts, preventing varchar growth, truncation, or failed coalescing after large WooCommerce/WP All Import bursts.
* Keep `source_contexts` as a unique bounded token set during atomic queue upserts while preserving every distinct trigger context needed by diagnostics and pipeline planning.
* Upgrade queue schema metadata to version 11 and compact duplicate stage/context values already stored by earlier canonical-queue releases without deleting URLs, claims, progress, retries, or completed stages.
* Apply the same set-union semantics to legacy CSS, LCP, and Varnish row consolidation so upgrades cannot recreate duplicate canonical metadata.

= 2.59.10.69 =
* Preserve the active full-site background warm plan when dashboard or WP-CLI foreground work preempts cron, instead of converting the resumed state into a targeted queue recovery workload.
* Resume the same full-site discovery cursor, Scheduled / Cron warm limit, selected URL count, queued canonical rows, and remaining discovery batches after foreground Pause, Cancel, completion, interruption, or lease expiry.
* Resume a full-site plan even when its current queue batch finished before foreground ownership was released but additional cursor batches still remain to be discovered.
* Keep mixed LCP, targeted, CSS, and external-cache stages inside the preserved full-site worker without allowing deferred LCP recovery to overwrite the full-site state.
* Respect Background warm pages per minute after foreground release; a configured value of 0 leaves the preserved full-site plan paused rather than misreporting it as foreground-blocked or targeted work.
* Restore missing cron scheduling for the preserved plan through the normal worker-recovery path without clearing canonical queue rows or resetting progress counters.

= 2.59.10.68 =
* Treat a page-pipeline URL lock collision as retryable deferred work instead of a successful skip, preventing pending CSS, LCP, Varnish, or LiteSpeed stages from being lost when a visit, cron worker, dashboard request, or WP-CLI process already owns the URL.
* Preserve a dashboard URL for resume when the REST request returns a coalesced lock result, including non-2xx REST responses, and display the LCP stage in the unified per-page result summary.
* Add bounded URL-lock retries to direct WP-CLI warm commands and the dashboard homepage HTML/HTML+CSS actions so transient visit/worker overlap does not become a false success or immediate terminal failure.
* Give the dashboard homepage warm actions the same UI foreground ownership, heartbeat, cooperative cron preemption, and release behavior as the full dashboard warm-up flow.
* Recover expired UI/WP-CLI foreground leases during normal status reads so a stale browser or CLI session cannot remain displayed as an active Automation Worker blocker until a later cron tick.
* Include terminal skipped canonical rows in the existing bounded processed-row retention cleanup so long-running targeted automation does not retain them indefinitely.
* Complete the cross-path regression audit for cron, dashboard, WP-CLI, visit integration, canonical stages, Varnish capability gating, scheduled/full-site limit ownership, and update/import coalescing without changing their established configuration ownership.

= 2.59.10.67 =
* Apply retry budgets and backoff per failing canonical stage so earlier HTML/CSS attempts cannot exhaust later Varnish or LiteSpeed retries.
* Reset the effective retry counter when an attempt completes a new stage, while preserving completed-stage metadata so the next attempt resumes only the remaining work.
* Represent LCP refresh explicitly in the common pipeline and mark it complete with the successful HTML regeneration instead of repeating it after an unrelated external-cache failure.
* Record terminal partial outcomes when HTML or another required stage completed but a later non-retryable stage failed; expose partial and failed lifecycle counts separately.
* Recover processing rows with expired leases, missing lease timestamps, or abandoned claims while preserving completed stages and bounded stage state.
* Preserve a newer rerun request during stale-lease recovery by resetting obsolete completion state only for that rerun instead of silently discarding the request.
* Keep dependency-skipped stages pending for the next attempt while treating documented ineligible or disabled stages as completed/skipped outcomes.

= 2.59.10.66 =
* Redesign Automation Worker status around the active UI, WP-CLI, or cron owner instead of presenting the background cron worker as the only executor.
* Report unique queued URLs separately from canonical HTML, CSS, LCP, Varnish, and LiteSpeed stage operations so external-cache stages no longer inflate the page count.
* Distinguish running scheduled warm-up, running targeted work, active UI/WP-CLI warm-up, scheduled full-site or targeted work, retry waiting, configuration pause, recovery, and attention-required states.
* Show the current owner, URL, pipeline stage, next retry or worker run, and full-site selected/limit counts when applicable.
* Present a paused dashboard warm-up as a resumable session without treating it as an active blocker for background automation.

= 2.59.10.65 =
* Moved Varnish-specific connection, secret state, capability, runtime, queue, performance, ESI, recent-result, and endpoint proof diagnostics into a dedicated Varnish Diagnostics accordion at the end of the Varnish Cache card.
* Removed the duplicate Varnish technical diagnostics section from Advanced Diagnostics while retaining general cross-system diagnostics there.

= 2.59.10.64 =
* Restore the explicit Varnish Cache on/off switch as a canonical setting, with ON opening the integration accordion and OFF closing it while preserving saved endpoints and secrets.
* Separate Varnish enablement from connection completeness so administrators can configure the integration before a working endpoint exists, while runtime invalidation, refill, ESI, shared-cache delivery, performance measurement, and Flush All participation require both states.
* Preserve upgrade behavior by enabling the restored switch for installations whose current connection marker already made Varnish active, while retaining an explicitly saved legacy OFF state.
* Replace the compact generic accordion header with the standard integration-card hierarchy so the Varnish title and description match the size, weight, color, and spacing used by Automation & Scheduling.
* Keep Also flush Varnish Cache in the external/server cache layers card and preserve its saved value independently from the Varnish integration switch.

= 2.59.10.63 =
* Merge successful frontend cache MISS and stale-revalidation storage into the matching canonical warm row after the response has been released.
* Treat the canonical HTML stage as satisfied only when every active orig/WebP/AVIF HTML cache variant exists for the URL.
* Let PHP-served cache HIT requests complete matching queued HTML work through a persistent-object-cache URL hint, avoiding a database lookup on ordinary hits and on hosts without a persistent object cache.
* Preserve active queue claims while a frontend visit contributes completed stages, and union those stages with the owning worker result instead of overwriting either source.
* Resume canonical rows from their stored completed-stage metadata so an already satisfied HTML stage can skip the duplicate loopback request and continue directly with pending Varnish or LiteSpeed work.
* Keep CSS bundle and LCP refresh requirements authoritative: pending CSS or LCP work still rebuilds the page through the common backend pipeline even when a previous visit created HTML.
* Complete HTML-only pending rows directly from the frontend visit and remove their low-cost pending URL hint without creating a foreground warm-up owner.

= 2.59.10.62 =
* Apply Scheduled / Cron warm limit only while selecting URLs for an explicit full-site background plan; targeted work from updates, imports, LCP refreshes, media discovery, CSS, and external-cache stages no longer consumes or expands that limit.
* Track full-site workload type, selected URL count, and discovery completion separately from total queue processing so a mixed canonical queue can finish every targeted URL while the full-site planner remains bounded.
* Preserve existing targeted canonical rows when a full-site after-flush or after-cleanup plan starts instead of clearing pending update/import work.
* Stop increasing the configured full-site limit when LCP work or canonical redirects are added; redirect targets replace their selected source URL without changing the selection cap.
* Report Scheduled / Cron warm limit independently from the active workload limit so targeted queues correctly expose a runtime limit of zero rather than falling back to the full-site setting.
* Add explicit shared-pipeline execution profiles: gentle rate-limited cron work, unthrottled dashboard foreground work, extended WP-CLI foreground work, and bounded single-request visit/revalidation work.
* Give cron, dashboard, WP-CLI, and visit profiles separate per-page operation budgets while preserving identical URL eligibility, locking, stage ordering, capability checks, and completion semantics.
* Mark dashboard homepage warm actions as UI-profile execution and retain cooperative UI/WP-CLI ownership over the lower-priority cron worker.

= 2.59.10.61 =
* Coalesce repeated post, WooCommerce object, term-update, and term-assignment hooks within the current request before resolving affected URLs.
* Use the official WP All Import start, per-record, and completion actions to accumulate changed post and term identifiers across import requests and release one persistent affected-URL planning batch when the import finishes.
* Keep the persistent import batch heartbeat current during long-running imports, flush bounded in-memory chunks every 100 imported records, and recover an interrupted import batch after its lease becomes stale.
* Resolve persistent affected changes in bounded 250-post/250-term planner chunks, deduplicate purge and warm URLs before any queue insert, and preserve the canonical one-row-per-URL queue contract.
* Preserve immediate post-deletion handling while batching update and taxonomy churn whose final state is available at request/import completion.
* Preserve the Warm affected pages after save setting and per-post cooldown while ensuring purge requirements are retained even when a URL is not eligible for warm-up.
* Retry a persisted affected batch when canonical queue persistence fails instead of discarding the update work after the page-cache purge.
* Debounce the affected-batch cron event, remove it during deactivation, and include the non-autoloaded batch option in normal plugin-data cleanup.

= 2.59.10.60 =
* Store background page work as one canonical `page_warm` queue row per URL and merge HTML, CSS bundle, LCP refresh, and Varnish requirements into bounded stage metadata.
* Route new `css_bundle`, `lcp_refresh`, and large `varnish_invalidate` enqueue requests through the canonical URL row instead of creating competing top-level queue rows.
* Consolidate existing pending/error legacy queue rows during the permanent schema upgrade while leaving active processing leases untouched until they finish.
* Preserve every contributing source context on the canonical row so affected saves, imports, media discovery, LCP observations, refresh-ahead, and external-cache work remain diagnosable after coalescing.
* Make the shared worker derive force-refresh, CSS, LCP, Varnish, LiteSpeed, and targeted behavior from the canonical stage/context metadata rather than the legacy job type alone.
* Persist completed canonical stages with the terminal queue result and reset them when a newer request arrives during processing.
* Preserve canonical stage requirements when a non-canonical URL is replaced by its verified local redirect target.
* Report Varnish queue activity from the canonical Varnish stage while retaining compatibility with any legacy processing invalidation lease that is still draining.
* Prevent legacy queue rows from being removed unless their canonical merge succeeds, and finalize the queue schema version only after consolidation completes.

= 2.59.10.59 =
* Route every dashboard crawler URL through the same complete backend page pipeline already used by cron, WP-CLI, targeted work, and warm-after-flush execution.
* Replace the dashboard JavaScript HTML/CSS/Varnish/LiteSpeed stage machine with one bounded REST request per URL; JavaScript now manages only job progress, pause/resume/cancel, logs, and counters.
* Renew and verify the dashboard foreground lease from inside the backend pipeline before and after HTML, CSS, Varnish, and LiteSpeed work so a newer UI or WP-CLI owner can preempt cooperatively.
* Keep per-URL locking, eligibility checks, retry classification, external-cache capability planning, variant selection, and completion decisions inside the common backend contract.
* Remove the obsolete manual-warm page-stage REST route, staged engine entry point, and one-bucket Varnish/LiteSpeed dashboard refill adapters.
* Make dashboard completion lines derive from the returned common pipeline stage summary instead of reconstructing external-cache state in the browser.
* Preserve the image conversion/media queue as a separate attachment-and-file pipeline; media-triggered affected URLs continue to join the shared page warm queue.

= 2.59.10.58 =
* Add one foreground warm-up ownership record shared by dashboard and direct WP-CLI warm commands, including source, status, generation, heartbeat, lease expiry, current stage, and current URL.
* Apply the agreed priority model: the newest dashboard or WP-CLI warm-up owns foreground execution, while the background cron worker always yields.
* Make ownership transfer cooperative: the replaced dashboard or WP-CLI worker stops at its next URL/stage heartbeat instead of continuing with an obsolete token or producing repeated failures.
* Preserve the existing cron/automation queue and progress when foreground work starts; foreground priority no longer calls the destructive cron stop path.
* Make dashboard Cancel end the foreground session and immediately resume pending background automation instead of storing a paused owner that blocks cron indefinitely.
* Make an explicit paused dashboard session retain its resumable state while releasing execution ownership so background automation may continue.
* Recover expired foreground leases automatically and reattach pending LCP, targeted page-warm, Varnish, and shared queue work to the background worker.
* Give direct WP-CLI warm commands a renewable foreground lease and release it at command shutdown; a newer dashboard or WP-CLI owner causes the older CLI pipeline to yield cleanly.
* Report Automation Worker states as Yielding to UI or Yielding to WP-CLI and expose the active foreground owner in the status payload.

= 2.59.10.57 =
* Remove the redundant Cron Warm Up master switch from Automation & Scheduling and canonical settings while retaining it as a legacy migration-only input.
* Preserve upgrade behavior by enabling each autonomous full-site trigger only when both the previous master switch and that trigger were enabled.
* Merge REST setting patches into the canonical migrated settings so the first post-upgrade trigger change is applied instead of being overridden by the legacy master value.
* Make Warm full site after Scheduled Cleanup and Warm full site after Flush All Cache independent triggers governed by the selected Full-site warm-up sources, Scheduled / Cron warm limit, and background work rate.
* Move Stale While Revalidate into the former master-switch position and rename the shared rate control to Background warm pages per minute.
* Keep targeted work from saves, imports, LCP refreshes, media discovery, and external-cache refill independent from the full-site triggers while using the shared background rate.
* Stop settings saves from clearing or stopping existing targeted background work merely because the removed master switch was off.
* Update Varnish warm-after-flush and refresh-ahead policy to use the autonomous trigger and shared background worker availability.

= 2.59.10.56 =
* Complete the Varnish and shared-automation regression pass across fresh and legacy connection state, generic and contract-capable control paths, single and multi-endpoint capability intersection, expired proof, ESI fallback, queue recovery, and Flush All ownership.
* Make targeted affected-page refill consume the current Cron warm pages per minute setting on every worker tick instead of using a hidden five-page rate.
* Apply the same central work rate to async CSS bundle rebuilds and page-specific LCP refreshes.
* Persist targeted, CSS-bundle, and LCP queue rows as paused when Cron warm pages per minute is 0, avoid scheduling a page worker in that state, and resume through the shared recovery path after the rate is restored.
* Verify the Varnish card, external/server cache layer card, Automation & Scheduling ownership, and both bundled CWP templates through the release regression checks.

= 2.59.10.55 =
* Add a throttled request-lifecycle recovery check that reattaches orphaned shared queue rows and restores missing cron worker schedules.
* Recover expired queue leases and stale cron execution locks before resuming automation work.
* Serialize cron schedule creation through a database-backed scheduler lock so concurrent requests cannot create duplicate workers.
* Add shared automation-worker health to the Automation & Scheduling card with pending, processing, next-run, blocked, paused, recovered, and attention states.
* Preserve queued page work when the central Cron warm pages per minute limit is 0 and report that state as paused instead of discarding the queue.
* Keep Varnish queue details in Advanced Diagnostics and preserve the simplified Varnish card, central TTL ownership, and external/server cache Flush All ownership.
* Leave both CWP Varnish templates unchanged.

= 2.59.10.54 =
* Reduce the normal Varnish status to four user-facing results: connection, automatic cache clearing, full-site cache clearing, and overall measured performance.
* Remove ESI, transport, contract, endpoint-proof, purge-method, runtime-strategy, queue, and raw performance terminology from the normal Varnish status.
* Replace technical connection and invalidation warnings in the normal card with short corrective guidance while preserving the full underlying failure evidence in diagnostics.
* Add a dedicated Varnish technical diagnostics panel under Advanced Diagnostics with connection policy, shared-cache lifetime, endpoint registry state, effective capabilities, runtime plans, queue state, operation metrics, and bounded performance results.
* Add per-endpoint diagnostic details for adapter, reachability, exact-invalidation proof, current capabilities, test time, proof expiry, and the latest failure.
* Summarize performance in the normal card from current second-pass latency and visible HIT evidence without exposing the raw measurement matrix.
* Preserve automatic runtime behavior, ESI policy, capability proofs, settings ownership, REST behavior, queues, generated drop-ins, and both CWP templates unchanged.

= 2.59.10.53 =
* Remove the obsolete hidden esiEnabled setting from canonical defaults, validation, persistence-change detection, runtime rendering, REST schemas, dashboard state, lifecycle state, and performance-profile ownership.
* Make a configured Varnish connection the only eligibility prerequisite for ESI capability testing; no user-facing or hidden enable switch remains.
* Activate public ESI automatically only while the current end-to-end public composition proof is effective across the configured topology.
* Activate private/session ESI automatically only after verified session isolation, shared-parent reuse, private-fragment no-store behavior, and onerror containment.
* Activate the WooCommerce classic mini-cart ESI adapter automatically only after the private transport proof also verifies the WooCommerce cookie/session carrier.
* Preserve inline fallback rendering whenever public, private, or WooCommerce proof is absent, expired, invalidated by configuration changes, or incomplete across a multi-endpoint topology.
* Keep Test Varnish as the behavioral source of ESI capability state and preserve the standalone CWP templates unchanged.
* Canonicalize legacy settings by dropping esiEnabled during normal settings sanitization without adding one-off migration or cleanup code.

= 2.59.10.52 =
* Replace the remaining hidden shared-cache and Varnish control enable flags with one internal, migration-safe Varnish connection state.
* Activate Varnish runtime automatically after a dedicated connection save, a detected/configured custom endpoint, a legacy active integration, or an isolated capability probe.
* Keep a fresh installation inactive when it contains only the untouched default endpoint, preventing default placeholders from creating shared-cache headers or endpoint registry profiles.
* Make targeted invalidation, TTL fallback, affected-page refill, site warm-up participation, HTML-variant refill, stale refresh, refresh-ahead gating, performance measurement, diagnostics, Flush All, REST, and WP-CLI use the same derived connection state.
* Preserve fail-closed capability planning: configured connections use only current verified operations and fall back automatically to bounded TTL expiry when exact invalidation is unavailable.
* Migrate the previous enable values into `varnishConnectionConfigured`, remove the obsolete fields from canonical settings, REST schemas, CLI normalization, performance profiles, and dashboard state, and keep the legacy values readable only during migration.
* Add a write-only connection intent to the dedicated Varnish Save action so the default local endpoint can be activated intentionally without restoring a user-facing enable switch.
* Prevent inactive default endpoints from seeding the per-endpoint capability registry and keep isolated Test Varnish probes temporary.
* Route WP-CLI Varnish state checks through the main UltraCache runtime helper and preserve the external/server cache card as the owner of Flush All Varnish inclusion.

= 2.59.10.51 =
* Make Automation & Scheduling the single source of truth for Varnish page lifetime, stale window, warm-up cadence, and refresh-ahead activation.
* Derive the managed Varnish HTML TTL from Fresh TTL and the stale-refresh window from Fresh TTL, Max stale window, and the central Stale While Revalidate switch.
* Derive the automatic-expiry fallback from the central Fresh TTL with a conservative internal ten-minute maximum instead of storing a second user-controlled Varnish TTL.
* Remove the obsolete Varnish-specific TTL, stale, targeted-refill, site-warm, refresh-ahead, threshold, scan-limit, and pinned-URL settings from canonical defaults, validation, REST schemas, CLI normalization, and dashboard JavaScript state.
* Automatically include verified Varnish in affected-page refill and every existing site warm-up pipeline instead of requiring separate Varnish switches.
* Activate Varnish refresh-ahead only when the central Cron Warm Up and Stale While Revalidate automation are active and the required soft-purge behavior is verified.
* Use Cron warm pages per minute as the bounded Varnish refresh-ahead work limit and keep the internal threshold policy automatic.
* Remove the unused Varnish refresh-ahead dashboard module and preserve the Varnish card as connection, test, measurement, manual action, and simple status only.
* Preserve the external/server cache layers card as the sole owner of whether Flush All Cache includes Varnish.
* Leave both CWP Varnish templates unchanged.

= 2.59.10.50 =
* Restore the previously approved Varnish Cache card title and description instead of exposing the internal shared-cache/control architecture in the dashboard heading.
* Remove the user-facing shared-cache delivery, managed invalidation, TTL-only, invalidation strategy, flush-scope, SWR, ESI, refill, Varnish warm-up, and refresh-ahead controls from the Varnish card.
* Keep the Varnish card focused on connection mode, endpoints, secret/token, timeout, Detect, Test, bounded performance measurement, one capability-aware manual flush action, and a compact status summary.
* Remove the separate entire-host flush button from the normal Varnish card; the remaining manual flush continues through the existing capability-driven runtime planner.
* Automatically keep shared-cache delivery and Varnish control enabled when a valid endpoint configuration is saved, avoiding hidden enable switches that could leave a configured integration inactive.
* Limit Varnish connection saves to connection-owned fields so the card no longer overwrites TTL, ESI, refill, warm-up, refresh, or scheduling values owned by other dashboard sections.
* Leave the existing Also flush Varnish Cache option in the external/server cache layers card as the sole control for including Varnish in Flush All Cache.
* Preserve all runtime planner, capability registry, canary, VCL contract, queue, measurement, CWP template, and stored-setting behavior outside this UI ownership cleanup.

= 2.59.10.49 =
* Add a bounded two-pass Varnish parent-cache performance snapshot for up to three trusted local URLs across the active original, WebP, and AVIF HTML variants, with a finite overall time budget and per-request timeout.
* Keep the performance snapshot diagnostic-only: it may warm the sampled objects but does not purge Varnish, modify cache settings, or automatically tune ESI, cart-fragments, grace, keep, or refresh-ahead behavior.
* Calculate second-pass HIT and cache-served rates only from visible cache-status evidence, and report signals-hidden instead of inferring a HIT rate when the host suppresses those signals.
* Record passive ESI render telemetry with bounded 1-in-32 sampling, including estimated public/private request volume, average and maximum render duration, average output size, and a rolling 24-hour window.
* Track WooCommerce classic mini-cart ESI traffic and render cost separately, while recording contained renderer errors without sampling so correctness failures remain visible.
* Add compact production counters for capability-planner runtime outcomes and selected invalidation strategies without duplicating queue lifecycle state.
* Show parent-cache samples, observed HTML variants, private and WooCommerce ESI cost, invalidation outcome health, sampling details, and measurement-based recommendations in the Varnish dashboard.
* Invalidate stored performance measurements when shared-cache delivery or the active HTML variant policy changes, and remove the snapshot during plugin-data cleanup and uninstall.
* Preserve the standalone CWP templates and the optional VCL contract byte-for-byte; this release changes plugin-side measurement and diagnostics only.

= 2.59.10.48 =
* Add an optional authenticated UltraCache CWP VCL v2 contract while preserving the standalone generic exact-PURGE path for sites without UltraCache or without the advanced contract enabled.
* Keep the advanced contract disabled by default and require explicit template enablement plus a matching random HTTP control token before accepting structured operations.
* Add versioned capability responses for exact PURGE, object-side exact and batch BAN, HTML-only BAN, entire-host BAN, ESI transport, and canonical HTML variants.
* Route verified CWP contract endpoints through object metadata BAN expressions so exact, batch, HTML, and host invalidation are ban-lurker friendly.
* Probe the contract independently on every configured HTTP endpoint and bind the adapter and capabilities to the existing isolated exact-invalidation canary proof.
* Preserve generic HTTP PURGE/BAN and admin-socket adapters when the versioned contract is missing, disabled, unauthenticated, or unsupported.
* Fall back immediately to the standalone generic exact-PURGE path when an authenticated contract exact-PURGE request fails, while never converting site-wide BAN operations into an unsafe PURGE / fallback.
* Require a bounded 32-128 character ASCII letter/number/underscore/hyphen token before the plugin attempts the optional contract, and preserve non-default frontend ports in exact invalidation requests.
* Confirm the VCL ban() boolean result before reporting a structured BAN operation as accepted.
* Invalidate a stored contract profile when the endpoint later reports that the contract is disabled, missing, or no longer authenticated.
* Do not advertise soft purge, SWR, or origin revalidation from the standalone CWP template because the per-domain template must not require an unverified purge VMOD import.
* Show the number of endpoints using the authenticated VCL contract in the Varnish dashboard and clarify that the HTTP control key must match the optional template token.

= 2.59.10.47 =
* Upgrade both bundled Control Web Panel Varnish templates to standalone WordPress/WooCommerce v2 templates that remain fully functional without UltraCache.
* Replace unanchored domain regex matching with exact CWP host comparison after removing an optional numeric Host port.
* Add a local-direct, front-proxy-aware exact PURGE receiver that invalidates the requested cache key and all of its Vary variants without requiring an UltraCache-specific header or token.
* Canonicalize cacheable HTML Accept headers into AVIF, WebP, or original buckets while respecting explicit q=0 exclusions, preventing equivalent browser Accept strings from fragmenting the Varnish object set.
* Store normalized object host and URL metadata on cacheable responses for future ban-lurker-friendly obj.http invalidation, and remove those internal headers before client delivery.
* Keep grace and keep as independent standalone policies, using ten minutes of grace for refresh/origin protection and a smaller five-minute keep window for conditional revalidation.
* Preserve the conservative WooCommerce PASS policy in the global-safe template and the existing explicit request/response approval handshake in the ESI template.

= 2.59.10.46 =
* Add a capability-driven Varnish runtime planner that selects targeted invalidation, site flush, queue processing, refill, and site-warm behavior only from current per-endpoint proofs.
* Normalize every Varnish runtime result as complete, partial, degraded, unsupported, or failed, and expose the selected strategy, fallback, execution state, and sanitized plan to REST, diagnostics, dashboard, action queue, and WP-CLI callers.
* Use verified exact PURGE/BAN for targeted operations; when soft purge is configured but not behavior-verified, fall back to verified hard invalidation and report the result as degraded instead of claiming soft-purge success.
* Replace unsupported site-wide assumptions with a bounded known-local-URL fallback when exact invalidation is verified, while explicitly retaining unknown or uncrawled objects for TTL expiry.
* Queue large known-URL fallback sets persistently and bound the synchronous fallback to 20 URLs when the queue is unavailable, leaving the remainder to the configured TTL-only window rather than issuing thousands of requests in one action.
* Prioritize persistent Varnish invalidation rows ahead of site warming so a delayed fallback operation cannot purge objects that the same warm pipeline has already refreshed.
* Re-evaluate capability proofs when queued invalidations run; expired or incomplete proof moves those rows to a degraded TTL-expiry result without sending unverified PURGE/BAN requests or scheduling a misleading refill.
* Gate Varnish site warm/refill work on the current targeted runtime plan, while allowing the isolated capability canary to exercise a configured transport before proof exists.
* Keep direct HTML-only and entire-host transport calls restricted to bounded topology tests; production site operations now pass through the runtime planner.

= 2.59.10.45 =
* Run a separate mutable generation canary through every configured HTTP Varnish endpoint instead of assigning one aggregate result to the full topology.
* Route canary warm-up, cache-retention proof, exact PURGE/BAN, post-invalidation verification, and refill verification through the same endpoint with the original frontend Host header.
* Store exact-invalidation proof only on the endpoint that independently changed its WordPress-served canary from generation 1 to generation 2; clear only the failing endpoint profile when its latest proof fails.
* Report working, partial-topology, and endpoint-proofs-failed results with per-endpoint reachability, transport acceptance, shared-cache evidence, and bounded failure details.
* Keep runtime invalidation disabled unless every configured endpoint has a current exact-invalidation proof, while preserving static-route-only evidence without treating it as WordPress page coverage.
* Synchronize the complete per-endpoint result set into the capability registry before removing verbose probe steps from the persisted diagnostic payload.
* Execute Varnish behavior tests in the main UltraCache class scope so private integration helpers remain callable, while retaining the previous test-runner class as a compatibility facade.
* Keep multi-endpoint ESI inactive until a separate per-endpoint ESI behavior probe verifies every active node.

= 2.59.10.44 =
* Add a non-autoloaded, bounded Varnish capability registry with one configuration-bound profile per configured endpoint.
* Track endpoint adapter, reachability evidence, exact PURGE/BAN, batch BAN, HTML-only and host flush, soft purge, origin revalidation, SWR, public/private ESI, HTML variants, proof timestamps, source, status, and bounded failure details.
* Evaluate managed capabilities as the intersection of every active endpoint so mixed or partially verified topologies cannot be reported as fully managed.
* Start each newly registered HTTP endpoint without inherited capability assumptions; each endpoint receives capability state only from its own current proof or an explicit native transport contract.
* Keep native Varnish admin BAN contracts per endpoint while maintaining separate reachability evidence and non-expiring native capability contracts.
* Synchronize Test Varnish results into endpoint profiles and return a truthful mixed-topology result when one aggregate canary cannot independently prove multiple HTTP endpoints.
* Gate exact invalidation, site-wide scopes, soft purge, SWR, refresh ahead, and ESI through current per-endpoint capability intersection.
* Expose the endpoint capability matrix through dashboard diagnostics and remove its option during plugin-data cleanup and uninstall.

= 2.59.10.43 =
* Separate standard shared-cache HTML delivery from managed Varnish control, allowing portable s-maxage delivery even when no PURGE/BAN endpoint is configured or verified.
* Add a dedicated shared-cache switch and a bounded TTL-expiry-only value for hosts where invalidation is unavailable, incomplete, or no longer behavior-verified.
* Preserve existing Varnish-enabled installations by treating the new shared-cache delivery switch as enabled until the new setting is explicitly saved.
* Use the normal page-cache TTL only when both exact URL and site-wide invalidation coverage are available; exact-only HTTP control continues to accelerate targeted invalidation while shared delivery remains on the shorter TTL.
* Keep ESI, stale-while-revalidate, refill, and refresh-ahead dependent on shared delivery plus the required verified Varnish capabilities.
* Carry managed and TTL-only lifetimes separately into the PHP engine and generated advanced-cache.php, and automatically downgrade the drop-in when a time-bounded HTTP capability proof expires.
* Refresh generated page-cache runtime artifacts after Varnish canary capability results change, while keeping Apache Static HTML Delivery on the conservative TTL for time-bounded HTTP proofs.
* Expose shared-cache delivery mode, effective TTL, control verification, and proof status in dashboard diagnostics and the reorganized Shared Cache & Varnish Control card.

= 2.59.10.42 =
* Add isolated Varnish generation canaries below uploads/ultracache/varnishtest, with WordPress path, query fallback, and direct-upload route probes while bypassing UltraCache page cache.
* Verify managed HTTP exact-URL invalidation by retaining generation 1, mutating the same canary to generation 2, invalidating the exact URL, and requiring the new generation to appear and remain stable after refill.
* Treat direct-upload-only proof as static-cache evidence rather than authorization for managed WordPress page invalidation, and expire HTTP behavior proofs after seven days.
* Keep Varnish discovery results as unsaved candidates until Test Varnish proves behavior, and distinguish transport acceptance from public invalidation verification.
* Gate synchronous and queued HTTP runtime invalidation on the current canary proof; unverified transports fall back to cache TTL expiry instead of reporting successful purge behavior.
* Stop treating generic HTTP PURGE or BAN as portable HTML-only or entire-host flush contracts; keep site-wide actions unavailable until native admin BAN or an independent topology proof supports the requested scope.
* Route both existing Varnish test REST actions through the same exact-URL canary test and leave the bundled CWP Varnish templates unchanged.

= 2.59.10.41 =
* Moved Image conversion test and Check test below Image compression level in the adjacent media-settings column.
* Aligned the Media Library Replacement heading and overview with the Convert new uploads settings-row design.
* Preserved all existing conversion-test and Media Library Replacement actions, guards, jobs, and test behavior.

= 2.59.10.40 =
* Add a Media Library Replacement workflow title and concise overview above the existing four primary actions.
* Rename the primary workflow buttons to Prepare Replacement, Apply Replacement, Verify Replacement, and Delete Original Files, including clearer running, resume, retry, and completion labels.
* Add a short explanation below each primary action while preserving the existing workflow order, handlers, guards, resumable jobs, status logic, and advanced recovery controls.

= 2.59.10.39 =
* Fix the Help FAQ CWP Varnish template downloads by exposing dashboard runtime data before the reusable UI module initializes, so both bundled `.tpl` buttons are rendered and downloadable.
* Remove the redundant post-install informational box and add Delay non-critical/local JS as step 2 in the PageSpeed guidance, with the existing selective-options warning moved to step 3.
* Update the Aggressive profile Delayed JS auto-start controls to use Mouse move and Scroll event triggers with a 2 second fallback timer.

= 2.59.10.38 =
* Simplify Detect Varnish Configuration to one public homepage probe: a portable Varnish response header is sufficient to confirm that the site is behind Varnish.
* Test the bounded configured, loopback, local-address, server-hostname, and reverse-DNS HTTP candidates directly with PURGE first and BAN second, then stop at the first accepted Varnish response and save its endpoint and method automatically.
* Remove temporary discovery files, signed probe URLs, warm-up loops, HIT-to-MISS-to-HIT verification, admin-socket probing, verbose attempt payloads, and related discovery-only cleanup. The existing Test Varnish behavior test remains unchanged.
* Keep the unsaved-settings reminder only for manual field changes.

= 2.59.10.37 =
* Make behavior-verified Varnish discovery apply and save the detected HTTP endpoint, method, timeout, invalidation strategy, and flush scope immediately, so the working configuration does not depend on a second manual save action.
* Return only the bounded actionable discovery result to REST instead of provider response bodies and verbose probe attempts, preventing successful detection from being lost before the dashboard can update.
* Update the Varnish form and saved-settings reference from the verified result so Test Varnish is available immediately. Manual field changes continue to show the existing Save Varnish Settings reminder.

= 2.59.10.36 =
* Keep every Varnish discovery result JSON-serializable by stripping invalid UTF-8 from provider responses, error messages, array keys, and nested result values before REST output.
* Truncate invalidation-response summaries by UTF-8 characters instead of raw bytes, preventing multilingual WordPress HTML from being cut inside a multibyte character and causing HTTP 200 responses with an empty body.
* Convert unexpected WP_Error, object, resource, and non-finite numeric values in Varnish diagnostic results into bounded JSON-safe representations instead of allowing REST serialization to fail silently.

= 2.59.10.35 =
* Add Detect Varnish Configuration to test a bounded set of configured, loopback, local-address, server-hostname, and reverse-DNS candidates on common Varnish ports without scanning arbitrary hosts.
* Verify HTTP PURGE and BAN candidates against isolated short-lived cacheable probe objects, requiring observable HIT to MISS/STALE to HIT behavior before filling the Varnish connection fields. Detect Varnish admin sockets and authenticated HTTP listeners when their secret or control key must be supplied separately.
* Fill detected settings without saving them, show an explicit unsaved-settings reminder, and block Detect, Test Varnish, and flush actions until Save Varnish Settings commits the current fields.
* Accept successful HTML synthetic invalidation responses only when a 2xx response includes portable Varnish evidence and an invalidation confirmation, including managed-host responses such as HTTP 200 Purged with X-Varnish.

= 2.59.10.34 =
* Make a saved per-URL Manual LCP selector immediately replace competing automatic winners with authoritative locked mobile, tablet, and desktop mappings; diagnostics now show the manual source and selector immediately instead of the previous automatic candidate, and repair already-saved selector scopes when their URL details are opened.

= 2.59.10.33 =
* Prevent the Aggressive performance profile from enabling Delay non-critical/local JS.

= 2.59.10.32 =
* Autosave Enable ESI fragment framework, Refill affected pages after targeted invalidation, Warm Varnish with site warm-up, and Refresh hot pages before expiry immediately when their switches change.
* Save each switch through the existing partial settings endpoint as an isolated boolean patch, so unsaved Varnish endpoints, secrets, timeout, dropdowns, thresholds, and pinned URLs are never included in the autosave request.
* Keep Save Varnish Settings for the remaining connection and advanced fields, and preserve the existing optimistic dashboard state, serialized save queue, server canonical response, success/error toast, and infrastructure-lock behavior.
* No cache runtime, VCL, ESI capability, queue, database, or server-template contract changes.

= 2.59.10.31 =
* Build the private ESI cookie carrier from the explicit built-in allowlist instead of copying the complete browser Cookie header. The suggested CWP templates and Help VCL transport only `esi_session`, `woocommerce_items_in_cart`, `woocommerce_cart_hash`, and one `wp_woocommerce_session_*` cookie.
* Restore private cookies only for signed UltraCache fragment endpoints carrying `esi_scope=private`; unrelated same-origin ESI includes cannot opt into the private/session carrier by adding the scope parameter alone.
* Mark private ESI subrequests as `X-Cache: PASS` before `return (pass)` so frontend diagnostics reflect their actual delivery mode.
* Apply the same transport hardening to the recommended CWP template, conservative global-safe template, and copyable Help VCL. Keep the existing CWP `%domain%` host-placeholder matching unchanged because its expansion is controlled by the active CWP template contract.
* Preserve the 20-second frontend ESI probe timeout, request opt-in handshake, canonical manual-warm redirect handling, and ESI capability contract; this VCL-only hardening requires template replacement/rebuild but no new plugin-side capability contract.

= 2.59.10.30 =
* Make the Public ESI, Private ESI, and Woo mini-cart ESI dashboard rows reflect the current stored Test Varnish verification proof instead of the separate runtime `effective` gate. A fully verified proof can no longer appear as `Fallback only` or `Test required`, and a successful ESI message is no longer rendered as a warning.
* Follow at most one HTTP 301/302/303/307/308 redirect during staged manual Varnish refill only when `Location` resolves to a verified local frontend URL. The canonical target is invalidated before the first refill bucket, then reused by the remaining Varnish and LiteSpeed stages.
* Reject external, malformed, and redirect-chain destinations without following them, and expose the HTTP code plus redirect destination in the returned warm-up error instead of the generic `Varnish ORIG bucket refill failed` message.
* Preserve the independent 20-second frontend ESI probe timeout, the request-opt-in handshake, and the existing ESI capability contract; a new Test Varnish run is not required solely for this update.

= 2.59.10.29 =
* Add the request-side `ultracache_esi_optin=1` browser handshake used by the recommended CWP VCL. The host-only session cookie is created only on pages that actually render the verified classic WooCommerce mini-cart ESI adapter; it is stripped by Varnish before origin/cache lookup.
* Restrict `X-UltraCache-ESI-Shared-Parent: 1` approval to cached parents whose trusted ESI metadata contains the exact `woocommerce-mini-cart` private fragment. Generic private fragments can no longer opt WooCommerce visitors into a shared parent.
* Upgrade atomic `.esi` sidecars to version 4 with a bounded `woocommerceMiniCart` flag, preserving older sidecars as valid ESI parents but never as Woo shared-parent approvals.
* Update the private/Woo Test Varnish probe to send the request opt-in marker, keep the independent 20-second frontend ESI timeout, bundle the matching CWP template, and update Help → FAQ plus the copyable VCL snippet.
* Protect the new marker helper from UltraCache defer/delay transforms. No visitor identifier, cart value, session ID, or persistent expiry is stored in the marker cookie.

= 2.59.10.28 =
* Add the explicit `X-UltraCache-ESI-Shared-Parent: 1` response handshake used by the unified Varnish template. Anonymous cacheable ESI parents containing private fragments may be approved for later WooCommerce-cookie HIT reuse; candidate cache misses retain their real cookies and remain uncacheable.
* Approve the signed private/session capability-probe parent so Test Varnish can verify shared-parent reuse, isolated no-store private fragments, and WooCommerce cookie transport against the unified template.
* Decouple frontend ESI composition requests from the Varnish admin endpoint timeout. Public/private/Woo probes now use a bounded independent 20-second timeout while admin socket operations retain their configured limit.
* Bundle both the recommended Control Web Panel handshake template and a conservative global-safe/PASS alternative, and update Help → FAQ plus the generic copyable VCL suggestion to describe the approval contract and both downloads.
* Bump the ESI capability contract so existing proofs require one new Test Varnish run after installing the matching plugin/template pair.

= 2.59.10.27 =
* Replace the bundled Control Web Panel Varnish template with the global-safe variant. Standard WooCommerce cart and session cookies remain on top-level requests so mixed CWP servers keep normal PASS behavior and shops without UltraCache cannot lose cart state.
* Keep public ESI and private/session transport plumbing in the shared template while making the classic WooCommerce mini-cart shared-parent optimization an explicit per-domain opt-in instead of a global behavior.
* Make both the bundled CWP template and the generic copyable Help VCL snippet global-safe, and explain the WooCommerce PASS guarantee plus the separate per-domain mini-cart ESI requirement.
* No cache engine, ESI capability, queue, database, or automatic server-configuration runtime changes.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/admin/js/ui.js`, and `resources/varnish/control-web-panel/ultracache-wordpress-woocommerce-esi.tpl`.

= 2.59.10.26 =
* Expand Help → FAQ with the actual public ESI, private/session ESI, and WooCommerce classic mini-cart transport requirements, plus the meaning of Verified, VCL update required, and Fallback only after Test Varnish.
* Add “I need a ready solution for my Control Web Panel (CWP) server.” with a clearly labelled Suggested ready-to-use configuration and direct download button.
* Bundle `resources/varnish/control-web-panel/ultracache-wordpress-woocommerce-esi.tpl`, preserving the CWP `%domain%`, `%backend_domain%`, `%proxy_ip%`, and `%proxy_port%` placeholders and including the tested WordPress/WooCommerce/public/private ESI rules.
* Expose the bundled same-origin template URL through the existing dashboard bootstrap configuration. No Varnish file is installed or changed automatically, and no cache, ESI capability, or queue runtime contract changes.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/admin/class-admin-trait.php`, `includes/admin/js/ui.js`, and new `resources/varnish/control-web-panel/ultracache-wordpress-woocommerce-esi.tpl`.

= 2.59.10.25 =
* Fix the WooCommerce private ESI transport proof so its diagnostic endpoint reads the original bounded backend `Cookie` header. WooCommerce normalization can no longer hide `woocommerce_items_in_cart` or `woocommerce_cart_hash` after Varnish has transported them correctly.
* Treat `time_budget` and `memory_budget` warm-up pauses as cooperative queue yields instead of failed attempts. The owned row returns to `pending`, its claim attempt is restored, and the existing cron worker continues it on the next tick without reaching the terminal retry limit.
* Keep normal HTTP, origin, cache-write, and integration failures on the existing retry/error path. No queue migration, VCL change, ESI contract change, or new background subsystem is introduced.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/esi/class-esi-endpoint-trait.php`, `includes/warmup/class-warm-runner-trait.php`, and `includes/warmup/class-cron-warm-orchestrator-trait.php`.

= 2.59.10.24 =
* Correct the completed-test status classification for private ESI and the WooCommerce classic mini-cart adapter. When public ESI is verified but the private cookie transport is absent, both rows now report `VCL update required` instead of `Fallback only` or `Test required`.
* Stop presenting the lifetime `refillFailures` metric as an active operational failure. The Varnish refill row now reflects the current test or active shared warm queue state, while historical counters remain available only in metrics diagnostics.
* Add a bounded sample of current terminal Varnish queue rows to diagnostics. Each detail includes the failed invalidation/refill type, URL, stored error message, attempt count, failure time, and stopped-retry state.
* Replace the generic `require attention` queue warning with actionable output that identifies what failed and tells the administrator which invalidation/test or warm-up action to run again after fixing the reported transport/origin error.
* Keep the Varnish/ESI capability contracts and server VCL unchanged; this plugin-only bugfix does not require a new Test Varnish run when the existing proof is valid.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/integrations/varnish/class-varnish-queue-trait.php`, and `includes/admin/js/varnish.js`.

= 2.59.10.23 =
* Fix bounded Varnish test-result storage so capability fingerprints and contract versions are attached after large diagnostic steps are compacted. Successful public/private ESI proofs therefore remain authoritative instead of immediately appearing as `configuration-changed` or `Run test again`.
* Move the generic public/private-session ESI VCL snippet out of the Varnish operational settings and into Help → FAQ under “My Varnish server has only a basic setup. How can I enable ESI and WooCommerce mini-cart support?”.
* Label the snippet explicitly as a suggested generic configuration that is not installed automatically and must be merged into the existing VCL, reviewed, compiled, reloaded, and followed by Test Varnish.
* Keep the ESI capability contract unchanged from 2.59.10.22; this bugfix does not invalidate an otherwise complete stored proof.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/integrations/varnish/class-varnish-test-action-trait.php`, `includes/integrations/varnish/class-varnish-esi-capability-trait.php`, `includes/admin/js/varnish.js`, and `includes/admin/js/ui.js`.

= 2.59.10.22 =
* Harden composite ESI parent delivery by suppressing origin ETag/Last-Modified validators and conditional `304 Not Modified` responses for marked ESI parents in both the WordPress early-hit path and generated `advanced-cache.php`. Non-ESI cached HTML retains the existing GET/HEAD validator behavior.
* Add bodyless fragment `HEAD` handling that validates signed context and private transport without invoking render callbacks. Fragment responses remove validators and content length, while GET renderer failures and soft time-budget overruns are contained through the registered fallback and returned as no-store responses.
* Add `max_render_ms` per fragment, a 32-include/64 KiB generated-directive parent budget with bounded filters, and fragment-output neutralization for nested or untrusted ESI directives. Excess parent placeholders remain inline fallback HTML rather than creating additional subrequests.
* Bind deterministic fragment tokens and context hashes to the active WordPress locale, switch the fragment endpoint to that locale during rendering, and restore the original locale afterward so native translated output cannot share a fragment URL across locales.
* Bump the Varnish ESI capability contract so existing proofs require a new Test Varnish run after the hardening upgrade.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `templates/advanced-cache.php.tpl`, `includes/class-ultra-cache-engine.php`, `includes/esi/functions.php`, `includes/esi/class-esi-registry.php`, `includes/esi/class-esi-rendering-trait.php`, `includes/esi/class-esi-endpoint-trait.php`, `includes/engine/class-engine-storage-trait.php`, `includes/engine/class-engine-response-headers-trait.php`, and `includes/integrations/varnish/class-varnish-capability-fingerprint-trait.php`.

= 2.59.10.21 =
* Add an explicit WooCommerce classic mini-cart private ESI adapter with the template helpers `ultracache_get_woocommerce_esi_mini_cart_markup()` and `ultracache_render_woocommerce_esi_mini_cart()`, plus the `[ultracache_esi_mini_cart]` shortcode. The shared parent contains only a static generic cart link fallback; live cart HTML is rendered exclusively by the private no-store fragment.
* Register a strict WooCommerce cookie scope for `woocommerce_items_in_cart`, `woocommerce_cart_hash`, and the `wp_woocommerce_session_` prefix. Extend Test Varnish with WooCommerce-specific cookie transport markers and require that proof before the built-in adapter may emit a private ESI include.
* Keep WooCommerce cart/checkout/account whole-page bypass behavior unchanged and integrate the classic adapter with the standard `div.widget_shopping_cart_content` replacement selector. When the adapter is rendered, UltraCache preserves the native `wc-cart-fragments` runtime and disables its optional delay/suppress controls for that request so add/remove-cart events refresh the mini-cart.
* Keep the WooCommerce Mini-Cart block separate from the classic adapter; the block continues using its Store API/Interactivity runtime and is not rewritten automatically.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/class-ultra-cache-engine.php`, `includes/engine/class-engine-frontend-assets-trait.php`, `includes/esi/class-esi-endpoint-trait.php`, `includes/integrations/varnish/class-varnish-capability-fingerprint-trait.php`, `includes/integrations/varnish/class-varnish-esi-capability-trait.php`, `includes/admin/js/varnish.js`, and new `includes/integrations/woocommerce/class-woocommerce-esi-trait.php`, `includes/integrations/woocommerce/functions.php`, and `includes/integrations/woocommerce/index.php`.

= 2.59.10.20 =
* Add private ESI fragment scope with exact cookie-name/prefix allowlists, zero shared TTL, bounded cookie-header filtering, mandatory static anonymous parent fallback rendering, current-user revalidation inside the fragment request, and explicit rejection from the public-fragment purge API.
* Add generic `req_top` private-session VCL transport rules with top-request spoofed-header stripping, public-fragment cookie removal, private-subrequest pass/no-store enforcement, and a per-definition transport-policy gate so a verified probe cannot enable cookies that were not also declared in VCL.
* Extend Test Varnish with repeated same-session and cross-session private transport verification against one shared parent. The proof requires isolated session output, identical parent render identity, a new private-fragment render identity on every delivery, no shared fragment storage, and successful `onerror="continue"` error containment.
* Upgrade ESI parent metadata to version 3 with separate public/private reference counts and expose private-scope capability status in the Varnish card plus public/private parent counts in the WordPress and `advanced-cache.php` response paths.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `templates/advanced-cache.php.tpl`, `includes/esi/functions.php`, `includes/esi/class-esi-registry.php`, `includes/esi/class-esi-rendering-trait.php`, `includes/esi/class-esi-endpoint-trait.php`, `includes/engine/class-engine-storage-trait.php`, `includes/engine/class-engine-response-headers-trait.php`, `includes/integrations/varnish/class-varnish-capability-fingerprint-trait.php`, `includes/integrations/varnish/class-varnish-esi-capability-trait.php`, and `includes/admin/js/varnish.js`.

= 2.59.10.19 =
* Add exact public ESI fragment invalidation through `ultracache_purge_esi_fragment()`. The API derives the deterministic signed fragment URL for one normalized context, invalidates only that Varnish object, leaves parent pages intact, returns a bounded operation result, and records dedicated production invalidation counters without duplicating the existing generic Varnish operation totals.
* Enforce definition-level total context and individual value byte limits in addition to the existing context-key allowlist, scalar-only values, token signature, output limit, and nesting guard. Add callback-free definition and stable context-hash inspection APIs for integrations.
* Upgrade ESI parent sidecars to version 2 with bounded unique-fragment and minimum/maximum fragment-TTL metadata while retaining compatibility with version 1 sidecars. Publish the compact lifecycle metadata from normal WordPress and `advanced-cache.php` delivery paths.
* Extend Varnish refill and shared warm-pipeline results with ESI parent-variant, fragment-reference, unique-reference, and TTL counters. Add compact fragment endpoint context, byte-size, and render-duration headers plus a render metrics action for external analytics.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `templates/advanced-cache.php.tpl`, `includes/esi/functions.php`, `includes/esi/class-esi-registry.php`, `includes/esi/class-esi-rendering-trait.php`, `includes/esi/class-esi-endpoint-trait.php`, new `includes/esi/class-esi-lifecycle-trait.php`, `includes/engine/class-engine-storage-trait.php`, `includes/engine/class-engine-response-headers-trait.php`, `includes/integrations/varnish/class-varnish-refill-trait.php`, `includes/integrations/varnish/class-varnish-metrics-trait.php`, and `includes/warmup/class-warm-page-pipeline-trait.php`.

= 2.59.10.18 =
* Add a short-lived signed parent/fragment probe to Test Varnish and verify real ESI composition across identity, gzip, and Brotli-client requests. The test confirms fragment output, independent fragment-object reuse across repeated parent deliveries, inline-fallback removal, blocked raw ESI markup, and a composed cache HIT when cache-status signals are visible.
* Persist an independent ESI capability proof fingerprinted to the current Varnish transport and site contract, expose it through diagnostics and the Varnish card, and keep normal registered fragments on inline fallback HTML until both the administrator switch and the verified proof are active.
* Add a copyable generic Varnish ESI configuration snippet, including backend compression normalization, and add lifecycle/uninstall cleanup for the stored capability result.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `uninstall.php`, `includes/esi/functions.php`, `includes/esi/class-esi-endpoint-trait.php`, `includes/integrations/class-varnish-trait.php`, `includes/integrations/varnish/class-varnish-capability-fingerprint-trait.php`, `includes/integrations/varnish/class-varnish-test-action-trait.php`, `includes/integrations/varnish/class-varnish-behavior-test-trait.php`, new `includes/integrations/varnish/class-varnish-esi-capability-trait.php`, `includes/diagnostics/class-diagnostics-rest-trait.php`, `includes/lifecycle/class-plugin-data-cleanup-trait.php`, and `includes/admin/js/varnish.js`.

= 2.59.10.17 =
* Add an atomic `.esi` sidecar for cached parent HTML containing trusted ESI includes, with bounded versioned fragment metadata shared by normal STORE writes, explicit warm writes, the WordPress early-hit path, and `advanced-cache.php`.
* Emit `Surrogate-Control: content="ESI/1.0"` plus ESI parent diagnostics only for marked parent responses, while stale/non-cacheable ESI parents retain a no-store surrogate contract and inline fallback behavior.
* Keep ESI parents on identity/gzip representations, remove and skip Brotli variants, remove and skip Apache Static HTML aliases, and restore or remove sidecars correctly across failed writes and ESI-to-non-ESI transitions.
* Remove `.esi` sidecars during targeted purge, cache-variant cleanup, and stale generated-CSS invalidation.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/class-ultra-cache-engine.php`, `includes/esi/class-esi-rendering-trait.php`, `includes/engine/class-engine-response-headers-trait.php`, `includes/engine/class-engine-storage-trait.php`, and `templates/advanced-cache.php.tpl`.

= 2.59.10.16 =
* Add the opt-in public ESI fragment foundation with a registry-based developer API, public-only scope enforcement, bounded context keys and output size, deterministic HMAC-signed context tokens, and a same-origin read-only fragment endpoint.
* Render inline server-side fallback HTML when ESI is disabled or not processed, convert token-matched UltraCache placeholders at the end of the canonical STORE/warm HTML pipeline into `<esi:include>` plus `<esi:remove>` markup, and neutralize unrelated raw ESI directives before trusted directives are inserted.
* Add the disabled-by-default ESI framework switch to the Varnish card and route it through canonical settings defaults, validation, REST schema, import/export, profile preservation, infrastructure permissions, and runtime mapping.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/class-ultra-cache-engine.php`, `includes/bootstrap/class-bootstrap-trait.php`, `includes/settings/class-settings-registration-trait.php`, `includes/settings/class-settings-rendering-trait.php`, `includes/settings/class-settings-persistence-trait.php`, `includes/settings/class-settings-validation-trait.php`, `includes/rest/class-rest-schemas-trait.php`, `includes/rest/class-rest-cache-trait.php`, `includes/admin/js/settings.js`, `includes/admin/js/lifecycle.js`, `includes/admin/js/varnish.js`, `includes/admin/js/dashboard-application.js`, and new `includes/esi/` files.

= 2.59.10.15 =
* Convert the Varnish and LiteSpeed integration cards into gated accordions with their main enable switches in the accordion headers. Enabling opens the integration automatically, disabling closes it, and disabled integrations cannot expose their configuration, actions, diagnostics, counters, or history.
* Gray and lock Apache Static HTML Delivery while Native LiteSpeed HTML Cache is active, and lock the LiteSpeed main switch while Apache Static HTML Delivery is active. Both disabled states expose explicit hover warnings while the existing backend mutual-exclusion contract remains enforced.

= 2.59.10.14 =
* Make Native LiteSpeed HTML Cache and Apache Static HTML Delivery mutually exclusive across dashboard toggles, REST saves, imports, profiles, WP-CLI, persistence, and runtime settings normalization. Enabling either mode now disables the other in the same atomic settings save.
* Resolve conflicting legacy/imported payloads deterministically in favor of Native LiteSpeed HTML Cache, preventing both server-level HTML delivery paths from remaining active together.

= 2.59.10.13 =
* Publish the native LiteSpeed TTL, site tag, exact URL tag, and `orig`/`webp`/`avif` vary contract from the early `advanced-cache.php` page-cache hit path.
* Keep stale UltraCache hits, query-string hits, and conditional `304 Not Modified` responses out of LSCache with `X-LiteSpeed-Cache-Control: no-cache`.

= 2.59.10.12 =
* Fix LiteSpeed managed-rule diagnostics so the guarded `.htaccess` read uses the authorized `litespeed_cache` filesystem context. Existing `# BEGIN/END UltraCache LiteSpeed Cache` rules are now detected correctly instead of being reported as `Not active`.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, and `includes/integrations/litespeed/class-litespeed-diagnostics-trait.php`.

= 2.59.10.11 =
* Consolidate the complete LiteSpeed integration into one full-width LiteSpeed card, matching the Varnish dashboard architecture. Native HTML cache enablement, targeted refill, site-warm inclusion, stale regeneration, refresh ahead, threshold/page limits, pinned URLs, Flush All inclusion, behavior testing, direct purge, and redetection now live together.
* Keep the LiteSpeed card visible whenever LiteSpeed is detected or any LiteSpeed setting is configured, so the behavior-test prerequisite can be enabled from the same card instead of from the general Cache Engine section.
* Move LiteSpeed origin evidence, managed-rule status, purge transport, active HTML buckets, observed `X-LiteSpeed-Cache`/`X-QC-Cache` headers, behavior results, production counters, refresh-ahead status, and recent operation history into the same card.
* Remove duplicate LiteSpeed summaries from Diagnostics, Advanced Diagnostics, Reverse Proxy Details, and External Cache Flush settings. The main LiteSpeed card is now the single dashboard surface for LiteSpeed configuration and telemetry.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/admin/js/cache.js`, `includes/admin/js/dashboard-application.js`, and `includes/admin/js/dashboard-diagnostics-ui.js`.

= 2.59.10.10 =
* Fix the Advanced Diagnostics dashboard crash introduced in 2.59.10.09 by defining the LiteSpeed diagnostics payload inside the `AdvancedDiagnosticsCard` component scope before rendering native-cache, stale-purge, refresh-ahead, behavior-test, and refill telemetry.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, and `includes/admin/js/dashboard-diagnostics-ui.js`.

= 2.59.10.09 =
* Add opt-in LiteSpeed stale exact-URL tag invalidation using the signed blocking control response. Affected pages may remain available as stale while UltraCache regenerates them, while the final pre-refill purge and the behavior test remain hard exact purges for deterministic replacement.
* Add a bounded LiteSpeed refresh-ahead candidate registry sourced from pinned URLs, home/posts/shop pages, selected menus, cache analytics, and sitemaps. Candidate URLs are normalized to the current site, deduplicated, prioritized, retained within fixed limits, and scheduled independently from Varnish candidates.
* Determine refresh eligibility from the actual UltraCache `orig`, `webp`, and `avif` HTML files and their `.fresh` markers against the existing Fresh TTL and administrator-selected threshold. Missing required buckets are eligible immediately; no uncertain LiteSpeed `Age` header is used.
* Route due LiteSpeed candidates through the existing persistent page-warm queue, per-page lock, lease heartbeat, retry classification, and warm pipeline. Each claimed page is rechecked, stale-purged, rebuilt, hard-purged, and refilled without adding a separate background worker; LiteSpeed discovery runs before Varnish discovery so an always-due Varnish scan cannot starve the independent LiteSpeed registry.
* Add stale-purge and refresh-ahead controls, bounded scanner status, source/count diagnostics, independent stale-purge counters, recent operation context, lifecycle cleanup, Help text, documentation, REST/settings mappings, and translations.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `uninstall.php`, `includes/integrations/litespeed/class-litespeed-control-trait.php`, `includes/integrations/litespeed/class-litespeed-metrics-trait.php`, `includes/integrations/litespeed/class-litespeed-diagnostics-trait.php`, `includes/integrations/litespeed/class-litespeed-refill-trait.php`, `includes/integrations/litespeed/class-litespeed-refresh-candidates-trait.php`, `includes/integrations/litespeed/class-litespeed-refresh-ahead-trait.php`, `includes/runtime/class-runtime-cache-services-trait.php`, `includes/maintenance/class-scheduled-maintenance-trait.php`, `includes/warmup/class-cron-warm-orchestrator-trait.php`, `includes/settings/class-settings-registration-trait.php`, `includes/settings/class-settings-rendering-trait.php`, `includes/settings/class-settings-validation-trait.php`, `includes/settings/class-settings-persistence-trait.php`, `includes/rest/class-rest-cache-trait.php`, `includes/rest/class-rest-routes-trait.php`, `includes/rest/class-rest-schemas-trait.php`, `includes/lifecycle/class-plugin-data-cleanup-trait.php`, `includes/admin/js/cache.js`, `includes/admin/js/dashboard-application.js`, `includes/admin/js/dashboard-diagnostics-ui.js`, `includes/admin/js/help.js`, `includes/admin/js/lifecycle.js`, and `includes/admin/js/settings.js`.

= 2.59.10.08 =
* Add a canonical native LiteSpeed behavior test that runs two public GET requests for every active `orig`, `webp`, and `avif` HTML bucket, one shared blocking exact-URL purge, and two additional public GET requests per bucket. PASS requires an observable post-purge MISS followed by HIT; hidden LiteSpeed/QUIC.cloud cache signals return INCONCLUSIVE rather than a false success.
* Add bounded production LiteSpeed telemetry for site purge, exact-URL purge, invalidated URL, and refill outcomes, including observed HIT, MISS, BYPASS, and hidden-signal counts. Diagnostic behavior-test traffic is explicitly excluded from production counters.
* Store and display the latest 30 sanitized LiteSpeed operations with context, bucket, HTTP/cache status, duration, counts, and local path only. Query strings, response bodies, and remote URLs are not retained.
* Extend the LiteSpeed dashboard card, Advanced Diagnostics payload, REST/API controller, external-cache detection schema, Help text, documentation, deactivation/uninstall cleanup, and translations with behavior-test results, per-bucket findings, production counters, and recent operation history.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `uninstall.php`, `includes/integrations/litespeed/class-litespeed-metrics-trait.php`, `includes/integrations/litespeed/class-litespeed-diagnostics-trait.php`, `includes/integrations/litespeed/class-litespeed-control-trait.php`, `includes/integrations/litespeed/class-litespeed-refill-trait.php`, `includes/runtime/class-runtime-cache-services-trait.php`, `includes/diagnostics/class-diagnostics-rest-trait.php`, `includes/rest/class-rest-litespeed-trait.php`, `includes/rest/class-rest-routes-trait.php`, `includes/lifecycle/class-plugin-data-cleanup-trait.php`, `includes/admin/js/api.js`, `includes/admin/js/cache.js`, `includes/admin/js/dashboard-application.js`, `includes/admin/js/dashboard-diagnostics-ui.js`, and `includes/admin/js/help.js`.

= 2.59.10.07 =
* Add independent LiteSpeed controls for targeted affected-page refill and inclusion in homepage, menu, full-site, cron, CLI, and warm-after-flush page pipelines.
* Extend the existing shared per-page warm contract to complete UltraCache HTML and configured CSS work first, dispatch one blocking exact LiteSpeed purge, and then issue one anonymous public GET for every active `orig`, `webp`, and `avif` HTML bucket.
* Route successful targeted LiteSpeed invalidations into the existing persistent page-warm queue, retaining queue coalescing, manual-job priority, per-URL locking, lease heartbeats, retry classification, and pause/resume checkpoints without adding a separate worker.
* Extend the staged dashboard crawler, REST stage contract, cron status, completion counters, Help text, and settings import/profile preservation for LiteSpeed warm results. Explicit LiteSpeed bypass responses are not counted as successful refills.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/integrations/litespeed/class-litespeed-control-trait.php`, `includes/integrations/litespeed/class-litespeed-refill-trait.php`, `includes/warmup/class-cron-warm-orchestrator-trait.php`, `includes/warmup/class-warm-page-pipeline-trait.php`, `includes/settings/class-settings-registration-trait.php`, `includes/settings/class-settings-rendering-trait.php`, `includes/settings/class-settings-validation-trait.php`, `includes/settings/class-settings-persistence-trait.php`, `includes/rest/class-rest-cache-trait.php`, `includes/rest/class-rest-routes-trait.php`, `includes/rest/class-rest-schemas-trait.php`, `includes/cli/class-wp-cli-cache-trait.php`, `includes/admin/js/dashboard-application.js`, `includes/admin/js/help.js`, `includes/admin/js/jobs.js`, `includes/admin/js/lifecycle.js`, `includes/admin/js/settings.js`, `includes/admin/js/ui.js`, and `includes/admin/js/warmup.js`.

= 2.59.10.06 =
* Add a short-lived HMAC-signed same-site LiteSpeed control endpoint with expiry validation and atomic replay protection. The endpoint emits the native `X-LiteSpeed-Purge` response only after the signed request is accepted and returns an explicit UltraCache acknowledgement to the blocking caller.
* Purge the native LiteSpeed site cache by the stable UltraCache site tag after full and update-driven page-cache invalidation, avoiding a server-wide `*` purge for UltraCache-owned HTML.
* Connect every `ultracache_after_purge_urls` event to exact affected-URL tag invalidation. Local URLs are normalized, query strings and foreign hosts are rejected, duplicates are coalesced, and requests are split into bounded batches of 20 targets.
* Keep native invalidation on the blocking signed response path so the LiteSpeed purge response has completed before the next warm/refill stage can run; retain the existing official LiteSpeed WordPress purge-all transport when UltraCache native LiteSpeed HTML caching is not enabled.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/class-rest-api.php`, `includes/bootstrap/class-bootstrap-trait.php`, `includes/integrations/litespeed/class-litespeed-transport-trait.php`, `includes/integrations/litespeed/class-litespeed-control-trait.php`, `includes/runtime/class-runtime-cache-services-trait.php`, `includes/maintenance/class-update-cache-invalidation-trait.php`, `includes/rest/class-rest-routes-trait.php`, `includes/rest/class-rest-litespeed-trait.php`, `includes/admin/js/dashboard-application.js`, and `includes/admin/js/help.js`.

= 2.59.10.05 =
* Add an opt-in native LiteSpeed HTML Cache setting with a managed `.htaccess` block placed before application rewrites. The block enables public cache lookup while bypassing non-GET/HEAD requests, query strings, authorization, unsafe cookies, configured dynamic paths, and file-like requests.
* Publish eligible UltraCache HTML with `X-LiteSpeed-Cache-Control` using the existing Fresh TTL, stable site and exact-URL tags, and `X-LiteSpeed-Vary` values that match companion ingress rules for isolated `orig`, `webp`, and `avif` cache keys.
* Extend Apache Static HTML Delivery responses with the same LiteSpeed TTL, site tag, and per-file image-bucket vary value; remove managed LiteSpeed rules on deactivation/uninstall and verify `.htaccess` writes inside the existing settings transaction.
* Add the LiteSpeed HTML Cache dashboard switch, Help text, REST/settings mappings, activation diagnostics, and settings-profile preservation.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/core/html-variant-functions.php`, `includes/core/filesystem-guards.php`, `includes/engine/class-engine-litespeed-response-trait.php`, `includes/engine/class-engine-response-headers-trait.php`, `includes/engine/class-engine-storage-trait.php`, `includes/class-ultra-cache-engine.php`, `includes/server/class-server-rules-trait.php`, `includes/settings/class-settings-registration-trait.php`, `includes/settings/class-settings-rendering-trait.php`, `includes/settings/class-settings-persistence-trait.php`, `includes/rest/class-rest-schemas-trait.php`, `includes/lifecycle/class-plugin-data-cleanup-trait.php`, `includes/admin/js/dashboard-application.js`, `includes/admin/js/help.js`, and `includes/admin/js/settings.js`.

= 2.59.10.04 =
* Separate LiteSpeed/OpenLiteSpeed web-server detection from confirmed cache activity. A LiteSpeed server name alone no longer marks the cache layer as enabled or flushable; observed `X-LiteSpeed-Cache`/`X-QC-Cache` headers are recorded independently from the available purge transport.
* Add a dedicated LiteSpeed transport trait and prefer the documented `litespeed_purge_all` WordPress hook. Use the native `X-LiteSpeed-Purge` response transport only after `X-LiteSpeed-Cache` evidence, or `X-QC-Cache` evidence combined with a LiteSpeed origin; retain older class/function APIs as final compatibility fallbacks.
* Revalidate the LiteSpeed transport when a purge runs, bump the external-cache detection schema, and stop reverse-proxy diagnostics from classifying a bare LiteSpeed `Server` header as active page cache.
* Update dashboard and Help text to describe the confirmed transport requirements accurately.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/integrations/litespeed/class-litespeed-transport-trait.php`, `includes/integrations/varnish/class-varnish-diagnostics-trait.php`, `includes/runtime/class-runtime-cache-services-trait.php`, `includes/admin/js/cache.js`, `includes/admin/js/dashboard-application.js`, and `includes/admin/js/help.js`.

= 2.59.10.03 =
* Finalize browser-observed LCP learning only from a five-second timer after page load; user input, scrolling, visibility changes, pagehide, and freeze no longer submit the current candidate early.
* Add one saved Manual LCP selector field inside every discovered URL detail panel, accepting CSS selectors, plain IDs, or image URL/fragments and refreshing that URL after changes.
* While LCP Frontend Discovery is enabled, ignore the General Inclusions Manual LCP selector and use only the per-URL selector for each discovered page; when discovery is disabled, the existing general setting remains effective.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `assets/js/lcp-observer.js`, `includes/admin/css/sections.css`, `includes/admin/js/api.js`, `includes/admin/js/dashboard-application.js`, `includes/admin/js/dashboard-diagnostics-ui.js`, `includes/diagnostics/class-lcp-diagnostics-trait.php`, `includes/engine/lcp/class-lcp-detection-trait.php`, `includes/engine/lcp/class-lcp-html-rewrite-trait.php`, `includes/engine/lcp/class-lcp-observation-storage-trait.php`, `includes/engine/lcp/class-lcp-observation-trait.php`, `includes/rest/class-rest-lcp-diagnostics-trait.php`, `includes/rest/class-rest-routes-trait.php`, `includes/settings/class-settings-persistence-trait.php`, `includes/lifecycle/class-plugin-data-cleanup-trait.php`, and `uninstall.php`.

= 2.59.10.02 =
* Finalize browser-observed LCP learning on first user input, page visibility loss, pagehide/freeze, or a 30-second idle fallback instead of submitting a provisional candidate 2.5 seconds after window load. This keeps late video frames eligible to become the final desktop/tablet/mobile LCP winner before two-of-three locking.
* Classify `<video>` before generic `currentSrc`/`src` image handling, distinguish poster-image LCP from video-frame LCP, accept validated same-site video resource URLs, and retain video mappings in diagnostics/storage filters.
* Apply `fetchpriority="high"`, remove `loading`, and set `preload="auto"` for confirmed video-frame LCP elements while preserving image/poster preload behavior for confirmed image resources.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `assets/js/lcp-observer.js`, `includes/admin/js/ui.js`, `includes/engine/lcp/class-lcp-detection-trait.php`, `includes/engine/lcp/class-lcp-observation-trait.php`, and `includes/engine/lcp/class-lcp-observation-storage-trait.php`.

= 2.59.10.01 =
* Keep the version Help modal at the reader's current scroll position while dashboard state updates continue in the background. The close-button focus now runs only when the modal opens and uses `preventScroll`, while Escape handling reads the latest close callback without retriggering focus.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, and `includes/admin/js/ui.js`.

= 2.59.09.119 =
* Fix the media-queue stale-claim reset query so the force-regeneration marker uses `$wpdb->esc_like()` and a `%s` replacement parameter instead of embedding SQL wildcards in the prepared query.
* Add a `How to Improve Performance and PageSpeed Scores` section immediately after the must-do post-install JavaScript check in the version Help modal, covering CSS bundle source diagnostics, targeted large-file exclusions, and selective optimization controls.
* Add an Images & Media Library FAQ workflow for users with SSH but no root access or installed WP-CLI, including local WP-CLI download, PHP and WordPress path discovery, and the full UltraCache media-conversion command.
* Add responsive code-block styling for the new command-based FAQ in UltraCache and Native dashboard themes.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/admin/css/sections.css`, `includes/admin/css/themes.css`, `includes/admin/js/ui.js`, and `includes/media/queue/class-media-queue-schema-trait.php`.

= 2.59.09.118 =
* Route `Warm affected pages after save` through the persistent shared page-warm queue instead of rebuilding only the original HTML bucket synchronously inside the save request. Published and non-public post status changes, WooCommerce object updates, public term changes, old/new term assignments, trash actions, and permanent deletions now enqueue the canonical `warmUrls` produced by the 2.59.09.117 affected-URL plan.
* Run each affected rebuild as one coalesced per-URL pipeline: force-refresh all active UltraCache HTML variants, rebuild the configured per-page/front-page CSS bundle scope, then perform exact Varnish invalidation followed by ORIG/WebP/AVIF refill when Varnish is enabled. Servers without Varnish complete the same HTML/CSS rebuild with the Varnish stage disabled.
* Keep feeds purge-only and exclude a deleted post permalink from warm processing while continuing to rebuild its homepage and archive surfaces. Preserve static front-page and posts-page URLs when either special page is deleted.
* Reuse queue uniqueness, processing leases, retry handling, and manual-warm priority so repeated `save_post`, `set_object_terms`, and WooCommerce hooks coalesce by canonical URL; one failed page remains isolated and does not stop the remaining affected-page rows.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `includes/admin/js/dashboard-application.js`, `includes/admin/js/help.js`, `includes/admin/js/ui.js`, `includes/warmup/class-warm-runner-trait.php`, `includes/warmup/class-cron-warm-orchestrator-trait.php`, and `includes/integrations/varnish/class-varnish-refill-trait.php`.

= 2.59.09.117 =
* Build one canonical affected-URL plan for post, WooCommerce object, term, and term-assignment changes. The plan includes the post permalink, homepage/static front, blog index, post-type archive or WooCommerce shop, the calculated affected pagination pages, public taxonomy archives, author archives, date archives, and related feeds.
* Canonicalize and deduplicate affected URLs into one plan, then derive `purgeUrls` and `warmUrls` from the same plan. Feeds remain purge-only, while every cacheable local HTML URL is eligible for post-save warm processing.
* Make post-save purge and warm consume the same plan instance, and reuse the same plan builders for direct post purges, permanent deletion before the post row is removed, term updates, and old/new term assignments. Resolve both term IDs and term-taxonomy IDs so removed and newly assigned public term archives are included.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/class-ultra-cache-engine.php`, `includes/warmup/class-warm-url-discovery-trait.php`, `includes/warmup/class-warm-runner-trait.php`, and `includes/warmup/class-warm-css-bundle-trait.php`.

= 2.59.09.116 =
* Make `Fresh TTL (minutes)` the single HTML freshness source for UltraCache disk cache and, when Varnish is enabled, the Varnish `s-maxage`/surrogate lifetime used by dynamic and Apache static HTML delivery.
* Remove the separate Varnish HTML TTL setting from dashboard state, Varnish forms, REST schemas, persistence, validation, profiles, and runtime configuration; Varnish refresh-ahead and capability fingerprints now consume the effective TTL derived from Fresh TTL.
* Set fresh-install defaults to 1440 minutes Fresh TTL and a 2880-minute maximum total stale window. Keep Fresh TTL editable without enabling local stale-while-revalidate; Max Stale remains conditional on that feature.
* Clarify that Max Stale is the maximum total cache age, with stale serving beginning only after Fresh TTL expires, and preserve normal UltraCache operation on servers without Varnish.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `languages/ultracache.pot`, `templates/advanced-cache.php.tpl`, `includes/admin/js/dashboard-application.js`, `includes/admin/js/dashboard-settings-actions.js`, `includes/admin/js/help.js`, `includes/admin/js/lifecycle.js`, `includes/admin/js/settings.js`, `includes/admin/js/varnish.js`, `includes/admin/js/varnish-refresh-ahead.js`, `includes/engine/class-engine-response-headers-trait.php`, `includes/integrations/varnish/class-varnish-capability-fingerprint-trait.php`, `includes/integrations/varnish/class-varnish-settings-trait.php`, `includes/integrations/varnish/class-varnish-stale-refresh-trait.php`, `includes/rest/class-rest-cache-trait.php`, `includes/rest/class-rest-schemas-trait.php`, `includes/runtime/class-runtime-config-trait.php`, `includes/server/class-server-rules-trait.php`, `includes/settings/class-settings-persistence-trait.php`, `includes/settings/class-settings-registration-trait.php`, `includes/settings/class-settings-rendering-trait.php`, `includes/settings/class-settings-validation-trait.php`, and `includes/storage/class-cache-asset-registry-trait.php`.

= 2.59.09.115 =
* Keep Varnish synchronized with newly warmed disk HTML by performing one exact hard invalidation of the canonical page URL after HTML/CSS warm stages and before public refill requests.
* Apply the invalidate-then-refill sequence to homepage, menu, full-site, cron, warm-after-flush, scheduled-cleanup, CLI, and hard targeted-page warm paths. Preserve the strict HTTP soft-purge origin-revalidation flow without converting it into a hard invalidation.
* Make the staged dashboard crawler invalidate once before its first orig/WebP/AVIF bucket, retain that state across pause/resume checkpoints, and stop the page pipeline when exact invalidation fails instead of reporting a refill against an older Varnish object.
* Include the exact-invalidation result in Varnish stage metadata so queue and dashboard results expose failures.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/admin/js/warmup.js`, `includes/integrations/varnish/class-varnish-invalidation-trait.php`, `includes/integrations/varnish/class-varnish-refill-trait.php`, `includes/rest/class-rest-cache-trait.php`, `includes/rest/class-rest-routes-trait.php`, and `includes/warmup/class-warm-page-pipeline-trait.php`.

= 2.59.09.114 =
* Add a two-second settling interval between the compact Test Varnish refill request and its public HIT verification request, matching the observed Varnish cache transition without changing production warm or refill behavior.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, and `includes/integrations/varnish/class-varnish-behavior-test-trait.php`.

= 2.59.09.113 =
* Fix manual warm progress counters by carrying the real cached, skipped, and failed counts into the process state rendered by the warm-up popup.
* Prevent WordPress canonical redirect handling from stripping signed UltraCache revalidation and CSS-scan query arguments on authenticated internal warm requests, including the site homepage.
* Scope the redirect bypass strictly to valid UltraCache revalidation or CSS-bundle scan contracts with the internal-request marker and runtime-control token; normal public and Varnish refill canonical redirects remain unchanged.
* Preserve the existing HTML, CSS bundle, Varnish refill, queue, and cron warm behavior.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/admin/js/jobs.js`, `includes/class-ultra-cache-engine.php`, and `includes/engine/class-engine-cache-decision-trait.php`.

= 2.59.09.112 =
* Fix the manual/menu/full-site Varnish refill fatal introduced when the standalone diagnostics were removed: production refill still depended on response-header and cache-classification methods that remained defined only in the lazy basic-test trait.
* Move the bounded Varnish response-header reader and portable MISS/HIT/BYPASS/STALE classifier into the normal transport layer shared by production refill, strict origin refill, and the compact Test Varnish runner.
* Remove the duplicate diagnostic-owned implementations and update every caller to the shared runtime transport contract, preventing warm operations from depending on a diagnostic trait.
* Add a cross-trait dependency check covering all methods from the lazy basic-test trait that are referenced by production Varnish runtime files.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/integrations/varnish/class-varnish-transport-trait.php`, `includes/integrations/varnish/class-varnish-behavior-test-trait.php`, `includes/integrations/varnish/class-varnish-refill-trait.php`, and `includes/integrations/varnish/class-varnish-origin-refill-trait.php`.

= 2.59.09.111 =
* Remove the optional Varnish HIT-verification setting and its additional public request for every refilled orig, WebP, and AVIF HTML bucket.
* Keep the production warm pipeline focused on its real stages: HTML cache generation, optional CSS bundle generation, and one public Varnish refill request per active HTML variant.
* Remove the separate verification stage, verification heartbeats, retry recommendations, HIT/bypass/inconclusive counters, and related manual warm-up REST/UI state.
* Count only the actual refill requests in production Varnish metrics; a refill succeeds when each selected public refill request returns a successful response.
* Preserve strict authenticated origin revalidation for HTTP soft-purge/SWR flows; this change affects only the extra post-refill HIT probe.
* Remove `varnishVerifyRefillHit` from settings registration, validation, REST schemas, dashboard forms, capability fingerprints, and client payloads.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/integrations/varnish/class-varnish-refill-trait.php`, `includes/integrations/varnish/class-varnish-capability-fingerprint-trait.php`, `includes/integrations/varnish/class-varnish-settings-trait.php`, `includes/warmup/class-warm-page-pipeline-trait.php`, `includes/warmup/class-cron-warm-orchestrator-trait.php`, `includes/rest/class-rest-cache-trait.php`, `includes/rest/class-rest-routes-trait.php`, `includes/rest/class-rest-schemas-trait.php`, `includes/settings/class-settings-registration-trait.php`, `includes/settings/class-settings-validation-trait.php`, `includes/settings/class-settings-persistence-trait.php`, `includes/settings/class-settings-rendering-trait.php`, `includes/diagnostics/class-diagnostics-rest-trait.php`, `includes/admin/js/varnish.js`, `includes/admin/js/settings.js`, `includes/admin/js/lifecycle.js`, `includes/admin/js/warmup.js`, `includes/admin/js/jobs.js`, `includes/admin/js/ui.js`, and `includes/admin/js/dashboard-application.js`.

= 2.59.09.110 =
* Remove the standalone Varnish Flush scope, Validators, Accept/VCL, Soft purge/SWR, and Multi-endpoint diagnostic actions, their lazy PHP runners and test traits, their REST routes, and their dashboard controls.
* Remove the Advanced Varnish diagnostics accordion, stored-result rendering, configuration-change comparison, VCL/Accept recommendation panel, and the JavaScript modules used only by those diagnostics.
* Keep one compact Test Varnish action for configured transport/authentication, one exact canonical front-page invalidation, and public refill verification, with its latest result stored separately from the last production invalidation.
* Keep the main Varnish status limited to support, mode, connection, purge method, effective flush scope, last production invalidation, refill state, queue state, last error, and last basic test.
* Remove advanced diagnostic payloads from dashboard responses and remove diagnostic-only REST/API/controller wiring while retaining the operational queue, metrics, settings, invalidation, refill, warm-up, and refresh-ahead surfaces.
* Remove dashboard-facing VCL and Accept-normalization snippet generation and replace stale diagnostic guidance with current capability-state messages.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/integrations/class-varnish-trait.php`, `includes/integrations/varnish/class-varnish-test-action-trait.php`, `includes/integrations/varnish/class-varnish-test-runner.php`, `includes/integrations/varnish/class-varnish-behavior-test-trait.php`, `includes/integrations/varnish/class-varnish-diagnostics-trait.php`, `includes/integrations/varnish/class-varnish-settings-trait.php`, `includes/integrations/varnish/class-varnish-metrics-trait.php`, `includes/integrations/varnish/class-varnish-flush-scope-trait.php`, `includes/integrations/varnish/class-varnish-soft-purge-trait.php`, `includes/integrations/varnish/class-varnish-stale-refresh-trait.php`, `includes/integrations/varnish/class-varnish-origin-refill-trait.php`, `includes/integrations/varnish/class-varnish-origin-revalidation-trait.php`, `includes/rest/class-rest-cache-trait.php`, `includes/rest/class-rest-routes-trait.php`, `includes/diagnostics/class-diagnostics-rest-trait.php`, `includes/cli/class-wp-cli-integrations-trait.php`, `includes/admin/class-admin-trait.php`, `includes/admin/js/api.js`, `includes/admin/js/cache.js`, `includes/admin/js/dashboard-application.js`, `includes/admin/js/varnish.js`, and `includes/admin/js/varnish-refresh-ahead.js`. Removed files: advanced Varnish diagnostic runners/test traits and `includes/admin/js/varnish-diagnostics.js`, `varnish-accept-normalization.js`, `varnish-metrics.js`, and `varnish-origin-revalidation.js`.

= 2.59.09.109 =
* Fix the Accept/VCL Advanced diagnostic fatal by moving the ETag comparison normalizer into the shared Varnish behavior contract used by the validator, flush-scope, and variant runners; remove the private duplicate from the validator-only trait.
* Separate successful diagnostic execution from the diagnostic finding in Advanced REST responses. Completed tests with partial, unsupported, or incompatible findings now return a normal HTTP 200 payload and update the diagnostic panel instead of being reported as a failed UltraCache request.
* Replace the combined validator failure message with a bounded `failedChecks` list that names the exact failing areas, such as ETag 304, Last-Modified 304, validator stability, conditional precedence, cookie policy, Authorization policy, or stale conditional behavior.
* Add cross-runner dependency checks for every lazy Varnish diagnostic so shared helper calls cannot silently remain private or absent from one runner composition.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/integrations/varnish/class-varnish-behavior-test-trait.php`, `includes/integrations/varnish/class-varnish-conditional-revalidation-test-trait.php`, and `includes/rest/class-rest-cache-trait.php`.

= 2.59.09.108 =
* Fix the Advanced Varnish Flush scope fatal caused by the lazy diagnostic runner inheriting shared behavior-request helpers that were incorrectly declared private in the parent diagnostics runner.
* Define the four cross-runner behavior helpers as protected shared internals: response-header reading, response classification, public behavior requests, and completed-step validation. Keep the two basic-test-only invalidation helpers private.
* Apply the same visibility contract to every lazy diagnostic runner that reuses the common behavior engine, preventing equivalent private-method fatals in Flush scope, Validators, Accept/VCL, and Soft purge/SWR actions without loading advanced diagnostic traits in the normal runtime.
* Add a diagnostic-runner visibility/composition regression check covering every cross-trait call to the shared behavior engine.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, and `includes/integrations/varnish/class-varnish-behavior-test-trait.php`.

= 2.59.09.107 =
* Fix the UltraCache dashboard fatal introduced by the Varnish diagnostic split: the runtime HTML-variant status called `get_varnish_accept_normalization_contract()` even though that shared contract remained defined only in the lazy Accept/VCL diagnostic trait.
* Move the small Accept-normalization contract and VCL-snippet builder into the normal Varnish diagnostics trait, where the dashboard uses them, while keeping browser-profile probing and Accept/VCL test execution lazy-loaded in the dedicated Advanced diagnostic runner.
* Preserve the 2.59.09.102 diagnostic boundary without loading the full advanced Accept test trait during normal dashboard or frontend runtime.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/integrations/varnish/class-varnish-diagnostics-trait.php`, and `includes/integrations/varnish/class-varnish-accept-normalization-trait.php`.

= 2.59.09.106 =
* Complete the Varnish simplification integration pass by keeping the independent basic diagnostic result separate from the latest production Varnish operation. Running Test Varnish no longer replaces the production last-invalidation state, and later production invalidations no longer make the dashboard forget the latest basic test.
* Make the compact dashboard read connection and basic-test health from `advancedDiagnostics.basic`, treat configuration-changed proof as requiring a new test, and recognize direct, batch, queued, and site-flush operations as valid production invalidation results.
* Align soft purge, stale-while-revalidate, and refresh-ahead guidance with the dedicated Soft purge / SWR diagnostic introduced in 2.59.09.102 instead of incorrectly directing administrators to the minimal Test Varnish action.
* Derive stale-while-revalidate status directly from the independently fingerprinted soft-purge capability, and remove the obsolete shared-TTL and stale evaluator paths that still expected fields from the former combined behavior test.
* Reuse the already normalized endpoint diagnostics from the Varnish CLI settings while building the dashboard payload instead of recalculating the same endpoint validation repeatedly.
* Preserve the simplified runtime boundaries: no server-specific direct-origin routing, no advanced test traits in the normal Varnish facade, no diagnostic writes to production metrics, and no status-triggered queue or refresh-ahead lifecycle work.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/admin/js/varnish.js`, `includes/admin/js/varnish-refresh-ahead.js`, `includes/diagnostics/class-diagnostics-rest-trait.php`, `includes/integrations/varnish/class-varnish-behavior-test-trait.php`, `includes/integrations/varnish/class-varnish-flush-scope-test-trait.php`, `includes/integrations/varnish/class-varnish-origin-refill-trait.php`, `includes/integrations/varnish/class-varnish-settings-trait.php`, `includes/integrations/varnish/class-varnish-soft-purge-trait.php`, and `includes/integrations/varnish/class-varnish-stale-refresh-trait.php`.

= 2.59.09.105 =
* Replace the former full-page Varnish status matrix with one compact operational summary covering support, mode, connection, purge method, effective flush scope, the latest production invalidation result when available, refill state, current queue state, the latest error, and the latest basic test.
* Group dashboard warnings by configuration, transport, invalidation, refill, VCL, and queue so each category contributes at most one concise message instead of repeating the same finding across multiple status rows.
* Move endpoint details, method-contract evidence, refresh-ahead state, production counters, basic request steps, VCL fragments, and other technical information into the existing closed Advanced Varnish diagnostics accordion.
* Keep the dashboard change presentation-only: no Varnish runtime, queue, capability, settings, metrics, or diagnostic execution behavior is changed.
* Remove the obsolete expanded-status rendering branches and automatic status-accordion opening, reducing `includes/admin/js/varnish.js` by more than 200 lines.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/admin/js/varnish.js`, and `includes/admin/js/varnish-diagnostics.js`.

= 2.59.09.104 =
* Gate refresh-ahead with one portable runtime contract: enabled Varnish HTTP endpoint mode, verified soft purge, a positive stale-while-revalidate value, an effective soft strategy, and the explicit refresh-ahead switch.
* Report refresh-ahead as unavailable in admin BAN mode and keep its candidate count, candidate sources, scan state, and recurring worker inactive whenever the runtime contract is not active.
* Collect and persist refresh-ahead candidates only inside the active scanner. Targeted invalidation and refill requests no longer update the candidate registry during normal frontend or administrative operations.
* Keep the shared cron worker scheduled for active refresh-ahead or real queue/site-warm work, and remove a refresh-ahead-only schedule during settings lifecycle synchronization when no other warm or Varnish work remains.
* Preserve the shared `page_warm` queue contract: enqueue schedules work, the cron worker recovers expired leases, manual resume restores deferred work, and canonical local redirects continue as canonical queue jobs.
* Simplify the refresh-ahead controls and status so candidate details are shown only while the scanner is active.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/integrations/varnish/class-varnish-refresh-ahead-trait.php`, `includes/integrations/varnish/class-varnish-refresh-candidates-trait.php`, `includes/integrations/varnish/class-varnish-invalidation-trait.php`, `includes/integrations/varnish/class-varnish-refill-trait.php`, `includes/maintenance/class-scheduled-maintenance-trait.php`, and `includes/admin/js/varnish-refresh-ahead.js`.

= 2.59.09.103 =
* Replace the unified Varnish capability fingerprint with independent transport, HTML invalidation, HTML variant, soft-purge, and public-refill contracts, so a TTL or media-policy change no longer invalidates unrelated connection or exact-invalidation proof.
* Bind the basic test and every Advanced Varnish diagnostic only to the contracts it actually verifies; stored diagnostic results are marked configuration-changed only when one of their relevant contracts changes.
* Reduce the persistent production metrics option to invalidation operations, successfully invalidated URLs, endpoint failures, refill attempts, refill successes, and refill failures. Current queue pending, processing, retrying, and terminal counts continue to come directly from the queue table.
* Stop persisting endpoint latency/health history, refill contexts, batching estimates, queue intake/retention totals, recent operation history, and ban-list pressure inside production metrics; diagnostic results remain in their separate bounded non-autoload options.
* Simplify the Varnish metrics UI to production invalidations, refill outcomes, endpoint failures, and the current queue lifecycle, without presenting diagnostic or historical counters as runtime health.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `includes/integrations/varnish/class-varnish-capability-fingerprint-trait.php`, `includes/integrations/varnish/class-varnish-settings-trait.php`, `includes/integrations/varnish/class-varnish-flush-scope-trait.php`, `includes/integrations/varnish/class-varnish-origin-refill-trait.php`, `includes/integrations/varnish/class-varnish-soft-purge-trait.php`, `includes/integrations/varnish/class-varnish-refresh-ahead-trait.php`, `includes/integrations/varnish/class-varnish-diagnostic-actions-trait.php`, `includes/integrations/varnish/class-varnish-metrics-trait.php`, `includes/diagnostics/class-diagnostics-rest-trait.php`, and `includes/admin/js/varnish-metrics.js`.

= 2.59.09.102 =
* Split the former combined Varnish audit into five independent manual Advanced diagnostics: flush scope, validators, Accept/VCL, soft purge/SWR, and multi-endpoint delivery. The minimal Test Varnish flow from 2.59.09.101 remains unchanged.
* Lazy-load only the diagnostic runner and test traits required by the selected action. Advanced topology, validator, variant, soft-purge, and endpoint test code is no longer composed into the normal `Ultra_Cache_WP` frontend runtime.
* Add dedicated infrastructure-protected REST actions and an Advanced Varnish diagnostics accordion. Soft-purge/SWR is shown only in HTTP endpoint mode and multi-endpoint testing only when multiple endpoints are configured.
* Store each diagnostic result in its own bounded, non-autoload option with redaction, recursion, key, string, and global item limits; expose only its concise status, message, and last-run time in the main panel.
* Keep diagnostic invalidations outside production endpoint/operation metrics and prevent advanced findings from changing configured runtime settings. Remove the obsolete eagerly loaded connection-test method and move soft-purge test-only code out of the runtime soft-purge trait.
* Delete all six diagnostic result options from both WordPress uninstall and the dashboard Delete everything workflow.
* Changed files: `ultracache.php`, `readme.txt`, `README.md`, `changelog.txt`, `uninstall.php`, `includes/integrations/class-varnish-trait.php`, `includes/integrations/varnish/class-varnish-diagnostic-actions-trait.php`, `includes/integrations/varnish/class-varnish-diagnostics-trait.php`, `includes/integrations/varnish/class-varnish-soft-purge-trait.php`, `includes/integrations/varnish/diagnostics/`, `includes/rest/class-rest-cache-trait.php`, `includes/rest/class-rest-routes-trait.php`, `includes/diagnostics/class-diagnostics-rest-trait.php`, `includes/admin/class-admin-trait.php`, `includes/admin/js/api.js`, `includes/admin/js/varnish-diagnostics.js`, `includes/admin/js/varnish.js`, `includes/admin/js/cache.js`, `includes/admin/js/dashboard-application.js`, `includes/cli/class-wp-cli-integrations-trait.php`, and `includes/lifecycle/class-plugin-data-cleanup-trait.php`.

= 2.59.09.101 =
* Reduce the primary Test Varnish action to one canonical front-page flow: one public request, one exact hard invalidation, one public refill request, and one follow-up request for visible MISS-to-HIT verification when cache signals are exposed.
* Keep HTML/entire-host topology, second-page/static behavior, variants and Accept profiles, validators, soft purge, origin revalidation, refresh-ahead capability, and ban-pressure inspection as feature-specific diagnostic engines for the separate Advanced actions introduced next.
* Store the run as a bounded `diagnostic-basic-test` result with the explicit outcomes Working, Working with hidden signals, authentication failure, invalidation failure, refill failure, or incomplete configuration.
* Isolate diagnostic invalidation from production operation and endpoint metrics so Test Varnish no longer increases endpoint latency/failure counters or production terminal-operation totals.
* Make the dashboard, queued REST action, and WP-CLI `varnish test` use the same minimal test, replace stale prior test fields instead of merging them, and show only the before-invalidation, after-invalidation, and refill-verification request steps.

= 2.59.09.100 =
* Make Varnish and shared warm-queue status generation read-only: aggregate queue counters no longer create or upgrade the queue table, recover workers, schedule cron events, or mutate queue ownership while the dashboard is loading.
* Split targeted page-warm worker inspection from worker recovery. Status reports `idle`, `scheduled`, `blocked-manual`, or `unscheduled` from persisted state only, while enqueue, cron tick, manual-warm release, and settings/plugin lifecycle retain the explicit recovery path.
* Stop refresh-ahead status from seeding static/menu/analytics candidates or updating the candidate registry; it now reports only the registry and capability state already produced by the active scanner.
* Make manual warm-up status lease-aware without writing: an expired lease is presented as interrupted during passive reads, while persistence and deferred LCP/targeted queue resume occur only from runtime/lifecycle callers.
* Add a read-only queue-schema availability check for status queries and keep schema creation, dbDelta, version updates, and worker scheduling in explicit operational paths.

= 2.59.09.99 =
* Replace topology-gated site-flush selection with a deterministic method contract: admin BAN and HTTP BAN use the explicit host plus HTML Content-Type expression for Automatic and manual HTML-only flushing, while HTTP PURGE uses entire-host site flushing unless a future provider-specific contract is explicitly implemented.
* Expose independent transport, exact invalidation, HTML invalidation, host invalidation, and soft-purge capability fields; transport readiness remains separate from the selected method's supported invalidation scopes.
* Keep the existing flush-topology run as optional diagnostic evidence only. Expired, inconclusive, hidden-header, static-route, or endpoint-behavior diagnostics no longer enable, disable, or change the effective runtime flush scope.
* Prevent the optional HTML topology test from silently substituting an entire-host PURGE when the configured HTTP method has no portable HTML-only contract.
* Update the Varnish scope control and status wording so HTML-only availability is based on the configured BAN contract rather than a successful topology test, while preserving the explicit Entire host action.

= 2.59.09.98 =
* Remove the server-environment direct-origin transport introduced in 2.59.09.97, including local listener derivation, forwarded Host routing, SERVER_ADDR/SERVER_PORT trust exceptions, and the direct-origin fallback branch in the warm runner; all portable warm and refill requests again use the canonical public WordPress URL through the existing guarded loopback contract.
* Separate ordinary BAN/PURGE refill from strict origin revalidation: normal manual, cron, warm-after-flush, and targeted hard-invalidation work now completes from the public refill response plus optional HIT verification without evaluating or persisting two-stage origin proof.
* Restrict authenticated origin revalidation and its VCL contract to HTTP soft/auto purge configurations, skip that test entirely in admin BAN and ordinary HTTP BAN/PURGE modes, and block fallback only when a claimed soft-purge job explicitly requires verified origin regeneration.
* Remove the unused private inner-cache/refill wrapper that duplicated the page-warm pipeline, and expose one bounded refill result state (`success`, `warning`, `retryable_error`, `terminal_error`, or `not_applicable`) while retaining the existing queue compatibility fields.
* Hide the Force refresh reached origin and Two-stage origin refill status rows when the active Varnish mode cannot use strict soft-purge origin revalidation.

= 2.59.09.97 =
* Try the current local PHP web-server listener directly for authenticated force-origin HTML rebuilds before using the public Varnish/VCL route, preserving the trusted public Host and forwarded scheme while limiting socket targets to loopback or the exact server addresses and port exposed by the active WordPress request.
* Keep the public VCL pass contract as the fallback when a direct origin listener cannot be derived or does not expose the WordPress origin marker, and record which transport reached each active orig/WebP/AVIF bucket.
* Correct conditional 304 validation so an ETag request requires its ETag and a Last-Modified request requires its Last-Modified value; a companion validator may be omitted by an upstream 304 but must remain coherent when present. Optional Content-Type metadata is reported as upstream-retained neutral metadata without turning an otherwise bodyless, validator-coherent 304 into a partial failure.
* Give cold primary and secondary HTML topology probes a separate bounded timeout of up to 10 seconds, preventing a legitimate post-BAN WordPress MISS from being classified as failed merely because the endpoint transport timeout was configured at two seconds.
* Advance the origin-revalidation, conditional-revalidation, HTML-flush, and topology capability contracts so the corrected live proof is regenerated by the next Test Varnish run.

= 2.59.09.96 =
* Delete the legacy `ultracache_varnish_html_ttl_default_migration_v1` option and site option from both the dashboard data-removal workflow and WordPress `uninstall.php`, preventing the obsolete Varnish HTML-TTL migration marker from remaining after a complete UltraCache removal.

= 2.59.09.95 =
* Give every authenticated force-origin HTML rebuild a unique bounded revalidation identity and active bucket marker, bypassing both Varnish object reuse and queryless Apache static delivery before the public orig/WebP/AVIF refill stage.
* Keep advanced-cache background stale revalidation on the same unique internal-request contract and recognize the new control arguments across cache exclusion, security, and query-normalization paths.
* Treat bodyless validator-coherent 304 responses as valid when an upstream retains optional representation metadata, record the exact Content-Type, Content-Encoding, or Content-Length headers separately, and add Apache rules that remove those headers from generated static 304 responses where the local server controls them.
* Verify admin-mode HTML-only flushing when the public static route exposes no Varnish signals: require the explicit Content-Type HTML BAN expression, verified HTML MISS-to-HIT behavior, and a representation-stable opaque static probe, while continuing to label static cache internals as unobservable rather than claiming per-object Varnish proof.
* Normalize targeted refill URLs before queue insertion, replace verified local redirect rows with their canonical target, and prevent a non-canonical queue identity from becoming a permanent terminal refill failure.
* Recover orphaned pending targeted refills by reattaching them to the shared cron worker, expose the refill worker state in Varnish diagnostics, and keep manual-warm ownership as the only intentional scheduling blocker.
* Expand Accept-normalization diagnostics with the first bounded canonical or browser profiles that failed bucket reuse, including expected bucket, observed bucket, and cache status, and advance the affected Varnish capability contract generations.

= 2.59.09.94 =
* Make expired shared warm-queue claims true ownership recovery: return the row to pending, clear its claim metadata, and decrement the attempt counter so an abandoned PHP worker does not consume an application retry.
* Add a renewable manual warm-up ownership lease. Each dashboard page stage renews the lease; a closed tab, browser crash, or interrupted REST sequence releases cron priority and resumes preserved targeted/LCP queue work after expiry while retaining the owner token and browser checkpoint for an intentional resume.
* Expose interrupted and lease-expiry state in the manual warm status, keep explicit Pause distinct from browser interruption, and preserve the existing pause behavior that deliberately blocks cron until the administrator resumes or ends the session.
* Complete the 2.59.09.94 regression-build pass over the permanent contracts for Varnish-disabled composition, HTTP PURGE/BAN and admin-mode transport, single/multiple/partial endpoints, soft purge, hidden-header diagnostics, orig/WebP/AVIF isolation, Apache static generation, manual/cron/targeted warm ownership, refresh-ahead state, WooCommerce recently-viewed handling, TranslatePress output buffering, and multisite-aware capability identity.

= 2.59.09.93 =
* Replace the archive warm-discovery query builder with fixed prepared SQL templates for post-type, author, year, month, day, and taxonomy scopes; table identifiers use `%i`, every runtime value uses a placeholder, and no SQL query variable is passed into `$wpdb->prepare()` or an execution method.
* Replace hardcoded `wp-content/plugins` and `wp-content/themes` profiler heuristics with the existing WordPress-derived plugin/theme public-path resolvers, and resolve the WordPress plugin API include through the centralized admin-include path helper instead of an `ABSPATH` string.
* Restrict the Varnish native I/O PHPCS suppression to the authenticated, bounded admin-socket helper block and restore the rules immediately afterward; HTTP Varnish operations continue through the WordPress HTTP API.
* Add explicit technical justification to every remaining single-line PHPCS suppression found by the compliance pass, covering post-render HTML transformation, public signed LCP telemetry, the WooCommerce-owned filter name, and managed wp-config.php string literals.
* Complete the 2.59.09.93 identifier, storage, enqueue/output, REST-route, JSON, SQL, and changed-file compliance scan without adding packaged audit utilities or one-time runtime cleanup code.

= 2.59.09.92 =
* Replace the previous single-page HTML flush check with an empirical topology audit that uses the front page plus a second canonical public HTML URL, proving that exact URL invalidation leaves the second page cached while HTML-only and entire-host scopes invalidate both pages through MISS/STALE-to-HIT sequences.
* Verify the explicit entire-host operation against the same HTML pages and public static probe, requiring static invalidation and refill when the asset is cached through Varnish or a stable BYPASS result when the static route is intentionally excluded.
* Gate Automatic and manual HTML-only scope selection on one current capability result that proves the configured transport, exact invalidation, HTML-only behavior, entire-host behavior, endpoint completion, and an observable static delivery topology; unobservable or stale proof falls back to the entire-host scope.
* Return authoritative full-success, partial-endpoint, and total-failure results for direct site-wide BAN/PURGE operations, including configured, successful, failed, and attempted endpoint target sets without collapsing partial outages into generic failure or success.
* Keep multi-endpoint public behavior unverified unless the test can bind behavior to each individual Varnish node; accepting invalidation on every configured endpoint proves transport delivery but no longer overclaims per-node cache behavior.
* Expand the Varnish dashboard with topology, transport, endpoint, per-endpoint behavior, exact URL, HTML-only, entire-host, static-route, and static-preservation results, and advance the flush-scope/topology capability contract generations.

= 2.59.09.91 =
* Preserve page-cache representation metadata when regenerated HTML or compressed output is byte-identical: atomic cache writes keep the existing payload while a bounded per-page freshness marker advances local TTL, stabilizing ETag and Last-Modified across no-change refreshes without leaving the object stale; Apache static aliases retain the same validator stability.
* Emit the selected identity representation ETag and Last-Modified on successful frontend PHP STORE responses, honor If-None-Match precedence over If-Modified-Since after a verified origin rebuild, and return an explicitly bodyless 304 or HEAD response without skipping the cache-store lifecycle.
* Keep 304 responses bodyless and metadata-focused across the WordPress engine and generated advanced-cache.php: preserve ETag, Last-Modified, Vary, and cache policy while removing Content-Type, Content-Encoding, and Content-Length from the conditional response.
* Apply an explicit private/no-store shared-cache contract to Authorization, cookie, bypassed, lock-limited, uncacheable, empty, and failed-store frontend responses; positive s-maxage and UltraCache surrogate TTL headers remain limited to successfully stored or served public HTML.
* Configure Apache static HTML files with stable MTime/Size validators and retain native conditional-request handling across identity, gzip, and Brotli aliases while preserving the same public TTL and Vary contracts used by PHP and advanced-cache delivery.
* Expand Test Varnish with per-active-variant validator stability, coherent and representation-clean ETag/Last-Modified 304 metadata, If-None-Match precedence, cookie and Authorization private-policy probes, and soft-purged stale conditional requests; the stricter conditional-revalidation contract invalidates older capability proof.

= 2.59.09.90 =
* Parse exact `image/avif` and `image/webp` Accept media ranges with bounded quality handling across WordPress rendering, page-cache lookup, generated `advanced-cache.php`, media URL rewriting, and Apache static HTML delivery; explicit `q=0` refusals and token-like parameter text no longer select an optimized HTML bucket.
* Keep exact media-format support checks request-local and bounded during full-document rewriting so the stricter parser is evaluated once per canonical Accept context rather than repeatedly for every rewritten image URL.
* Update the generated Varnish Accept-normalization contract to match complete media-range tokens, preserve AVIF-before-WebP server preference only for accepted representations, and normalize refused AVIF/WebP profiles to the correct fallback bucket instead of creating cross-capability cache objects.
* Align Apache static compression selection with exact `br`/`gzip` tokens: ordinary q-free browser headers keep Brotli-first delivery, while explicit encoding-quality headers use the identity cache object so Apache cannot contradict the quality-aware PHP/drop-in selector or serve compression for token substrings.
* Strengthen canonical and non-canonical Varnish variant tests with q=0, parameter-token, and mixed-format profiles, requiring exact `X-UltraCache-Variant` identity and visible `Vary: Accept` evidence before declaring orig/WebP/AVIF isolation compatible.
* Mark missing variant identity or Vary evidence as inconclusive, detect wrong-bucket HIT responses as fragmentation, and bind the stricter HTML-variant and Accept-normalization semantics to updated capability contract generations.

= 2.59.09.89 =
* Make advanced-cache stale revalidation single-owner with an atomic cache-root lease, then dispatch one bounded complete authenticated loopback request after the stale response is flushed so concurrent stale visitors cannot start duplicate WordPress rebuilds.
* Send inner-cache background revalidation with the same internal, warm, force-refresh, revalidate, runtime-token, and site-specific VCL-signature request contract used by manual and queued origin refreshes.
* Mark stale local HTML as private/no-store with Surrogate-Control no-store so an expired UltraCache disk object cannot repopulate Varnish as a fresh shared object; also suppress positive shared-cache contracts on Set-Cookie, Pragma no-cache, private/no-store/no-cache, and surrogate no-store responses.
* Strengthen soft-purge proof with exact zero-redirect requests, HTTP stale-warning detection, high-confidence fresh-HIT evidence, bounded polling after the initial stale/grace response, and explicit revalidation-timeout/request-failure outcomes.
* Evaluate the configured stale-while-revalidate directive against the actual soft-purge STALE-to-fresh-HIT sequence, exposing stale and fresh proof separately and binding the stronger origin-revalidation, soft-purge, and SWR semantics to new capability contract generations.

= 2.59.09.88 =
* Classify every shared-queue enqueue as accepted, inserted, coalesced, upgraded, rejected, duplicate, or failed using the authoritative WordPress database result instead of reporting every represented URL as a newly queued row.
* Add permanent queue result levels for success, warning, partial, retrying, skipped, and terminal error outcomes, preserving lifecycle status separately from diagnostic severity for Varnish invalidation and targeted page-warm work.
* Expose pending and processing invalidations/refills separately, report planned, processing, retrying, partial, warning, completed, skipped, and terminal queue states, and prevent partial or warning results from appearing as green success in the dashboard.
* Retain completed/skipped auxiliary Varnish rows for one day and terminal errors for fourteen days by default, with bounded filters and cumulative pruning counters recorded in the existing non-autoload Varnish metrics state.
* Aggregate queue intake, partial operations, warning operations, terminal errors, endpoint failures, and retention activity once per operation/request lifecycle; updating the persisted Last result with refill details no longer records the same invalidation twice.

= 2.59.09.87 =
* Replace separate endpoint/TTL-only Varnish capability signatures with one permanent SHA-256 fingerprint shared by HTML-only flush, authenticated two-stage refill, soft purge, refresh ahead, and the persisted behavior-test result.
* Bind empirical proof to integration mode, normalized endpoint set, invalidation method and strategy, flush scope, shared HTML TTL, stale-while-revalidate value, active orig/WebP/AVIF policy, `Vary: Accept` requirement, WordPress home/site and multisite context, admin-secret presence, and versioned UltraCache VCL/runtime contracts.
* Mark mismatched capability results as configuration-changed at read time so stale behavior tests lose verified/compatible/supported state and require a new Test Varnish run.
* Include a secret-derived but non-reversible origin-revalidation identity only inside the final fingerprint so WordPress salt/runtime-token changes invalidate old VCL proof, while diagnostics expose neither the Varnish secret nor the revalidation identity.
* Add bounded capability-fingerprint diagnostics and contract generations, keep endpoint ordering/case normalization stable, and exclude unrelated operational settings such as request timeout, warm switches, refresh limits, and pinned URLs from empirical capability identity.

= 2.59.09.86 =
* Redesign refresh ahead so the scanner performs only exact anonymous public Age probes and durable `page_warm` enqueue; it no longer soft-purges Varnish or changes cache state before a persistent queue row exists.
* Move refresh-ahead eligibility recheck and soft purge into the atomic queue worker after claim ownership, then continue through the existing strict authenticated origin-refresh and all-bucket public refill pipeline only when the object is still near expiry or already stale.
* Persist bounded refresh-ahead purge phases and failed endpoint subsets in the existing queue state, retry only failed endpoints, resume directly after a recorded completed purge, and invalidate stale endpoint state when the configured endpoint set changes.
* Add fair per-candidate probe scheduling with `lastProbedAt`, `nextProbeAt`, `probeCount`, bucket, result, and Age state; never-probed and increasingly overdue candidates gain bounded priority so pinned/home pages cannot starve lower-priority sitemap or analytics candidates.
* Keep site-flush refill selection priority-based and independent of refresh-ahead due scheduling, skip already queued URLs without consuming the run probe budget, and apply bounded next-probe timing for fresh HIT, MISS, transient error, pending, and queued outcomes.
* Use WordPress HTTP APIs with zero redirects, an exact trusted local URL, no cookies, and no UltraCache internal markers or runtime token for refresh-ahead probes, preserving authenticated headers exclusively for actual internal origin rebuild and refill work.

= 2.59.09.85 =
* Stop page-warm, Varnish refill/verification, and CSS source loopbacks from following redirects; HTTP 301/302/303/307/308 now finish as explicit canonical-URL mismatches instead of warming or scanning a different final destination.
* Require every UltraCache internal execution context to present both the internal marker and a valid runtime-control token, so public clients cannot alter page-build concurrency, lock waits, CSS on-entry behavior, or warm-request cookie handling by spoofing headers.
* Authenticate ordinary warm requests as well as force-refresh requests, require the dedicated warm or CSS context marker where applicable, and reject CSS scan query flags that are not backed by the authenticated loopback contract.
* Validate Varnish refill targets as exact trusted frontend loopback URLs before dispatch, fail closed when an internal token cannot be generated, and classify invalid-target/authentication failures as terminal rather than retrying them as network errors.
* Report refused redirects with dedicated canonical failure classes and preserve the exact queued URL identity across HTML warm, Varnish variants, HIT verification, and CSS source discovery.

= 2.59.09.84 =
* Replace all-or-nothing queued Varnish invalidation results with authoritative per-URL/per-endpoint accounting for bounded admin/HTTP BAN batches, exact HTTP PURGE, and soft PURGE; partial endpoint success is no longer applied as the same result to every queue row.
* Add permanent failed-endpoint retry state to the shared queue schema so each URL retries only the Varnish endpoints that actually failed, while a newer invalidation request clears the subset and runs every configured endpoint again.
* Bind retry subsets to the endpoint configuration generation that produced them; when the configured endpoint set changes, the row discards the stale subset and invalidates the complete current endpoint set instead of silently omitting added or removed infrastructure targets.
* Queue refill only for URLs whose required endpoint set completed successfully, keep partial/transient URLs pending with bounded retries, finish non-retryable endpoint/configuration failures as terminal errors, and report actual network request, completed, partial, retrying, and failed counts in the Varnish dashboard.
* Keep detailed per-URL transport state in memory only for the active worker and exclude it from the persisted last-result transient, retaining bounded aggregate diagnostics without growing the stored Varnish result with every URL/endpoint combination.

= 2.59.09.83 =
* Rebuild Varnish admin-secret authentication so every retry opens a new CLI connection, reads that connection’s current challenge, and calculates a fresh SHA-256 authenticator from the matching secret material instead of reusing a token from an earlier challenge.
* Preserve the exact externally defined admin secret bytes while retaining bounded LF/no-trailing-line-break compatibility attempts, without exposing the secret, challenge, or authenticator in diagnostics.
* Add bounded complete-write handling for Varnish CLI commands and reject empty, oversized, or control-character-bearing BAN expressions before opening the admin connection, preventing command-boundary injection through malformed expressions.
* Keep authenticated `ban` and bounded `ban.list` as the only admin commands issued by the transport, preserve direct VCLI `200` banner handling, and bound accepted secret, command, and response sizes.

= 2.59.09.82 =
* Renew the claimed queue lease and URL-scoped warm lock through bounded heartbeats around HTML variants, CSS generation, Varnish refill, and HIT verification; stop processing and preserve authoritative ownership when either token is lost.
* Classify page-pipeline failures as transient or terminal so only network/time-budget, retryable HTTP, and cache-write failures receive bounded retries; ineligible endpoints, configuration failures, and strict origin-proof failures now finish without blind reruns.
* Treat successful Varnish refill with bypassed, inconclusive, unavailable, or not-HIT verification as a completed pipeline with an explicit warning instead of repeating HTML, CSS, and refill work solely because diagnostic HIT evidence was incomplete.
* Require every requested orig/WebP/AVIF HTML bucket to complete before the HTML stage succeeds, reporting partial-variant writes as failures instead of silently accepting a single cached bucket.
* Keep manual warm-up verification non-destructive by returning warning metadata and displaying the actual HIT verification status without failing an otherwise completed manual page warm.

= 2.59.09.81 =
* Add atomic claim tokens and bounded processing leases to shared page-warm, CSS, LCP-refresh, and queued Varnish invalidation rows so a worker can persist a result only while it still owns the authoritative queue row.
* Verify the permanent claim schema after `dbDelta()`, recover expired processing leases back to pending runtime state, preserve active claims during ordinary and scheduled retention cleanup, and expose processing separately from planned and retrying work.
* Coalesce requests that arrive during processing by marking the owned row for one rerun instead of deleting or replacing it; the current worker releases ownership and the upgraded request runs with fresh attempts.
* Increment attempts only after a row is actually claimed, condition completion updates on both processing status and claim token, and return lock-coalesced rows to pending without recording a failed execution.
* Remove the remaining one-time Varnish HTML TTL migration hook and its obsolete marker option so the plugin contains no Varnish test-era migration or automatic cleanup path.

= 2.59.09.80 =
* Remove the one-time legacy Varnish refill migration and every runtime reference to the obsolete `varnish_refill`, `varnish_refill_soft`, `targeted_warm`, and `targeted_warm_soft` queue types; no automatic cleanup or conversion of test rows is performed.
* Consolidate HTML warm work under the permanent `page_warm` queue type and store strict soft-purge origin requirements in the dedicated `requires_verified_origin` column instead of encoding behavior in separate job-type names.
* Coalesce ordinary and targeted page-warm requests through the queue unique key without delete-and-reinsert behavior, preserving stricter origin requirements and targeted source context when the same URL is queued again.
* Update Varnish queue statistics, refresh-ahead duplicate detection, queue priority, retention, and shared warm execution to use the new page-warm contract while leaving atomic worker claiming for the next version.

= 2.59.09.79 =
* Migrate pending/error legacy `varnish_refill` and `varnish_refill_soft` rows into the shared targeted page-warm pipeline, remove completed legacy rows, and stop every active producer from creating detached refill jobs.
* Add unified warm queue lifecycle states for planned, retrying, completed, skipped, and failed page work, with bounded retry delays for transient per-page pipeline failures and terminal skipped handling for ineligible endpoints.
* Aggregate Varnish refill outcomes by manual, cron, warm-after-flush, scheduled-cleanup, targeted-purge, refresh-ahead, and CLI context while retaining bounded overall metrics outside the queue table.
* Prune completed auxiliary invalidation/page-warm rows after their retention window and keep the existing shared pipeline, per-URL lock, strict soft-purge origin proof, and orig/WebP/AVIF verification behavior unchanged.

= 2.59.09.78 =
* Route targeted Varnish invalidation follow-up work into the shared per-page warm pipeline instead of creating new detached `varnish_refill` rows.
* Add shared targeted warm queue sources for hard invalidation and strict soft purge, using the existing cron/manual ownership model, feed/non-HTML preflight, orig/WebP/AVIF refill, and optional HIT verification.
* Require verified authenticated origin refresh for strict soft-purge page warming and stop before public refill when that proof is unavailable; one-stage fallback remains blocked.
* Coalesce targeted, site-warm, legacy refill, manual, cron, and warm-after-flush work by URL through queue upgrades and a shared per-URL pipeline lock so the same page is not processed concurrently by multiple sources.

= 2.59.09.77 =
* Run ordinary cron and warm-after-flush pages through the shared per-page HTML, optional CSS, direct Varnish variant refill, and optional HIT-verification pipeline before marking the same warm queue row complete.
* Apply the existing Varnish-with-site-warm-up switch consistently to dashboard, cron, and warm-after-flush jobs, while keeping LCP-only refresh jobs outside the site Varnish warm flow.
* Stop creating detached critical `varnish_refill` jobs after a site-wide flush; the configured warm-after-flush job now performs Varnish work per page, and known non-HTML targets finish as skipped instead of cron errors.
* Give active dashboard/cron site warm-up priority over auxiliary persistent Varnish queue and refresh-ahead work so the requested per-page pipeline uses the current run budget first.

= 2.59.09.76 =
* Split dashboard full-site and menu warm jobs into resumable per-page HTML, optional CSS, direct Varnish orig/WebP/AVIF refill, and final HIT-verification stages, with the active URL and stage shown in the existing long-job modal.
* Persist a checkpoint after every completed page stage so Pause, browser interruption, and Resume continue from the next unfinished stage without creating detached `varnish_refill` queue jobs for manual warm-up.
* Prevent WooCommerce `woocommerce_recently_viewed` from making authenticated UltraCache internal warm and Varnish refill requests uncacheable, while leaving normal visitor cookie behavior unchanged.

= 2.59.09.75 =
* Add a unified per-page warm pipeline contract for dashboard/manual warm actions, preserving existing REST result fields while reporting HTML, CSS, Varnish refill, and HIT-verification stages separately.
* Complete all selected stages for one page before reporting that page as successful; a selected Varnish or verification failure now fails the same manual warm item instead of creating detached follow-up work.
* Reject known feed, REST, XML, JSON, RSS, Atom, sitemap, and XML-RPC endpoints before issuing an HTML warm request, while leaving cron and warm-after-flush consolidation for the next roadmap steps.

= 2.59.09.74 =
* Rotate refresh-ahead Age probes across the active orig, WebP, and AVIF HTML buckets instead of always probing AVIF first, while retaining all-bucket refill and optional HIT verification for eligible pages.
* After a successful site-wide Varnish flush, queue a bounded highest-priority refill set from the existing multi-source candidate registry, capped at 25 URLs by default instead of attempting a full-site refill.
* Add refill-queue deduplication/backpressure metadata and a bounded 100-URL pending cap so large invalidation bursts cannot create unbounded refill work.

= 2.59.09.73 =
* Replace the Cache Statistics-only refresh-ahead list with one bounded multi-source registry combining the front page, posts/shop pages, navigation menus, pinned critical URLs, recent purge/refill activity, optional analytics observations, and cursor-based WordPress sitemap discovery.
* Add a visible pinned critical URLs field and candidate-source diagnostics, while allowing refresh ahead to operate without Cache Statistics and without adding a frontend beacon.
* Store the candidate pool in one non-autoloaded capped option, reuse the existing cron/queue/lock flow, and remove the registry during plugin data cleanup and uninstall.

= 2.59.09.72 =
* Add a site-specific VCL pass contract for authenticated UltraCache force-refresh and revalidation requests, derived from WordPress salts without storing the signature in plugin settings.
* Extend Test Varnish with explicit proof that every active HTML bucket reached the WordPress origin, and require that proof before soft purge can be verified or selected.
* Preserve soft-purge refill semantics in the persistent queue and block the ordinary one-stage fallback when a soft-purged URL can no longer complete verified origin revalidation.

= 2.59.09.71 =
* Extend Test Varnish with bounded non-canonical browser Accept profiles and report raw Accept normalization as Normalized, Fragmented, Inconclusive, or Not required.
* Add a policy-aware VCL fragment that collapses HTML document Accept headers to the active UltraCache orig/WebP/AVIF buckets without modifying server configuration automatically.
* Add an Accept normalization status row and copyable VCL fragment inside the existing Varnish status accordion.

= 2.59.09.70 =
* Preserve explicit HTTP and HTTPS schemes for administrator-configured Varnish HTTP endpoints instead of silently forcing HTTP; scheme-less host:port endpoints remain HTTP for backward compatibility.
* Treat Varnish admin CLI status 201 from ban.list as a successful truncated response, report Partial lower-bound ban-pressure metrics, and keep optional ban-list diagnostics separate from endpoint health.
* Record manual dashboard Varnish refill verification in bounded aggregate metrics and present confirmed one-stage refill fallback and admin-BAN refresh-ahead availability accurately.

= 2.59.09.69 =
* Correct the unified Varnish test status so successful behavior verification also reports connection/authentication and invalidation-command stages as verified.
* Normalize legacy or unreadable ban-pressure results to neutral Unavailable status instead of retaining the earlier error state.
* Prefer the latest unified-test ban-pressure result in dashboard diagnostics so the accordion updates immediately and remains consistent after reload.

= 2.59.09.68 =
* Replace the two Varnish test buttons with one Test Varnish action that runs the complete public cache-behavior, invalidation, variant, TTL, conditional-revalidation, HTML-only, and optional admin diagnostic sequence.
* Keep authenticated ban-list inspection as an optional diagnostic that no longer changes endpoint health when it is unavailable or unreadable.
* Add explicit connection/authentication and invalidation-command stages to the Varnish status accordion.

= 2.59.09.67 =
* Set the Varnish shared HTML TTL default to 1440 minutes and migrate the earlier 0/60-minute default values once.
* Move the complete Varnish status and test output into a collapsed accordion that opens automatically when either Varnish test starts.
* Remove the admin-socket warning and current-mode explanatory footer from the Varnish card.

= 2.59.09.66 =
* Made HTML-only Varnish capability detection topology-agnostic by verifying the HTML HIT → invalidation → MISS/STALE → HIT sequence independently from the public static delivery route.
* Classify static delivery as through Varnish, explicit Varnish bypass, Varnish-visible but unverified, or outside/unobservable; require static preservation only when a real Varnish static HIT exists.
* Separate Automatic eligibility from manual HTML-only eligibility, expose the static route and preservation result in the Varnish card, and show the actual behavior-test result message instead of a generic completion notice.
* Remove the bounded Varnish metrics option from the dashboard Delete All Plugin Data flow as well as normal uninstall.

= 2.59.09.65 =
* Added bounded per-endpoint Varnish health, average latency, consecutive-failure, and last-success/failure metrics without writing to the database for every individual endpoint request.
* Added aggregated invalidation, batching, refill-verification, and persistent queue retry counters to the existing Varnish card.
* Added a narrowly scoped authenticated admin-mode `ban.list` inspection with bounded response size and active, completed, request-dependent, and object-only ban-pressure diagnostics; no arbitrary Varnish CLI execution was introduced.

= 2.59.09.64 =
* Added capability-gated hot-page refresh ahead using the existing Cache Statistics summary, Varnish Age, shared HTML TTL, verified soft purge, the persistent refill queue, and WP-Cron.
* Added bounded controls for refresh threshold and maximum pages per scan, with no frontend analytics beacon and no new queue table or scheduler.
* Added Varnish-card diagnostics for candidate count, runtime prerequisites, and the latest bounded refresh-ahead scan.

= 2.59.09.63 =
* Added representation-specific ETag and Last-Modified validators to PHP page-cache and advanced-cache.php HTML delivery.
* Added standards-based If-None-Match and If-Modified-Since handling with bodyless 304 responses for fresh GET/HEAD cache hits while preserving full-body delivery for UltraCache STALE objects.
* Extended Test Cache Behavior and the Varnish card with ETag availability, Last-Modified availability, public conditional 304 diagnostics, and Apache/PHP source reporting when visible.

= 2.59.09.62 =
* Added capability-gated stale-while-revalidate controls for public UltraCache HTML responses.
* Applied the shared stale refresh window consistently to PHP cache delivery, advanced-cache.php, and Apache Static HTML Delivery.
* Extended Test Cache Behavior and the Varnish card to distinguish emitted headers from verified stale/grace and HIT behavior.

= 2.59.09.61 =
* Added capability-tested HTTP soft purge with stale/grace verification and automatic queued refill.
* Added Automatic, BAN, PURGE, and Soft purge + refill invalidation strategies to the Varnish card.
* Kept hard invalidation as the runtime fallback whenever soft purge is unverified or the endpoint configuration changes.

= 2.59.09.60 =
* Add empirical two-stage Varnish refill: authenticated UltraCache force-refresh rebuilds the active inner HTML variants first, followed by normal public requests that populate Varnish.
* Verify the origin stage with the existing `X-Ultra-Cache-Force-Refresh: wp-engine` marker; when Varnish serves or hides the force-refresh request, use the existing one-stage fallback instead of claiming origin access.
* Show two-stage availability and queued-refill origin-stage counts in the Varnish card, and report verified origin refresh or fallback in manual warm-up logs.

= 2.59.09.59 =
* Add optional post-refill Varnish HIT verification for each active orig, WebP, and AVIF HTML variant, using one additional normal public request per variant.
* Keep refill success separate from verification evidence: hidden headers report Inconclusive, bypassed or repeated MISS responses are reported explicitly, and verification does not fail an otherwise successful refill.
* Show verification controls and queued-refill counters in the Varnish card, and add Varnish warmed, HIT verified, bypassed, and inconclusive counters to the manual warm-up popup and completion summary.

= 2.59.09.58 =
* Added persistent affected-page Varnish refill after successful targeted invalidation.
* Added optional Varnish warming for dashboard manual cache warm-up requests across active HTML variants.
* Reused the existing UltraCache warm queue and WP-Cron worker; no additional queue table or scheduler was introduced.

= 2.59.09.57 =
* Add an optional Varnish HTML TTL that emits a positive `s-maxage` only for verified public HTML cache responses, while leaving existing Varnish policy untouched when set to 0.
* Apply the same shared-cache contract to PHP page-cache hits, successful fresh stores, advanced-cache.php delivery, and Apache Static HTML Delivery without marking bypassed or private responses as public.
* Extend Test Cache Behavior and the Varnish card with shared-TTL diagnostics that distinguish an observed header on a verified HIT from missing or inconclusive evidence.

= 2.59.09.56 =
* Use one canonical orig/WebP/AVIF HTML variant policy across PHP cache delivery, advanced-cache.php, warm bucket selection, and Apache Static HTML Delivery; inactive media rewriting now uses only the orig bucket.
* Send `Vary: Accept` only when active HTML image rewriting can change the cached document, while retaining `Vary: Accept-Encoding` for compressed HTML and exposing the selected UltraCache variant when Varnish or debug headers are enabled.
* Extend Test Cache Behavior and the Varnish card with active-bucket diagnostics and bounded canonical Accept-profile checks that report compatible, fragmented, or inconclusive Varnish variant handling.

= 2.59.09.55 =
* Add Automatic, HTML pages only, and Entire host scopes for site-wide Varnish flushing, while retaining an explicit entire-host action in the existing Varnish card.
* Extend Test Cache Behavior with a local static-object probe and enable HTML-only flushing only after cached HTML is invalidated, the static object remains a Varnish HIT, and the HTML object refills successfully.
* Fall back to the existing entire-host flush whenever HTML-only behavior is untested, inconclusive, rejected, or broader than HTML, and invalidate the stored capability when the Varnish endpoint configuration changes.

= 2.59.09.54 =
* Add persistent `varnish_invalidate` and reserved `varnish_refill` jobs to the existing cron warm queue, with deduplication, bounded endpoint-aware processing, three attempts, and delayed retries.
* Keep small targeted Varnish invalidations synchronous, while queueing large URL sets or endpoint fan-out so post and product saves are not blocked by many network requests.
* Preserve pending Varnish jobs across ordinary warm resets, manual warm priority, cache flushes, and cron state changes; process them before ordinary warm work and show pending invalidation, refill, and failed-job counters in the Varnish card.

= 2.59.09.53 =
* Normalize, validate, and deduplicate targeted Varnish invalidation URLs before contacting configured endpoints, rejecting external, unsupported, unsafe-query, and oversized targets while honoring active page-cache exclusions.
* Combine exact URL paths into bounded per-host BAN batches for HTTP BAN and admin-secret mode, while preserving one exact request per unique URL for HTTP PURGE.
* Show received, unique, duplicate, rejected, batch, and request counts for the latest targeted Varnish invalidation in the existing Varnish card.

= 2.59.09.52 =
* Add a public Varnish cache behavior test that performs repeated front-page requests, targeted invalidation, immediate refill, and conservative HIT/MISS/STALE/BYPASS classification.
* Show per-step cache behavior results in the existing Varnish card, including HTTP status, Age, UltraCache source, timing, and an explicit Inconclusive result when Varnish headers are hidden.

= 2.59.09.51 =
* Split the Varnish PHP integration into focused settings, endpoint, transport, invalidation, and diagnostics traits without changing purge behavior.
* Split the Varnish dashboard UI and controller into dedicated local admin modules while preserving the existing card and actions.

= 2.59.09.50 =
* Make Media Regeneration crash-resumable: renew the shared processor lease between atomic media units, recover abandoned processing rows back to pending after the expired lease is replaced, preserve regeneration cursors, and never count an interrupted claim as a conversion failure.
* Add graceful WP-CLI SIGINT/SIGTERM handling so Ctrl+C stops after the current atomic media unit, persists queue state, and releases the processor lock instead of leaving manual recovery work.

= 2.59.09.49 =
* Allow the Media Library Replacement Theme CSS inventory table through the central custom-table validator so Prepare can create and verify the complete registry schema.
* Add a typed ok backup warning before a new or failed Prepare and before Restart Replacement Plan; Resume continues from existing server state without asking again.

= 2.59.09.48 =
* Replace the LCP observer viewport bucket's layout-dependent clientWidth/innerWidth read with matchMedia breakpoints, avoiding the forced reflow attributed to lcp-observer.js while preserving the existing mobile, tablet, and desktop thresholds.

= 2.59.09.47 =
* Render each discovered LCP URL as an independent inline accordion: details load directly below the selected URL, clicking the same URL closes it, and opening another URL leaves existing details open without preloading unopened rows.
* Replace the compact LCP viewport lookup's dynamically assembled prepared SQL with one fixed ten-slot placeholder query, eliminating the WordPress.DB.PreparedSQL.NotPrepared error without suppressing the database check.

= 2.59.09.46 =
* Fix the LCP URL detail REST schema to accept the stored 64-character SHA-256 page hash, matching the list payload and detail handler so selecting a discovered URL no longer fails with rest_invalid_param.

= 2.59.09.45 =
* Move the LCP Diagnostics & Settings accordion above Media settings & Media Library replacement as a full-width card.
* Fix the compact LCP URL list, cursor pagination, and click-to-load details to validate the stored SHA-256 page hashes instead of incorrectly expecting SHA-1 hashes; treat a single * search as no filter.

= 2.59.09.44 =
* Require manage_options plus activate_plugins or manage_network_plugins for Redis and Varnish configuration, secret changes, connection tests, and manual flushes, while keeping APCu, SQLite, and Disk test/flush actions available with manage_options.
* Apply the same stronger permission to Flush All Cache only when it is configured to include an active Varnish integration, and expose a dashboard capability flag that disables protected Redis/Varnish controls without relying on the UI as the security boundary.

= 2.59.09.43 =
* Rename the section to LCP Diagnostics & Settings and move the administrator-only audience and discovery-duration controls into it, while keeping the master LCP Frontend Discovery switch below LCP Image Priority.
* Remove LCP observation records from the global dashboard diagnostics payload. Opening the accordion now loads only a compact page of 10 discovered URLs, with cursor pagination that requests the next or previous page only after the corresponding button is pressed.
* Add a separate URL-detail endpoint so selectors, resources, observations, candidate evidence, refresh state, and mapping actions are loaded only after an administrator selects one URL. The browser keeps only the current URL page and one selected detail payload.

= 2.59.09.42 =
* Add optional LCP Frontend Discovery below LCP Image Priority with public or administrator-only audience, durations from one hour to indefinitely, and defaults of disabled, public, and indefinite. URLs containing query parameters are rejected by both the frontend observer and server endpoint, and finite-duration cached observer configurations stop locally at expiry.
* Use the first valid browser observation immediately, then lock one persistent mapping per page and viewport when the same candidate appears in two of the last three visits. Locked scopes stop loading or reporting through the observer, while Forget and Relearn reset the stored row without creating per-visit learning transients.
* Replace authenticated per-page learning sessions with persistent database learning state, migrate existing confirmed mappings as locked, remove legacy LCP learning/pending/cooldown transients, and keep page-specific purge and warm-refresh updates only when the active candidate changes or becomes locked, and invalidate cached frontend HTML when discovery enablement, audience, or duration changes.

= 2.59.09.41 =
* Require the existing file-mutation permission for settings updates that change Apache Static HTML Delivery, Gzip, or Brotli, matching their existing `.htaccess` side effect without changing the settings persistence or reconciliation flow.

= 2.59.09.40 =
* Remove the residual `ultracache_crawl_scope_summary` option and site option during full plugin uninstall, including the final critical cleanup pass so loaded shutdown callbacks cannot leave it behind.

= 2.59.09.39 =
* Remove anonymous authority from browser-observed LCP learning. Confirmed mappings, cache purges, preload changes, and refresh-queue jobs can now be changed only through an authenticated administrator learning session scoped to one page and viewport with a WordPress nonce.
* Add authenticated Start learning for pages without an existing mapping and authenticated Relearn for existing mappings. Automatic mode requires two matching observations inside the same expiring session, manual mode accepts only currently configured selectors, and existing confirmed mappings remain unchanged until an administrator explicitly starts learning.

= 2.59.09.38 =
* Verify the complete transformed Theme CSS temporary file with the prepared streamed checksum before committing it, then verify the actual active CSS target in resumable chunks before marking replacement rows as applied. Missing-temp and legacy committed-state recovery now accept a prior rename only when the active file checksum matches the prepared output, not merely its size.

= 2.59.09.37 =
* Correct the default/native dashboard Help modal title styling so the title uses WordPress dark text on the white modal background. Separate the native title-color rule from the FAQ panel border/background rule.

= 2.59.09.36 =
* Remove the 5 MB Theme CSS cutoff. Scan and validate CSS files of any total size through persisted byte offsets, bounded per-request chunks, and boundary carry so large files resume without being loaded fully into memory.
* Apply all prepared replacements for each Theme CSS file through an exact streamed backup and a separate transformed temporary file. Commit the active CSS only after the complete source checksum and every prepared replacement are confirmed, with resumable reconciliation around interrupted file commits.
* Verify transformed Theme CSS files in resumable chunks and persist per-reference old/new-fragment evidence. Upgrade the Media Library Replacement schema additively from version 9 to 10 without dropping existing registry data, and clean Theme CSS temporary and backup directories during Delete All or uninstall.

= 2.59.09.35 =
* Replace the Theme CSS full-tree manifest build with resumable directory discovery persisted by cursor and a dedicated per-job CSS inventory table. Scan the inventory in bounded requests and validate the same file set through a second resumable traversal before Prepare can complete, without imposing a total file or directory limit.
* Upgrade the Media Library Replacement schema additively from version 8 to 9 so the new Theme CSS inventory table is created without dropping existing replacement registry tables. Remove runtime use of the legacy large manifest option and include the new inventory in restart, Delete All, and uninstall cleanup.

= 2.59.09.34 =
* Store automatic browser-observed LCP learning under one stable database identity per page and viewport. New candidates are confirmed through one expiring pending transient per page/viewport, preserving the current confirmed mapping until the replacement receives a second matching observation and preventing selector-driven database-row growth.
* Make public LCP observation throttling independent of the reported element selector, record refresh cooldown before cache purge or refresh-queue attempts, include selector changes in candidate equality and first-seen resets, and prune old legacy pending rows in bounded recurring cleanup batches without imposing a total page or record limit.

= 2.59.09.33 =
* Require the existing file-mutation capability boundary before a resumable Media Library Replacement Do job can start or continue when its prepared plan contains Theme CSS replacements, and repeat the guard immediately before Theme CSS files are written. Jobs without Theme CSS replacements continue to require only `manage_options`.
* Remove synchronous full-Media-Library fallback paths from REST and WP-CLI media processing. Media discovery and conversion now fail explicitly when the bounded persistent queue is unavailable instead of collecting or processing the full library in one request.

= 2.59.09.32 =
* Remove the Secret constants, detailed Media Library Replacement lifecycle, source/build-process, and Varnish disclosure sections from `readme.txt` and `README.md`, while keeping the concise feature and setup documentation.
* Move the complete Installation and must-do post-install block in the WordPress.org `readme.txt` to immediately before Screenshots. Documentation-only release; dashboard Help, FAQ, cache, media, and optimization runtime behavior are unchanged.

= 2.59.09.31 =
* Remove the complete 80-question FAQ from `readme.txt` and `README.md`, keeping the concise installation and must-do post-install workflow in both repository documents.
* Move the same FAQ into the version-specific dashboard Help modal, organized into eight collapsed topic groups with individually expandable questions, counts, keyboard-native details controls, and matching UltraCache/Native theme styles. Dashboard documentation only; cache and optimization runtime behavior is unchanged.

= 2.59.09.30 =
* Add a concise must-do post-install JavaScript compatibility check to `readme.txt` and `README.md`: test the public site in a private browser window, copy Console errors, analyze them in JS Defer / Delay Safeguards & Diagnostics, append the proposed safeguards, save both lists, flush cache, and warm the front page until the Console is clear.
* Expand the version Help modal with the detailed browser-testing workflow, correct private-window shortcuts for Chrome/Edge and Firefox, guidance for Defer Instead versus Do Not Defer or Delay, and the exact cache flush/front-page warm-up loop. Documentation and dashboard-help release; cache and optimization runtime behavior is unchanged.

= 2.59.09.29 =
* Expand `readme.txt` and `README.md` with a practical, user-facing FAQ covering public page cache, wp-admin and logged-in Object Cache behavior, WooCommerce exclusions, query strings, warm-up, CSS/JavaScript/fonts, automatic and manual LCP learning, AVIF/WebP conversion, media queues, Media Library Replacement, object-cache backends/drop-ins, integrations, diagnostics, storage, cleanup, and support.
* Clarify that `/wp-admin/` is never page-cached while enabled Object Cache still accelerates dynamic administration requests by reusing cached queries, options, and WordPress objects. Documentation-only release; runtime cache and optimization behavior is unchanged.

= 2.59.09.28 =
* Add a fixed top-right `Rate us!` dashboard link that opens the UltraCache WordPress.org review form in a new tab. Keep the existing version-specific Help control fixed at the lower-right corner and apply matching Native/UltraCache theme styling and keyboard focus treatment to both controls.
* Add a final `Still having questions?` support callout inside the version Help modal with a direct `Ask on forums` link to the UltraCache WordPress.org support forum. Both external links use `noopener noreferrer`; cache, media, and optimization runtime behavior is unchanged.

= 2.59.09.27 =
* Remove the final generated selector `IN (...)` and `NOT IN (...)` SQL fragments from persistent LCP storage. Manual-selector page lookup now uses one fixed prepared page query followed by validated hash matching in PHP, preserving database ordering and exact selector selection without dynamic placeholders.
* Synchronize configured LCP selectors with fixed prepared statements: confirmed automatic mappings are staled in one bounded update when manual mode is active, while distinct manual/legacy-browser hashes are compared against the configured set and only removed hashes are updated. This clears the four remaining Plugin Check prepared-SQL findings without suppressions or raw SQL fragments.

= 2.59.09.26 =
* Refactor LCP Diagnostics counts, filters, search, refresh-status handling, and updated_at/id cursor pagination so every database sink receives a fixed SQL template prepared directly with allowlisted values. Remove the generic `$attention_sql`, `$count_sql`, `$row_sql`, and `$queue_query` execution paths that triggered the remaining Plugin Check prepared-SQL findings.
* Join the one matching `lcp_refresh` queue row into each bounded diagnostics page instead of issuing a generated `IN (...)` status query, and cache the cron-warm queue table-existence check through the shared UltraCache object-cache key. Preserve Attention/Confirmed/Pending/Stale/All tabs, 20/50/100 limits, exact aggregate counters, queue-state filters, row actions, and last-successful-refresh fallback.

= 2.59.09.25 =
* Refactor the browser-observed LCP storage and lifecycle database paths so `wpdb::prepare()` is applied directly at each `get_row()`, `get_results()`, and `query()` sink. Exact-row lookup, manual-selector lookup, automatic mapping lookup, viewport winner lookup, atomic observation upsert, competing-mapping staling, and selector synchronization no longer pass generic prepared SQL variables into database methods.
* Keep dynamic selector `IN` / `NOT IN` clauses limited to generated placeholder lists while every table identifier and runtime value remains bound through `%i`, `%s`, or `%d`. Preserve the existing self-healing table retry, automatic/manual precedence, pending-to-confirmed behavior, winner replacement, relearn/forget lifecycle, and targeted LCP refresh flow without changing the observations schema.

= 2.59.09.24 =
* Remove the unused runtime atomic-file writer that could create temporary sibling files for arbitrary targets. Runtime configuration no longer contains a dormant generic PHP-file replacement path; the existing guarded WordPress drop-in writer remains limited to `advanced-cache.php` and `object-cache.php`.
* Harden the shared guarded write helpers so generic file writes may create only the inert `index.php` directory marker with the exact `Silence is golden` payload, while generic renames reject every `.php` target. Managed cache drop-ins continue through the dedicated allowlisted drop-in writer.

= 2.59.09.23 =
* Move the Media Library Replacement schema-upgrade lock from direct `add_option()` calls to the shared `{prefix}ultracache_locks` table. Acquisition is atomic, expired locks can be taken over, release is token-guarded, the existing 60-second lifetime is preserved, and a still-active legacy option lock is respected while an expired legacy row is removed.
* Restore the plugin-wide invariant of zero direct `add_option()` calls and keep Media Library Replacement table creation serialized through the existing central lock subsystem.

= 2.59.09.22 =
* Remove conflicting `advanced-cache.php` and `object-cache.php` files immediately after the administrator confirms the existing Remove action. UltraCache no longer creates, returns, or references PHP backups for foreign cache drop-ins; removal remains restricted to those two exact WordPress content-directory paths through the existing capability-protected REST action and canonical WP_Filesystem drop-in helpers.
* Delete the obsolete `uploads/ultracache/cache/backups/dropins/` directory through the guarded UltraCache filesystem cleanup path and remove the empty parent backup directory when possible. Dashboard conflict text and confirmation now describe permanent removal instead of backup-and-remove behavior.

= 2.59.09.21 =
* Replace the fixed lower-right version label with a keyboard-operable `Help for [installed version]` button that opens a responsive, theme-aware setup modal. The modal contains the practical Aggressive-profile setup guide for compression, warm-up scope, image conversion, font optimization, WooCommerce, MailerLite, object cache, Varnish, scheduling, and the first cache/media preparation run; it closes by button, overlay, or Escape and restores focus to the trigger.
* Expand the WordPress.org `Installation` instructions and repository README with the same concise quick-setup workflow and direct users to the version-specific dashboard help modal.

= 2.59.09.20 =
* Enable `Warm affected pages after save` and `Apache Static HTML Delivery (.htaccess)` in the Aggressive performance profile. Applying Aggressive now turns on targeted post-save warming and direct Apache delivery of eligible prebuilt anonymous HTML cache files, while the individual controls remain available for manual adjustment.

= 2.59.09.19 =
* Move the complete browser-observed LCP diagnostics interface out of Advanced Diagnostics into its own full-width `LCP Diagnostics` accordion placed immediately above Advanced Diagnostics. The existing counters, server-side tabs, filters, pagination, mapping details, refresh/relearn/forget actions, and themed confirmation dialog remain unchanged; Advanced Diagnostics now contains only the remaining server, cache, storage, security, and runtime inspection panels.

= 2.59.09.18 =
* Scale LCP Diagnostics for large sites with server-side tabs, URL/selector/resource search, viewport/source/resource/refresh filters, 20/50/100-row limits, indexed updated/status/source/viewport ordering, and stable updated_at/id cursor pagination. Advanced Diagnostics now opens on Attention, loads only one bounded result page, reports exact aggregate counts including failed refreshes, keeps row actions within the active filters/page, and avoids rendering or transferring the full observations table even when thousands of URLs have learned mappings.

= 2.59.09.17 =
* Add automatic browser-observed LCP learning when no manual LCP selector is configured. The generic PerformanceObserver now records the actual text, image, background-image, or video-poster candidate per page and viewport; automatic candidates require two matching anonymous visits before confirmation, manual selectors continue to take immediate precedence, a confirmed browser winner suppresses further speculative LCP selection for that response, exact observed `<img>` resources receive eager/high-priority markup, image-backed candidates reuse the existing targeted purge and `lcp_refresh` warm queue, text candidates do not create image preloads, and diagnostics identify automatic versus manual sources while explicitly explaining that logged-in refreshes are ignored.

= 2.59.09.16 =
* Fix creation and use of the dedicated LCP observations table by adding `ultracache_lcp_observations` to the central validated UltraCache custom-table allowlist. The table name now reaches schema creation, existence checks, diagnostics, browser-observation writes, and lifecycle cleanup instead of being rejected as an invalid custom identifier.

= 2.59.09.15 =
* Add browser-observed LCP diagnostics to Advanced Diagnostics with persistent summary counts, recent mapping details, viewport/selector/element/resource metadata, observation history, current warm-refresh state, and the last successful page-specific LCP refresh. Add themed confirmation actions to forget a mapping, retain it as stale and relearn, refresh only the affected page cache, or open the public page; all mutations use a capability-protected REST endpoint, the existing targeted purge and LCP warm queue, and no full-site or CSS-bundle rebuild.

= 2.59.09.14 =
* Harden browser-observed LCP lifecycle handling: confirmed mappings no longer expire after seven days; removed or older competing selectors are retained as stale diagnostics while only one confirmed winner per page and viewport can emit a preload; observation, storage, and refresh queue entry share the page-cache eligibility decision; resource validation accepts trusted WordPress public content/uploads/theme/plugin hosts including CDN-rewritten base URLs; the observations table verifies its real existence and repairs/retries after an unexpected removal; and LCP refresh jobs received during a manual warm-up remain deferred in the existing queue and resume automatically when the manual session ends.

= 2.59.09.13 =
* Make the Image conversion test dialog and the Plugins-screen deactivation dialog follow the per-user UltraCache admin theme selection instead of hard-coded dark colors or the operating-system color scheme. The dashboard modal now consumes the existing theme tokens and updates with an open-theme change; the deactivation dialog receives the stored admin theme through its localized configuration and applies matching native/UltraCache surfaces, text, borders, controls, focus states, and responsive actions.

= 2.59.09.12 =
* Store browser-observed LCP mappings in the dedicated `{prefix}ultracache_lcp_observations` table instead of one expiring transient map. The table keeps one confirmed mapping per normalized page URL, exact manual selector, and viewport; uses atomic observation-count updates, indexed page/resource lookups, bounded retention cleanup, lazy schema creation for active-plugin updates, activation-time creation, and complete uninstall/Delete All cleanup. No transient-data migration is included.

= 2.59.09.11 =
* Connect browser-observed LCP learning to the existing database-backed cron warm queue: changed page/selector/viewport mappings now purge only the affected page-cache variants while preserving generated CSS bundles, enqueue a priority lcp_refresh job, force-refresh all active page-cache buckets without rebuilding CSS bundles, avoid full-site crawl expansion for standalone LCP refreshes, de-duplicate pending URL refreshes, and apply a bounded retry cooldown to prevent repeated slider-driven purge/warm loops.

= 2.59.09.10 =
* Extend Delay icon fonts to matching same-origin stylesheets inserted dynamically after the initial HTML. UltraCache now holds the stylesheet on print media, patches its @font-face rules with font-display: swap before activation, restores the original media value, preserves the stylesheet's existing load callback, honors the visible include/exclude patterns, and exposes measured matching/patching cost through window.ultracacheIconFontDelayTiming and a DevTools User Timing entry.

= 2.59.09.09 =
* Keep SVG uploads unchanged when upload conversion is enabled: image/svg+xml files now bypass raster resize and AVIF/WebP encoding without producing or deleting the uploaded file.
* Improve Delay icon fonts discovery and matching: front-page HTML icon-family class tokens such as material-icons are included in scanner results, and visible include/exclude patterns match font-family and font-file names across spaces, hyphens, and underscores (for example material-icons, Material Icons, and MaterialIcons-Regular).

= 2.59.09.08 =
* Separated manual LCP element targeting from resource priority: selectors are preserved exactly, direct text targets act only as LCP boundaries, direct image/background/poster resources receive priority without descendant guessing, and dynamic targets learn their actual browser-observed resource per page and viewport for the next cached response. Added a generic PerformanceObserver helper, page-scoped HMAC/rate-limited observation storage with targeted cache purge, verified-resource preload injection including SVG, and restored the missing generic tag-processor candidate extractor.
* Kept Priority Preloads, request-chain delay entries, and CSS async exclusion lists editable while their runtime switches are off; stopped adding implicit ID/class prefixes to manual LCP selectors, accepted SVG throughout LCP discovery/preload/runtime matching, removed the SR7-specific module-background shortcut, and stopped anonymous inline scripts from being delayed by third-party content-pattern matching.
* Made the JS Defer / Delay and CSS Bundle safeguard diagnostics full-width dashboard sections, and moved update-triggered frontend purge execution into its own operation-focused engine trait without changing behavior.
* Added separate, profile-enabled purge controls for successful WordPress core, active plugin, and active parent/child theme updates; update purges invalidate page HTML and frontend asset maps once per operation, optionally flush configured external page caches and start the existing warm queue, while leaving object cache and optimized media untouched.
* Reorganized the dashboard so Query-string Args Caching sits directly below Cache Engine and Warm Cache, while JS and CSS safeguard diagnostics sit directly beneath their related frontend optimization panels; setting IDs and runtime behavior are unchanged.
* Documented the trusted internal media-replacement dependency exception for Plugin Check without changing runtime behavior.
* Added Media Library Replacement to promote verified AVIF/WebP rewrite variants into WordPress attachment originals and generated sizes, with attachment metadata, database-reference, and Theme CSS updates.
* Added a resumable, server-authoritative Check / Prepare / Do / Verify / Delete Originals workflow with persisted progress, pause/resume/retry, cross-browser recovery, concurrency leases, time budgets, and explicit destructive confirmations.
* Added readiness and pre-write validation that blocks mutation when generated destinations, attachment candidates, output policy, registry plans, database scans, or Theme CSS baselines are incomplete or have changed.
* Added guarded, idempotent verification and original cleanup, plus recovery foundations for metadata, database references, Theme CSS, and interrupted replacement stages.
* Added database-wide media-reference indexing and matching for the current WordPress table prefix, including serialized/JSON validation, deduplication, verification, bounded keyset cursors, and WP-CLI access through the same replacement engine.
* Added separate Image Output Format and Fallback Format controls plus a shared Image compression level for AVIF/WebP optimization, upload generation, regeneration, conversion tests, and Media Library Replacement.
* Added sample image conversion comparisons, registered intermediate-size coverage, exact reuse of matching existing variants, and opt-in regeneration of already optimized images with current quality settings.
* Improved the media dashboard workflow, long-job progress UI, queue repair/recount controls, status reporting, and reliable handling of interrupted or concurrently opened operations.
* Added and strengthened SQLite object caching, then refactored Redis, APCu, SQLite, Disk, and runtime-only behavior into explicit backend classes while preserving the WordPress object-cache API.
* Refactored large plugin components into smaller operation-focused files for media, settings, diagnostics, JavaScript, LCP, fonts, CSS bundles, warm-up, REST/profiling, lifecycle, server rules, and shared core helpers.
* Added targeted class loading and lazy component loading to reduce initial PHP parsing while preserving WordPress-compatible bootstrap order, hooks, REST, WP-CLI, and public APIs.
* Added deactivation and uninstall cleanup policies to the standard Plugins screen, with controlled retention or removal of settings, custom tables, runtime/cache files, and plugin-owned data.
* Fixed Apache Static HTML Delivery rule synchronization and aligned dashboard, Help, Diagnostics, and translation text with the existing query-string allowlist behavior.
* Hardened filesystem/path containment, table scope, confirmation tokens, capabilities, nonces, serialized-data handling, generated-file validation, permissions, and destructive cleanup guards.
* Updated WordPress.org metadata, translations, diagnostics, REST/WP-CLI parity, compliance-sensitive code paths, and release packaging.

= 2.59.07.61 =
- Route real upload conversion through the existing UltraCache AVIF/WebP encoder chain instead of using WordPress image-editor AVIF saves for final output. WordPress image-editor use is now limited to resizing the intermediate source when the configured maximum upload side requires it.
- Add a specific Convert new uploads help tooltip without fallback language; this control converts the uploaded attachment itself and reports encoder failures visibly.

= 2.59.07.60 =
- Move Maximum upload image side to Advanced settings and keep Convert new uploads at the end of the AVIF / WebP Batch Conversion box.
- Rename Generate on Upload to Rewrite on upload in the media settings UI.
- Make upload conversion failures self-diagnostic: the visible WordPress upload error now includes source file, detected/target MIME, editor class, destination filename, save return data and candidate output-file validation state.
- Validate the actual file written by the WordPress image editor from multiple WordPress save-result candidates before reporting a missing output file.

= 2.59.07.59 =
- Fix upload conversion output validation so successful WebP/AVIF saves are measured through the UltraCache filesystem helper before falling back to WordPress filesize helpers.
- Add debug context when upload conversion save validation fails after the image editor reports success.

= 2.59.07.58 =
* Adds real new-upload image conversion controlled from the AVIF / WebP Batch Conversion panel. When enabled, WordPress uploads are converted to the selected Image Output Format during the normal upload flow.
* Adds Maximum upload image side with a default of 1920. Larger uploaded images are resized proportionally before WebP/AVIF save; smaller images keep their dimensions and are only converted.
* Uses WordPress upload and image editor APIs for the new upload conversion path. Conversion failure returns a visible upload error instead of silently keeping the original file or switching format.

= 2.59.07.57 =
- Fixed manual warm-up handling so frontend loopback `write-failed` headers no longer stop a cacheable 200 HTML page from being written by the controlled manual warm-up flow.
- Fixed skipped manual warm-up URLs so REST 200 `skipped` payloads are shown as skipped instead of raw `/crawl-page` failures in the admin progress log.
- Simplified manual warm-up progress messages to report user-facing outcomes such as Cached, Cached + CSS, Skipped, or Failed instead of cache-file counts or internal CSS/HTML ordering details.

= 2.59.07.56 =
- Kept the six manual warm-up actions distinct by scope and mode while tightening the manual warm-up completion contract: HTML-only actions do not trigger automatic CSS bundle preparation, and HTML + CSS actions keep CSS bundle work inside the manual session.
- Changed manual crawl-page handling so non-200, empty, non-HTML, or cache-rejected URLs are marked as skipped without REST 500 retries, preventing repeated self-requests for the same failing URL.
- Moved per-page CSS bundle preparation until after the URL proves it returns cacheable HTML, preventing CSS scans for 404/feed/non-HTML URLs, and added in-session canonical URL de-duplication for manual warm-up runs.

= 2.59.07.55 =
- Added explicit Cache Engine wording for post-save warming as “Warm affected pages after save” and kept it disabled by default.
- Changed post-save warming so it warms only scoped affected URLs instead of using site-front/feed seed URLs from the broader purge helper.
- Skipped autosaves, revisions and auto-drafts for post-save warming, added a per-post cooldown, filtered feed URLs from that path, and prevented post-save warm requests from auto-starting CSS bundle scans or media-variant bucket loops.

= 2.59.07.54 =
* Add a General Inclusions accordion below General Exclusions and move Manual LCP selector, Priority Preloads, and Delay Non-Critical Request Chains into it.
* Rename the delayed font pattern list to Delay These Fonts / Icon Font and clarify that it can match any chosen font, while commonly being used for icon fonts.

= 2.59.07.53 =
* Split matching delayed icon-font @font-face blocks out of the generated font-mix CSS bundle so text/font-mix CSS can remain blocking while icon-font CSS is emitted through the delayed icon-font stylesheet path.
* Reuse the existing Delay icon fonts pattern list during font-mix bundle consolidation and keep the bundle replacement atomic when the delayed companion stylesheet is written.

= 2.59.07.52 =
* Add first-party and third-party parallel execution controls for frontend deferred and delayed JavaScript.
* Apply the parallel execution flags to native defer/async conversion and to delayed JavaScript lane replay.
* Keep ordered execution as the default for both JavaScript paths.

= 2.59.07.51 =
* Reworked the delayed JavaScript loader so non-third-party delayed scripts run first in their own ordered lane before delayed analytics, consent, embeds, and other third-party scripts.
* Released the jQuery-ready hold after the first-party lane instead of waiting for delayed third-party scripts, preventing third-party consent/analytics code from leaving basic frontend interactions inactive.
* Added per-script timeout/fail-forward handling for delayed external scripts so missing load/error events cannot leave a delayed lane active indefinitely.

= 2.59.07.50 =
* Hardened TranslatePress page-cache compatibility so the translated-output buffer only runs for frontend HTML GET/HEAD requests.
* Skipped the TranslatePress compatibility buffer for admin, AJAX, REST, cron, CLI, JSON, feed, robots, sitemap, WooCommerce AJAX, and other non-HTML request contexts.
* Kept the existing translated-HTML storage timing and UltraCache internal query-argument cleanup unchanged, including internal revalidation requests that generate public cache HTML.

= 2.59.07.49 =
* Fixed TranslatePress compatibility so UltraCache internal revalidation query arguments are stripped from cached frontend URLs before HTML is stored, preventing public language-switcher links such as /en/... from retaining ultracache_revalidate or ultracache_rt parameters.

= 2.59.07.48 =
* Fixed TranslatePress page-cache storage so translated URLs are cached after TranslatePress finishes its frontend output-buffer translation, preventing alternate-language URLs from storing or serving the default Greek HTML.
* Kept the normal non-TranslatePress cache path unchanged; the compatibility buffer is only activated on frontend page-cache requests when TranslatePress is detected.

= 2.59.07.47 =
* Replaced the SQLite WAL-size selector with an automatically saved maximum SQLite database-size selector using 32, 64, 128, 256, 512, 1024, and 2048 MB choices; the default is 256 MB.
* Enforced the selected main SQLite database-file limit with `PRAGMA max_page_count` and added an automatic disposable-cache rebuild when a reduced limit is below the current file size.
* Added proactive SQLite capacity maintenance that removes expired entries first and then the oldest cache entries when used pages reach 90% of the selected limit, targeting 80% after cleanup.
* Separated WAL maintenance from the user database-size setting with a 16 MB post-checkpoint retention target, 1000-page automatic checkpoints, and a non-blocking cross-process maintenance lock.

= 2.59.07.46 =
* Added an automatically saved SQLite WAL target-size selector with 32, 64, 128, 256, 512, 1024, and 2048 MB choices; new and invalid configurations default to 256 MB.
* Applied the selected SQLite WAL target consistently to the generated object-cache drop-in, SQLite runtime configuration, and WAL checkpoint maintenance threshold.

= 2.59.07.45 =
* Fixed SQLite object-cache write lockout when the WAL file exceeded its maintenance target, while retaining a hard combined database and journal size cap.
* Preserved failed SQLite add attempts in request-local cache without falsely reporting persistent success, preventing repeated `alloptions` database reloads during backend write failures.
* Verified SQLite set operations changed persistent storage before reporting success.

= 2.59.07.44 =
* Added a user-controlled stale-worker circuit-breaker threshold under Queue Missing Media During Page Generation, validated as a positive integer and stored in the existing UltraCache settings option.
* Moved the Media Worker Safety status below the related missing-media queue controls.
* Reworked rolling stale-worker tracking to use bounded time buckets plus the latest 25 diagnostics, allowing large thresholds without storing one full option record per incident.
* Preserved the stale-worker count and latest quarantine diagnostics that opened a global pause until an administrator explicitly resumes media generation.
* Fixed PHP 8.4 nullable-parameter deprecation warnings in font CSS rewriting and the object-cache REST endpoint.

= 2.59.07.43 =
* Removed the top divider from the Media Worker Safety summary.

= 2.59.07.42 =
* Changed: Added an always-visible, compact five-line Media Worker Safety summary directly below the existing optimized-image, media-queue, and queue-health statistics. No separate dashboard card was added.
* Changed: The summary reports the current safety status, recent stale-worker incidents against the rolling threshold/window, remaining cooldown, latest quarantined attachment and timestamp, and the automatic queue action.
* Changed: Removed duplicated incident counts and cooldown timing from the background-control helper text; detailed state now has one stable location in the media summary.

= 2.59.07.41 =
* Replaces the one-strike global media pause with a per-item quarantine: a stale `processing` row becomes `failed`, remains excluded from automatic retries, and can be returned explicitly through Retry Failed.
* Adds a three-minute quiet-period cooldown after each stale worker so the previous PHP process has time to terminate before another media worker may start.
* Tracks stale-worker incidents in a rolling 30-minute window. The global media circuit opens only after three incidents in that window; the threshold, window, and cooldown remain filterable through `ultracache_media_stale_worker_threshold`, `ultracache_media_stale_worker_window_seconds`, and `ultracache_media_stale_worker_cooldown_seconds`.
* Rejects signed loopback workers, cron workers, automatic dispatch, and dashboard conversion while the cooldown is active, while preserving a single delayed cron continuation for automatic recovery.
* Clears rolling incident history only on an explicit administrator resume, preventing an accidental request from silently resetting the global safety threshold.
* Exposes cooldown time, recent incident count, threshold, and quarantined-item diagnostics in media queue state; the dashboard disables manual conversion during cooldown and shows the remaining quiet period.
* Adds uninstall cleanup for the new bounded stale-worker state option.

= 2.59.07.40 =
* Prevents a stalled media encoder from exhausting PHP-FPM by failing closed when a media queue claim exceeds its processing lease instead of automatically recycling the row to `pending`.
* Opens the persistent media background circuit breaker, clears the watchdog cron event, preserves bounded stale-item diagnostics, and requires an explicit administrator resume before any further automatic media work can start.
* Blocks immediate, cron, on-demand, and dashboard dispatch while another media queue row is still `processing`, so an expired dispatcher lock cannot create a replacement worker beside a potentially live PHP process.
* Stops self-chaining HTTP workers after each successful unit; the next bounded unit is scheduled through one delayed cron event instead.
* Makes queue completion claim-safe by requiring the original status, attempt number, and start timestamp before a worker may persist its result, preventing a delayed worker from overwriting a circuit-breaker or newer claim state.
* Treats an expired media processor lock as lost ownership and prevents the expired owner from finalizing queue state.
* Replaces the on-demand affected-page select-then-insert sequence with an atomic upsert, removing the confirmed duplicate-key race under concurrent frontend discovery.

= 2.59.07.39 =
* Prevents authenticated dashboard requests from causing false `DONOTCACHEPAGE` failures during manual warm-up.
* Honors each frontend loopback response so a URL that genuinely bypasses page cache fails independently while the remaining warm-up queue continues.

= 2.59.07.38 =
* Manual dashboard warm-up now bypasses the existing UltraCache page cache and atomically replaces each cache entry after successful generation.
* Authenticates internal force-refresh requests and bypasses Apache static delivery for those requests.

= 2.59.07.37 =
* Gives manual full-site and menu warm-up priority by stopping and clearing the cron warm queue before the dashboard crawler starts.
* Blocks cron warm starts, ticks, and scheduled cache cleanup while a manual warm-up is active or paused, and releases the block after completion or cache-generation reset.
* Persists authenticated manual warm-up ownership across pause and resume so scheduled cleanup cannot start a competing cron crawler.

= 2.59.07.36 =
* Fixes false Brotli detection in the HTML compression capability probe and restores Gzip selection when the server does not provide compression.

= 2.59.07.35 =
* Makes the HTML compression probe use an HTML response and forces the selector to Server managed when server-level Gzip or Brotli is detected.
* Hardens the SQLite object-cache backend with atomic add/replace/counter operations, persistent write-result handling, restrictive storage permissions, storage limits, secure deletion, and public-access verification.
* Restricts Apache static HTML delivery to trusted site hosts and applies quality-aware `Accept-Encoding` negotiation to the advanced-cache delivery path.
* Resolves the reported Plugin Check findings in the AVIF self-test and SQLite object-cache manager.

= 2.59.07.34 =
* Removes environment-specific deployment references from public release documentation.
* Keeps release history exclusively in `changelog.txt`; `readme.txt` now contains only plugin information and usage documentation.

= 2.59.07.33 =
* Fixes the WordPress early-hit page-cache path so it serves available Brotli or Gzip variants according to the request `Accept-Encoding` values.
* Sends matching `Content-Encoding` and `X-UltraCache-Encoding` headers for compressed early cache hits.

= 2.59.07.32 =
* Probes server-managed compression and PHP Gzip/Brotli support before opening the HTML Compression selector, then enables only the supported choices.
* Adds compressed Apache static HTML aliases with matching `Content-Encoding`, `Vary`, and UltraCache source headers.
* Clears the existing HTML page cache when compression or Apache static delivery mode changes so new aliases are rebuilt consistently.

= 2.59.07.31 =
* Shows Redis, APCu, SQLite, and Disk in one row on desktop, two columns on tablet, and one column on mobile.
* Expands the SQLite backend test with explicit Write, Read, Delete, and Expiration results in the Object Cache status panel.

= 2.59.07.30 =
* Adds SQLite as a fourth selectable WordPress object-cache backend for single-server sites with the PHP SQLite3 extension.
* Implements persistent signed-payload storage with WAL mode, expiration, global groups, multisite isolation, group flush, full flush, and bounded cleanup of expired entries.
* Adds SQLite availability, version, journal mode, entry count, storage size, read/write testing, fallback selection, profile auto-detection, and dashboard flush controls.
* Stores the database in the protected UltraCache object-cache directory and keeps SQLite database, WAL, and shared-memory files intact when the Disk backend is flushed.

= 2.59.07.29 =
* Removes six unreachable functions from `includes/admin/js/app.js`: the unused Cache Analytics card, committed-settings reset helper, asynchronous action-state helper, duplicate CSS bundle scope accessor, obsolete Safe Defer toggle helper, and the unrendered latest-profile JS safety loader.
* Removes the matching unreachable debug-profile handler, state, and prop plumbing from `includes/admin/js/diagnostics.js`. Browser Scanner, Runtime Scan, Console Error Handler, DB-backed diagnostic queues, and their visible controls remain unchanged.
* Removes 22 unused module imports from `includes/admin/js/app.js`, including obsolete profile/list helpers, unused UI primitives, diagnostic utilities, and cache-format helpers. This reduces accidental cross-module coupling and makes missing dependencies easier to detect during future changes.
* Narrows the internal `window.UltraCacheAdmin` export surfaces by removing 32 helpers/constants/components that have no consumer outside their defining module. Internally used helpers remain private and keep the same implementation; consumed exports and module names are unchanged.
* Keeps `includes/admin-dashboard.js` as the same 12-line bootstrap and retains the deterministic WordPress script/style dependency order established by the refactor.

= 2.59.07.28 =
* Stabilizes the per-user dashboard theme system introduced in 2.59.07.27 without changing frontend optimization, cache behavior, media conversion, warm-up, REST payloads, performance settings, or the saved theme values.
* Adds semantic `uc-dashboard-header` and `uc-dashboard-header-actions` classes to the existing header composition so responsive theme controls can be styled without relying on broad utility-class selectors. The title, description, toggle, and Flush All Cache action remain in the same order and use the same callbacks.
* Improves the `UltraCache Theme` control accessibility: the visible text is now a real label bound to the checkbox, the checkbox exposes switch semantics through `role="switch"` and `aria-checked`, the saving state is exposed through `aria-busy`, and the decorative slider is hidden from assistive technology.
* Guards the theme toggle callback before invoking it, preserving the current optimistic save/rollback behavior while preventing an avoidable runtime failure if the component is ever rendered without an `onChange` callback.
* Completes the native and UltraCache admin canvas backgrounds across `#wpcontent`, `#wpbody`, and `#wpbody-content`, avoiding uncovered strips around the dashboard when switching themes or using narrower wp-admin layouts.
* Adds explicit `color-scheme` values for native and UltraCache modes so browser-rendered controls and scrollbars follow the active light/dark dashboard appearance consistently.
* Stabilizes the header action layout: controls stay aligned on desktop, occupy the available width on WordPress mobile breakpoints, and preserve the existing full-width mobile button behavior without changing the rest of the dashboard flex/grid rules.
* Adds keyboard-visible focus styling specifically for the theme switch and adds a scoped `prefers-reduced-motion` rule for dashboard transitions and animations. Mouse interaction and the existing visual themes remain unchanged.

= 2.59.07.27 =
* Adds the per-user UltraCache dashboard theme system after the JavaScript and CSS refactor, without changing frontend optimization, cache, media, warm-up, object-cache, Varnish, or external-cache behavior.
* Makes the WordPress-native dashboard appearance the default for users who have not selected a theme. The existing dark UltraCache appearance remains available unchanged through the new `UltraCache Theme` toggle beside `Flush All Cache`.
* Stores the preference per administrator in the `ultracache_admin_theme` user-meta key (`native` or `ultracache`). The preference is not stored in the shared performance settings and does not trigger a settings save, cache purge, warm-up, or frontend change.
* Adds the authenticated `POST /ultracache/v1/admin-theme` REST route. It accepts only `native` or `ultracache`, uses the existing `manage_options` permission check and REST nonce, and returns the persisted theme.
* Removes the per-user theme meta during full settings/data uninstall cleanup while preserving it when the selected uninstall policy explicitly keeps settings.
* Adds `includes/admin/js/theme.js` for theme normalization, immediate root/body theme application, optimistic per-user saving with rollback on REST failure, and the compact header toggle component.
* Adds `includes/admin/css/themes.css` as the final style layer after tokens, foundation, components, and sections. Native mode uses WordPress admin surfaces, borders, form controls, buttons, admin color variables, notices, menus, modals, and scrollbars while UltraCache mode retains the current design.
* Renders the saved `data-uc-theme` value and matching admin body class server-side before React mounts, preventing a dark-to-light flash on native mode. JavaScript keeps the root attribute and body class synchronized when the toggle changes.
* Adds the explicit `ultracache-admin-theme` script handle and `ultracache-admin-css-sections` style handle while preserving the final public `ultracache-admin-css` handle.

= 2.59.07.26 =
* Splits the former 1,711-line `includes/admin-dashboard.css` into four ordered stylesheets under `includes/admin/css/`: `tokens.css`, `foundation.css`, `components.css`, and `sections.css`.
* Keeps the complete CSS rule stream byte-for-byte identical when the four files are concatenated in dependency order. No selector, declaration, media query, specificity, or cascade order is changed in this release.
* Preserves the public WordPress style handle `ultracache-admin-css`. It now points to `sections.css` and depends on `ultracache-admin-css-components`, which depends on `ultracache-admin-css-foundation`, which depends on `ultracache-admin-css-tokens`.
* Leaves `includes/admin-dashboard.css` as a compatibility notice only; it is no longer enqueued. Adds `includes/admin/css/index.php` to prevent directory browsing.
* Establishes the CSS layer boundaries needed for the future WordPress-native/default and UltraCache dashboard theme switch without introducing that switch yet.

= 2.59.07.25 =
* Adds `includes/admin/js/app.js` as the dedicated application-composition module. It owns the remaining dashboard helpers, App component, action orchestration, section composition, and complete React element tree that previously remained in `includes/admin-dashboard.js`.
* Moves the existing application body structurally rather than rewriting it: the module imports the same core/API/settings/help/UI/diagnostics/jobs/warm-up/media/cache/lifecycle modules, configures them in the same order, creates the same state/actions, and mounts the same App component through the existing lifecycle mount helper.
* Adds the explicit `ultracache-admin-app` WordPress script handle after all feature/lifecycle dependencies and before the final bootstrap. The final `ultracache-admin-js` handle now depends only on `ultracache-admin-app`.
* Keeps `window.ultracacheData` localized immediately before the final bootstrap handle. The app module performs no runtime initialization until `bootstrap()` is called, so the existing localized configuration remains available before any dashboard settings, stats, diagnostics, paths, or REST configuration are read.
* Registers translations for the new app handle and preserves the existing translation registration for the final bootstrap.

= 2.59.07.24 =
* Adds `includes/admin/js/lifecycle.js` as the dedicated React state and dashboard-lifecycle module, loaded through the explicit WordPress script dependency manifest before the final dashboard bootstrap.
* Moves the complete App-level React state/ref initialization out of `includes/admin-dashboard.js`, including settings, stats, diagnostics, media counts/support/queue state, forms, job/process state, action queues, modal/accordion state, scanner state, persistence refs, cancellation refs, and manual media-session ownership refs.
* Moves toast insertion/dismissal callbacks into the lifecycle module while preserving IDs, replacement behavior, the 50-toast cap, persistence flags, and the existing default timeout.
* Moves all 12 App-level effects into the lifecycle module: Redis activation verification, settings-ref synchronization, before-unload protection, toast expiration timers, reverse-proxy notices, cache-plugin conflict notices, responsive/mobile handling, passive cache-stat polling with visibility pause/resume, and advanced/Varnish/Redis form synchronization.
* Preserves passive dashboard behavior: no frontend compression probe or browser scan is started automatically, cache-stat polling remains disabled when the setting is off, only one stats refresh can be in flight, and polling still pauses while the document is hidden.
* Moves process ETA calculation, dashboard-root lookup, and React 18/legacy ReactDOM mounting into the lifecycle module without changing displayed ETA wording or root-element compatibility.
* Keeps form-default evaluation lazy where it was previously conditional, so the scheduled warm-up and Varnish server default providers are not called when explicit saved values already exist.
* Adds the `ultracache-admin-lifecycle` script handle with `wp-element`, `wp-i18n`, and core dependencies, registers its translations, and makes the final dashboard script depend explicitly on it.

= 2.59.07.23 =
* Fixes the cache-module extraction regression introduced in 2.59.07.22 where `VarnishCard` called the shared `formatLooseTime()` helper without importing it from `includes/admin/js/core.js`, causing `ReferenceError: formatLooseTime is not defined` and preventing the UltraCache dashboard from rendering.
* Adds `formatLooseTime` to the explicit core-helper destructuring in `includes/admin/js/cache.js`; no Varnish settings, REST calls, cache behavior, dashboard markup, or CSS are changed.
* Adds a focused Varnish-card render smoke check with a populated `last.time` value so extracted components cannot pass validation while missing a runtime helper used only by a conditional render path.

= 2.59.07.22 =
* Adds `includes/admin/js/cache.js` as the dedicated cache-backend and cache-layer dashboard module.
* Moves the Redis/object-cache card, APCu card, OPcache card, Varnish card, external-cache cards, conflicting cache-helper notice, and their formatting/default helpers out of `includes/admin-dashboard.js`.
* Moves object-cache backend/fallback selection, Redis settings save/test/flush, full object-cache count, conflicting drop-in recheck/removal, Varnish settings/test/flush, OPcache/APCu flush, LiteSpeed/Nginx flush, external-cache redetection, and Flush All Cache orchestration into the cache module.
* Preserves the existing queued-action path for `purge_all`, `object_cache_flush`, `object_cache_full_count`, `apcu_flush`, and `varnish_flush_all`; no queue action name, polling interval, status handling, toast text, or refresh behavior is changed.
* Preserves Redis password handling, backend validation, APCu auto-inclusion in Flush All Cache, Varnish HTTP/admin mode defaults, detailed Varnish REST error propagation, and existing conflicting-drop-in confirmation behavior.
* Adds the explicit WordPress script handle `ultracache-admin-cache`, loaded after core/API/UI and before the final dashboard bootstrap, and registers its translations.

= 2.59.07.21 =
* Adds `includes/admin/js/warmup.js` as the dedicated warm-up feature module. It owns warm HTML/CSS job classification, CSS bundle scope normalization, first-visit CSS bundle setting helpers, warm job labels/scopes, crawl-page item retries, crawl batch retrieval, front-page warm actions, full-site/menu warm start/resume/restart flows, and CSS-bundle preparation orchestration.
* Adds `includes/admin/js/media.js` as the dedicated media feature module. It owns WebP/AVIF conversion-unit processing, HTTP 422 bounded retry and terminal failure reporting, retryable processor-lock handling, media batch retrieval, exclusive manual-session start/stop, conversion preflight, queue repair/rebuild orchestration, failed/completed queue actions, background-work pause/resume, and optimized-file recount handling.
* Preserves the 2.59.07.09 media behavior where a conversion failure is retried up to its server-provided limit, counted once only when terminal, logged with attachment/source/format/stage/code/detail evidence, and does not stop the remaining dashboard conversion queue.
* Preserves the 2.59.07.12 exclusive dashboard media-session behavior: dashboard conversion acquires ownership before preflight, visitor/upload/cron workers cannot launch competing conversions, ownership is carried through resumable jobs, and it is released on completion, pause, or failure.
* Keeps the generic persisted job runner in `includes/admin/js/jobs.js`; `admin-dashboard.js` now supplies only shared React state callbacks and dispatches each job item/batch to the warm-up or media module.
* Adds explicit WordPress script handles `ultracache-admin-warmup` and `ultracache-admin-media`, loads them after their core/API dependencies and before the final dashboard bootstrap, and registers script translations for both handles.

= 2.59.07.20 =
* Resumes the staged admin-dashboard refactor after the 2.59.07.19 wp-admin isolation hotfix, using 2.59.07.19 as the exact functional baseline and retaining all request-context isolation and scoped drop-in reconciliation changes.
* Adds the ordered internal module `includes/admin/js/jobs.js` for generic persisted dashboard-job orchestration; the module is loaded after diagnostics and before the final `admin-dashboard.js` bootstrap through the explicit WordPress script dependency manifest.
* Moves dashboard job localStorage persistence (`loadSavedJob`, `saveJob`, and `clearSavedJob`) into the jobs module while preserving the existing `ultracache-dashboard-job-state-v3` storage key and invalid/corrupt-storage fallback behavior.
* Moves saved-job resume/restart eligibility, pending-item detection, media-rebuild generation recognition, and warm-up generation stale-after-flush protection into a pure `getJobControls()` helper.
* Moves generic job-state initialization and restart normalization into the jobs module, preserving cursor/next-cursor handling, the 100-item persisted pending batch cap, log trimming, counters, queue-building state, start time, batch size, ETA samples/checkpoints, and warm-up generation persistence.
* Moves process-panel state normalization into the jobs module without changing current/total clamping, media visibility while inactive, cancellation state, logs, counters, or ETA fields.
* Moves generic batch fetching orchestration, pending-item continuation, cursor progression, pause/cancel persistence, per-item counter aggregation, media ETA sampling, completion cleanup, resumable failure persistence, and exclusive-session release handling into `createJobRunner()`.
* Keeps feature policy outside the generic engine through callbacks: REST batch selection, media conversion units, warm-up URL processing/retries, manual media-session ownership, media queue progress merging, completion messages, stats refresh, and media queue refresh remain controlled by the existing dashboard code.

= 2.59.07.19 =
* Adds strict request-context isolation for the frontend engine: frontend output buffering, JavaScript/CSS tag filters, frontend enqueue callbacks, resource-hint mutation, WooCommerce frontend script-data filtering, and store-profile shutdown handlers are no longer registered during wp-admin, REST, AJAX, or cron requests.
* Keeps cache invalidation hooks active in admin contexts, including post, product, term, menu, theme, widget, front-page, and permalink changes, so admin isolation does not disable cache purging after content changes.
* Stops automatic page-cache and object-cache drop-in reconciliation on every unrelated wp-admin, REST, AJAX, and plugin-management request. Drop-ins continue to synchronize during activation, settings persistence/rollback, explicit dashboard access, and WP-CLI operations.
* Removes the complete temporary 2.59.07.18 Elementor/admin asset diagnostic implementation as scheduled: property, hooks, registry snapshots, payload attachment, dashboard script registration, and `includes/admin/js/temporary-admin-asset-diagnostics.js`.

= 2.59.07.18 =
* Adds a temporary, read-only admin asset diagnostic for the UltraCache dashboard to investigate delayed Elementor 4.x failures such as `React is not defined`, `elementorModules is not defined`, and `Angie is not available` without changing any third-party script registration, enqueue, dequeue, dependency, or execution behavior.
* Captures WordPress script-registry snapshots immediately before and after the existing UltraCache Elementor Notes suppression at `admin_enqueue_scripts`, `admin_print_scripts-toplevel_page_ultracache`, and `admin_print_footer_scripts-toplevel_page_ultracache`.
* Records relevant Elementor, Angie, Notes, editor-MCP, `wp-element`, React, ReactDOM, and `wp-components` handles together with their source URL, declared dependencies, version, script group, registration/enqueue status, pending `to_do` state, completed `done` state, and the surrounding WordPress script queues.
* Adds `includes/admin/js/temporary-admin-asset-diagnostics.js`, loaded only on the UltraCache dashboard. It records browser runtime snapshots at 0 ms, 1.2 seconds, and 5 seconds for `React`, `ReactDOM`, `wp.element`, `elementorModules`, and `Angie`, plus the actually rendered relevant script tags and their `type`, `async`, `defer`, and `data-wp-strategy` attributes.
* Exposes the collected evidence as `window.UltraCacheTemporaryAdminAssetDiagnostics` and writes collapsed console groups prefixed with `[UltraCache temporary admin asset diagnostic]` for quick copying from the live WordPress test environment.

= 2.59.07.17 =
* Extracts the JavaScript defer/delay diagnostics interface from `includes/admin-dashboard.js` into the new ordered module `includes/admin/js/diagnostics.js` without changing its rendered markup, CSS classes, labels, list-editing behavior, REST routes, or save flow.
* Moves Browser Scanner result grouping, Runtime Scan result rendering, captured runtime/resource error presentation, Console Error Handler parsing workflow, DB-backed JS Diagnostic Queue status/actions, append-to-Defer and append-to-exclusion controls, and suggestion deduplication/presence checks into the diagnostics module.
* Moves the CSS Bundle Exclusions diagnostics field and its profile result metrics, exclusion coverage checks, copy/append controls, JSON download trigger integration, clear action, and result rendering into the same module.
* Moves the Speed Diagnostics / Performance Profiler card, its CSS bundle and critical-chain summaries, UltraCache overhead probe, frontend rewrite breakdown, duplicate/mixed-status CSS link diagnostics, top callback/origin tables, slow checkpoints, download/clear controls, and CSS-exclusion copy actions into the diagnostics module.
* Moves shared diagnostic helpers `getJsDelaySafetySuggestions()`, `getJsDelayReviewSuggestions()`, `isSuggestionPresentInDraft()`, `getNextMediaEtaCheckpoint()`, and `formatEtaDuration()` out of the monolith.
* Moves the pure Browser Runtime Scan URL/snapshot helpers out of the `App` component: display-URL sanitization, runtime scan URL construction, scan-ID verification, runtime result normalization, popup script inventory collection, direct popup snapshot reading, and navigation-loss snapshot creation.
* Adds an explicit diagnostics runtime configuration boundary for the localized `ultracacheData` object and detected plugins public path. The extracted UI continues to use the same frontend probe URL, Runtime Scan nonce, and console-error path examples as before.
* Extends the deterministic WordPress script manifest with `ultracache-admin-diagnostics`. Load order is now `namespace.js` -> `core.js` / `api.js` -> `settings.js` / `help.js` / `ui.js` -> `diagnostics.js` -> `admin-dashboard.js`; the diagnostics script is registered for WordPress translations.
* Updates `includes/admin-dashboard.js` to require and consume the diagnostics module through `window.UltraCacheAdmin`, then configures it after the localized runtime data and public paths are available.

= 2.59.07.16 =
* Extracts performance-profile definitions and profile patch logic from `includes/admin-dashboard.js` into the new ordered module `includes/admin/js/settings.js`, including profile detection, preserved-setting stripping, object-cache patch splitting, and the Safe/Balanced/Aggressive/All Off presets.
* Moves JavaScript strategy, WooCommerce frontend/cart-fragment strategy, HTML compression delivery, line-list normalization, append-only merging, and active-profile recognition into the settings module without changing existing option values or profile behavior.
* Moves settings import/export filtering, payload creation, import validation, JSON download handling, visible exclusion-list deduplication, broad WooCommerce-path coverage, overlap detection, and targeted line removal into the same settings module.
* Adds an explicit settings runtime configuration boundary for plugin version, site origin, and the detected WooCommerce public path; export metadata and broad WooCommerce-list matching continue to use the same live dashboard values as before.
* Extracts the complete option-specific help registry, generic help generation, and label-with-help renderer into the new ordered module `includes/admin/js/help.js`.
* Extends the deterministic WordPress script manifest with `ultracache-admin-settings` and `ultracache-admin-help`; final load order is `namespace.js` -> `core.js` / `api.js` -> `settings.js` / `help.js` / `ui.js` -> `admin-dashboard.js`. The settings module is registered for WordPress script translations.

= 2.59.07.15 =
* Extracts reusable dashboard presentation primitives from `includes/admin-dashboard.js` into the new ordered module `includes/admin/js/ui.js` without changing their HTML structure, existing class names, CSS, labels, control behavior, REST calls, settings, queues, or dashboard layout.
* Moves the toast viewport; support action links, inline support card, and support modal; generic cards and accordions; statistic cards; buttons; toggle controls; text, number, select, custom-select, textarea, saveable-textarea, and multiselect fields; detail rows; status pills; and the shared progress panel.
* Keeps dashboard-specific help lookup, help-label rendering, visible-list merging, and warm-source parsing in the monolith for now, and supplies them to the UI module through an explicit runtime configuration boundary so the extracted components retain their previous behavior.
* Adds `ultracache-admin-ui` to the deterministic WordPress script manifest with load order `namespace.js` -> `core.js` / `api.js` -> `ui.js` -> `admin-dashboard.js`, and registers the UI module for WordPress script translations.
* Updates `includes/admin-dashboard.js` to require and consume the UI module through `window.UltraCacheAdmin`; the extracted component declarations and support-link constant no longer remain duplicated in the monolith.

= 2.59.07.14 =
* Extracts the first stable dashboard modules from the 11,000-line `includes/admin-dashboard.js` monolith without changing the rendered interface, settings, REST routes, request payloads, queue behavior, or feature logic.
* Adds `includes/admin/js/core.js` for the shared WordPress element/i18n references, React hooks, public-path normalization and joining, class-name composition, safe localStorage access, viewport detection, content-encoding helpers, common number/count/file/byte/duration/time formatters, and the generic sleep helper.
* Adds `includes/admin/js/api.js` for the complete REST route map, REST client configuration, nonce/header handling, GET query construction, action-specific payload normalization, noisy JSON recovery, structured REST error metadata, HTTP status preservation, empty/invalid response handling, and generic batch-response normalization.
* Updates `includes/admin-dashboard.js` to consume the `core` and `api` modules through `window.UltraCacheAdmin` while preserving the previous function names at the dashboard call sites; no feature code receives its own fetch wrapper.
* Extends the deterministic WordPress script manifest so loading order is `namespace.js` -> `core.js` / `api.js` -> `admin-dashboard.js`, with `wp-element` and `wp-i18n` loaded before the core module.
* Aligns the packaged POT project-version header with the plugin release metadata.

= 2.59.07.13 =
* Adds the internal `window.UltraCacheAdmin` module namespace and duplicate-module guard as the foundation for the staged dashboard split.
* Registers local dashboard scripts through a deterministic WordPress dependency manifest while keeping the existing dashboard monolith, UI, settings, REST requests, and runtime behavior unchanged.
* Keeps `admin-dashboard.js` as the final module entry point and loads the namespace first through the explicit `ultracache-admin-namespace` dependency.

= 2.59.07.12 =
* Gives a dashboard Media Conversion run exclusive queue ownership before its preflight scan, preventing visitor, upload, cron, maintenance, and loopback background workers from starting competing conversion units.
* Allows a background unit already inside an encoder to finish, while the dashboard waits for the shared processor lock instead of stopping the manual job.
* Renews and persists the dashboard session token across conversion requests and resumable jobs, then releases ownership on completion, pause, or failure so pending background work can resume.
* Adds an expiring recovery watchdog so an abandoned or closed dashboard tab cannot leave background media generation disabled indefinitely.

= 2.59.07.11 =
* Keeps Async Remaining CSS disabled when the Aggressive performance profile is applied.

= 2.59.07.10 =
* Resolves arbitrary explicit missing globals from exact provider filenames, script handles, and scanned definitions instead of limiting provider matching to a small hardcoded set of WordPress/core globals.
* Resolves `PerfectScrollbar is not defined` to the exact `perfect-scrollbar` provider and the direct `theme-addons.js` consumer.
* Runs provider resolution before fallback stack-source evidence, removing repeated basename and path variants for the same script.
* Canonicalizes and deduplicates suggestions by effective owner-relative exclusion target.
* Reduces missing jQuery plugin method results to the exact provider and direct consumer, excluding indirect callers from appendable fixes.

= 2.59.07.09 =
* Gives captured browser runtime errors priority over static delay/defer classifications and always retains exact non-core stack-source evidence, including sources already present in a safeguard list.
* Connects the existing jQuery plugin provider resolver to the Runtime Scan execution path, allowing errors such as `counter.appear is not a function` to resolve the script that registers `jQuery.fn.appear` before generic missing-global handling.
* Adds structured per-unit media conversion diagnostics for source, storage, WordPress image editor, Imagick, GD, and final output-validation failures.
* Reports the effective attempted media format instead of the internal `best` queue policy; WebP-only mode now reports `webp` and automatic fallback failures report `avif+webp`.
* Returns retry attempt/limit metadata for failed media queue units and lets the dashboard complete the bounded retries for one attachment without aborting the whole optimization job.
* Records one terminal failed attachment after the retry limit, shows its attachment ID, source file, format, stage, code, and detail, then continues with the next queued attachment.

= 2.59.07.08 =
* Removes plugin-owned trait/class declaration conflict guards while retaining the WP-CLI environment condition.
* Repairs the gettext template header and removes local development paths from source references.
* Rewrites and aligns the packaged readmes, keeps `readme.txt` below 10 KB, and documents every distributed JavaScript helper.
* Separates the optimized AVIF/WebP file counter completely from Cache Statistics, dashboard-stat snapshots, cache-stat polling, and the generic JavaScript `stats` state.
* Stores only the dedicated AVIF, WebP, and total file counts in the non-autoloaded WordPress option `ultracache_media_file_counts`; no JSON file, sidecar, or other filesystem storage is added.
* Loads the file counter independently during dashboard bootstrap and returns it independently as `mediaFileCounts` from the existing media queue REST response, preventing cache-stat refreshes from resetting it to zero.
* Updates the dedicated counter when UltraCache creates or deletes optimized files and keeps the previous database values during the one-time option rename from `ultracache_media_storage_stats_v2`.
* Removes the Optimized Images card from the Cache Statistics panel and removes media-file values from engine/cache-stat payloads.
* Renames Refresh Storage Stats to Recount Optimized Image Files; the action scans `uploads/ultracache/images` and corrects only the AVIF/WebP file counter.

= 2.59.07.07 =
* Fixes optimized-image counters resetting to `0 AVIF · 0 WebP` after a dashboard refresh by including the persistent media-storage option in the initial passive dashboard payload.
* Merges the current persistent media counters into cached dashboard-stat snapshots before returning them, preventing a stale snapshot from overwriting live totals.
* Synchronizes legacy `imagesOptimized`, `avifImagesOptimized`, and `webpImagesOptimized` aliases with the persistent counters so older cached payload fields cannot take precedence with stale zero values.
* Keeps persistent media totals visible even when general cache-stat polling is disabled; reading these counters is a lightweight option lookup and does not scan the filesystem.

= 2.59.07.06 =
* Moves Stop All Media Background Work / Resume All Media Background Work to the final position in the media queue action list so the emergency control appears after normal processing, maintenance, retry, and cleanup actions.

= 2.59.07.05 =
* Adds a persistent Stop All Media Background Work / Resume All Media Background Work control that invalidates outstanding dispatcher tokens, clears media cron watchdogs, cancels deferred dispatch, returns claimed queue rows to pending, and blocks upload, page-generation, cron, immediate-worker, REST, dashboard, and direct AVIF/WebP conversion entry points after the current physical encode finishes.
* Keeps the media queue and existing optimized files intact while generation is stopped; refreshing the dashboard cannot resume processing automatically, and resuming can continue from the preserved pending queue.
* Merges Rebuild Media Queue and Verify / Repair Queue into one Rebuild / Repair Media Queue action. The scan now checks every attachment's required physical derivatives, marks current outputs complete, requeues missing or stale outputs, and shares the conversion lock so queue repair cannot race an active encoder.
* Treats an optimized derivative as current only when it exists and is at least as new as its source file, allowing changed originals or thumbnails to be repaired without deleting valid outputs first.
* Removes the redundant cache warm-up explanatory note and simplifies the media conversion panel description.

= 2.59.07.04 =
* Renames "Queue Missing Media on Demand" to "Queue Missing Media During Page Generation" so the option name matches the actual discovery trigger.
* Rewrites the setting description to state only when discovery occurs: uncached page generation, warm-up, cron warm, and stale regeneration, with conversion handled separately in the background.
* Simplifies the related help text without listing unrelated actions that do not trigger media generation.

= 2.59.07.03 =
* Makes missing-media on-demand processing immediate without converting inside the visitor request: the request queues the attachment and sends one signed, non-blocking same-site REST worker request after WordPress finishes the response and page-cache write.
* Defers the initial dispatch through a PHP shutdown callback so a fast conversion cannot purge the affected page before the originating request finishes storing that page in cache.
* Adds a dedicated database dispatcher lock held across the worker chain, so concurrent frontend visits, uploads, warm-up requests, and cron recovery can produce only one active background media dispatcher.
* Chains one physical image unit at a time through the existing shared conversion lock and timeout-safe processor; successful units dispatch the next worker while pending work remains.
* Keeps WP-Cron as a watchdog and fallback only. Failed loopback dispatch, conversion-lock contention, and conversion failures use bounded fallback/backoff schedules instead of launching workers from every visitor.
* Protects the public worker route with a short-lived HMAC bound to the dispatcher token, site URL, and WordPress authentication salt; stale, expired, or non-owner requests are rejected.
* Resets stale processing rows before watchdog recovery, allowing abandoned conversions to return to the bounded retry flow.
* Updates the Queue Missing Media on Demand description to distinguish immediate background dispatch from conversion inside the visitor request.

= 2.59.07.02 =
* Adds a dedicated database lock for Media Queue Rebuild chunks so refresh, resume, another browser tab, WP-CLI, and automatic queue building cannot scan/update the rebuild cursor concurrently.
* Adds a persistent rebuild generation token. Restart publishes a new generation before waiting for the lock, causing any older in-flight chunk or delayed browser request to stop as stale instead of updating the new run.
* Makes rebuild requests idempotent per generation, so retrying the same initial request does not delete and restart the queue a second time when the first response was lost.
* Persists the rebuild generation in the dashboard job state, silently waits for an active chunk lock during refresh/resume, and rejects saved state belonging to an older rebuild.

= 2.59.07.01 =
* Keeps the existing long-job progress bar and simplifies only the Media Queue Rebuild status area to Total units, Finished, and Time left.
* Removes the rebuild-only Overall Progress text and chunk scan/queue log lines that could present stale or misleading information while a new rebuild starts.
* Uses the fixed eligible Media Library attachment total (`libraryTotal`) as the rebuild denominator instead of the mutable queue-row total, preventing on-demand queue additions from producing results such as 28,675 / 28,677.
* Resets a fresh rebuild display to zero/Calculating until the first authoritative chunk response arrives, preserves exact progress across pause/resume, and prevents a non-complete job from showing 0s remaining.

= 2.59.06.100 =
* Bounds media conversion failures with a dedicated `consecutive_failures` queue column. A row becomes `failed` after three consecutive failed or abandoned claims instead of remaining pending forever; any successful physical-image unit resets the counter, and Retry Failed resets it for an explicit new attempt.
* Separates `skippedThisRun` from `alreadyOptimizedThisRun`, eliminating the WP-CLI skipped-total double count.
* Returns non-2xx REST responses for media queue lock conflicts and conversion/retry-limit failures: 409 for lock contention, 422 for conversion failures, and 500 for other processing errors.
* Wraps the GD opaque-JPEG source decode and generated-AVIF decode in scoped warning handlers so codec warnings are captured in diagnostics instead of leaking into output.
* Replaces the three remaining focused WPCS `json_encode()` fallbacks with WordPress `wp_json_encode()` calls.

= 2.59.06.99 =
* Replaces transient-only optimized-media storage totals with persistent aggregate counters stored in `ultracache_media_storage_stats_v2`.
* Updates AVIF/WebP file counts and byte totals immediately when UltraCache creates, replaces, or deletes generated derivatives, so dashboard values survive transient expiry, Redis eviction, and process restarts.
* Seeds the persistent counters from the latest legacy storage scan when available and keeps the last known values visible when reconciliation is incomplete instead of reporting an incorrect zero.
* Makes Refresh Storage Stats reconcile the persistent counters against the filesystem; complete scans become authoritative while capped/incomplete scans preserve the last known totals and mark reconciliation as needed.
* Adds dashboard status text distinguishing reconciled persistent counters from last-known counters that still need filesystem reconciliation.
* Removes the new persistent storage statistics option through the existing UltraCache runtime-data uninstall policy while leaving generated media files untouched.

= 2.59.06.98 =
* Clarifies the Media Conversion capability summary so Imagick installation, AVIF encoder verification, and WebP availability are reported as distinct states.
* Updates media runtime diagnostics to label AVIF results as self-test Passed/Failed and WebP results as Available/Unavailable instead of ambiguous Yes/No values.
* Keeps the automatic AVIF safety test and runtime behavior unchanged; this release only corrects capability reporting terminology.

= 2.59.06.97 =
* Removes the complete AVIF encoder self-test status panel from the Media Conversion dashboard, including the explanatory text and Imagick/GD result lines.
* Retains the automatic environment-fingerprinted AVIF safety test exclusively as an internal runtime capability gate for generation and frontend delivery.

= 2.59.06.96 =
* Removes the manual AVIF self-test button and its authenticated REST trigger from the dashboard after completing the encoder regression diagnosis.
* Retains the automatic, environment-fingerprinted opaque-JPEG and transparent-RGBA AVIF safety tests as runtime capability gates for generation and frontend delivery.

= 2.59.06.95 =
* Fixes content-dependent Imagick AVIF corruption by preserving the source image's native channel layout instead of activating an alpha channel on opaque JPEG files.
* Keeps native transparency for PNG/WebP sources without manufacturing alpha for JPEG sources; the GD conversion path now requests alpha preservation only for source formats that can carry it.
* Extends the AVIF self-test with a bundled opaque 300x169 odd-height JPEG regression fixture in addition to the transparent 16x16 RGBA PNG, and requires both tests to pass for each encoder.
* Increments the AVIF self-test algorithm version so previously cached results are invalidated and the expanded test runs automatically after upgrade.
* Does not delete existing generated AVIF files automatically; previously generated AVIF derivatives must be regenerated after installing this release.

= 2.59.06.94 =
* Bundles a deterministic 16x16 RGBA PNG for AVIF encoder validation instead of trusting codec presence or container metadata alone.
* Adds persistent, environment-fingerprinted AVIF self-tests for Imagick and GD that encode the bundled image, fully decode the generated AVIF, and validate known red, green, blue, white, transparent, and semi-transparent pixels.
* Uses the self-test result as runtime capability truth: failed AVIF engines are excluded from generation, existing AVIF files are no longer selected for frontend HTML/CSS rewrites, and `best` media work requires WebP when no AVIF engine passes.
* Adds an authenticated REST diagnostic endpoint and a Media Conversion dashboard button showing separate Imagick and GD pass/fail reasons.
* Makes WebP the recommended default for fresh/default settings and performance profiles while preserving existing saved output selections.
* Stores the AVIF result in `ultracache_avif_encoder_self_test_v1`, invalidates it when the PHP/image-library fingerprint or bundled test asset changes, and removes it through UltraCache data cleanup/uninstall.

= 2.59.06.93 =
* Adds a staged media-optimization ETA that measures the first 10 completed attachments, recalibrates after 100 attachments, and recalibrates again at every 500-attachment checkpoint.
* Keeps the current ETA between checkpoints while reducing the remaining time after every completed attachment, and preserves measured timing data across pause/resume without counting paused time.
* Propagates the exact eligible Media Library attachment total from the queue discovery query, replacing the provisional queue-row denominator and allowing progress and ETA to remain meaningful while the queue is still building.
* Shows the ETA sample size in the dashboard and displays a clear estimation countdown until the initial 10-attachment sample is available.

= 2.59.06.92 =
* Fixes the dashboard media optimizer regression where the shared `processJobItem()` helper referenced the React component-local `cancelRequestedRef` directly and raised `ReferenceError: cancelRequestedRef is not defined`.
* Passes a cancellation callback explicitly from the dashboard job runner into the media item processor, preserving pause/resume checks between physical-file conversion requests without leaking component-local state into module scope.

= 2.59.06.91 =
* Changes manual, REST, and background media conversion from whole-attachment processing to one physical source-file conversion unit per request.
* Keeps attachment progress resumable by detecting existing AVIF/WebP derivatives and returning the remaining unit count after every request.
* Adds secondary time- and memory-budget checks between physical files for full-attachment CLI and maintenance callers.
* Preserves explicit WP-CLI full-attachment regeneration while keeping web and cron workers on resumable single-file units.
* Replaces transient media processor coordination with the shared token-owned UltraCache lock table so dashboard, cron, REST, and CLI queue workers cannot overlap.
* Atomically claims pending media queue rows and prevents completed queue rows from re-running conversion after a lost or repeated response.
* Removes automatic browser retries for media failures, returns interrupted units to pending for explicit Resume, pauses the job on the first HTTP/server error, and adds a 250 ms delay between successful conversion units.
* Limits web queue processing to one conversion unit with an 8-second requested budget and a 15-second hard cap, while background processing uses delayed success, lock, and failure backoff schedules.
* Reduces stale media-processing recovery from 10 minutes to 2 minutes.
* Adds repository-level Composer, PHPCS, EditorConfig, and WordPress Coding Standards configuration for repeatable plugin linting.
* Refreshes the translation template metadata and adds the new media queue status/error strings.

= 2.59.06.90 =
* Adds local PHPCS tooling under `tools/phpcs` with PHPCS, WordPress Coding Standards, and PHPCompatibilityWP for WordPress.org audit checks.
* Documents the local PHPCS/PHPCBF commands and ignores the generated Composer `vendor/` directory.

= 2.59.06.89 =
* Improves same-URL reload-loop diagnostics by scanning printed plugin/theme scripts for upstream startup `.change()` / `trigger("change")` event triggers when the final redirect/listener script is already covered.
* Adds exclusion-first upstream trigger suggestions for delayed local WooCommerce/orderby scripts that can wake another plugin's redirect listener.
* Falls back to fetching the looped page's script inventory from the stored scan detail when the runtime report does not include scripts.

= 2.59.06.88 =
* Makes interrupted Browser Runtime Scan matching less brittle by ranking local delayed WooCommerce/filter startup scripts from the printed page even when the scan cannot read their JavaScript contents before navigation.
* Prioritizes delayed theme WooCommerce startup scripts, including product/order scripts that are likely to fire synthetic change events before another plugin redirects.
* Keeps interrupted-navigation findings manual and exclusion-first under "Do Not Defer or Delay" candidates.

= 2.59.06.87 =
* Teaches Browser Runtime Scan to detect when the diagnostic popup navigates away before the in-page collector can report, covering reload/redirect loops that happen before console errors are captured.
* Sends same-origin popup script inventory with direct Browser Runtime Scan harvests so REST diagnostics can analyze the actual scripts printed on the interrupted page.
* Adds exclusion-first suggestions for startup navigation/change triggers, including WooCommerce/orderby synthetic change patterns that can activate another plugin's redirect listener after JavaScript delay.

= 2.59.06.86 =
* Adds a deterministic plugin ZIP builder that writes internal archive paths with forward slashes, so WordPress recognizes the single `ultracache/` root folder during manual uploads.
* Verifies release ZIPs reject backslash entries, git artifacts, missing `ultracache/ultracache.php`, and files outside the `ultracache/` root.

= 2.59.06.85 =
* Adds Runtime Scan same-URL reload-loop detection that persists scan navigation evidence across reloads and records the last synthetic startup event before unload.
* Marks reload-loop fixes as exclusion-first so they appear as "Do Not Defer or Delay" candidates instead of Defer Instead fixes.
* Updates dashboard grouping for exclusion-first scan findings so they are counted and shown in the correct Browser Scanner section.

= 2.59.06.84 =
* Renames scan-result exclusion action buttons from the internal "Do Not Defer or Delay" target name to "Add to exclusions".
* Quotes "Do Not Defer or Delay" in append buttons and nearby scan-result status text so users understand it is the visible exclusion list name.

= 2.59.06.83 =
* Removes Advanced Runtime Font CSS Rewrite from the Balanced and Aggressive profile patches so no performance profile enables that advanced font rewrite automatically.
* Improves Runtime Scan and Console Error Handler suggestions for order-sensitive local plugin/theme dependencies by adding the shared owner JavaScript directory when the crashed consumer and matched provider live under the same owner path.

= 2.59.06.82 =
* Corrects the Varnish admin CLI response reader to match Varnish's own protocol: a fixed 13-byte status/length header followed by the declared body length plus the terminating newline.
* Fixes the admin-auth follow-up read so Varnish response bodies cannot leave a newline behind and desynchronize the next CLI response.

= 2.59.06.81 =
* Fixes the manual object-cache backend test so newly typed Redis passwords and clear-password requests are included in the REST probe payload before settings are saved.

= 2.59.06.80 =
* Fixes Varnish admin-secret mode by parsing the Varnish CLI response status line dynamically instead of assuming one fixed header width.
* Updates the Varnish admin auth hash builder to try the exact secret-file byte forms Varnish accepts, covering secrets copied with or without the trailing newline from `/etc/varnish/secret`.

= 2.59.06.79 =
* Makes the Varnish test REST endpoint return its diagnostic payload for normal connection-test failures instead of hiding endpoint details behind a generic HTTP 500 dashboard error.
* Updates the dashboard Varnish test action to merge failed diagnostic payloads and show each endpoint's exact `server: FAIL - reason` line in the error toast and Varnish card.

= 2.59.06.78 =
* Rewords the historical 2.59.06.60 changelog note about removed third-party matcher fragments so automated remote-file scans do not mistake archived domain examples for active plugin behavior.

= 2.59.06.77 =
* Rewrites the dashboard info-icon help into plain-language, code-derived explanations that describe what each control changes, why it can improve speed, and what to test before trusting it.
* Adds specific help coverage for cache delivery, media, JavaScript timing, CSS delivery, font optimization, WooCommerce controls, query/cookie safety lists, object cache, Redis, Varnish, external cache flushing, and warm-up/scheduling controls.
* Updates the bespoke JS safeguard, Browser Scanner, Console Error Handler, CSS diagnostics, Delayed JS auto-start, Font-Mix CSS, WooCommerce strategy, Apache Static HTML Delivery, and Object Cache Fallback tooltips to match the same explanation style.
* Regenerates `languages/ultracache.pot` so the new explicit tooltip strings and 2.59.06.77 metadata are reflected in the translation catalog.

= 2.59.06.76 =
* Moves "Bundle Generated Font-Mix CSS" from CSS Delivery into Fonts Optimization so the control lives beside the font pipeline it affects.
* Adds a new opt-in "Async Generated Font-Mix CSS Bundle" control that async-loads only the consolidated `bundle-font-mix-*.css` file while leaving individual `css-font-mix-*` source files untouched.
* Runs Font-Mix CSS consolidation before the async CSS pass when the new async Font-Mix option is enabled so the consolidated bundle can be classified and rewritten.
* Adds richer info-icon help for WooCommerce frontend strategy presets, including Off, Safe, Balanced, Aggressive, and Custom behavior.
* Adds missing info-icon help to the bespoke JS safeguard, Browser Scanner, Console Error Handler, CSS Bundle Exclusions, page URL diagnostic, and Delayed JS auto-start controls.

= 2.59.06.75 =
* Adds expanded info-icon help across dashboard option controls while keeping the short descriptions visible below each title.
* Adds a visible Apache Static HTML Delivery (.htaccess) option that serves conservative queryless anonymous HTML cache aliases before PHP on Apache-compatible hosts.
* Writes stable `index-orig.html`, `index-webp.html`, and `index-avif.html` aliases beside hashed page-cache files, with source markers so purges do not delete unrelated aliases.
* Expands Browser Cache Headers .htaccess coverage for web manifests, AVIFS, WASM, EOT, audio/video files, and revalidation-oriented HTML/JSON/XML handling.
* Keeps Apache Static HTML Delivery separate from Browser Cache Headers and removes its managed rules on deactivation, plugin data cleanup, and uninstall.
* Removes UltraCache-managed Browser Cache Headers and Apache Static HTML .htaccess blocks during uninstall without touching rules outside those markers.

= 2.59.06.74 =
* Adds an opt-in "Bundle Generated Font-Mix CSS" control in CSS Delivery that consolidates UltraCache-generated `optimized-css/css-font-mix-*.css` stylesheet links into one ordered blocking CSS bundle.
* Keeps the generated font-mix bundle classified as layout-risk CSS so Async CSS diagnostics do not treat it as an async candidate.
* Adds WooCommerce-box info-icon help as a UI test, moving the individual WooCommerce option descriptions into native hover/focus titles while leaving the rest of the dashboard copy unchanged.

= 2.59.06.73 =
* Adds a visible WooCommerce cart-fragments behavior dropdown with Off, Delay request, and Suppress empty-cart execution modes.
* Adds an empty-cart cart-fragments suppression mode that prevents `wc-cart-fragments` execution on anonymous cacheable pages without WooCommerce cart/session cookies, while keeping cart, checkout, account, logged-in, and active cart/session-cookie contexts on normal WooCommerce behavior.
* Keeps cart-fragments Delay and Suppress empty-cart execution mutually exclusive during dashboard saves/imports.

= 2.59.06.72 =
* Reworks the WooCommerce dashboard card into "WooCommerce Controls" and moves WooCommerce Safe Mode into that section so WooCommerce cache safety, request timing, and cleanup controls live together.
* Adds a visible WooCommerce frontend strategy dropdown with Off, Safe, Balanced, Aggressive, and Custom presets that write the existing cart-fragments delay and WooCommerce asset-cleanup toggles instead of adding a hidden runtime switch.
* Renames the cart-fragments timing control to "WooCommerce release timer" to mirror the general Delayed JS timing model.

= 2.59.06.71 =
* Renames the "Safe Asset Cleanup" dashboard card to "WooCommerce Asset Timing" so the section matches its WooCommerce-specific controls.
* Adds visible WooCommerce cart-fragments delay controls that can queue `get_refreshed_fragments` AJAX on anonymous cacheable pages and release it with the Delayed JS timing model or a WooCommerce-specific timer, while skipping logged-in, cart, checkout, account, and active cart/session-cookie contexts.
* Adds `assets/js/woocommerce-cart-fragments-delay.js` as the frontend helper for the new WooCommerce cart-fragments delay feature and keeps it protected as an UltraCache-owned helper script.

= 2.59.06.70 =
* Removes hidden runtime JavaScript safeguards for WordPress inline dependency blocks, GTM bootstrap snippets, and third-party dependency-library delay bypasses so Browser Scanner and Console Error Handler can propose visible "Defer Instead of Delay" or "Do Not Defer or Delay" safeguards from actual detected breakage.
* Moves inline analytics delay markers such as `gtag(`, `dataLayer`, and `gtm.start` into the visible Safe Third-Party Delay Patterns defaults instead of matching them through a private inline-script list.
* Removes hidden CSS and asset cleanup safeguards from CSS bundle exclusions, aggressive async CSS admin-asset blocking, frontend authoring asset stripping, and broad icon-font auto-detection; visible lists and scanner output are now authoritative, while UltraCache-owned helper JavaScript remains internally protected.
* Updates Delay icon fonts UI copy to clarify that only entries in the visible font pattern list are delayed.

= 2.59.06.69 =
* Makes the "Defer Instead of Delay" and "Do Not Defer or Delay" JavaScript safeguard lists mutually exclusive: appending to one removes overlapping entries from the other, paired saves send both final lists together, and settings sanitization removes remaining overlaps.

= 2.59.06.68 =
* Renames JavaScript safeguard action labels and scan status text so findings are described as appending to "Defer Instead of Delay" or "Do Not Defer or Delay" instead of the ambiguous "fallback exclusion" wording.

= 2.59.06.67 =
* Forces the Frontend JavaScript Manipulation safeguard editors for "Defer Instead of Delay" and "Do Not Defer or Delay" into a true two-column, one-row layout instead of relying on utility classes that could stack them vertically.

= 2.59.06.66 =
* Changes the Balanced and Aggressive profile default CSS bundle mode from Safe to Aggressive while keeping CSS bundling enabled and user-maintained CSS exclusions preserved.
* Keeps the Aggressive profile on native Defer as the base JavaScript strategy instead of broad Delay all JS, with targeted delay modules still enabled for speed.
* Makes the force-defer list act as "Defer Instead of Delay" across Delay all JS, targeted third-party delay, non-critical/local delay, LCP Boundary Delay, and delayed-placeholder restoration.
* Improves runtime JS diagnostics so missing WordPress/core globals suggest both the provider and the crashing consumer, filters UltraCache helper stack frames, detects duplicate-execution redeclare errors, and recognizes jQuery Migrate shorthand failures.
* Fixes pasted console parsing for jQuery Migrate shorthand failures where Chrome prefixes the TypeError with `jquery.min.js?...` and appends the `JQMIGRATE: Migrate is installed` notice, so the real error still produces a `jquery-migrate.min.js` suggestion.
* Lets Browser Scanner and Console Error Handler escalate persistent findings from "Defer Instead of Delay" to the stronger "Do Not Defer or Delay" fallback instead of hiding already-deferred suggestions.
* Updates the JavaScript safeguard UI to pair "Defer Instead of Delay" with the stronger "Do Not Defer or Delay" fallback and shared save/append controls.

= 2.59.06.64 =
* Fixes ordered delayed-JavaScript replay when another runtime removes, replaces, or independently restores an UltraCache placeholder while the loader is processing its original DOM snapshot.
* Replaces delayed placeholders atomically instead of inserting the executable script while the inert placeholder is still present.
* Skips detached placeholders and suppresses duplicate execution by preserved script ID or exact source URL plus execution mode; records skipped duplicate/detached counts on the document element for diagnostics.
* Makes the force-defer list act as "Defer Instead of Delay" across Delay all JS, targeted third-party delay, non-critical/local delay, LCP Boundary Delay, and delayed-placeholder restoration.
* Improves runtime JS diagnostics so missing WordPress/core globals suggest both the provider and the crashing consumer, filters UltraCache helper stack frames, detects duplicate-execution redeclare errors, and recognizes jQuery Migrate shorthand failures.
* Lets Browser Scanner and Console Error Handler escalate persistent findings from "Defer Instead of Delay" to the stronger "Do Not Defer or Delay" fallback instead of hiding already-deferred suggestions.
* Updates the JavaScript safeguard UI to pair "Defer Instead of Delay" with the stronger "Do Not Defer or Delay" fallback, and changes the Aggressive profile to use native Defer instead of broad Delay all JS.

= 2.59.06.63 =
* Prevents the CSS bundle source scan and final page warm loopbacks from receiving mod_pagespeed/ngx_pagespeed-rewritten HTML by sending the supported `PageSpeed: off` and backward-compatible `ModPagespeed: off` request headers.
* Requests unrewritten origin HTML for those internal operations so PageSpeed wrapper URLs such as `A.*.css.pagespeed.cf.*.css` are not passed to UltraCache cache-write validation when the server honors the supported per-request override.

= 2.59.06.62 =
* Fixes managed `wp-config.php` block replacement and uninstall removal so only the delimited block is removed while the surrounding line breaks are preserved; `<?php` can no longer be joined to the following `define()` statement.
* Strengthens candidate `wp-config.php` validation by requiring a normal full PHP opening tag, preventing malformed `<?phpdefine(...)` content from passing as a short opening tag plus an unknown `phpdefine()` call.
* Applies the same boundary-preserving removal and full-opening-tag validation to WordPress uninstall cleanup.

= 2.59.06.61 =
* Removes the standalone Redis manual-test control and its dedicated REST/action-queue surface so unsaved form values are no longer mixed with the already-bootstrapped object-cache runtime.
* Makes Save Redis Settings perform Redis connection, authentication, and read/write validation before changing wp-config.php, stored settings, or the generated object-cache drop-in; failed validation leaves the previous configuration untouched.
* Reloads after a verified Redis save, performs a one-time payload probe against the actually active backend, and labels the result with the tested backend.
* Replaces duplicate object-cache status rows with a concise runtime status, configured backend, Redis connection, PHP extension availability, backend-specific payload probe, and Redis prefix.

= 2.59.06.60 =
* Removes redundant Google-hosted Maps tile/static-host and reCAPTCHA static-host matcher fragments while retaining the existing Google Maps and reCAPTCHA entry-point patterns.
* Replaces the Google Fonts, dashboard heavy-action, and cron warm-up option-based locks with a shared token-guarded `ultracache_locks` table supporting atomic acquisition, expired-lock takeover, renewal, and owner-only release.
* Replaces the two remaining create-or-update `add_option()` branches with direct non-autoloaded `update_option()` calls, leaving no direct `add_option()` calls in UltraCache.
* Adds the lock table to activation, validated table handling, bounded expired-row cleanup, Delete All cleanup, and WordPress uninstall cleanup.

= 2.59.06.59 =
* Documents the two intentional `var_export( ..., true )` calls used to generate valid PHP string literals for UltraCache-managed `wp-config.php` password constants.
* Adds narrowly scoped PHPCS exceptions for `WordPress.PHP.DevelopmentFunctions.error_log_var_export`; the calls return strings and do not emit debug output.

= 2.59.06.58 =
* Completes the final reviewer validation across declared URLs, WordPress-native asset enqueueing, remote dependency checks, path resolution, guarded storage, late escaping, prefixes/dynamic names, generated drop-ins, and full uninstall cleanup.
* Regenerates `languages/ultracache.pot` from the current PHP and JavaScript sources, updates source references/header metadata, adds previously missing translatable strings, and removes obsolete catalog entries.
* Revalidates the AVIF Imagick/GD/WebP fallback policy and Safe CLS responsive-dimension safeguards without changing their runtime behavior.

= 2.59.06.57 =
* Removes 221 `function_exists()` declaration wrappers and six `class_exists()` declaration wrappers from UltraCache-owned functions/classes, leaving guards only for the standard `WP_Object_Cache` and `wp_cache_*` drop-in symbols.
* Gives advanced-cache and object-cache internal helpers separate `ultracache_advanced_cache_*` and `ultracache_object_cache_*` names so both drop-ins can load without shared helper declarations or load-order fallbacks.
* Prefixes the remaining plugin-owned object-cache keys for action-job schema/rows, cron-warm schema, runtime JS diagnostic jobs, CSS rewrite-map rows, and payload diagnostics with `ultracache_`.
* Removes the unused case-only REST class alias and the duplicate admin `ultracache-root` element/lookup.

= 2.59.06.56 =
* Preserves every existing image `width` and `height` attribute instead of replacing percentage, `auto`, empty, zero, boolean, or otherwise non-numeric values with intrinsic pixel dimensions.
* Skips Safe CLS processing for an image when either existing dimension attribute is non-numeric, and skips inline `max-width: none` images without injecting plugin CSS or changing responsive styles.
* When exactly one positive numeric dimension exists, calculates only the missing dimension from the resolved intrinsic aspect ratio instead of copying the source image's full opposite dimension.
* Adds both intrinsic dimensions only when both attributes are absent, while leaving `srcset`, `sizes`, inline styles, classes, and responsive theme behavior unchanged.
* Extends the Safe CLS raster-image exclusion to SVGZ as well as SVG and bumps release metadata from 2.59.06.55 to 2.59.06.56. No files or directories were added or deleted.

= 2.59.06.55 =
* Makes AVIF conversion prefer Imagick first and use GD only when a real transparent/semi-transparent AVIF encode-and-decode probe verifies alpha preservation.
* Adds an equivalent real Imagick AVIF alpha probe instead of trusting format advertisement alone, so unusable AVIF codecs are not treated as supported.
* Falls back to WebP as the effective media output when neither Imagick nor GD can produce a verified alpha-safe AVIF file, and keeps WebP available as the per-image fallback when an AVIF file is missing.
* Detects the source image by its real MIME type as well as its extension, handles renamed PNG/JPEG files correctly, and rejects SVG/SVGZ from all raster conversion paths.
* Preserves alpha in the direct GD and Imagick conversion paths and updates media support/reset probe cache keys.

= 2.59.06.54.01 =
* Prevents the Delete Everything/deactivation and WordPress uninstall requests from recreating UltraCache-owned database state after cleanup by defining an explicit uninstall-in-progress guard before teardown.
* Skips deactivation-hook work, cache-asset/CSS-rewrite table creation, and object-cache flush-report persistence while the uninstall guard is active.
* Refactors uninstall table removal through a validated UltraCache-only helper, verifies each requested table is absent, and repeats the two affected table drops as the final full-cleanup operation.
* Deletes and re-verifies the final `ultracache_object_cache_last_flush_report`, `ultracache_cache_asset_refs_db_version`, and `ultracache_css_rewrite_map_db_version` options after drop-in/file cleanup.

= 2.59.06.54 =
* Removes the uniquely delimited UltraCache managed-constants block from the exact active `wp-config.php` during plugin uninstall, regardless of the selected data-retention policy.
* Resolves only the configuration file loaded by WordPress or authoritatively located by WP-CLI; no WordPress-root or parent-directory path guessing is added.
* Writes only through `WP_Filesystem::put_contents()`, validates the resulting PHP, verifies the update by SHA-256 read-back, and retains the original contents only in memory for immediate verified rollback.

= 2.59.06.53 =
* Replaces every internal short-form plugin identifier with the full ultracache/ULTRACACHE prefix across PHP, JavaScript, generated drop-in templates, persistent keys, hooks, nonces, REST/AJAX integration, HTML identifiers, diagnostics, uninstall cleanup, translations, and documentation.
* Removes the unused action-queue option helper and obsolete action_jobs_rows_v1 cache cleanup.
* Bounds runtime JavaScript scan transient names with a fixed MD5 suffix.
* Corrects Delete All and uninstall cleanup for the active action-queue heavy lock, cron warm transient, and dynamic Google Fonts database locks while removing obsolete option cleanup entries.

= 2.59.06.52 =
* Encodes all frontend helper configuration passed through `wp_add_inline_script()` with `JSON_HEX_TAG`, `JSON_HEX_AMP`, `JSON_HEX_APOS`, and `JSON_HEX_QUOT` to prevent inline-script context breakout across all five helper-data callers.
* Restricts the WordPress-engine full-page cache output path to canonical files inside `ULTRACACHE_CACHE_DIR` whose basename matches `index-(orig|avif|webp)-<32-character MD5>.html` before raw HTML output.
* Restricts the early `advanced-cache.php` drop-in output path to canonical files inside `ULTRACACHE_CACHE_DIR` using the same UltraCache filename format, allowing only the generated `.html`, `.html.gz`, and `.html.br` payloads.
* Documents the two intentional raw full-page cache output paths with narrow PHPCS exceptions; HTML escaping is not applied because it would corrupt the complete cached WordPress response.

= 2.59.06.51 =
* Removes the remaining native filesystem fallback branches from guarded reads, file metadata, directory listing/deletion, media optimized-file checks, runtime cleanup, diagnostics, font cleanup, profiling, warm-crawl cleanup, and uninstall cleanup. These paths now fail closed when WP_Filesystem is unavailable.
* Replaces `tempnam()` with WordPress `wp_tempnam()` and verifies that the returned temporary path remains inside the requested guarded directory.
* Removes confirmed unused helpers: `ultracache_safe_chmod()`, `ultracache_safe_stream_set_blocking()`, `ultracache_uninstall_home_path()`, `ultracache_json_encode_for_inline_script()`, `ultracache_content_cache_reference_matches()`, `ultracache_request_profile_hook_priority_details()`, `ultracache_font_css_file_diagnostics()`, and the obsolete native recursive-delete helper.
* Keeps all existing storage locations and runtime behavior otherwise unchanged. No files or directories were added or deleted.

= 2.59.06.50 =
* Removes the unused `ultracache_safe_copy()` helper and its native `copy()` fallback.
* Removes the native `file_put_contents()` fallback from `ultracache_safe_file_put_contents()`; generated UltraCache files now write only through `WP_Filesystem::put_contents()`.
* Removes the native `rename()` path from `ultracache_safe_rename()`; generated cache and drop-in temporary files now move into place only through `WP_Filesystem::move()`.
* Replaces the temporary `.htaccess` file and rename workflow with a direct `WP_Filesystem::put_contents()` write. UltraCache retains the original `.htaccess` content only in memory, verifies the new content by SHA-256 read-back, restores or removes the file if verification fails, and removes the obsolete temporary `.htaccess` writable-path allowance.

= 2.59.06.49 =
* Restores the Redis and Varnish password fields as explicit administrator controls. Saving a non-empty Redis password writes `WP_REDIS_PASSWORD`; saving a non-empty Varnish password writes `ULTRACACHE_VARNISH_PASSWORD`. Empty fields preserve existing managed values, and dedicated remove actions delete only UltraCache-managed values.
* Adds a uniquely delimited UltraCache managed-constants block to the active `wp-config.php`. Existing `WP_CACHE`, `WP_REDIS_PASSWORD`, or `ULTRACACHE_VARNISH_PASSWORD` definitions outside that block are never moved, replaced, or removed; externally managed password constants are reported as configured and remain read-only in the dashboard.
* Replaces the previous custom wp-config.php backup, temporary-file, native copy, native file-write, and native rename workflow. The new writer uses `WP_Filesystem::get_contents()` and `WP_Filesystem::put_contents()`, validates the generated PHP, verifies the written content by SHA-256 read-back, and retains the original content only in memory for immediate verified rollback.
* Adds combined settings/wp-config transaction handling. If page-cache, browser-cache, or object-cache synchronization fails after a constants update, UltraCache restores the previous settings and original wp-config.php content; an unverified rollback is surfaced as a dedicated error instead of being hidden by the original save failure.
* Generates constant values with safe PHP literals and validates managed-block parsing for quotes, backslashes, line breaks, duplicate definitions, external definitions, and the active `WP_CACHE` state.
* Password values remain excluded from WordPress options, dashboard responses, REST responses, WP-CLI output, diagnostics, logs, embedded runtime configuration, and generated cache drop-ins. Responses expose only configured/managed/external status flags.
* Updates REST permissions so password writes require both `manage_options` and `activate_plugins` plus the existing REST nonce. The dashboard never displays the stored value; a blank field means keep, while removal requires a separate explicit action.
* Removes the obsolete wp-config backup-registry cleanup entry rather than adding previous-version cleanup. No migration, legacy lookup, backward-compatibility layer, old-file cleanup, or old-option cleanup was added.

= 2.59.06.48 =
* Removes the generated executable runtime-secret PHP sidecar and all related path discovery, rendering, synchronization, protection, diagnostics, object-cache loading, and uninstall code. No replacement secret file is created.
* Redis authentication now uses only the standard `WP_REDIS_PASSWORD` constant from the active `wp-config.php`. Scalar passwords and Redis ACL arrays containing username/password are supported; `WP_REDIS_USERNAME` remains an optional scalar username source.
* Varnish authentication now uses only the uniquely prefixed `ULTRACACHE_VARNISH_PASSWORD` constant from the active `wp-config.php`.
* Derives the early-runtime revalidation/control secret deterministically from the existing WordPress authentication keys and salts, so no additional secret needs to be persisted in the database or filesystem.
* Updates `advanced-cache.php` and `object-cache.php` generation so early Redis authentication and runtime-control validation read constants/salts directly, without requiring a generated secret include.
* Removes Redis and Varnish password inputs from REST update/test schemas and WP-CLI mutation paths. Dashboard fields are read-only status indicators, and client/API/CLI responses expose only configured yes/no flags.
* Forces any transient dashboard password keys to remain blank before option persistence. Runtime consumers hydrate credentials from constants only; diagnostics and logs expose no secret values.
* Updates readme documentation with the required `WP_REDIS_PASSWORD` and `ULTRACACHE_VARNISH_PASSWORD` definitions.

= 2.59.06.47 =
* Removes the generated executable `runtime-config.php` sidecar and its JSON predecessor. UltraCache no longer writes, loads, protects, reconciles, or cleans a standalone runtime configuration file.
* Embeds the normalized secret-free early page-cache configuration directly into the standard WordPress `advanced-cache.php` drop-in as a JSON-decoded array generated at drop-in build time.
* Adds an SHA-256 embedded-configuration marker to `advanced-cache.php`; drop-in status and diagnostics now verify that the embedded configuration matches the current dashboard settings.
* Removes the dedicated runtime-config bootstrap hook, file synchronization cycle, protection-file generation, warm-up sync call, path helper, diagnostics path card, and uninstall cleanup associated with the deleted sidecar architecture.
* Preserves the current runtime secret file architecture unchanged for the following dedicated secret-constants stage. Redis/Varnish password storage and wp-config.php writing are outside this patch.
* Updates dashboard diagnostics to report `embedded_in_advanced_cache` configuration instead of a runtime-config.php file.

= 2.59.06.46.02 =
* Corrective validation patch for the final path-refactor test. `ultracache_wordpress_admin_include_path()` now rejects any value containing `/` or `\` before basename normalization and allowlist matching, so values such as `../file.php` cannot be reduced to an approved filename.
* includes/core/functions.php: extends `ultracache_loaded_wp_config_path()` for WP-CLI. Normal web requests continue to use PHP's loaded-file list; WP-CLI requests use `WP_CLI\Utils\locate_wp_config()` because WP-CLI evaluates wp-config.php instead of including it. UltraCache adds no ABSPATH/root/parent search fallback.
* The existing wp-config read/write, backup, temporary-file, atomic-replace, capability, and guard behavior remains unchanged. The exact path returned by either authoritative runtime source continues to be the only primary config accepted by UltraCache's companion-path guard.

= 2.59.06.46.01 =
* Corrective public-path compliance patch after the 2.59.06.46 scan. Functional plugin, theme, uploads, wp-includes, and wp-admin URL matching no longer assumes default directory names such as `/plugins/`, `/themes/`, `/uploads/`, `/wp-includes/`, or `/wp-admin/`.
* includes/core/functions.php: adds `ultracache_wordpress_includes_public_path()` and `ultracache_wordpress_admin_public_path()`, resolving root-relative WordPress core/admin public paths through `includes_url()` and `admin_url()` while preserving file-versus-directory references.
* JavaScript optimization, LCP protection, runtime scanning, cache bypass, diagnostics, and default dependency exclusions now consume dynamic WordPress public-path resolvers. Plugin-specific CDN heuristics retain only owner/slug fragments such as `/woocommerce/assets/`; they no longer assume the configured plugins root name.
* includes/admin/class-admin-trait.php and includes/admin-dashboard.js: expose resolved public paths through the existing `wp_add_inline_script()` configuration and use them for WooCommerce matching and path examples. Dead profile copies of preserved path settings were removed.
* Product-filter, Slider Revolution, Elementor, Divi, WooCommerce, WordPress core JS, generated-assets, uploads, plugin, and theme references now derive from WordPress APIs. No remote request, asset load, storage location, cache key, setting key, migration, or compatibility fallback was added.

= 2.59.06.46 =
* Final path-compliance scan: verifies that active PHP code contains no `WP_CONTENT_DIR` or `WP_PLUGIN_DIR` references, no hardcoded plugin/uploads filesystem roots, and no `ABSPATH`-based wp-config.php assumptions. Direct-access guards remain unchanged; the unavoidable WordPress core-root `ABSPATH` and `WPINC` uses remain isolated in their documented canonical resolvers.
* includes/core/functions.php: adds `ultracache_mu_plugins_root_dir()` and `ultracache_mu_plugins_root_url()` as the only access points for WordPress's configurable must-use plugin path/URL constants, because WordPress exposes no public helpers for those roots. Font scanning, path-to-URL conversion, profiler ownership, and readable-root guards now consume the centralized resolvers instead of reading `WPMU_PLUGIN_DIR` / `WPMU_PLUGIN_URL` directly.
* readme.txt and README.md: replaces default-layout examples such as `wp-content/uploads/...` and `/wp-content/plugins/` with wording based on the active WordPress uploads/plugins directories, so the documentation remains correct for custom content, uploads, and plugin locations.
* ultracache.php: replaces the object-cache failure message's literal `wp-content/object-cache.php` reference with the WordPress content-directory location, preserving the same error condition and action.

= 2.59.06.45 =
* includes/core/functions.php: adds `ultracache_loaded_wp_config_path()` to resolve the exact `wp-config.php` file already loaded by the current WordPress request through PHP's authoritative `get_included_files()` list. The plugin no longer assumes that wp-config.php is under the WordPress core root or one directory above it. No root/parent fallback search is retained.
* includes/core/functions.php: adds `ultracache_is_loaded_wp_config_companion_path()` and updates readable, writable, and destructive path guards so wp-config access is limited to the actually loaded config file and UltraCache's existing temporary/backup filename patterns in that exact directory. The write, backup, temporary-file, and atomic-replace behavior itself is intentionally unchanged for the separate reviewer finding.
* ultracache.php: changes `get_wp_config_path()` to consume the loaded-config resolver while preserving the existing readability check, error handling, WP_CACHE parser, and enable/disable workflow.
* Removes the final wp-config root/parent path assumptions from the active runtime. Existing WordPress core-root helpers remain only for genuine core paths and includes.
* This patch changes wp-config.php path discovery only. It does not alter wp-config.php contents, backup retention, temporary files, atomic writes, runtime secrets, cache storage, drop-ins, settings, or uninstall policy. No migration, legacy lookup, compatibility fallback, file move, or directory move was added.

= 2.59.06.44 =
* includes/core/functions.php: adds `ultracache_wordpress_admin_include_path()` and `ultracache_require_wordpress_admin_include()` as the single approved resolver/loader for the WordPress core admin files used by UltraCache (`file.php`, `image.php`, `plugin.php`, and `upgrade.php`). The unavoidable WordPress core-root `ABSPATH` dependency is isolated in `ultracache_wordpress_core_root_dir()`; callers no longer concatenate `ABSPATH . 'wp-admin/includes/...'` themselves.
* UltraCache table installers, image-editor diagnostics, plugin inventory/deactivation, home-path discovery, and WP_Filesystem initialization now load their required WordPress core APIs through the centralized helper. Existing functions, timing, database schemas, and failure returns remain unchanged.
* includes/core/functions.php and ultracache.php: replaces remaining non-guard WordPress-root uses for cron-command generation, runtime path identity, and existing wp-config.php candidate construction with `ultracache_wordpress_core_root_dir()`. This changes path discovery only; wp-config.php read/write behavior is intentionally unchanged for its later dedicated reviewer-compliance design.
* uninstall.php: adds uninstall-local WordPress core/admin include resolvers and removes repeated direct `ABSPATH . 'wp-admin/includes/file.php'` construction. The single unavoidable uninstall `ABSPATH` read is isolated and documented.
* Direct-access guards and generated runtime-file guards using `defined('ABSPATH')` remain unchanged because they are access-control checks, not file/directory location logic. `WPINC` remains isolated in the existing canonical wp-includes resolver.

= 2.59.06.43 =
* includes/core/functions.php: changes `ultracache_runtime_config_storage_dir()` from direct `WP_CONTENT_DIR` concatenation to the existing `ultracache_wordpress_content_dir()` resolver backed by `WP_Filesystem_Base::wp_content_dir()`. `runtime-config.php` and `runtime-config.json` remain at the same WordPress content-directory `cache/ultracache/` location; this patch changes path discovery only.
* includes/core/functions.php: removes the remaining direct `WP_CONTENT_DIR` candidate from runtime-secret path discovery and uses the centralized WordPress content-directory resolver instead. Runtime-secret location, file format, protection, and read/write behavior remain unchanged for their later dedicated reviewer-remediation stage.
* readme.txt and README.md: describe required cache drop-ins as residing in the WordPress content directory without presenting the internal `WP_CONTENT_DIR` constant as the integration path.
* Removes all active PHP references to `WP_CONTENT_DIR` while retaining required WordPress-core `ABSPATH`/`WPINC` use, wp-config.php discovery, and the current runtime configuration architecture for their separate roadmap stages.

= 2.59.06.42 =
* uninstall.php: replaces direct `WP_CONTENT_DIR` use for `advanced-cache.php` and `object-cache.php` with `ultracache_uninstall_wordpress_content_dir()`, which resolves the active WordPress content directory through `WP_Filesystem_Base::wp_content_dir()` before constructing the required drop-in paths.
* uninstall.php: centralizes the current runtime-config cleanup path through `ultracache_uninstall_runtime_config_storage_dir()` instead of directly concatenating `WP_CONTENT_DIR . '/cache/ultracache/'`. The runtime-config files remain in their existing location until the later dedicated runtime-configuration storage stage.
* uninstall.php: routes generated CSS/font/deferred-JS cleanup through the existing WordPress uploads resolver, so uninstall uses the same `uploads/ultracache/...` roots as runtime writers and does not carry legacy cache-directory lookup or migration logic.
* uninstall.php: removes redundant `ABSPATH` and `WP_CONTENT_DIR` candidates from runtime-secret path identity and uses the WordPress home/content resolvers instead. WordPress core include paths that officially require `ABSPATH` remain unchanged.
* This patch changes uninstall path resolution only. Runtime storage, wp-config.php modification behavior, runtime-secret architecture, cache operation, generated-asset generation, and plugin settings are unchanged. No migration, legacy path lookup, compatibility fallback, file move, or directory move was added.

= 2.59.06.41 =
* includes/core/functions.php: replaces UltraCache's direct `WP_CONTENT_DIR` cache-drop-in resolver with `ultracache_wordpress_content_dir()`, which obtains the active WordPress content-directory path from `WP_Filesystem_Base::wp_content_dir()`. `advanced-cache.php` and `object-cache.php` remain in the WordPress-required content-directory root.
* includes/core/functions.php: adds dedicated WordPress Filesystem helpers for cache-drop-in existence, reads, atomic replacement, deletion, backup copying, size, and modification time. Drop-in operations no longer use UltraCache's generic filesystem wrappers or native PHP fallback operations.
* includes/engine/class-engine-dropin-lifecycle-trait.php: routes advanced-cache.php status, comparison, installation, replacement, and removal through the dedicated WP_Filesystem drop-in API. The generated drop-in contents and runtime behavior are unchanged.
* includes/class-object-cache-manager.php: routes object-cache.php status, ownership verification, installation, replacement, and removal through the same dedicated WP_Filesystem drop-in API. Object-cache backend selection and runtime configuration are unchanged.
* includes/settings/class-settings-trait.php: resolves drop-in conflicts through the canonical Filesystem API path, reads metadata through WP_Filesystem, and performs optional backup/copy/delete operations through the same filesystem transport. Removes the direct `WP_CONTENT_DIR` availability checks from active drop-in management.
* includes/diagnostics/class-diagnostics-trait.php and includes/cli/class-wp-cli-settings-stats-trait.php: use the canonical drop-in existence helper instead of native filesystem checks.
* This patch changes only cache-drop-in path resolution and lifecycle I/O. Page-cache/object-cache data storage, generated assets, runtime-config.php, runtime secrets, wp-config.php handling, and uninstall cleanup remain assigned to their separate roadmap stages. No migration, legacy path lookup, or compatibility fallback was added.

= 2.59.06.40 =
* includes/core/functions.php: changes the canonical page-cache root from `wp-content/cache/ultracache/` to the WordPress-resolved `uploads/ultracache/cache/` path and changes disk object-cache storage from `wp-content/cache/ultracache-objects/` to `uploads/ultracache/object-cache/`.
* templates/advanced-cache.php.tpl and includes/engine/class-engine-dropin-lifecycle-trait.php: replace hardcoded `WP_CONTENT_DIR` cache paths with build-time injected, WordPress-resolved cache and runtime-config paths. The advanced-cache drop-in location itself remains unchanged under the WordPress content directory.
* Page-cache HTML, compressed variants, locks, temporary media files, drop-in backups, diagnostics profiles, and the legacy file analytics buffer now resolve below `uploads/ultracache/cache/`. Existing files are not moved or read from legacy paths.
* ultracache.php: keeps `runtime-config.php` and its protection files at their current dedicated path until the later runtime-configuration storage stage, so executable runtime configuration is not moved into uploads.
* uninstall.php: updates clean-install cleanup roots to the new uploads page-cache and disk-object-cache directories, with no migration or legacy cache cleanup logic.
* readme.txt and README.md: document the new WordPress uploads-based cache and object-cache layout.

= 2.59.06.39 =
* includes/diagnostics/class-diagnostics-trait.php: replaces stale font-pipeline, CSS-bundle storage, and CSS-bundle summary readers that still looked under the internal page-cache directory with `ultracache_generated_asset_dir()` calls. Diagnostics now inspect the same WordPress uploads locations used by the writers for css-bundles, font-css, optimized-css, google-fonts, and the CSS bundle manifest.
* includes/cli/class-wp-cli-settings-stats-trait.php: changes the WP-CLI CSS bundle self-test from `wp-content/cache/ultracache/css-bundles/manifest.json` to the canonical `uploads/ultracache/css-bundles/manifest.json` path resolved through `ultracache_generated_asset_dir()`.
* ultracache.php, uninstall.php: adds the `deferred-inline-js` bucket to Delete All and uninstall generated-runtime cleanup so every ephemeral browser-loaded generated asset directory is covered. Persistent optimized AVIF/WebP files under `uploads/ultracache/images` remain intentionally excluded.
* Confirms that all active generated-asset writers already use the centralized WordPress uploads helpers introduced before this patch: CSS bundles, optimized CSS, font CSS, localized Google Fonts, deferred inline JavaScript, and optimized images remain under `uploads/ultracache/...`. This patch removes the remaining stale cache-root readers; it does not move files and adds no legacy lookup, migration, or fallback path.
* Page-cache, disk-object-cache, logs/analytics, drop-ins, wp-config.php, and runtime-secret storage remain unchanged for their dedicated roadmap stages.

= 2.59.06.38 =
* includes/core/functions.php: adds `ultracache_plugin_dir()` and `ultracache_plugin_url()` as the single WordPress-native resolver pair for UltraCache-owned files and URLs. Both are derived from `ULTRACACHE_FILE` through `plugin_dir_path()` / `plugin_dir_url()` and sanitize all optional relative paths.
* ultracache.php, includes/class-media-converter.php, includes/class-object-cache-manager.php, includes/admin/class-admin-trait.php, includes/diagnostics/class-diagnostics-trait.php, includes/engine/class-engine-dropin-lifecycle-trait.php, includes/engine/class-engine-frontend-assets-trait.php: replaces runtime concatenation of `ULTRACACHE_PATH`, `ULTRACACHE_URL`, and direct `plugins_url()` calls with the centralized plugin path/URL helpers. The initial bootstrap include remains based on the main-file constants because the helper file must load first.
* includes/core/functions.php: adds `ultracache_uploads_storage_dir()` and `ultracache_uploads_storage_url()` as the single filesystem/URL joiners for WordPress uploads. They consume the existing `ultracache_uploads_base_info()` result and preserve custom uploads directories, custom uploads URLs, multisite paths, and URL-encoded relative segments.
* includes/core/functions.php: routes generated CSS/JS/font assets, optimized image paths, uploads public-path markers, and their URLs through the centralized uploads helpers without changing their current `uploads/ultracache/...` locations.
* includes/engine/class-engine-media-image-trait.php, includes/media/class-media-html-rewrite-trait.php, includes/media/class-media-path-url-trait.php, includes/media/class-media-queue-trait.php: replaces seven direct `wp_get_upload_dir()` reads with `ultracache_uploads_base_info()` so media resolution, HTML rewriting, on-demand queue discovery, and attachment lookup share the same normalized uploads identity.
* This patch only centralizes path resolution. Page-cache, disk-object-cache, logs, analytics, drop-in, wp-config.php, and runtime-secret storage locations remain unchanged for their dedicated roadmap stages. No migration, legacy lookup, compatibility fallback, file move, or directory move is added.

= 2.59.06.37 =
* includes/core/functions.php: adds centralized WordPress-aware resolvers for the standard plugins root, WordPress core root, and wp-includes directory. The plugins root is now derived from the main plugin file through plugin_dir_path(), while the unavoidable core-root ABSPATH/WPINC use is isolated and documented in one place.
* includes/core/functions.php: replaces every active WP_PLUGIN_DIR use in installed-plugin resolution, font scanning, public URL/path mapping, readable-root allowlists, and callback profiling with the centralized plugins-root resolver. Callback profiling now classifies uploads through wp_upload_dir() data instead of a generic WP_CONTENT_DIR path.
* includes/core/functions.php, includes/diagnostics/class-diagnostics-trait.php: changes diagnostic path classification/redaction from direct WP_CONTENT_DIR/ABSPATH comparisons to known plugin, theme, uploads, WordPress-core, and document-root resolvers. No absolute server paths are exposed.
* includes/core/functions.php, includes/class-object-cache-manager.php, includes/engine/class-engine-analytics-trait.php: replaces filesystem-path-based Redis, APCu, and analytics namespace seeds with one installation-stable identity based on database identity, table prefix, and multisite network constants.
* templates/object-cache.php.tpl, templates/advanced-cache.php.tpl, includes/engine/class-engine-dropin-lifecycle-trait.php: injects the same non-filesystem namespace seed into generated drop-ins so dashboard/runtime diagnostics and drop-in cache operations use identical Redis/APCu/analytics prefixes.
* Namespace keys intentionally change in this clean-install pre-public build. No legacy-prefix lookup, cache-key migration, or backward-compatibility fallback is added.
* Existing page-cache, disk-object-cache, generated-asset, drop-in, wp-config.php, and runtime-secret storage locations remain unchanged for their later dedicated roadmap stages.

= 2.59.06.36 =
* includes/admin-dashboard.js, PERFORMANCE_PROFILES: removes the three dead Safe, Balanced, and Aggressive copies of `delayFunctionalThirdPartyJsPatterns`. Profile application already preserves this user-editable setting through `PERFORMANCE_PROFILE_PRESERVED_SETTING_KEYS`, so these copied values were never applied.
* Keeps the canonical PHP default matching-fragment list unchanged for installation defaults, reset/default restoration, and the dashboard Populate action. The listed third-party domains are detection patterns for scripts already present on the site; UltraCache does not request or load files from those providers.

= 2.59.06.35 =
* includes/engine/class-engine-js-optimization-trait.php, build_deferred_external_inline_script_tag(): replaces the manually compiled `<script src="..." defer>` markup for generated deferred inline-JS assets with `wp_get_script_tag()`, while preserving the generated asset URL, defer state, original attributes, and UltraCache metadata.
* includes/engine/class-engine-js-optimization-trait.php, restore_delayed_script_record_tag(): replaces manual opening/closing script reconstruction with `wp_get_script_tag()` for external scripts and `wp_get_inline_script_tag()` for inline scripts, while preserving the restored source, body, nonce, integrity, crossorigin, referrer policy, ID, and other valid original attributes.
* includes/engine/class-engine-js-optimization-trait.php, build_delayed_script_tag(): replaces manually concatenated delayed external-script placeholder markup with `wp_get_script_tag()` and passes unescaped attribute values to WordPress so core performs final attribute serialization and escaping.
* includes/engine/class-engine-js-optimization-trait.php, build_delayed_inline_script_tag(): replaces manually concatenated delayed inline-script placeholder markup with `wp_get_inline_script_tag()` and lets WordPress serialize both the placeholder attributes and inline body.
* includes/engine/class-engine-js-optimization-trait.php, apply_delayed_script_replacements_with_processor(): removes the unreachable `'<script>'` default value from the required record opening tag, eliminating the reviewer-detected raw script literal without adding a fallback path.
* includes/engine/class-engine-js-optimization-trait.php, collect_js_inline_dependency_defer_recommendations(): stops rebuilding a temporary `<script>` opening tag only to inspect its ID and reads the ID from the complete regex-matched tag instead.
* Removes the related NonEnqueuedScript PHPCS suppressions because the affected final-HTML transformations now use the WordPress 5.7+ script-tag APIs. Existing plugin-owned admin and frontend files continue to load through `wp_register_script()`, `wp_enqueue_script()`, and `wp_add_inline_script()`.

= 2.59.06.34 =
* Corrects the PayPal Terms and Privacy URLs in readme.txt and README.md to the working US Legal Hub URLs.

= 2.59.06.33 =
* ultracache.php lines 6 and 21: bumps the plugin header and ULTRACACHE_VERSION constant from 2.59.06.32 to 2.59.06.33.
* ultracache.php lines 1015-1023: replaces duplicated ABSPATH-based runtime-secret token/path construction with the shared ultracache_get_runtime_secret_site_token() and ultracache_get_runtime_secret_path() helpers.
* ultracache.php lines 3915-3918: resolves the browser-cache .htaccess from get_home_path() through ultracache_get_wordpress_home_path(), so WordPress subdirectory installations update the public home root instead of ABSPATH.
* includes/core/functions.php lines 608-704: adds shared WordPress-home, effective document-root, stable runtime-secret token, and canonical outside-document-root runtime-secret path helpers.
* includes/core/functions.php lines 706-775: resolves installed plugin roots from get_plugins() real main-file entries, then uses plugin_dir_path() and plugin_dir_url() instead of concatenating a slug directly onto WP_PLUGIN_DIR/plugins_url().
* includes/core/functions.php lines 2596-2599 and 2906-2909: replaces dirname(dirname(__DIR__)) own-plugin root discovery with the existing ULTRACACHE_PATH constant.
* includes/core/functions.php lines 2993-2997: validates readable root server configuration files against the WordPress home path instead of ABSPATH.
* includes/core/functions.php lines 3013-3018: makes the runtime-secret filesystem guard consume the shared canonical runtime-secret path helper.
* includes/core/functions.php lines 3175-3179: validates browser-cache .htaccess writes against the WordPress home path instead of ABSPATH.
* includes/class-object-cache-manager.php lines 252-258: makes object-cache Redis secret loading use the same shared runtime-secret token/path helpers as the main plugin.
* includes/settings/class-settings-trait.php lines 1204-1209: detects installed W3 Total Cache-related plugins through the WordPress get_plugins() inventory helper instead of file_exists(WP_PLUGIN_DIR . slug).
* includes/rest/class-rest-profiler-trait.php lines 3623-3627, 3647-3656, and 3962-3973: removes direct WP_PLUGIN_DIR + slug fallbacks from runtime JS discovery and resolves plugin roots only through the installed-plugin main-file helper.
* includes/diagnostics/class-diagnostics-trait.php lines 1332, 1360, 1392, 1409, and 1418: reports secret-file document-root placement against the effective server document root instead of ABSPATH string-prefix checks.
* includes/diagnostics/class-diagnostics-trait.php lines 2273-2275 and 2300: reports the shared effective server document root in server diagnostics.
* uninstall.php lines 33-83 and 451-457: computes uninstall-time runtime-secret cleanup from get_home_path()/DOCUMENT_ROOT using the same canonical outside-document-root location rules.
* readme.txt line 8 and README.md line 3: updates release metadata to 2.59.06.33.

= 2.59.06.32 =
* Removes the generic diagnostic database query wrappers that passed prepared SQL through an opaque `$query` parameter.
* Executes the analytics table and MySQL variable diagnostics through direct, scoped `$wpdb` calls with placeholders where values or identifiers are dynamic.
* Keeps database error suppression and unavailable-value behavior unchanged; no cache, analytics collection, or frontend runtime behavior changes.

= 2.59.06.31 =
* Corrects the first two Console Error Suggestion actions so they append to the unsaved JS Delay / Defer Exclusions draft instead of Defer those scripts.
* Renames those actions to Add This Script Exclusions and Add Full Dependency Chain to Exclusions.

= 2.59.06.30 =
* Replaces the two per-result JS scanner append buttons with four choices: defer this script, defer the full discovered owner chain, delay this script, or delay the full discovered owner chain.
* Appends the selected pattern only to the corresponding unsaved textarea draft; the other three buttons disappear only for that finding, while other findings remain unchanged.
* Removes the provider-contact disclaimer text from Safe Third-Party Delay Patterns and Known Functional Third-Party Delay Patterns.

= 2.59.06.29 =
* Removes same-request manual CSS bundle tag generation when a page bundle is built too late for WordPress enqueue.
* Applies page CSS bundle replacement only when the WordPress-enqueued bundle markup is present in the rendered HTML.
* Preserves the original stylesheet links unchanged when the enqueued bundle markup is missing; the generated bundle is used on a later request through normal enqueue.

= 2.59.06.25 =
* Renames per-result scanner Append buttons to Append to exclusions.
* Adds per-result Append to Safe Third-Party Delay Patterns buttons for Browser Runtime Error scans and Console Error Suggestions.
* Uses 5px button margins and appends to the existing delaySafeThirdPartyJsPatterns setting without changing scanner logic.

= 2.59.06.24 =
* Hardens DB diagnostics so optional database probes suppress visible WordPress database errors and return Unavailable when unsupported.
* Removes the unsafe SELECT @@query_cache_size fallback for MySQL 8 compatibility.
* Keeps the change limited to DB diagnostics; no cache/runtime behavior changes.

= 2.59.06.23 =
* Renames the UI setting from Delay icon font-face blocks to Delay icon fonts.
* Merges Auto-detect likely icon fonts into Delay icon fonts so the single visible switch enables both the delayed icon-font feature and its broad icon-font detection.
* Keeps the existing internal settings synchronized for profiles and saves: enabling Delay icon fonts also enables delayIconFontsAutoDetectEnabled; disabling it turns both off.

= 2.59.06.22 =
* Removes the Populate Defaults and Download CSS JSON buttons from CSS Bundle Exclusions & Diagnostics.
* Keeps Run CSS Diagnostics, Clear CSS Result, and Save Exclusions available; no runtime behavior changes.

= 2.59.06.21 =
* Replaces the separate Gzip and Brotli cache compression switches with a single HTML Compression dropdown while keeping the same internal settings.
* Runs server-compression detection only when an admin selects UltraCache gzip or Brotli compression, and keeps compression off when server-side gzip or Brotli is already active.

= 2.59.06.20 =
* Updates changelog.txt with the reviewer-hardening changes from the 2.59.06.15 through 2.59.06.20 cycle.
* Keeps readme.txt and README.md free of changelog sections; changelog history remains in changelog.txt only.

= 2.59.06.19 =
* Fixes fresh-install drop-in conflict detection so current UltraCache advanced-cache.php and object-cache.php markers are recognized as UltraCache-managed.
* Limits guarded drop-in owner reads to the exact WordPress drop-in paths instead of broad wp-content access.
* Adds the current object-cache drop-in marker used by the owner detector; no legacy marker compatibility was added.

= 2.59.06.18 =
* Adds reviewer-facing comments for unavoidable final rendered HTML rewrites where wp_enqueue_style() or wp_enqueue_script() cannot apply after resources have already been printed.
* Clarifies that late admin print hooks only dequeue conflicting third-party admin assets and do not print scripts.

= 2.59.06.17 =
* Replaces hardcoded generated upload URL/path checks with helpers based on WordPress upload directory data and UltraCache generated-asset helpers.
* Replaces broad wp-content readable-root logic with explicit plugin, mu-plugin, theme, uploads, cache, and core include roots.
* Replaces direct ABSPATH-relative URL-to-file mapping with the central local URL resolver.

= 2.59.06.16 =
* Adds Async external CSS for stylesheet links whose host is different from the current site host.
* Places the Async external CSS switch in CSS Delivery above Aggressive Async CSS and adds a visible exclusion field in CSS Bundle Exclusions & Diagnostics.
* Ensures async external CSS wins over CSS bundling so external stylesheets are not bundled when converted to async CSS.

= 2.59.06.15 =
* Adds a diagnostic-only fallback output buffer for valid store-profile requests when the WordPress template enhancement output-buffer callback does not run.
* Saves a skipped diagnostic profile with output-buffer-callback-not-run when neither the normal callback nor the fallback can produce a profile.
* Improves diagnostic profile headers and dashboard messaging for missing STORE profile JSON cases.

= 2.59.06.14 =
* Plugin Check: write the CSS rewrite-map atomic upsert with inline `$wpdb->prepare()` inside `$wpdb->query()` so the prepared-SQL sniff can verify it directly.

= 2.59.06.13 =
- Defers the automatic Local Google Fonts rebuild triggered by the toggle so settings save can finish first and the rebuild starts as a background dashboard queue job without blocking the UI flow.

= 2.59.06.11 =
- Cleans UltraCache-owned runtime options and transient prefixes during uninstall/Delete all data, including ultracache_* and ultracache_* transient rows.
- Removes generated runtime CSS/font directories under uploads/ultracache during full cleanup: css-bundles, font-css, google-fonts, and optimized-css.
- Keeps persistent optimized image derivatives under uploads/ultracache/images by design.
- Keeps the Media Optimization Image Output Format dropdown from 2.59.06.09 and the exact-file warm verification from 2.59.06.10.

= 2.59.06.07 =
- Matches CSS bundle sources using canonical URL variants so source URLs with ?ver= can match css_rewrite_map rows stored without query args.
- Allows optimized-css/font-css generated links to be recognized as aliases of their original manifest sources during page CSS bundle replacement.
- Keeps the change limited to CSS bundle source matching; no generated path, profile, JS, or font-build behavior changes.

= 2.59.06.04 =
- Builds page CSS bundle markup from the existing manifest when the WordPress-enqueued bundle tag is absent from the final cache rewrite buffer.
- Fixes warm-up results where a CSS bundle was built but the cached HTML still had no css-bundles reference.
- Keeps the fix limited to page CSS bundle insertion/replacement; no CSS profile, generated path, or JS/font behavior changes.

= 2.59.06.02 =
- Writes runtime generated font-css/optimized-css assets to uploads/ultracache so generated URLs match generated files.
- Prunes runtime font CSS map entries whose generated target CSS file is missing before printing frontend config.
- Saves the cleaned runtime font CSS map after stale targets are removed so frontend JS does not request missing CSS files.

= 2.59.06.01 =
- Removes the hidden Google Fonts manual-rebuild backoff bypass added in 2.59.06.
- Changes the Google Fonts write-failure retry guard to a visible short 10-15 second window.
- Persists Google Fonts failure details so diagnostics can show the actual failure reason instead of only failed counts.

= 2.59.06 =
- Restores uploads/ultracache generated-asset write/delete permissions in the guarded filesystem layer.
- Fixes Google Fonts/local font CSS generation paths that were blocked after generated assets moved under uploads/ultracache.
- Changes Speed Diagnostics loopback requests from profile-bypass to internal revalidate/force-refresh so timing breakdowns can be saved.
- Adds Google Fonts rebuild failure details to the diagnostics status when a stylesheet still cannot be generated.

= 2.59.04 =
- Replaces remaining page-cache storage writable checks with the WordPress-native UltraCache filesystem wrapper.
- Removes root-only review helper markdown files from the production package while keeping required source/build notes in readme.txt.
- Updates CSS rewrite map SQL table identifiers to use WordPress database identifier placeholders and updates tested metadata.

= 2.58.90.04 =
- Moves the Delayed JS loader from raw wp_head inline output to assets/js/delayed-js-loader.js.
- Enqueues the loader through wp_enqueue_scripts with WordPress-native script APIs.
- Passes the unified delayed-JS auto-start configuration through wp_add_inline_script() before the helper.

= 2.58.90.03.04 =
- Fixes Runtime/Console Scanner explicit `_ is not defined` handling so underscore can be suggested from actual page inventory.
- Deduplicates scanner suggestions that point to the same script by preferring exact path fragments over duplicate WordPress handles.
- Keeps provider/source suggestions in the same pass for both Browser Runtime Scanner and Extract Console Error Suggestions.

= 2.58.90.03.01 =
- Fixed Runtime/Console JS suggestion resolver for explicit missing globals such as "jQuery is not defined".
- Uses error source + active plugin/theme source-file evidence + final page script inventory to suggest the matching provider script only.
- Does not infer unrelated WordPress core dependencies; already protected failing sources remain marked separately from missing provider additions.

= 2.58.90.03 =
- Moved the Runtime JS Scan collector into assets/js/runtime-js-scan-collector.js.
- Enqueues the collector only for verified runtime scan requests through wp_enqueue_scripts.
- Passes scan configuration with wp_add_inline_script() before the helper and removes the old raw inline/wp_head/output-buffer scanner paths.

= 2.58.90.02.02 =
- Replaced the MailerLite helper loading path with a clean wp_enqueue_scripts implementation.
- Removed the MailerLite HTML rewrite insertion path and wp_print_scripts() usage.
- Keeps admin_url('admin-ajax.php') configuration through wp_add_inline_script() before the helper.

= 2.58.90.02.01 =
- Broadened MailerLite lazy nonce helper detection to include official plugin assets and MailerLite Universal markers.
- Preserves WordPress script API loading and admin_url('admin-ajax.php') endpoint handling.

= 2.58.90.02 =
- Moved the MailerLite lazy nonce frontend helper into assets/js/mailerlite-lazy-nonce.js.
- Loads the helper through WordPress script registration/printing APIs with dynamic Ajax endpoint data.
- Kept the existing lazy nonce runtime behavior and admin_url('admin-ajax.php') endpoint handling.

= 2.58.90.01 =
- Added staged frontend JavaScript helper enqueue infrastructure and migration inventory.
- Added assets/js documentation placeholders for upcoming WordPress-registered helper files.

= 2.58.83 =
- Evidence-based JS error scanner: source/stack/code-search findings are appendable, review-only scanner output removed, and hardcoded resolver flow disabled.

* Synced performance profiles with the unified delayed JS auto-start model.
* Renamed Safe Defer JS to Defer JS and Frontend JS & Request Chains to Frontend Javascript manipulation.
* Safe profile keeps all Frontend Javascript manipulation switches off.
* Balanced enables only the selected delayed JS features: safe third-party, non-critical/local, known functional third-party, and all third-party delay.
* Aggressive adds Delay all JS with a 0.05s unified fallback.
* Moved Delayed JS auto-start triggers into one dropdown and set all event triggers off by default.

2.58.76 - JS diagnostic queue DB compliance fix
- Replaced interpolated JS diagnostic queue table SQL with prepared identifier placeholders.
- Added targeted object-cache reads and invalidation for JS diagnostic queue job/status lookups.

2.58.75 - JS diagnostics spacing and label polish
- Adds 12px gaps to JS diagnostics action button rows.
- Adds 10px top spacing to Runtime Scan context, runtime action buttons, console action buttons, and runtime status message.
- Sets Page URL to scan and Console errors to analyze labels to 12px and #6f7b8f.

2.58.74 - Fixed JS diagnostics Browser Scanner / Console Error Handler two-column layout and title style consistency.
2.58.73 - Fixed JS diagnostics layout regression where Clear Console Input referenced a missing React handler.
2.58.72 - Reordered JS Delay/Defer diagnostics UI into exclusions, browser scanner, console handler, and shared queue status sections with improved runtime progress visibility.
2.58.71 - Removed borders from Advanced Settings mini action/diagnostic boxes and populate-warning notices for a cleaner UI.
2.58.70 - Fixed Advanced Settings & Exclusions layout so the five sections render as separate accordion card boxes instead of one shared wrapper.
2.58.69 - Advanced Settings accordion split and JS diagnostic result UI polish
- Adds a DB-backed JS diagnostic queue for browser runtime and pasted-console diagnostics.
- Adds queue start, pause, resume, cancel, progress, latest status, and stored result buckets.
- Stores Confirmed Error Fixes, Suggestions, Review Only, Already Listed, and Ignored buckets without auto-appending exclusions.

2.58.66 - Theme scan stage
- Adds a diagnostics-only Theme Scan Stage for unresolved runtime JS errors.
- Scans the active child theme first, then the parent theme, using guarded UltraCache file reads.
- Emits review-only exact theme JS candidates; Safe Defer toggle behavior is unchanged.

2.58.65 - Runtime error group resolver
- Added a Runtime Error Group Resolver for Safe Defer/Delay diagnostics.
- Maps failing console/stack source URLs to known plugin groups where confirmed, including WooCommerce Products Filter.
- Keeps MailerLite validation-messages.js as an exact confirmed source fix instead of a generic messages/global suggestion.
- Unknown plugin/theme source owners are review-only and are not appendable confirmed fixes.

2.58.64 - HTML adjacency resolver
- Added a final-HTML external-script plus immediate-inline dependency resolver for runtime/console JS diagnostics.
- Missing globals such as MailerLite messages now resolve to the adjacent provider script instead of a raw/global token.

2.58.63 - Safe Defer diagnostic fixes
- Runtime/console diagnostics no longer append broad generic dependency fixes such as jquery, jquery-core, wp-i18n, wp-hooks, wp-api-fetch, react, react-dom, or wp-element.
- Runtime diagnostics now keep WordPress/React foundation errors as exact resolved review-only candidates unless a specific plugin/script group is detected.
- Added specific confirmed resolver entries for WOOF/WooCommerce Products Filter and direct MailerLite validation-messages.js errors.
- Removed the browser-side console parser fallback from Extract Console Error Suggestions.
- Replaced the remaining aggressive-profile broad JS exclusion seed with the curated tested dependency path list.

2.58.62 - Safe Defer defaults cleanup
- Safe Defer JS now appends only curated WordPress foundation script paths.
- Removed broad generic dependency defaults from Append Tested Dependency Defaults.
- Removed the legacy Safe Defer init-script scan from the Safe Defer toggle and profile apply flow.

2.58.61 - Final font-display store-stage rewrite
- Runs linked stylesheet font-display normalization at the absolute cache-store finalizer and inside the write path, after CSS/JS/LCP transformations.
- Handles root-relative local stylesheet URLs before resolving source paths, so Elementor/theme/plugin font CSS can be rewritten to patched UltraCache CSS copies.

2.58.60 - Final linked font-display normalization pass
- Restored a final source-level linked stylesheet font-display normalization pass after async CSS transforms so late/restored local font CSS links are rewritten to UltraCache patched copies.
- Keeps runtime CSSOM font-display patch as fallback only; primary fix is cached CSS href replacement.

= 2.58.60 =
* UI: align uc-field-label styling with switch title typography across Advanced Settings fields.

2.58.58 - Dropdown title style alignment
- Dropdown setting titles now use the same visual title styling as switch labels.

2.58.57 - JS strategy cleanup and APCu flush lock
- Removed Defer all eligible JS from the full-site strategy dropdown; full-site strategy is now Off or Delay all eligible JS.
- Renamed LCP Boundary Defer to LCP Boundary Delay in the dashboard UI.
- Replaced Delayed local JS auto-start mode/seconds fields with one dropdown: interaction only, 0.1, 0.5, and 1-9 seconds.
- Removed the Disabled auto-start option; use the full-site delay switch instead.
- Forced Also flush APCu ON when APCu is selected as the object cache backend, with updated UI text.

2.58.56 - Native defer inline externalization
- Defer all eligible JS now externalizes safe inline scripts into generated deferred cache files so inline companions keep DOM order with native deferred external scripts.
- Delay all eligible JS remains the separate delayed-loader strategy.

2.58.55 - JS full-site strategy dropdown and separated defer/delay all behavior
2.58.54 - Visible delayed local JS auto-start controls
- Added Advanced Settings & Exclusions controls for delayed local JS auto-start: interaction only, custom seconds, or disabled.
- Replaced the hardcoded 12s local delayed JS auto-start with saved visible settings.
- Kept uncapped parallel delayed JS loading, ordered execution, jQuery ready barrier, and Elementor lazy background helper.

2.58.53 - Uncapped parallel delayed JS load without preload
- Removed the hardcoded parallel group cap from the delayed JS loader.
- External delayed scripts now load in uncapped contiguous parallel groups when the delayed batch starts.
- Kept ordered DOM execution, jQuery ready barrier, Elementor lazy background helper, and no delayed-JS preload links.

2.58.52 - Parallel delayed JS load without preload
- Removed delayed JS preload-window link injection from 2.58.51.
- Added windowed parallel script insertion with ordered execution for delayed JS batches.
- Moved local delayed auto-start later so initial load is more interaction-first.

2.58.52 - Delayed JS preload window
- Added a bounded preload-ahead window for delayed local/all scripts to reduce one-by-one network waterfalls.
- Kept strict DOM-order execution and the jQuery ready barrier so dependency order remains protected.
- Kept the 2.58.50 Elementor lazy-background class helper and avoided the 2.58.49 faster-execute/preload regression.

2.58.50 - Elementor lazy background compatibility rollback
- Reverted the 2.58.49 faster-local-queue and Elementor background preload/reveal performance experiment.
- Kept the 2.58.48 jQuery ready barrier and JS diagnostics UI cleanup.
- Added a lightweight Elementor lazy-background class helper that reveals nearby containers without running Elementor JS earlier or preloading all backgrounds.

2.58.48 - Delayed JS ready barrier and diagnostics UI cleanup
- Added a delayed-JS jQuery ready barrier so local/all delayed batches hold jQuery ready callbacks until the delayed batch has finished in DOM order.
- Cleaned the JS Delay / Defer Exclusions controls: confusing append/scan/debug buttons were replaced with explicit Analyze, Runtime Scan, Append Confirmed Error Fixes, and Append Suggestions actions.
- Added visible explanations under each JS diagnostic/action button and removed the broad /wp-includes/js/ path from tested dependency defaults.

2.58.47 - Precise JS exclusion matching for Delay all JS
- Generic visible JS exclusions such as woocommerce no longer blind-match unrelated handles like googlesitekit-events-provider-woocommerce.
- WooCommerce exclusions are now path/exact-handle aware, so real WooCommerce assets remain protectable without blocking Site Kit providers.
- Auto init-scan output now rejects broad root tokens such as woocommerce, frontend, main, plugin, script, data, and params.

2.58.46 - Delay wins over native defer
- When Defer all JS is active, script_loader_tag no longer emits native defer for the remaining scripts.
- Force-defer rules are suppressed during the absolute delay-all final pass so delayed Site Kit dependencies cannot run after native-deferred dependents.
- The final ordered delayed queue remains the authoritative pass for all eligible external and inline scripts unless matched by visible JS exclusions.

2.58.45 - Absolute Delay All JS rule
- Defer all JS now converts every delayable external and inline script into the ordered delayed layer unless matched by unified JS exclusions.
- Existing delayed scripts are normalized into the same all-js delayed queue so local and third-party pieces do not split execution order.
- Unified exclusions remain authoritative for whole WordPress script groups.

2.58.42 - JS exclusion and script group regression fix
- Treat the unified JS Delay / Defer Exclusions list as the authoritative exclusion source across defer, delay, non-critical delay, and LCP boundary paths.
- Normalize WordPress script group handles so one base-handle exclusion protects related js-before, js, js-after, js-extra, and translations companions.
- Avoid splitting WordPress script groups at script_loader_tag time when inline companions are registered.

- CLI warm_frontpage_html_css now warms HTML-only with success when CSS Bundling is disabled instead of failing on missing bundle injection.
- APCu object-cache CLI flush message now clarifies PHP-process scope and PHP-FPM/web APCu limitations.
- Varnish purge coordination now records/warns when Varnish is enabled but Flush All Include Varnish is OFF, avoiding misleading full-purge feedback.

2.58.39 - Final WordPress.org package
- Verified no remote asset enqueue, no wp_localize_script usage, no global ob_start usage, and no unexpected direct wp_remote_* calls beyond guarded infrastructure wrappers.
- Removed one frontend console warning from a MailerLite nonce fallback failure path.

2.58.38 - Escaping / returned HTML audit
- Added a shared inline-script JSON encoder that applies JSON_HEX_* flags for script-safe JSON literals.
- Updated runtime font map, speculation rules, runtime JS scan collector, and SR7/LCP selector inline scripts to use script-safe JSON output.
- Escaped the fallback LCP image preload href before injecting the generated link tag.

2.58.37 - Final regex review pass
- Switched font/local stylesheet scanners to WP_HTML_Tag_Processor.
- Removed legacy async CSS link rewrite regex fallbacks and moved noscript fallback insertion to the HTML API path.

2.58.36 - Admin enqueue modernization
- Updated the UltraCache admin dashboard script enqueue to use the WordPress 6.3+ args array with in_footer => true.
- Kept admin script execution behavior unchanged and did not add a script loading strategy.

2.58.35 - CSS bundle scanner HTML API
- Switched CSS bundle stylesheet discovery to WP_HTML_Tag_Processor for head/link scanning.
- Removed the remaining CSS bundle link-scan regex path from the warm verification counter.

- Normalized the GPLv2 license URI between the plugin header and readme.

2.58.33 - HTTP wrapper URL normalization revert
- Reverted esc_url_raw() normalization in the general UltraCache safe HTTP wrapper after it correlated with bypassing frontend optimization output.
- Kept WordPress safe HTTP transport, reject_unsafe_urls, bounded timeout/redirection, and the infrastructure wrapper PHPCS rationale.

2.58.30 - Final technical dead-code cleanup
- Removed unused private helpers left behind by recent HTML API, font, CSS, JS, LCP, and media refactors.

2.58.29 - Font/Icon scan suspicious candidate cleanup
- Filter suspicious encoded/random-looking font-family candidates from Font/Icon scan results.
- Keep real icon/font family names such as Font Awesome, eicons, feather, swiper-icons, and theme icon fonts.

2.58.28 - Safe Defer / scan HTML API cleanup
- Switched Safe Defer front-page script scanner to WP_HTML_Tag_Processor.
- Switched runtime JS inventory scan to WP_HTML_Tag_Processor.
- Switched front-page font scan style/link discovery to WP_HTML_Tag_Processor.
- Removed legacy regex attribute extraction helpers from those scanner paths.

2.58.27 - Image/dimension HTML API cleanup
- Use WP_HTML_Tag_Processor by default for Safe CLS image dimension injection.
- Remove the regex fallback from Safe CLS image width/height injection.
- Remove the regex fallback from lazy-load/async image attribute mutation.

2.58.26 - Admin settings FIFO cleanup
- Removed stale pending settings/debounce refs from the old save model.
- Kept scoped settings save/apply behavior and the current UI FIFO flow.

2.58.25 - Delayed font noscript fallback cleanup
- Prevent Safe Async CSS processing from re-wrapping existing noscript fallback links.
- Keep delayed icon-font noscript fallbacks clean without nested noscript tags.

2.58.24 - Leftover CSS HTML API cleanup
- Converted leftover CSS stylesheet consolidation from offset/substr HTML rebuilding to WP_HTML_Tag_Processor attribute mutation.
- Kept source stylesheet consolidation scoped to the existing leftover CSS bundle path with no regex replacement fallback.

2.58.23 - Google Fonts live output cleanup
- Run Google Fonts HTML API cleanup through the WordPress template enhancement output buffer for bypass/uncached responses.
- Keep wp_resource_hints source filtering and avoid regex fallbacks.

2.58.22 - Google Fonts resource hints source filter
- Added wp_resource_hints filtering for Google Fonts dns-prefetch/preconnect hints when Local Google Fonts Optimization is enabled.
- Kept HTML API cleanup for manually injected Google Fonts hint links.

2.58.21 - Font stylesheet link HTML API cleanup
- Removed regex fallback mutation for Google Fonts stylesheet link href rewrites.
- Neutralized remote Google Fonts resource hints with WP_HTML_Tag_Processor attribute mutation instead of regex tag removal.
- Removed regex fallback mutation for self-hosted font CSS link and font-display normalized stylesheet link rewrites.

2.58.20 - LCP/preload/image HTML API cleanup
- Removed the regex fallback from the LCP image candidate optimization path.
- Existing LCP preload link normalization now uses WP_HTML_Tag_Processor only.
- UltraCache-managed ambiguous/duplicate LCP preloads are neutralized with HTML API attribute mutation instead of regex removal.

2.58.19 - Media filtered-content HTML API cleanup
- Removed the regex fallback from WordPress content/block image URL rewrite callbacks.
- Filtered content image URL rewriting now uses WP_HTML_Tag_Processor directly under the WordPress 6.9+ baseline.
- Left full-page media URL token discovery and CSS url() parsing unchanged for later focused cleanup.

2.58.18 - Script delay HTML API cleanup
- Switched the full HTML script delay/wrap application path to WP_HTML_Tag_Processor.
- Removed the offset/substr assembly path for applying already-decided delayed script replacements.

2.58.17 - JS script loading attribute HTML API cleanup
- Switched the Defer All JS script loading attribute mutation path to WP_HTML_Tag_Processor.
- Removed the regex fallback from protected script loading attribute normalization.
- Left full script tag replacement/delay wrapping paths unchanged for later focused cleanup.

2.58.16 - HTML attribute helper cleanup
- Removed regex fallback mutation from the shared HTML tag attribute helpers.
- Shared attribute add/remove operations now use the WordPress HTML API path and leave the tag unchanged if the processor cannot safely update it.

2.58.14 - Move CSS bundle cached-HTML stylesheet replacement to the WordPress HTML API without regex fallback.
2.58.13 - Hide recovered noisy REST output details from the admin UI while keeping resilient JSON recovery.
2.58.12 - Add resilient REST response parser for noisy admin REST responses

2.58.11 - Remove REST output buffer guard
- Removed the UltraCache REST bootstrap output buffer and the matching rest_pre_serve_request discard filter to avoid unclosed ob_start review risk.

2.58.10 - Profile toggle enforcement
- Fixed profile application so Pre-render on Save and Stale While Revalidate are no longer stripped from profile saves.
- Added Enable Debug to the profile-managed off state so All Off turns debug headers off.
- Kept Pre-render on Save and Stale While Revalidate enabled for Safe, Balanced, and Aggressive profiles.

2.58.09 - Safe loopback request for JS inventory scan
- Routed the runtime JS inventory scan through the shared UltraCache safe loopback request helper.
- Kept JS inventory scan requests on the same trusted same-site URL policy, SSL fallback reporting, and debug logging used by other internal scans.

2.58.08 - Admin runtime config inline script
- Replaced the admin dashboard ultracacheData runtime config use of wp_localize_script with wp_add_inline_script and wp_json_encode before the module script.
- Kept wp_set_script_translations dedicated to dashboard translation loading.

2.58.07 - REST output guard for dashboard batch jobs
- Protected UltraCache REST JSON responses from third-party PHP notices or warnings printed before the JSON payload.
- Made dashboard REST parsing fail with a clear invalid JSON or empty response error instead of returning null to warm-up and media queue jobs.
- Kept batch response normalization strict so invalid REST payloads no longer surface as unrelated processed-property crashes.
- Raised plugin metadata to PHP 8.1+ while keeping WordPress 6.9+ as the target.

2.58.06 - Settings save FIFO and scoped response apply
- Scoped dashboard settings responses to the keys saved by each switch, dropdown, or form so unrelated UI state is not rolled back by later saves.
- Routed profile follow-up saves for object-cache autodetect and Safe Defer JS scans through the same patch-scoped settings save path.
- Removed changelog content from the readme files so changelog entries live only in changelog.txt.

2.58.05 - WordPress.org escaping and external services documentation cleanup
- Routed WordPress content/block media rewrites through a context-aware callback with escaped rewritten attributes.
- Updated External services documentation for Google Fonts, third-party optimization patterns, Varnish/reverse proxy endpoints, and PayPal links.

2.58.04 - Translator comment cleanup for Plugin Check i18n placeholders
- Added missing translator comments for placeholder-based i18n strings reported by Plugin Check.

2.58.03 - Full i18n pass and localization template refresh
- Expanded PHP and admin dashboard JavaScript i18n coverage for user-facing text.
- Kept commands, paths, keys, statuses, handles, and executable snippets untranslated.
- Refreshed the POT template.

2.58.02 - Repository localization cleanup
- Replaced direct unsafe loopback SSL bypass requests with the UltraCache safe loopback helper.
- Added admin JavaScript i18n setup and generated the UltraCache POT template.
- Added a first PHP i18n pass for REST/admin-facing messages.

2.58.01 - Initial public release
- Initial public release build.