alonso.torres 4c9d30ef6a ✨ Make plugin writes fail while the workspace is read-only ...

A read-only workspace (saves failing, a user who cannot edit, a version
preview) only hid the editing tools: plugins, the MCP among them, still
changed shapes, and those edits were never saved. Every plugin write now
throws a read-only error, whatever the throwValidationErrors flag, the
same way a write to a removed shape does.

`check-permission` with a write permission runs the new `check-writable`,
which covers most writers. Writers without a permission check (most
context methods such as create*, group, align or flatten, the z-order
methods, applyTypography on a text range, removing a ruler guide) call it
themselves, and shape setters get it through `check-shape-writable`.
Reads, comments and undo blocks keep working, so a block opened before a
lock still closes.

The MCP instructions tell the agent what the read-only error means.

2026-11-03 11:17:34 +01:00

..

api_types.yml

✨ Add token source to plugins (#12183)

2026-10-16 17:58:51 +02:00

base_instructions.md

⏪ Backport MCP from staging (part 1)

2026-04-20 19:37:02 +02:00

initial_instructions.md

✨ Make plugin writes fail while the workspace is read-only

2026-11-03 11:17:34 +01:00