MCP Server v0.0.1-beta.25

What's new

• Editing the code of an experience that is running, paused, or completed but still showing a variation asks you to confirm that experience first, because the change reaches visitors as soon as it is saved, with no preview. Cloning it to a draft is offered as the safer path.
• Archiving an experience asks you to confirm that experience first, because an archived experience can't be restored.
• Confirmations are asked one experience at a time, never as one reply for several, and a delete first looks the item up, names it and says the delete is permanent. Deleting a goal, location or audience first lists the experiences found using it.
• Draft checks list the live experiences that run on the same pages as a draft, so you can check them before launch, and flag a web experience with no location as blocking, because it would never run or collect visitors.
• Creating a goal that relies on Google Analytics warns you when GA4 isn't connected in the project.
• Reports explain that a conversion rate is a percentage, so the gap between two rates is in percentage points, while the change between variations is a ratio.
• The workflow prompts for updating an experience and checking drafts show code changes word for word, offer a draft clone before editing a running experience, and read every draft before calling it ready.

No reconnect is needed to upgrade.