chore(mollifier): clarify server-changes note — monitoring only, no diversion

The previous wording implied the buffer/drainer was active protection;
in this release they're audit-only. Spell out that no trigger calls are
diverted or rate-limited yet, and that active smoothing follows later.

Author: d-cs

.server-changes/mollifier-burst-protection.md

@@ -3,4 +3,4 @@ area: webapp
 type: feature
 ---
 
-Add the trigger mollifier: an opt-in burst-protection layer for the trigger hot path that detects per-env trigger storms and (when enabled) buffers them into Redis so the run engine can drain them at a sustainable rate. All new env vars default off, so existing deployments see no behaviour change. Operators can enable shadow-mode-only observability with `MOLLIFIER_SHADOW_MODE=1` (logs `mollifier.would_mollify` when an env exceeds the configured threshold, no buffer writes). Enabling `MOLLIFIER_ENABLED=1` with a per-org `mollifierEnabled` flag turns on dual-write monitoring: each over-threshold trigger is recorded in a Redis buffer alongside the normal `engine.trigger` call, and a background drainer pops and acks entries. Emits the `mollifier.decisions` OTel counter for per-env rate visibility.
+Lay the groundwork for an opt-in burst-protection layer on the trigger hot path. This release ships **monitoring only** — operators can observe per-env trigger storms via two opt-in modes, but no trigger calls are diverted or rate-limited yet (active burst smoothing follows in a later release). All new env vars default off, so existing deployments see no behaviour change. With `MOLLIFIER_SHADOW_MODE=1`, each trigger evaluates a per-env rate counter and logs `mollifier.would_mollify` when the threshold is crossed. With `MOLLIFIER_ENABLED=1` plus a per-org `mollifierEnabled` flag, over-threshold triggers are also recorded in a Redis audit buffer alongside the normal `engine.trigger` call, drained by a background no-op consumer. Emits the `mollifier.decisions` OTel counter for per-env rate visibility.