Status: attention (Cloudflare + Sentry oauth-pending; Copilot insights blocked on subscription)

Executive summary

Cloudways production stack (saguiar-prod-vultr-atl, server 1615235, Vultr ATL hfn-4GB) is healthy. All critical services running (apache2, nginx, mysql, php8.2-fpm, varnish, redis, memcached, imunify360). Disk: 20 GB used / 120 GB (18%), ~95 GB free (confirmed by Cloudways graph + SSH df). Daily backups configured.

Recurring "WordPress 6.2.2" flag is now RESOLVED: live site runs WordPress 7.0 (SSH wp core version). The Cloudways app_version field is stale installer metadata, not a real lag. Closes the anomaly carried from the 2026-05-18 → 2026-05-20 runs.

Cloudways

• Services: running — apache2, imunify360, memcached, mysql, nginx, php8.2-fpm, redis-server, varnish. Stopped: newrelic-sysmond (expected). Disabled: elasticsearch, opensearch, rabbitmq, supervisor (expected).
• Disk: 20 GB / 120 GB used (18%), ~95 GB free; flat trend across the day — no pressure. Live uploads dir 741 MB.
• Per-app DB: live fctbkwwahp ≈ 2,912 MB; staging emubdqbbhw ≈ 2,615 MB.
• Bandwidth: monthly datapoint 45,350 (low, consistent with small-traffic WP).
• WordPress: live = 7.0 (SSH). Cloudways field shows 6.2.2 = stale metadata.
• Copilot insights: blocked — 403 "Active Copilot subscription required" (paid feature not enabled).

Cloudflare

skipped: oauth-pending — both CF MCPs unauthenticated; unattended run can't drive OAuth.

Sentry

skipped: oauth-pending — sentry MCP unauthenticated.

Drift / self-heal

• Self-heal (enrichment): added read-only SSH wp core version probe → confirmed live WP 7.0, settled the stale-6.2.2 flag. Proposal proposals/2026-06-13-v1.md recommends baking the probe into STEP 2 (queued for Sam, not auto-applied — edits routine SKILL.md).
• Wording drift (low): Cloudways copilot 403 changed from "optin required" to "subscription required"; same blocked outcome, no code change needed.

QA block (4-way MC; A = recommended)

QA — Cloudflare + Sentry oauth-pending (ongoing): A. Leave as-is, self-recovers post-OAuth (Recommended). B. Split into post-auth-only routines. C. curl-based edge probes instead. D. Other.