== Changelog ==

= 0.1.2 =

_Release date: 2026-08-12_

**Highlights**

* Documentation refresh: readme.txt and changelog.txt aligned to the standard templates.

**Changed**

* Version bumped 0.1.1 → 0.1.2.
* readme.txt: added Extra Configurations section, Automatic download subsection in Installation, Previous versions link in Changelog.
* changelog.txt: 0.1.1 entry reformatted to follow the standard template (Highlights, Changed, Compatibility, Tests).
* PHPCompatibility scan (5.6–8.5): real PHP floor is **7.2**. Project declares **8.4** (ecosystem exception).
* wp-compat scan against WordPress 4.7: **zero WPCompat errors**. Real WP floor is **≤ 4.7**. Project declares **7.0** (ecosystem support window).

**Compatibility**

* WordPress: 4.7 - 7.1
* PHP: 7.4 - 8.5

**Tests**

* PHP Coding Standards: PHP_CodeSniffer 3.13.6
* WordPress Coding Standards: WPCS 3.4.1
* PHPStan: level 9, 0 errors
* PHPCompatibility: 8.4–8.5 clean (real floor 7.2)
* wp-compat: 0 errors against WP 4.7

= 0.1.1 =

_Release date: 2026-08-12_

**Highlights**

* Compatibility scans completed and documented. No code changes.

**Changed**

* Version bumped 0.1.0 → 0.1.1.
* PHPCompatibility scan (5.6–8.5) completed: real PHP floor is **7.2** (highest-required feature is `object` return type, introduced in PHP 7.2). The project deliberately declares **8.4** to match the ROBOTSTXT ecosystem — this is a documented exception to `AGENTS-deploy.md` §"PHP compatibility check".
* wp-compat scan against WordPress 4.7: **zero WPCompat errors**. The Manager's code uses only WordPress APIs available since 4.7 or earlier. The real WordPress floor is **≤ 4.7**; the project declares `Requires at least: 7.0` to match the ecosystem support window.
* `.pot` file regenerated for v0.1.1.

**Compatibility**

* WordPress: 4.7 - 7.1
* PHP: 7.4 - 8.5

**Tests**

* PHP Coding Standards: PHP_CodeSniffer 3.13.6
* WordPress Coding Standards: WPCS 3.4.1
* PHPStan: level 9, 0 errors
* PHPCompatibility: 8.4–8.5 clean (real floor 7.2)
* wp-compat: 0 errors against WP 4.7

= 0.1.0 =

_Release date: 2026-08-12_

**Highlights**

* Phase 1 scaffold of Manager (by ROBOTSTXT) — client-side dashboard for the ROBOTSTXT plugin ecosystem. Read-only catalog view with local install-state resolution.

**Added**

* Plugin header, autoloader (Composer with manual fallback), lifecycle hooks, constants (`ROBOTSTXT_MANAGER_VERSION`, `ROBOTSTXT_MANAGER_DIR`, `ROBOTSTXT_MANAGER_URL`, `ROBOTSTXT_MANAGER_BASENAME`).
* `Robotstxt_Manager_Loader` action/filter queue (identical pattern to Core/Mollie/Sync).
* `Robotstxt_Manager_Encryption` — AES-256-CBC encrypt/decrypt for the API key, using WordPress `AUTH_KEY` + `AUTH_SALT` for key derivation. Same pattern as Core's Forgejo token encryption.
* `Robotstxt_Manager_Core_Client` — HTTP client for the remote Plugins Core REST API. Authenticated via `Authorization: Bearer <key>` header. Implements `test_connection()`, `get_catalog()` (cached in transient), `clear_catalog_cache()`.
* `Robotstxt_Manager_Settings` — Settings API page with Store URL, API Key (masked, encrypted, last-4 hint, delete-on-empty preservation), Catalog Cache TTL, Data-on-Uninstall opt-in. AJAX "Test connection" button with nonce + capability check.
* `Robotstxt_Manager_Admin` — Top-level admin menu (label "ROBOTSTXT") with catalog table view. Resolves local install/active/update state for every catalog entry using `get_plugins()` + `is_plugin_active()`. "Refresh catalog" admin-post action.
* `uninstall.php` with opt-in data deletion (default: preserve all options and transients).
* Per-project tooling: Composer, PHPCS + WPCS + PHPCompatibility, PHPStan level 9 + wp-compat, PHPUnit. `bin/preflight.sh` and `bin/deploy.sh`.

**Compatibility**

* WordPress: 4.7 - 7.1
* PHP: 7.4 - 8.5

**Tests**

* Phase 1 scaffold — plugin-header tests included. Additional tests for Core client, settings, and admin rendering in follow-up phases.