release: 1.0.13 — WP 7.1 compat bump

[odanree]

Summary

• Bumps Tested up to from 7.0 → 7.1 and Stable tag from 1.0.12 → 1.0.13 in readme.txt and the plugin header.
• Adds a 1.0.13 entry to readme.txt (Changelog + Upgrade Notice) and CHANGELOG.md.
• No functional plugin code changes.

Why

WP.org sent the standard "WordPress 7.1 field guide — is your plugin ready?" email ahead of the 2026-08-19 release. Two areas of 7.1 could plausibly affect this plugin:

1. Client-side media processing — the browser now resizes/compresses/generates thumbnails before uploads reach the server. This could change what our wp_handle_upload and wp_generate_attachment_metadata filters receive.
2. jQuery UI 1.14.2 — non-issue for us (grep confirmed no jQuery UI usage anywhere in the plugin).

Verification

Stood up a WordPress 7.1-RC3 sandbox with wp-playground CLI (PHP-WASM 8.3 + SQLite, no Docker), auto-mounted this plugin, and drove the Media Library upload path with Playwright.

Confirmed clean on 7.1-RC3:

• Plugin activates with no fatal errors, no PHP warnings, no admin notices
• Admin dashboard, Settings, and Performance Toggles pages render correctly
• Media Library upload succeeds with no errors surfaced
• wp_handle_upload at class-optimizer.php:65 still fires with the expected $upload array shape
• wp_generate_attachment_metadata at class-resizing-processor.php:53 still fires; all four ODR-registered sub-sizes are generated by core (odr_content_optimized, odr_content_retina, odr_mobile_optimized, odr_tablet_optimized)

Conclusion: WP 7.1's client-side media processing preserves the server-side hook contract this plugin depends on. No code changes needed — just the compat marker bump.

Environmental limitation: End-to-end WebP conversion was not exercised in the sandbox because the plugin's own 100MB WP_MEMORY_LIMIT guard at class-optimizer.php:223 tripped in the WASM PHP environment. On a normal PHP-FPM host with 256MB+ that guard passes. Worth noting as a follow-up (hair-trigger for shared hosts on 128MB), but out of scope for this PR.

Test plan

• Merge to main
• Tag v1.0.13 on main — fires the WPORG_SVN_* deploy workflow
• Verify WP.org listing updates to Tested up to: 7.1 after deploy
• Confirm Stable tag line resolves to the correct SVN tag path (previous drift caused tags/refs/heads/main; fixed in 1.0.10)
• Optional cleanup: delete stale chore/tested-up-to-7.0 branch (that unmerged work is the likely source of the SVN=7.0.4 vs local=7.0 drift and is now superseded)