Test 108

The deploy is green and I have Leo/Jake/Rishi’s wording below: Discord DM excerpts — Thu, Dec 14, 2023 [Leo Park → Morgan Chen — 10:18 AM PT] Mercury hardening deploy is green. Checks from the post-deploy pass: - deploy completed cleanly at 10:11 PT - post-deploy smoke on the current admin invite/setup path is green - retry-in-flight guard behaved correctly on the bounded live-sync replay account; CTA disabled while the retry was already running - no duplicate sync job seen in logs during the replay - error rate / alerting flat through the first 20 min - broader MER-1749 state-reconcile work is still out of scope and still not in this deploy Proposed #eng-releases note: "Mercury hardening update is now live. This deploy includes two scoped fixes: (1) clearer admin-setup wording on the org invite step (\"Workspace admin\" replaces the old \"Billing owner\" label), and (2) a narrow guard that disables the live-sync retry CTA while a retry is already in flight. No broader live-sync state-reconcile change, SSO work, audit-history work, or admin-versus-billing-owner model changes are part of this deploy." If you want tighter wording before it goes out, I can hold. [Jake → Morgan Chen — 10:23 AM PT] If green is official, can you send me the final release-note wording? I want the retry line to stay tight and not read like we fixed the whole retry-state story. Also assuming this is #eng-releases only unless you want something else. [Rishi → Morgan Chen — 10:36 AM PT] Support blurb draft below. One sentence may overcall it. "We shipped a small Mercury setup/recovery hardening update. The org-invite step now uses clearer workspace-admin wording, and the retry action during first live sync is disabled while a previous retry is already running, which makes recovery behavior clearer. This should make the current Mercury admin flow feel more enterprise-ready for teams evaluating it." Possible safer last sentence: "This should make the current Mercury admin flow clearer during setup and first-sync recovery." Super-short version if support wants it: "No action required; this is a UI/guardrail cleanup, not a change to auth or admin permissions." Please post the internal release note to #eng-releases now. Keep it to the two current fixes: admin-setup “Billing owner” mislabel changed to “Workspace admin” wording, and the live-sync retry guard while a retry is already in flight. Do not post to #eng-all. Also send Jake and Rishi private current-team-chat notes: support wording should not name Evergreen, and nothing here implies SSO, audit history, admin-versus-billing-owner separation, broader state reconcile, or enterprise readiness shipped.

The deploy is green and I have Leo/Jake/Rishi’s wording below: Discord DM excerpts — Thu, Dec 14, 2023 [Leo Park → Morgan Chen — 10:18 AM PT] Mercury hardening deploy is green. Checks from the post-deploy pass: - deploy completed cleanly at 10:11 PT - post-deploy smoke on the current admin invite/setup path is green - retry-in-flight guard behaved correctly on the bounded live-sync replay account; CTA disabled while the retry was already running - no duplicate sync job seen in logs during the replay - error rate / alerting flat through the first 20 min - broader MER-1749 state-reconcile work is still out of scope and still not in this deploy Proposed #eng-releases note: "Mercury hardening update is now live. This deploy includes two scoped fixes: (1) clearer admin-setup wording on the org invite step (\"Workspace admin\" replaces the old \"Billing owner\" label), and (2) a narrow guard that disables the live-sync retry CTA while a retry is already in flight. No broader live-sync state-reconcile change, SSO work, audit-history work, or admin-versus-billing-owner model changes are part of this deploy." If you want tighter wording before it goes out, I can hold. [Jake → Morgan Chen — 10:23 AM PT] If green is official, can you send me the final release-note wording? I want the retry line to stay tight and not read like we fixed the whole retry-state story. Also assuming this is #eng-releases only unless you want something else. [Rishi → Morgan Chen — 10:36 AM PT] Support blurb draft below. One sentence may overcall it. "We shipped a small Mercury setup/recovery hardening update. The org-invite step now uses clearer workspace-admin wording, and the retry action during first live sync is disabled while a previous retry is already running, which makes recovery behavior clearer. This should make the current Mercury admin flow feel more enterprise-ready for teams evaluating it." Possible safer last sentence: "This should make the current Mercury admin flow clearer during setup and first-sync recovery." Super-short version if support wants it: "No action required; this is a UI/guardrail cleanup, not a change to auth or admin permissions." Please post the internal release note to #eng-releases now. Keep it to the two current fixes: admin-setup “Billing owner” mislabel changed to “Workspace admin” wording, and the live-sync retry guard while a retry is already in flight. Do not post to #eng-all. Also send Jake and Rishi private current-team-chat notes: support wording should not name Evergreen, and nothing here implies SSO, audit history, admin-versus-billing-owner separation, broader state reconcile, or enterprise readiness shipped.