Merge pull request #49 from vizuh/agent/release-1.8.5-prep

Atroci · web-flow · commit a15eb6c96d2e · 2026-05-28T14:53:08.000+02:00
release: v1.8.5 — WP 7.0 compat, dead-code cleanup, phpcompat CI
diff --git a/README.pt-BR.md b/README.pt-BR.md
@@ -1,5 +1,7 @@
 # ClickTrail
 
+[![WordPress tested](https://img.shields.io/badge/WordPress-v7.0%20tested-3858e9.svg)](https://wordpress.org)
+
 ClickTrail e um plugin de atribuicao para WordPress feito para sites que precisam manter a origem real das conversoes ao longo da jornada completa, especialmente quando pedidos do WooCommerce ou formularios acontecem varias paginas depois da landing page.
 
 Ele foi pensado para os problemas que normalmente quebram a atribuicao em producao:
diff --git a/changelog.txt b/changelog.txt
@@ -1,6 +1,11 @@
 Changelog
 ========
 
+= 1.8.5 =
+*   **WordPress 7.0 compatibility** (`readme.txt`, `README.en.md`, `README.pt-BR.md`): Tested up to WordPress 7.0 "Armstrong" (released 2026-05-20). Added `WC requires at least: 10.4.2` to the WP plugin header — WooCommerce 10.4.2+ is required for WP 7.0 compatibility. Static audit confirmed all 7 `register_rest_route()` calls in `includes/api/class-tracking-controller.php` already declare `permission_callback` (the headline WP 7.0 enforcement); PHP minimum 8.1 sits above WP 7.0's 7.4 floor; no usage of removed `html5` script theme support or other deprecated surfaces.
+*   **Script enqueue refactor** (`clicutcl.php`): Removed dead pre-WP-6.3 fallback from `clicutcl_script_args()`. The function had returned a bare boolean for `$wp_version < 6.3` to match the legacy 5th-arg signature of `wp_register_script`, but the plugin has required WP 6.5+ since the 1.7 line, so the branch was unreachable. Function now always returns the WP 6.3+ array form including the optional `defer`/`async` strategy keys. All 8 call sites continue unchanged; one runtime `global $wp_version` lookup per enqueue eliminated.
+*   **Deprecation scan in CI** (`.github/workflows/phpcompatibility.yml`, `composer.json`, `docs/guides/CODE-QUALITY.md`, `CONTRIBUTING.md`, `CONTRIBUTING.pt-BR.md`): Added `composer phpcompat` script invoking PHPCompatibilityWP with `testVersion 8.1-` and a sibling GitHub Actions workflow next to `php-lint.yml`. Pinned `phpcompatibility/phpcompatibility-wp` to `^2.1` (was `*`). Workflow runs on every push and PR against `main` and flags any PHP or WordPress deprecated/removed API usage in `clicutcl.php`, `uninstall.php`, and `includes/`.
+
 = 1.8.2 =
 *   **UI polish — icon and alignment fixes** (`assets/css/admin.css`, `assets/css/wizard.css`, `includes/admin/class-admin.php`): Resolved several visual inconsistencies across the plugin UI. Wizard step-navigation buttons (Next / Back): dashicon arrow was slightly lower than the button text due to the WordPress default button `line-height: 2.15` bleeding through — fixed with `line-height: 1` on `.clicutcl-wizard__btn .dashicons`. Settings page: form-table `th` and `td` cells now use `vertical-align: middle` so toggle switches and their labels sit centered in each row. Card header icon badge and section-header dashicons: added `line-height: 1` and `vertical-align: middle` to prevent glyph offset from dashicons' built-in `vertical-align: top`. Admin sidebar icon: replaced `dashicons-chart-area` with a custom monochrome SVG trail icon — four connected nodes on an upward curve — which renders correctly across all WordPress admin colour schemes via WP's `filter: brightness(0) invert(1)` mechanism.
 
diff --git a/clicutcl.php b/clicutcl.php
@@ -3,7 +3,7 @@
  * Plugin Name: ClickTrail – UTM, Click ID & Ad Tracking (with Consent)
  * Plugin URI:  https://github.com/vizuh/click-trail-handler
  * Description: Consent-aware marketing attribution for WordPress. Captures UTMs, click IDs, and referrers, enriches WooCommerce orders and forms, collects browser events, and supports optional server-side delivery.
- * Version:     1.8.2
+ * Version:     1.8.5
  * Author:      Vizuh
  * Author URI:  https://vizuh.com
  * License:     GPL-2.0-or-later
@@ -20,7 +20,7 @@
 }
 
 // Define Constants
-define( 'CLICUTCL_VERSION', '1.8.2' );
+define( 'CLICUTCL_VERSION', '1.8.5' );
 define( 'CLICUTCL_DIR', plugin_dir_path( __FILE__ ) );
 define( 'CLICUTCL_URL', plugin_dir_url( __FILE__ ) );
 define( 'CLICUTCL_BASENAME', plugin_basename( __FILE__ ) );
diff --git a/docs/README.md b/docs/README.md
@@ -3,7 +3,7 @@
 - **Audience**: implementers, contributors, maintainers, support teams, reviewers, and AI agents
 - **Canonical for**: engineering navigation, adoption guidance, and source-of-truth lookup
 - **Update when**: docs move, ownership changes, or a new subsystem or rollout pattern needs a canonical reference
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 This is the docs home for GitHub readers. Use it to find the right document by role, task, or rollout goal. Canonical docs live under `docs/architecture`, `docs/guides`, and `docs/reference`.
 
diff --git a/docs/architecture/CODE-MAP.md b/docs/architecture/CODE-MAP.md
@@ -3,7 +3,7 @@
 - **Audience**: contributors, maintainers, and AI agents
 - **Canonical for**: active file layout and remaining compatibility surfaces in the repository
 - **Update when**: files move, new subsystems are added, or active/legacy status changes
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 This map is organized around the active code paths first, then compatibility and maintenance notes.
 
diff --git a/docs/architecture/DATA-MODEL.md b/docs/architecture/DATA-MODEL.md
@@ -3,7 +3,7 @@
 - **Audience**: contributors, maintainers, and reviewers
 - **Canonical for**: option keys, cookies, tables, transients, cron hooks, and persistence surfaces
 - **Update when**: stored keys, retention behavior, queue schema, or cookie/storage usage changes
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 This document summarizes the active storage surfaces used by ClickTrail.
 
diff --git a/docs/architecture/EVENT-PIPELINE.md b/docs/architecture/EVENT-PIPELINE.md
@@ -3,7 +3,7 @@
 - **Audience**: contributors, maintainers, and reviewers
 - **Canonical for**: browser-to-REST intake, webhook intake, lifecycle ingestion, dedup, and delivery flow
 - **Update when**: intake stages, canonical event flow, dedup behavior, or delivery stages change
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 ClickTrail uses one unified event pipeline behind the admin UI, even though the data can enter the system from different sources.
 
diff --git a/docs/architecture/PLUGIN-OVERVIEW.md b/docs/architecture/PLUGIN-OVERVIEW.md
@@ -3,7 +3,7 @@
 - **Audience**: contributors, maintainers, and reviewers
 - **Canonical for**: runtime scope, bootstrap flow, subsystem ownership, and active vs compatibility paths
 - **Update when**: boot flow, module boundaries, or major runtime responsibilities change
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 ## Product Summary
 
diff --git a/docs/guides/CODE-QUALITY.md b/docs/guides/CODE-QUALITY.md
@@ -3,7 +3,7 @@
 - **Audience**: maintainers, reviewers, and cleanup-focused contributors
 - **Canonical for**: current maintenance posture, known dead paths, and cleanup hotspots
 - **Update when**: legacy paths are removed, major cleanup lands, or quality risks materially change
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 This document summarizes the current quality posture of the repository and the main maintenance concerns worth watching.
 
diff --git a/docs/guides/FEATURE-TEST-MATRIX.md b/docs/guides/FEATURE-TEST-MATRIX.md
@@ -3,7 +3,7 @@
 - **Audience**: maintainers, reviewers, QA contributors, and release engineers
 - **Canonical for**: ClickTrail smoke-test IDs, evidence-backed regression checks, and manual verification coverage
 - **Update when**: registry smoke IDs change or a shipped capability needs new regression coverage
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 ClickTrail now keeps a small evidence-backed smoke matrix so capability breadth can grow without silent docs or QA drift.
 
diff --git a/docs/guides/OPERATIONS-RUNBOOK.md b/docs/guides/OPERATIONS-RUNBOOK.md
@@ -3,7 +3,7 @@
 - **Audience**: maintainers, support engineers, and reviewers
 - **Canonical for**: activation checks, queue behavior, diagnostics, and common failure handling
 - **Update when**: operational troubleshooting, queue behavior, diagnostics surfaces, or recovery steps change
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 ## Activation and Boot
 
diff --git a/docs/guides/SETTINGS-AND-ADMIN.md b/docs/guides/SETTINGS-AND-ADMIN.md
@@ -3,7 +3,7 @@
 - **Audience**: contributors, maintainers, designers, and reviewers
 - **Canonical for**: admin IA, screen structure, option mapping, and settings save behavior
 - **Update when**: tabs, settings grouping, screen slugs, or admin save contracts change
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 This document describes the active admin experience and how it maps back to the stored option keys.
 
diff --git a/docs/reference/FEATURE-REGISTRY.md b/docs/reference/FEATURE-REGISTRY.md
@@ -3,7 +3,7 @@
 - **Audience**: contributors, maintainers, reviewers, and release engineers
 - **Canonical for**: internal capability registry, destination metadata, adapter metadata, and smoke-test IDs
 - **Update when**: a capability, destination, adapter, docs target, or smoke ID is added, renamed, or removed
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 This document describes the internal feature registry used to keep ClickTrail's growing surface area aligned across admin UI, diagnostics, docs, and QA.
 
diff --git a/docs/reference/HOOKS-REFERENCE.md b/docs/reference/HOOKS-REFERENCE.md
@@ -3,7 +3,7 @@
 - **Audience**: contributors, integrators, and maintainers
 - **Canonical for**: public filters and actions exposed by the plugin
 - **Update when**: a public hook is added, removed, renamed, or changes contract
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 This document lists the public custom hooks currently exposed by the active codebase.
 
diff --git a/docs/reference/INTEGRATIONS.md b/docs/reference/INTEGRATIONS.md
@@ -3,7 +3,7 @@
 - **Audience**: contributors, maintainers, reviewers, and solution engineers
 - **Canonical for**: supported integrations, providers, CMP sources, webhook sources, and delivery adapters
 - **Update when**: integration support level, adapter list, provider list, or capability messaging changes
-- **Last verified against version**: `1.7.0`
+- **Last verified against version**: `1.8.5`
 
 This document lists the active integrations and external-facing connection points in the current codebase.
 
diff --git a/readme.txt b/readme.txt
@@ -212,6 +212,11 @@ Yes. ClickTrail can listen to its own banner, Cookiebot, OneTrust, Complianz, GT
 
 == Changelog ==
 
+= 1.8.5 =
+*   **WordPress 7.0 compatibility**: Tested up to WordPress 7.0 "Armstrong" (released 2026-05-20). Requires WooCommerce 10.4.2 or later for WP 7.0 compatibility.
+*   **Script enqueue refactor**: Removed dead pre-WP-6.3 fallback from `clicutcl_script_args()`. All supported installs (WP 6.5+) now use the array-form registration and optional `defer`/`async` strategy keys.
+*   **Deprecation scan in CI**: Added `composer phpcompat` and a PHPCompatibilityWP GitHub Actions workflow to flag PHP and WordPress deprecated/removed API usage on every push.
+
 = 1.7.2 =
 *   **NitroPack compatibility**: ClickTrail now detects NitroPack and automatically attempts to exclude its scripts from NitroPack's "Postpone JS" feature via two mechanisms: the `nitropack_js_url_exclude` filter and the `data-nitropack-exclude` HTML attribute on script tags. Without this, postponed scripts can cause empty UTM data on leads when users navigate away before interacting with the page.
 *   **NitroPack diagnostic warning**: The Diagnostics conflict scan now surfaces a `warn` finding when NitroPack is active, with instructions to verify script exclusions in NitroPack → Optimization → JavaScript → Script exclusions.
