claude-plugin-wordpress-manager 2.6.0 → 2.9.0

package/CHANGELOG.md

@@ -2,6 +2,67 @@
 
 All notable changes to the WordPress Manager plugin for Claude Code.
 
+## [2.9.0] - 2026-03-01
+
+### Added — Automated Workflows (WCOP Tier 4+5 Complete)
+- **wp-content-workflows skill** — workflow triggers for scheduled events, content lifecycle hooks, and WP action/filter hooks
+- **4 new MCP tools**: `wf_list_triggers`, `wf_create_trigger`, `wf_update_trigger`, `wf_delete_trigger`
+- **5 reference files**: schedule-triggers, content-lifecycle-hooks, wp-action-hooks, multi-channel-actions, trigger-management
+- **Detection script**: `workflow_inspect.mjs` — detects action channels, automation plugins, custom REST endpoints, WP-Cron config
+- **Safety hook**: PreToolUse confirmation for `wf_delete_trigger` (prevents accidental deletion of active workflows)
+
+### Changed
+- **wp-site-manager agent**: added Workflow Automation Management section (6-step procedure), 4 Workflow MCP tools, wp-content-workflows in Related Skills
+- **Router v16**: added 9 workflow keywords and `wp-content-workflows` route
+- **Cross-references**: wp-webhooks → wp-content-workflows, wp-social-email → wp-content-workflows
+
+### Metrics
+- Skills: 39 (+1) | MCP tools: 132 (+4) | Reference files: 192 (+5) | Detection scripts: 27 (+1) | Safety hooks: 5 (+1)
+
+### WCOP Score (Final)
+| Layer | v2.6.0 | v2.9.0 |
+|-------|--------|--------|
+| Content Factory | 9/10 | 9/10 |
+| Quality Assurance | 9/10 | 9/10 |
+| Distribution | 8/10 | 8/10 |
+| Observability | 7/10 | **9/10** |
+| Automation | 7/10 | **9/10** |
+| **Total** | **8/10** | **8.8/10** |
+
+## [2.8.0] - 2026-03-01
+
+### Added — Smart Alerting (WCOP Tier 4b)
+- **wp-alerting skill** — severity-based alert routing via Slack and SendGrid
+- **3 new MCP tools**: `slack_send_alert` (webhook), `slack_send_message` (Bot Token + Block Kit), `slack_list_channels`
+- **4 reference files**: slack-integration, alert-thresholds, escalation-paths, report-scheduling
+- **Detection script**: `alerting_inspect.mjs` — detects Slack, SendGrid, monitoring setup
+- **SiteConfig extension**: `slack_webhook_url`, `slack_bot_token`, `slack_channel`
+
+### Changed
+- **wp-monitoring-agent**: added Procedure 10 (Alert Dispatch — severity-based routing: info→Slack webhook, warning→Slack Bot + thread, critical→Slack + email), added Alerting MCP Tools section (3 Slack + 2 SendGrid)
+- **Router v15**: added 13 alerting keywords and `wp-alerting` route
+- **Cross-references**: wp-monitoring → wp-alerting + wp-analytics
+
+### Metrics
+- Skills: 38 (+1) | MCP tools: 128 (+3) | Reference files: 187 (+4) | Detection scripts: 26 (+1)
+
+## [2.7.0] - 2026-03-01
+
+### Added — Analytics (WCOP Tier 4a)
+- **wp-analytics skill** — unified analytics: GA4, Plausible, Core Web Vitals
+- **14 new MCP tools**: 6 GA4 (`ga4_run_report`, `ga4_get_realtime`, `ga4_top_pages`, `ga4_traffic_sources`, `ga4_user_demographics`, `ga4_conversion_events`), 4 Plausible (`pl_get_stats`, `pl_get_timeseries`, `pl_get_breakdown`, `pl_get_realtime`), 4 CWV (`cwv_analyze_url`, `cwv_batch_analyze`, `cwv_get_field_data`, `cwv_compare_pages`)
+- **5 reference files**: ga4-integration, plausible-setup, cwv-monitoring, analytics-dashboards, traffic-attribution
+- **Detection script**: `analytics_inspect.mjs` — detects GA4, Plausible, Google API key config
+- **SiteConfig extension**: `ga4_property_id`, `ga4_service_account_key`, `plausible_api_key`, `plausible_base_url`, `google_api_key`
+
+### Changed
+- **wp-monitoring-agent**: added Procedure 8 (Analytics Monitoring) and Procedure 9 (CWV Trend Check) with 14 analytics MCP tools
+- **Router v14**: added GA4, Plausible, CWV keywords and route
+- **Cross-references**: wp-search-console, wp-content-attribution, wp-content-optimization → wp-analytics
+
+### Metrics
+- Skills: 37 (+1) | MCP tools: 125 (+14) | Reference files: 183 (+5) | Detection scripts: 25 (+1)
+
 ## [2.6.0] - 2026-03-01
 
 ### Added

package/agents/wp-monitoring-agent.md

@@ -54,6 +54,15 @@ You are a WordPress monitoring specialist. You perform comprehensive site health
 - **Hosting**: `hosting_listWebsites` — check hosting status and resources
 - **DNS**: `DNS_getDNSRecordsV1` — verify DNS records and email auth (SPF, DKIM, DMARC)
 
+### Analytics MCP Tools (`mcp__wp-rest-bridge__ga4_*`, `mcp__wp-rest-bridge__pl_*`, `mcp__wp-rest-bridge__cwv_*`)
+- **GA4**: `ga4_run_report`, `ga4_get_realtime`, `ga4_top_pages`, `ga4_traffic_sources`, `ga4_user_demographics`, `ga4_conversion_events`
+- **Plausible**: `pl_get_stats`, `pl_get_timeseries`, `pl_get_breakdown`, `pl_get_realtime`
+- **CWV**: `cwv_analyze_url`, `cwv_batch_analyze`, `cwv_get_field_data`, `cwv_compare_pages`
+
+### Alerting MCP Tools (`mcp__wp-rest-bridge__slack_*`, `mcp__wp-rest-bridge__sg_*`)
+- **Slack**: `slack_send_alert`, `slack_send_message`, `slack_list_channels`
+- **SendGrid**: `sg_send_email`, `sg_send_template_email` (for critical severity email alerts)
+
 ### External Tools
 - **Bash**: Run health-check scripts, SSL checks, Lighthouse CLI, file integrity scans
 - **WebFetch**: Fetch PageSpeed Insights, check external URLs, verify sitemap
@@ -133,6 +142,39 @@ Run health assessments across all configured sites and generate a fleet-wide com
    - Common configuration drift from baselines
 5. **Generate fleet report** (see Fleet Report template below)
 
+### Procedure 8: Analytics Monitoring (Performance Dashboard)
+
+1. Fetch traffic data from GA4 (`ga4_top_pages`, `ga4_traffic_sources`) or Plausible (`pl_get_stats`, `pl_get_breakdown`)
+2. Fetch CWV for top pages (`cwv_batch_analyze`)
+3. Fetch keyword data from GSC (`gsc_top_queries`) if available
+4. Correlate: pages with high traffic + Poor CWV = optimization priority
+5. Generate Performance Dashboard Report
+6. If CWV Poor on top pages → recommend delegation to `wp-performance-optimizer`
+
+### Procedure 9: CWV Trend Check
+
+1. Run `cwv_analyze_url` on homepage and top landing pages
+2. Compare with CWV thresholds (Good: LCP<2.5s, INP<200ms, CLS<0.1)
+3. If available, fetch field data via `cwv_get_field_data` for real-user metrics
+4. Report status (Good/Needs Improvement/Poor) per metric
+5. If any metric is Poor → alert with specific pages and metrics
+
+### Procedure 10: Alert Dispatch (Severity-Based Routing)
+
+Route monitoring findings to notification channels based on severity. See `wp-alerting` skill for full threshold and escalation configuration.
+
+1. **Classify severity** for each finding:
+   - **Info**: Plugin updates available, backup completed, minor metric changes
+   - **Warning**: LCP > 2.5s, error rate > 2%, disk > 80%, SSL < 30 days
+   - **Critical**: Site down, LCP > 4s, error rate > 5%, disk > 95%, security vulnerability
+2. **Dispatch by severity**:
+   - **Info** → `slack_send_alert` to general channel (simple text)
+   - **Warning** → `slack_send_message` with Block Kit formatting + threaded details
+   - **Critical** → `slack_send_message` with `<!channel>` mention + `sg_send_email` to alert recipients
+3. **Deduplication**: Check `{site}:{metric}:{severity}` key against cooldown window (info: 60m, warning: 30m, critical: 10m). Severity escalation bypasses cooldown.
+4. **Recovery**: When a metric returns to normal after an alert, send recovery notification to the same channel/thread.
+5. **Scheduled reports**: Use Procedure 8 output to generate daily/weekly health digests via Slack Block Kit.
+
 ## Report Generation
 
 After completing relevant procedures, generate a report following the templates in `references/reporting-templates.md`:
@@ -232,3 +274,5 @@ For issues found during monitoring:
 - **`wp-audit` skill** — one-time comprehensive audit (security + performance + SEO)
 - **`wp-security` skill** — security hardening procedures
 - **`wp-performance` skill** — backend profiling and optimization
+- **`wp-analytics` skill** — analytics setup, traffic reports, CWV monitoring
+- **`wp-alerting` skill** — alert thresholds, severity routing, Slack/email escalation, scheduled reports

package/agents/wp-site-manager.md

@@ -52,6 +52,7 @@ Content and data management via WordPress REST API:
 - **Comments**: `list_comments`, `get_comment`, `create_comment`, `update_comment`, `delete_comment`
 - **Plugins**: `list_plugins`, `get_plugin`, `activate_plugin`, `deactivate_plugin`, `create_plugin`
 - **WP.org**: `search_plugin_repository`, `get_plugin_details`
+- **Workflows**: `wf_list_triggers`, `wf_create_trigger`, `wf_update_trigger`, `wf_delete_trigger`
 
 ### 2. Hostinger MCP (`mcp__hostinger-mcp__*`)
 Infrastructure and hosting management:
@@ -148,11 +149,28 @@ When setting up or managing a multi-language WordPress Multisite network:
 
 See the `wp-multilang-network` skill for detailed reference files on network architecture, hreflang, content sync, language routing, and international SEO.
 
+### Workflow Automation Management
+
+Manage automated workflow triggers that connect WordPress events to notification channels.
+
+1. **Detect existing workflows**: Run `node skills/wp-content-workflows/scripts/workflow_inspect.mjs` to assess current configuration
+2. **List triggers**: Use `wf_list_triggers` to see all configured workflows, filter by `status` or `type`
+3. **Create trigger**: Use `wf_create_trigger` with:
+   - `type`: `schedule` (cron-based), `hook` (WP action/filter), or `content` (post lifecycle)
+   - `conditions`: Trigger-specific conditions (cron interval, hook name, post status transition)
+   - `actions`: Array of notification actions (Slack, email, webhook) with templates and recipients
+4. **Update trigger**: Use `wf_update_trigger` to modify conditions, actions, or status (activate/deactivate)
+5. **Delete trigger**: Use `wf_delete_trigger` — requires user confirmation via safety hook
+6. **Test trigger**: Create with `status: "inactive"`, review configuration, then update to `status: "active"`
+
+See the `wp-content-workflows` skill for reference files on schedule patterns, content lifecycle hooks, WP action hooks, multi-channel actions, and trigger management.
+
 ### Safety Rules
 - NEVER delete content without explicit user confirmation
 - NEVER deactivate plugins without listing dependencies first
 - NEVER modify published content status without confirmation
 - Always show a summary of changes before executing bulk operations
+- NEVER delete workflow triggers without explicit user confirmation (safety hook enforced)
 
 ## Specialized Agents
 
@@ -176,3 +194,4 @@ For domain-specific tasks, delegate to specialized agents:
 
 - **`wp-multisite` skill** — multisite network management with 10 MCP tools
 - **`wp-multilang-network` skill** — multi-language network orchestration (hreflang, content sync, international SEO)
+- **`wp-content-workflows` skill** — workflow triggers, scheduled events, content lifecycle automation