M10: clarify Zotero command response shapes (#6700)

This commit is contained in:
Mex authored and GitHub committed 2026-11-17 00:20:17 +01:00
1 parent 4a347e070a
commit 646fbc7cd5
1 file changed
+8 -5
+8 -5
View File
@@ -19,11 +19,14 @@ Citations (each runs one of the commands below).
| `ui.zotero.status` | `{busy, waitingForAnswer, last}` |
| `ui.zotero.answer` | `{"button": n}`: answer a question Zotero is asking (OK/Yes 1, No/Cancel 0; with Yes/No/Cancel: Yes 2, No 1, Cancel 0) |
They run in the app (and through the control channel and MCP bridged to the app). A command
returns at once with `{"started": …}`; Zotero then works in its own window and WordCraft answers
it in the background. All changes from one command are one undo step. If New or Open replaces
the document while a command is running, Zotero's remaining calls for it get an error and the
new document is left as it is.
They run in the app (and through the control channel and MCP bridged to the app). The six Zotero
actions return at once with `{"started": …}`; Zotero then works in its own window and WordCraft
answers it in the background. All changes from one action are one undo step. If New or Open
replaces the document while an action is running, Zotero's remaining calls for it get an error
and the new document is left as it is.
`ui.zotero.status` returns the current state. A successful `ui.zotero.answer` returns
`{"answered": n}` for the selected button.
From a terminal, against a file: