From c0079aabe99be12b8edc928addf1cb6708de77bb Mon Sep 17 00:00:00 2001
From: prxnvt <53838599+prxnvt@users.noreply.github.com>
Date: Wed, 21 Oct 2026 17:22:50 -0400
Subject: [PATCH] Docs: a failed macro run rolls back workbook changes; a file
 it already wrote stays

The intro said a macro run rolls everything back on an error, but a step that exports or prints to a path writes the file before a later step can fail, and the Running section says that file stays. The intro now limits the guarantee to workbook changes.
---
 docs/macros.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/macros.md b/docs/macros.md
index dc0c044c7..7c7953ccf 100644
--- a/docs/macros.md
+++ b/docs/macros.md
@@ -4,8 +4,9 @@
 
 GridCraft macros are typed, declarative lists of commands, not VBA. Every step runs a GridCraft
 command (the same ids the ribbon, CLI and MCP use) or one of three bounded control steps. A macro
-declares the inputs it works on, runs as one undo step, rolls everything back on an error, checks
-where its results will land before it writes them, and does not touch files without permission.
+declares the inputs it works on, runs as one undo step, rolls all workbook changes back on an
+error (a file it already wrote stays), checks where its results will land before it writes them,
+and does not touch files without permission.
 Agents run macros with `macro.run` like any other command.
 
 This page describes the macro format, its tokens, and running and checking macros. The engine has