Commit 0551d146ac4 for woocommerce

commit 0551d146ac437b3ca3ecca7cd5ec4d4bf3896a21
Author: Rafael Meneses <meneses.tio@gmail.com>
Date:   Wed Aug 12 12:57:25 2026 -0300

    Add extension fatal-error alerts to the release monitoring guide (#67637)

    * docs: Add extension fatal-error alerts to the release monitoring guide

    The release monitoring guide covered public signals only (WordPress.org
    forums and GitHub issues). Extension fatals on WP Cloud - the earliest
    field signal that a release broke extensions - were invisible to the
    release lead unless they knew every owning team's alert channel.

    Every Automattic-owned extension now has a Grafana fatal-error alert
    that routes to the owning team's channel and also to the shared
    #woo-core-releases-notifications Slack channel. Document that channel
    as part of the monitoring window: how to read an alert, who owns the
    triage, and how to tell stale-extension noise from a release
    regression.

    Refs ARC-1820

    Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

    * docs: clarify that an old extension version is a signal not a cause

    The release monitoring guide told the release lead that fatals from old
    extension versions right after a release usually mean the site updated
    WooCommerce without updating the extension. That reads a cause out of a
    single signal: an old extension version points at a possible compatibility
    issue, but it does not prove the release is innocent, and a lead following
    it could dismiss a real regression. Reword it so the old version reads as a
    signal and the lead compares both the WooCommerce and the extension versions
    before ruling out a regression.

    Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

    ---------

    Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

diff --git a/docs/contribution/releases/monitoring.md b/docs/contribution/releases/monitoring.md
index 228bf9b3eac..05cddd6cac6 100644
--- a/docs/contribution/releases/monitoring.md
+++ b/docs/contribution/releases/monitoring.md
@@ -18,6 +18,14 @@ Check newly created threads on the [WordPress.org Forums](https://wordpress.org/

 Watch the [Newest Created Issues](https://github.com/woocommerce/woocommerce/issues?q=is%3Aissue%20state%3Aopen%20sort%3Acreated-desc) and verify that none are critical.

+## Extension Fatal-Error Alerts
+
+Every Woo-owned extension has a Grafana fatal-error alert on WP Cloud, backed by the internal *Woo\* Fatals on WP Cloud* dashboard. Alerts post to the owning team's channel and to `#woo-core-releases-notifications`. Watch that channel during the monitoring window.
+
+When an alert fires, open the linked dashboard panel to see how many sites are affected, then reply on the alert to ping the owning team - triage is theirs. If the fatal traces back to the release, treat it as a candidate critical issue (see below).
+
+An old extension version can point to a compatibility issue, but it does not prove the release caused the fatal. Compare the affected WooCommerce and extension versions before calling it a non-regression.
+
 ## Handling Critical Issues

 If monitoring uncovers a bug that **cannot wait** for the next scheduled release, plan a point release. Before doing so, confirm that the issue: