leemour · Oct 20, 2026 · Oct 20, 2026
diff --git a/docs/release-notes-review.json b/docs/release-notes-review.json
@@ -1,20 +1,20 @@
 {
   "tg": {
-    "version": "v0.76.0",
+    "version": "v0.77.0",
     "roadmapSha256": "978bfe805c38732b567388b00cbe701d12721599bc2d3e8dae060fee8f83baab",
-    "reviewedAt": "2026-10-19",
-    "conclusion": "Reviewed Telegram 0.76.0 (Core 0.362.0): without a terminal, session start qr and setup print the login QR code as text for an agent to paste into the chat as a code block, and a renewed code is pasted again; --json adds one {\"event\":\"qr\"} stderr line per code; --qr-file is removed; login stays off MCP. store clear --left names the chats it deletes and takes --dry-run. Core 0.351.0-0.362.0 fixes chats leave/join store updates, sent-message chat, re-keyed chat privacy, hidden-chat search, schedule last.json and the first serve after an upgrade; messages forward answers with the copy in the target chat. Changed native pages: changelog, cli-contract, commands, people (snake_case sample), query-language, rankings and cli-contract (cli-core links pinned to v0.350.0), security, sessions, troubleshooting (renamed heading), usage; RU/ES updated. The troubleshooting correction that quoted --qr-file <png> is retired: the heading is gone. Roadmap unchanged: richer sending, chat notes and max parity are not shipped."
+    "reviewedAt": "2026-10-20",
+    "conclusion": "Reviewed Telegram 0.77.0 (Core 0.370.0): tg guide lists memo's person-brief as 'One person across every tool' from cli-core MEMO_SCENARIOS; the scenario check now also refuses shell characters left unquoted in a step (tg's steps were already quoted). Core 0.363.0-0.370.0: store version 25 keeps a chat's history (chat_revisions) and a read by a re-keyed chat's old id finds it; a left chat is found by any of its ids in reads of its kept history, while chats track and store gaps plan refuse it. Changed native pages: changelog, and the v0.77.0 release links in cli-contract; RU/ES updated. Roadmap unchanged: richer sending, chat notes and max parity are not shipped."
   },
   "max": {
-    "version": "v0.65.0",
+    "version": "v0.66.0",
     "roadmapSha256": "f1628c3c19b2ea49f41fb57147b92bb0f9d29081ed577d1be3755a8a35b2a961",
-    "reviewedAt": "2026-10-19",
-    "conclusion": "Reviewed MAX 0.64.0-0.65.0 (Core 0.362.0): 0.64.0 briefly added --qr-file and stopped opening the QR code in a browser in a narrow terminal; 0.65.0 removes --qr-file, and without a terminal session start qr and setup print the QR code as text for an agent to paste as a code block; one code per run, about 2 minutes, rerun when it expires; the cloud password needs a terminal; login is not on MCP. store clear --left names its chats and takes --dry-run; a chat the owner returned to is no longer marked left. Changed native pages: changelog, commands, security (checks everything in the table), sessions (new Login through an agent section), and release links in bot/cli-contract/usage; EN/ES (and RU commands) updated. Roadmap unchanged: optional local copy, event actions, video notes, cloud password and native installers are not shipped."
+    "reviewedAt": "2026-10-20",
+    "conclusion": "Reviewed MAX 0.66.0 (Core 0.370.0): max guide catch-up and the first screen of max --help quote the filter, max review 'date>1d' --unanswered 4h (unquoted, a shell wrote a file named 1d and dropped the filter; the site's correction for it is retired); Works with shows memo's title from cli-core MEMO_SCENARIOS. Core 0.363.0-0.370.0: store version 25 keeps a chat's history; a left chat is found by any id, chats track and store gaps plan refuse it. Changed native pages: changelog, scenarios (quoted step), and the v0.66.0 release links in bot/cli-contract/usage; EN/ES (RU scenarios) updated. Roadmap unchanged: optional local copy, event actions, video notes, cloud password and native installers are not shipped."
   },
   "zm": {
-    "version": "v0.30.0",
+    "version": "v0.31.0",
     "roadmapSha256": "d6932e6c14696349630b8a975a2d32fb36bf79728ec8bd808457a72d79d9ae2d",
-    "reviewedAt": "2026-10-19",
-    "conclusion": "Reviewed Zoom 0.30.0 (Core 0.348.0): zm session start works without a terminal, printing 'Open this URL to approve Zoom login:' and the URL on stderr (kept with --quiet) and waiting for the browser callback on this computer; only the paste fallback needs a terminal; --no-input and CI still refuse; --interactive is removed. Changed native pages: changelog, commands, installation (Windows and cache folders in the uninstall list), security (any other write is refused), sessions (agent paragraph), troubleshooting; RU/ES updated. Roadmap unchanged: broader meeting preparation remains planned and is not shipped."
+    "reviewedAt": "2026-10-20",
+    "conclusion": "Reviewed Zoom 0.31.0 (Core 0.348.0 -> 0.370.0): Works with takes memo's person-brief title from cli-core MEMO_SCENARIOS; the scenario check refuses shell characters left unquoted in a step (zm's steps were already quoted); the shared store moves to version 25 (chat history) when first opened. Changed native pages: changelog; RU/ES updated. Roadmap unchanged: broader meeting preparation remains planned and is not shipped."
   }
 }
diff --git a/docs/reviews/2026-10-20-scenario-quoting-pins.md b/docs/reviews/2026-10-20-scenario-quoting-pins.md
@@ -0,0 +1,35 @@
+# tg 0.77.0, max 0.66.0, zoom 0.31.0, memo 0.81.0, drive 0.19.0
+
+Reviewer: Claude (scenario quoting session), 20 October 2026. Portal base `e494e59`.
+
+All five releases adopt cli-core 0.370.0 (cli-core#1675): `checkGuide` refuses a scenario step whose shell
+characters (`>`, `<`, `|`, `&`, `;`, backtick, `$(`, globs) are left outside quotes, and memo's cross-tool scenario
+titles come from one place, `MEMO_SCENARIOS`. The site found the bug this fixes: max 0.65.0's `catch-up` step
+`max review date>1d --unanswered 4h` made a shell write a file named `1d` and drop the filter. Core 0.363.0–0.369.0
+come along: store version 25 (a chat's history) and left chats found by any id.
+
+## Sources
+
+- Tags and npm: tg v0.77.0, max v0.66.0, zoom v0.31.0, drive v0.19.0, cli-memo v0.81.0 (`npm view` matches each).
+- Change lists: `git diff <old tag> <new tag> -- docs scenarios CHANGELOG.md` per tool.
+
+## Portal changes beside the ports
+
+- `scripts/docs-corrections.json`: the max `scenarios` correction that quoted `date>1d` is retired; 0.66.0 ships
+  the quoted step, and the RU/ES scenario translations carry it too.
+- `tools.json`: drive's and memo's `guideRefs` overrides are retired; their commits (drive `c86e077`, memo `fb5b7da`)
+  are in v0.19.0 and v0.81.0.
+
+## Review inventory
+
+| Page and locale | Reader task | Terms and opening | Behavior evidence | Links and exports | Result and owner |
+| --- | --- | --- | --- | --- | --- |
+| max: changelog (0.66.0), scenarios, en/es (scenarios ru/es); release links in bot, cli-contract, usage | Catch up after a day away | quoted `'date>1d'`; store version 25 | max v0.66.0 changelog and `scenarios/catch-up.md` | links pinned to v0.66.0 | Reviewed, Claude |
+| tg: changelog, cli-contract (release links), ru/es | Read a left chat's history | store version 25; left chat by any id | tg v0.77.0 changelog | links pinned to v0.77.0 | Reviewed, Claude |
+| zm: changelog, ru/es | — | shared store version 25 | zoom v0.31.0 changelog | — | Reviewed, Claude |
+| drive: changelog (English, as the page says), commands (`--json=id,name`), ru/es | Keep only some fields with `--json` | `name`, not `title` | drive v0.19.0 `docs/commands.md` | — | Reviewed, Claude |
+| memo: changelog 0.79.0–0.81.0 (English, as the page says), mcp, ru/es | Let an agent decide project findings | a changed text refuses only the findings citing it | cli-memo v0.81.0 `docs/mcp.md` | — | Reviewed, Claude |
+
+## Remaining (owning repositories)
+
+- None found in these releases.
diff --git a/scripts/docs-corrections.json b/scripts/docs-corrections.json
@@ -1997,30 +1997,5 @@
         }
       ]
     }
-  },
-  {
-    "tool": "max",
-    "slug": "scenarios",
-    "reason": "max 0.65.0 scenarios/catch-up.md leaves date>1d unquoted, so a copied command makes the shell redirect output to a file named 1d and drops the date filter; tg quotes the same filter.",
-    "replacements": {
-      "en": [
-        {
-          "before": "   max review date>1d --unanswered 4h\n",
-          "after": "   max review 'date>1d' --unanswered 4h\n"
-        }
-      ],
-      "ru": [
-        {
-          "before": "   max review date>1d --unanswered 4h\n",
-          "after": "   max review 'date>1d' --unanswered 4h\n"
-        }
-      ],
-      "es": [
-        {
-          "before": "   max review date>1d --unanswered 4h\n",
-          "after": "   max review 'date>1d' --unanswered 4h\n"
-        }
-      ]
-    }
   }
 ]
diff --git a/tools.json b/tools.json
@@ -9,7 +9,7 @@
       "ru": "MAX в терминале: боты через официальный Bot API и ваш личный аккаунт.",
       "es": "MAX Messenger desde la terminal: bots con la Bot API oficial y tu cuenta personal."
     },
-    "docsRef": "v0.65.0"
+    "docsRef": "v0.66.0"
   },
   {
     "name": "tg",
@@ -21,20 +21,15 @@
       "ru": "Клиент Telegram для терминала и ИИ-агентов, с вашим собственным аккаунтом.",
       "es": "Un cliente de Telegram para la terminal y para agentes de IA, con tu propia cuenta."
     },
-    "docsRef": "v0.76.0"
+    "docsRef": "v0.77.0"
   },
   {
     "name": "drive",
     "displayName": "Google Drive",
     "repo": "WireCatLabs/drive-cli",
     "package": "@wirecat/drive-cli",
     "lang": "en",
-    "docsRef": "v0.18.0",
-    "guideRefs": {
-      "usage": "c86e077a5ffac187ce079572a844318bc8b6a663",
-      "search": "c86e077a5ffac187ce079572a844318bc8b6a663",
-      "recipes": "c86e077a5ffac187ce079572a844318bc8b6a663"
-    },
+    "docsRef": "v0.19.0",
     "summary": {
       "en": "Import selected Google folders, search documents locally and keep tags, notes and source-backed memories.",
       "ru": "Импортируйте выбранные папки Google, ищите документы локально и сохраняйте теги, заметки и записи памяти с источниками.",
@@ -47,7 +42,7 @@
     "repo": "WireCatLabs/zoom-cli",
     "package": "@wirecat/zoom-cli",
     "lang": "en",
-    "docsRef": "v0.30.0",
+    "docsRef": "v0.31.0",
     "profile": false,
     "summary": {
       "en": "Keep Zoom transcripts and recordings, search meeting evidence and give your agent context for the next call.",
@@ -66,12 +61,7 @@
       "ru": "Заметки, почта и сообщения в одном месте для вашего ИИ-агента: поиск, теги, люди и память, на вашем компьютере.",
       "es": "Tus notas, correo y mensajes en un solo lugar para tu agente de IA: búsqueda, etiquetas, personas y recuerdos, en tu ordenador."
     },
-    "docsRef": "v0.78.0",
-    "guideRefs": {
-      "recipes": "fb5b7da5482a2be561e4ec49ec2dc765f7a2993b",
-      "search": "fb5b7da5482a2be561e4ec49ec2dc765f7a2993b",
-      "configuration": "fb5b7da5482a2be561e4ec49ec2dc765f7a2993b"
-    },
+    "docsRef": "v0.81.0",
     "profile": false
   }
 ]
diff --git a/translations/drive/changelog.es.md b/translations/drive/changelog.es.md
@@ -4,6 +4,26 @@ title: "Historial de cambios"
 
 Los detalles técnicos de las versiones se conservan en el idioma del proyecto original. Las guías traducidas explican las tareas habituales.
 
+## 0.19.0 — 20.10.2026
+
+### Added
+
+- **The shared store moves to version 25 when first opened** (cli-core 0.366.0): it adds a history of chat
+  changes for the messengers that share it. Nothing is sent.
+
+### Fixed
+
+- **`drive guide` lists memo's `decision-trail` under "Works with"**, the memo scenario whose steps run
+  `drive search`, next to `person-brief`, whose title is now capitalised as in memo and the other tools. Both titles
+  come from cli-core (0.348.0 → 0.370.0), whose scenario check also catches shell characters left outside
+  quotes in a step.
+
+- **Project context with Memo**: the guides now explain selected-folder sync, the shared-store source,
+  source dates and coverage limits, and why a connected-app read alone does not import a document.
+
+- **`--json` help names a real field**: it said `--json=id,title`, which is refused; Drive results use `name`, so it
+  now says `--json=id,name`.
+
 ## 0.18.0 — 19.10.2026
 
 ### Added

diff --git a/translations/drive/changelog.ru.md b/translations/drive/changelog.ru.md
@@ -4,6 +4,26 @@ title: "История изменений"
 
 Технические сведения о выпусках ниже сохранены на языке исходного проекта. Практические инструкции доступны в переведённых руководствах.
 
+## 0.19.0 — 20.10.2026
+
+### Added
+
+- **The shared store moves to version 25 when first opened** (cli-core 0.366.0): it adds a history of chat
+  changes for the messengers that share it. Nothing is sent.
+
+### Fixed
+
+- **`drive guide` lists memo's `decision-trail` under "Works with"**, the memo scenario whose steps run
+  `drive search`, next to `person-brief`, whose title is now capitalised as in memo and the other tools. Both titles
+  come from cli-core (0.348.0 → 0.370.0), whose scenario check also catches shell characters left outside
+  quotes in a step.
+
+- **Project context with Memo**: the guides now explain selected-folder sync, the shared-store source,
+  source dates and coverage limits, and why a connected-app read alone does not import a document.
+
+- **`--json` help names a real field**: it said `--json=id,title`, which is refused; Drive results use `name`, so it
+  now says `--json=id,name`.
+
 ## 0.18.0 — 19.10.2026
 
 ### Added

diff --git a/translations/drive/commands.es.md b/translations/drive/commands.es.md
@@ -15,7 +15,7 @@ Las opciones se aplican al perfil seleccionado y a esta ejecución.
 |---|---|
 | `-V, --version` | output the version number. |
 | `--profile <name>` | explicit Google account profile (alternative to the first word). |
-| `--json` | print machine-readable JSON; --json=id,title keeps only those fields. |
+| `--json` | print machine-readable JSON; --json=id,name keeps only those fields. |
 | `--jsonl` | print machine-readable JSON lines. |
 | `--quiet` | suppress optional diagnostics. |
 | `--debug` | on failure, show the full error record: cause and stack. |

diff --git a/translations/drive/commands.ru.md b/translations/drive/commands.ru.md
@@ -15,7 +15,7 @@ title: "Команды Drive"
 |---|---|
 | `-V, --version` | output the version number. |
 | `--profile <name>` | explicit Google account profile (alternative to the first word). |
-| `--json` | print machine-readable JSON; --json=id,title keeps only those fields. |
+| `--json` | print machine-readable JSON; --json=id,name keeps only those fields. |
 | `--jsonl` | print machine-readable JSON lines. |
 | `--quiet` | suppress optional diagnostics. |
 | `--debug` | on failure, show the full error record: cause and stack. |

diff --git a/translations/max/bot.en.md b/translations/max/bot.en.md
@@ -316,7 +316,7 @@ max sales bot api answer-on-callback --callback-id f9LHodD0cOL5 --body '{"notifi
 max sales bot api send-message --user-id 4815162342 --body-file message.json
 ```
 
-Path and request parameters are flags, body is JSON in `--body`, `--body -` (from the pipe) or `--body-file`. `--body-file -` also reads stdin. The native parameter `timeout` is called `--poll-timeout`, and the global `--timeout` limits the entire command. The general option `--store-token <profile>` is not available for current MAX methods: they all reject it before performing the operation. Before sending, the body is checked against the schema, and the error message contains the field and what was expected in it, without the value itself. A list of all operations and which ones read and which ones write is [Bot API coverage](https://github.com/WireCatLabs/max-cli/blob/v0.65.0/docs/dev/bot-api-coverage.md).
+Path and request parameters are flags, body is JSON in `--body`, `--body -` (from the pipe) or `--body-file`. `--body-file -` also reads stdin. The native parameter `timeout` is called `--poll-timeout`, and the global `--timeout` limits the entire command. The general option `--store-token <profile>` is not available for current MAX methods: they all reject it before performing the operation. Before sending, the body is checked against the schema, and the error message contains the field and what was expected in it, without the value itself. A list of all operations and which ones read and which ones write is [Bot API coverage](https://github.com/WireCatLabs/max-cli/blob/v0.66.0/docs/dev/bot-api-coverage.md).
 
 <a id="для-скриптов-и-агентов"></a>
 

diff --git a/translations/max/bot.es.md b/translations/max/bot.es.md
@@ -319,7 +319,7 @@ max sales bot api answer-on-callback --callback-id f9LHodD0cOL5 --body '{"notifi
 max sales bot api send-message --user-id 4815162342 --body-file message.json
 ```
 
-Los parámetros de ruta y consulta son opciones; el cuerpo es JSON en `--body`, `--body -` (tubería) o `--body-file`. `--body-file -` también lee stdin. El parámetro nativo `timeout` se llama `--poll-timeout`; el global `--timeout` limita todo el comando. `--store-token <profile>` no está disponible en los métodos MAX actuales: todos lo rechazan antes de ejecutar. Se valida el cuerpo contra el esquema y los errores muestran el campo y lo esperado, sin revelar su valor. Lista de operaciones y clasificación lectura/escritura: [cobertura Bot API](https://github.com/WireCatLabs/max-cli/blob/v0.65.0/docs/dev/bot-api-coverage.md).
+Los parámetros de ruta y consulta son opciones; el cuerpo es JSON en `--body`, `--body -` (tubería) o `--body-file`. `--body-file -` también lee stdin. El parámetro nativo `timeout` se llama `--poll-timeout`; el global `--timeout` limita todo el comando. `--store-token <profile>` no está disponible en los métodos MAX actuales: todos lo rechazan antes de ejecutar. Se valida el cuerpo contra el esquema y los errores muestran el campo y lo esperado, sin revelar su valor. Lista de operaciones y clasificación lectura/escritura: [cobertura Bot API](https://github.com/WireCatLabs/max-cli/blob/v0.66.0/docs/dev/bot-api-coverage.md).
 
 <a id="для-скриптов-и-агентов"></a>