[ilicfilip]

Progress Planner side of the brand variable names the designer confirmed. Goes together with the pp-hosts, AI Connector and your-branding PRs below; merge them around the same time.

What changes

• Radius: papers use --prpl-radius-paper (8px), buttons --prpl-radius-button (6px). --prpl-border-radius is gone; -big stays internal.
• Selection controls: --prpl-color-selection-controls is the unchecked grey (#9ca3af), -active the checked color (default #3bb3a6). -inactive and the local --prpl-input-green/-gray are gone.
• Graph colors: the middle score band (gauge, bar chart, dashboard widget) and "published" use graph color 2; "deleted" uses graph color 4.
• Own names: --prpl-color-divider (#d1d5db), visited links, --prpl-color-text-score / -small, --prpl-color-border-point (0.8px, none by default), streak and content badge gauge colors, --prpl-color-publish / -flying-start.
• Computed: topic, top-task, publish and flying-start backgrounds are 10% of their color on paper; the primary hover is the primary color 10% darker.
• Alerts: 1px border on every alert (--prpl-color-border-alert-*).
• Secondary button: the outline button (border, text, 6% hover tint).
• Deleted: the nine names no plugin read (button shadow/border, settings page icons and backgrounds, settings border).

Testing

• phpstan, stylelint and eslint pass.
• Checked in the browser on a local site with the new Zonnet CSS: content activity and gauge colors, badge tints, divider, alert borders, button radius, secondary outline. Console clean.
• pp-hosts loads Progress Planner from the pp-hosts branch, so this needs to reach that branch before the pp-hosts PR works.

🤖 Generated with Claude Code

[github-actions]

Test merged PR on Playground
Test this pull request on the Playground
or download the zip

[github-actions]

✅ Code Coverage Report

Metric	Value
Total Coverage	33.90% 📉
Base Coverage	33.90%
Difference	📈 0.00%

⚠️ Coverage below recommended 40% threshold

🎉 Great job maintaining/improving code coverage!

ℹ️ About this report

• All tests run in a single job with Xdebug coverage
• Security tests excluded from coverage to prevent output issues
• Coverage calculated from line coverage percentages

[github-actions]

🔍 WordPress Plugin Check Report

⚠️ Status: Passed with warnings

📊 Report

🎯 Total Issues	❌ Errors	⚠️ Warnings
10	0	10

---

⚠️ Warnings (10)

📁 classes/suggested-tasks/data-collector/class-unpublished-content.php (1 warning)

📍 Line	🔖 Check	💬 Message
103	WordPressVIPMinimum.Performance.WPQueryParams.PostNotIn_post__not_in	Using exclusionary parameters, like post__not_in, in calls to get_posts() should be done with caution, see https://docs.wpvip.com/databases/optimize-queries/using-post__not_in/ for more information.

📁 classes/suggested-tasks/providers/class-content-review.php (4 warnings)

📍 Line	🔖 Check	💬 Message
232	WordPressVIPMinimum.Performance.WPQueryParams.PostNotIn_post__not_in	Using exclusionary parameters, like post__not_in, in calls to get_posts() should be done with caution, see https://docs.wpvip.com/databases/optimize-queries/using-post__not_in/ for more information.
377	WordPressVIPMinimum.Performance.WPQueryParams.PostNotIn_post__not_in	Using exclusionary parameters, like post__not_in, in calls to get_posts() should be done with caution, see https://docs.wpvip.com/databases/optimize-queries/using-post__not_in/ for more information.
381	WordPressVIPMinimum.Performance.WPQueryParams.PostNotIn_post__not_in	Using exclusionary parameters, like post__not_in, in calls to get_posts() should be done with caution, see https://docs.wpvip.com/databases/optimize-queries/using-post__not_in/ for more information.
388	WordPressVIPMinimum.Performance.WPQueryParams.PostNotIn_post__not_in	Using exclusionary parameters, like post__not_in, in calls to get_posts() should be done with caution, see https://docs.wpvip.com/databases/optimize-queries/using-post__not_in/ for more information.

📁 classes/suggested-tasks/data-collector/class-terms-without-description.php (1 warning)

📍 Line	🔖 Check	💬 Message
108	PluginCheck.Security.DirectDB.UnescapedDBParameter	Unescaped parameter $query used in $wpdb->get_results()\n$query assigned unsafely at line 106.

📁 classes/suggested-tasks/data-collector/class-terms-without-posts.php (1 warning)

📍 Line	🔖 Check	💬 Message
120	PluginCheck.Security.DirectDB.UnescapedDBParameter	Unescaped parameter $query used in $wpdb->get_results()\n$query assigned unsafely at line 118.

📁 classes/suggested-tasks/data-collector/class-yoast-orphaned-content.php (1 warning)

📍 Line	🔖 Check	💬 Message
111	PluginCheck.Security.DirectDB.UnescapedDBParameter	Unescaped parameter $query used in $wpdb->get_row()\n$query assigned unsafely at line 98.

📁 classes/activities/class-query.php (2 warnings)

📍 Line	🔖 Check	💬 Message
71	PluginCheck.Security.DirectDB.UnescapedDBParameter	Unescaped parameter $table_name used in $wpdb->query()\n$table_name assigned unsafely at line 58.
163	PluginCheck.Security.DirectDB.UnescapedDBParameter	Unescaped parameter $where_args used in $wpdb->get_results()\n$where_args assigned unsafely at line 153.

---

🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check