Skip to content

docs: Documents & files section with Google Drive, Notion, Yandex Disk and Markdown (EN/RU/ES) - #668

Merged
leemour merged 5 commits into
mainfrom
docs/documents-files
Nov 17, 2026
Merged

leemour merged 5 commits into
mainfrom
docs/documents-files

Conversation

@leemour

@leemour leemour commented Nov 17, 2026 •

Copy link
Copy Markdown
Member

What

A new sidebar group, Documents & files, under "Connect a source", in EN/RU/ES. It holds:

  • Google Drive, with a new portal start page (translations/overviews/drive.*.md), as Notion already has.
  • Notion, unchanged (its portal start page already follows the same order).
  • Markdown and Obsidian (content/docs/markdown*.mdx), a new site-owned page. There is no Markdown tool: memo
    reads folders of notes, so the page works like the Google Meet page does for gcal.

The group is built like Meetings & Calls and CRM (toolGroups in lib/docs-sidebar-tree.tsx, labels in
lib/words.ts). URLs do not change.

Page order

Each new page opens with what the reader gets, then what the agent can do for them, then "On this page", then the
ideas a newcomer needs (Markdown folder or Obsidian vault; profile and local copy), then the rest.

Sources

  • Markdown: cli-memo v0.135.0 (pinned in tools.json), docs/notes.md, docs/commands.md, docs/installation.md.
  • Google Drive: drive-cli v0.65.0, docs/index.md, docs/installation.md, docs/usage.md, docs/commands.md.
  • No placeholders in runnable commands: the example folder ~/Notes and the example Drive folder link are labelled.

Merged from #669

  • Yandex Disk (content/docs/ydisk*.mdx): a site page before ydisk's first release (the owner allows unreleased
    tools). A "Coming soon" lead-in says the npm package is not out yet. Commands checked against ydisk-cli main.
  • Notion: a "How it works" section after the contents list.

Checks run locally

pnpm lint, search:check, sync, docs:release-notes, test (525 passed), docs:contracts, docs:check,
typecheck, cspell on the new pages. next build cannot run on this machine: it hits an 11 GB cap on main too.

Why CI adds swap before next build

next build hung at random in CI: 4 of 9 builds on this branch, and it can hit main too. I ran it in a systemd
cgroup that reports its memory peak, on the same ubuntu-latest runner (4 CPUs, 16 GB RAM):

Run Result
main, swap allowed passed, 14.3 to 14.4 GB RAM plus 2.1 to 2.9 GB swap
this branch, swap allowed passed once at 14.2 GB plus 1.4 GB swap; killed once on a runner with no swap (14.6 GB)
main and this branch, no swap, 13 GB cap 8 of 8 killed at 13 GB during compile
turbopackPluginRuntimeStrategy: "workerThreads", no swap 2 of 2 killed at 14.8 GB
8 GB swap file 2 of 2 passed in about 3.7 minutes

So the build needs about 17 GB, more than the runner has. Some runners have 3 GB of swap and some have none. With
none, the machine stalls instead of failing, which is the hang. This branch's few extra pages do not change the peak
in a way the runs can tell apart from main. The check, search-playground and Deploy build jobs now add an 8 GB
swap file before next build.

Notion's start page also lists writing to Notion now. 0.3.0 to 0.5.0 added it, and the old list still said it had no write
commands.

🤖 Generated with Claude Code

@leemour leemour changed the title docs: Documents & files section with Google Drive, Notion and Markdown (EN/RU/ES) docs: Documents & files section with Google Drive, Notion, Yandex Disk and Markdown (EN/RU/ES) Nov 17, 2026
@leemour

leemour commented Nov 17, 2026

Copy link
Copy Markdown
Member Author

Heads-up from the ydisk session: #670 is merged. It groups Telegram, MAX and WhatsApp under Messengers, renames Memo to Notes (Memo) in the menu, lists Beeline only in the Russian menu, and removes the Phone calls page (content/docs/voip*.mdx, voip in meta*.json and in toolGroups.meetingsCalls). This branch still has voip in content/docs/meta.json and lib/docs-sidebar-tree.tsx, so the rebase needs to drop it there. #673 (service logos) will also touch lib/docs-sidebar-tree.tsx.

leemour added a commit that referenced this pull request Nov 17, 2026
…bar, tools in two columns (#673)

Services on the site now show their own logos instead of monochrome line
icons.

**Where**
- Landing page (EN/RU/ES): the source row under the hero, the "What you
can use today" table, and the setup picker on home, features and
examples.
- Docs sidebar: tool folders (Telegram, MAX, WhatsApp, Google Drive,
Google Calendar, Notion, Zoom, Bitrix24) and the Google Meet, Telemost
and Beeline pages. `markdown` and `ydisk` are mapped too, for the
Documents & files pages in #668.

**Logos**: files in `public/logos/`, shown as `<img alt="">` next to the
visible name. Each is recorded in `design/logos/SOURCES.md` (source,
licence, how drawn). New: Google Meet (Google's product-logo set),
Markdown (Simple Icons, CC0), Yandex Telemost and Beeline (their sites'
icons), Yandex Disk (App Store icon). Notion, Zoom, Bitrix24, MAX and
amoCRM come from WireCat Desktop.

**Kept generic**: Telegram is a paper plane on a blue disc, as in
Desktop, because its API terms forbid its logo in another product.
Email, Asterisk and Memo keep their line icons.

**Layout**: in "What you can use today", the WireCat Desktop card now
sits beside the heading. The tool list spans the full width in two
columns. Under 900 px the card goes under the intro, and under 760 px
the list becomes one column.

Checked in a dev server: all three languages, light and dark, at 1400 px
and 390 px. No broken images, no page errors, no horizontal overflow,
and the picker still copies the chosen logo.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
leemour added a commit that referenced this pull request Nov 17, 2026
… mail in EN/RU/ES (#672)

Readers of the tg, max, wa, zm and mail overviews could not see what the
tool gives them: the pages opened with setup and a guide table. Each
overview is now a benefit-first page in EN, RU and ES, following the
overview template from the docs-marketing plan (cli-private
`plans/2026-11-17-docs-marketing/overview-template.md`).

## What changed per tool

Every page now has: an opening that names the reader's gain, a numbered
"On this page", **What you get** (gains with a fact each), **Things a
newcomer would not guess**, a You/Agent example, **Why <tool>** with
facts from the comparison page plus a link to it and one "fits better"
line, what it can do by task, **How it works**, a start, **Limits** and
a task-to-guide table.

- **tg:** gains (replies you owe, offline search with word forms and
meaning, promises, voice without Premium, group rules, auto-replies, 185
Bot API methods). Proof: no WireCat server, official API with your own
app, the three search rows no other tool on the comparison documents,
keyring. Limits: meaning search needs a 219 MB model, call history,
privacy settings and stickers not yet in tg.
- **max:** Russian page written first. Gains include moderation by rules
(marks by default) and the Bot API. Proof: the compare rows only max has
(unread in all chats, owe/owed, meaning and offline search, local voice,
morning digest, agent limits). Limits state the internal API and the MAX
user agreement risk once, plainly, with a link to security (answers the
search-intent question "is automating a personal account allowed").
- **wa:** was 16 lines of links. Now a full page. Proof: the "hold every
send when WhatsApp says slow down" row only wa has. Keeps the `wa/bot`
and `wa/permissions` links the browser test needs. `server install` +
`server start` named correctly (install alone starts nothing, macOS and
Linux only).
- **zm:** sidebar label loses its long dash ("Zoom: start here").
Example ends with a previewed `remote-meetings update` the user
approves. Quick start no longer has the `<public-client-id>` placeholder
(WC-DOC-12): it installs, then links First run.
- **mail:** gain moves to the first sentence, the page-about-the-page
opening goes, providers table moves under "What it can do", "Why mail"
adds the two rows only mail has (one store with chats, undo). "Every
change can be undone" narrowed to moves and deletions, with a Limits
line on deleted drafts and Gmail's 30-day Trash. `session start` runs
without `--address` (it asks at a terminal).
- **Docs start page:** the mail row no longer says "(read only)" in EN,
RU, ES.
- **`tests/zoom-docs.spec.ts`:** follows the new Zoom H1.

## Titles (`lib/seo-copy.json` → `toolTitles`, the HTML H1 and
`<title>`)

| Tool | Lang | Before | After |
|---|---|---|---|
| tg | en | Telegram CLI client for AI agents | Telegram MCP server and
CLI for your own account |
| tg | ru | CLI-клиент Telegram для ИИ-агентов | Telegram MCP-сервер и
CLI для личного аккаунта |
| tg | es | Cliente CLI de Telegram para agentes de IA | Servidor MCP y
CLI de Telegram para tu cuenta |
| max | en | MAX CLI for AI agents and bots | MAX messenger MCP server,
CLI and Bot API |
| max | ru | MAX CLI для ИИ-агентов и ботов | MCP-сервер и CLI для
мессенджера MAX |
| max | es | CLI de MAX para agentes de IA y bots | Servidor MCP y CLI
de MAX Messenger |
| wa | en | WhatsApp CLI for your AI agent and business bots | WhatsApp
MCP server and CLI for your personal account |
| wa | ru | WhatsApp CLI для ИИ-агентов и бизнес-ботов | WhatsApp
MCP-сервер и CLI для личного аккаунта |
| wa | es | CLI de WhatsApp para tu agente de IA y bots de empresa |
Servidor MCP y CLI de WhatsApp para tu cuenta |
| zm | en | Connect Zoom transcripts and recordings to your AI agent |
Zoom transcripts MCP server and CLI |
| zm | ru | Подключите расшифровки и записи Zoom к ИИ-агенту |
MCP-сервер и CLI для расшифровок Zoom |
| zm | es | Conecta las transcripciones y grabaciones de Zoom a tu
agente de IA | Servidor MCP y CLI para transcripciones de Zoom |
| mail | en | Connect your mail to your AI agent over IMAP | IMAP mail
MCP server and CLI with offline search |
| mail | ru | Подключите почту к ИИ-агенту по IMAP | MCP-сервер почты по
IMAP с поиском без интернета |
| mail | es | Conecta tu correo a tu agente de IA por IMAP | Servidor
MCP de correo IMAP con búsqueda sin conexión |

Titles are the SEO set from cli-private `seo-keywords.md`. Meta
descriptions (frontmatter) are new: a gain plus a fact, different from
the opening.

## Reviewer checklist (template's 11 points), per page

Checked on each page in EN, RU and ES.

| # | Check | tg | max | wa | zm | mail |
|---|---|---|---|---|---|---|
| 1 | A newcomer can say what they get from the first screen | ✅ | ✅ | ✅
| ✅ | ✅ |
| 2 | First sentence names a gain, reader or agent as subject | ✅ | ✅ |
✅ | ✅ | ✅ |
| 3 | "What you get", 5 to 7 gains, no command in bold | ✅ 7 | ✅ 6 | ✅ 6
| ✅ 6 | ✅ 6 |
| 4 | You/Agent example with a source and an approved write | ✅ | ✅ | ✅
| ✅ | 🟡 the draft is asked for and saved, nothing is sent, no separate
yes |
| 5 | Fact against a named rival, comparison link, fits-better line | ✅
| ✅ | ✅ | ✅ | ✅ |
| 6 | Nothing technical before "What you get" | ✅ | ✅ | ✅ | ✅ | ✅ |
| 7 | Title, description and opening are three different sentences | ✅ |
✅ | ✅ | ✅ | ✅ |
| 8 | Claims true at the `docsRef` pin | ✅ | ✅ | ✅ | ✅ | 🟡 two facts
from main (below) |
| 9 | Ends with a next step (guide table) | ✅ | ✅ | ✅ | ✅ | ✅ |
| 10 | VOICE: no `;`, long dashes, `ё`, guillemets, hype words | ✅ | ✅ |
✅ | ✅ | ✅ |
| 11 | `docs:opening` passes (run on the files by name, since it only
scans `content/docs`) | ✅ | ✅ | ✅ | ✅ | ✅ |

**Claims dropped or narrowed as unverifiable at the pin:** "search
forgives typos" (max), "every change can be undone" (mail), "speakers
stay unknown" and "needs ffmpeg" (zm), "some of it is not checked
against real WhatsApp" (wa, also editorial history per AUTHORING), "only
to the people you choose" for tg auto-replies (narrowed: replies go to
everyone a rule matches unless you limit the audience). **From mail-cli
main, not the pin (4 commits apart):** the first sync reads 30 days by
default (`src/commands/sync.ts`), Gmail empties Trash after 30 days.

## Checks run locally

`pnpm lint`, `pnpm search:check`, `pnpm docs:release-notes`, `pnpm
docs:contracts`, `pnpm docs:check`, `pnpm check:links --source`, `pnpm
test` (515 passed), `pnpm typecheck`, `docs:opening` on the 15 overview
files by name. `pnpm docs:spell` fails on main already (55 issues in
other files, none in changed files) and is not in CI. `next build` was
not run locally (memory cap on this machine); the Full validation
workflow is dispatched on this branch for the build, links, SEO and
browser tests.

Not touched: drive, notion and Documents & files (#668, #669), and b24,
gcal, memo, pbx.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour force-pushed the docs/documents-files branch from a82018e to 98e14ba Compare November 17, 2026 15:58
leemour added a commit that referenced this pull request Nov 17, 2026
…ywords in EN, RU and ES (#675)

Search engines and AI answer engines read a page's `<title>`, H1 and
description first. Ours hid the phrase people type: tool pages said
"Connect Bitrix24 CRM to your AI agent" instead of "Bitrix24 MCP
server", subpages put a generic word first with a long dash ("The MCP
server — Telegram", "Install — Notion"), and the Notion landing was just
"Notion". This PR puts the product and "MCP server" or "CLI" first in
EN, RU and ES.

## Approach

- **Tool landings** (`toolTitles` in `lib/seo-copy.json`): the keyword
set from the docs-marketing plan for all 11 tools, Notion added. tg,
max, wa, zm and mail keep the titles #672 merged.
- **Tool subpages:** new `pageTitles` templates per locale, with
per-tool overrides, used by `documentationTitle` in `lib/seo.ts` for
both the H1 and `<title>`. For example "Install the Notion CLI and MCP
server", "Telegram MCP server setup for Claude Code, Codex and Cursor",
"Download and export Telegram chat history". Pages without a template
read "Telegram: People", with no long dash.
- **Descriptions:** new `pageDescriptions` (140 to 160 characters,
keyword once) for the memo, b24, pbx and gcal overviews and every MCP
page. They are checked before the synced frontmatter.
- **Site pages:** keyword titles such as "Connect your AI agent to your
chats, mail and documents" (was "Start here"). The old short name stays
as `sidebarTitle`, so the menu does not change. The 9 pages that
`docs:opening` now re-checks got their "On this page" lists and wording
fixes.
- **Markdown copies** (`/llms.mdx/...`) carry the same title as the HTML
page.
- All 805 page titles stay unique per language. Browser specs follow the
new H1s.

Query choices were checked against Google autocomplete in each language:
"telegram mcp server", "mcp telegram claude code", "export telegram chat
history", "google drive mcp", "notion mcp", "bitrix24 mcp" / "битрикс24
mcp", "obsidian mcp", "exportar chat de telegram".

### Examples

| Page | Before | After |
|---|---|---|
| en `tg/mcp` | The MCP server — Telegram | Telegram MCP server setup
for Claude Code, Codex and Cursor |
| en `notion/installation` | Install — Notion | Install the Notion CLI
and MCP server |
| ru `b24` | Подключите CRM Bitrix24 к ИИ-агенту | Битрикс24 MCP-сервер
и CLI для CRM |
| ru `tg/search` | Поиск — Telegram | Поиск сообщений и переписки в
Telegram |
| es `notion` | Notion | Servidor MCP y CLI de Notion con búsqueda sin
conexión |
| es `drive/installation` | Instalar y conectar — Google Drive | Instala
la CLI y el servidor MCP de Google Drive |

## Left out

- **Overview descriptions for tg, max, wa, zm, mail, drive and notion:**
written in #672 and the documents PR #668. Not overridden here.
- **Home page title** (`homeTitle`): unchanged. Proposal: lead with
"Local MCP servers for your AI agent" and drop the long dash.
- **voip, beeline:** handled by #670.
- **Compare pages:** a generic "<Product> MCP servers and CLIs compared"
for now. Titles naming rivals need each page read.
- **Contributor pages** (architecture, testing, build-*), except "Create
your CLI": low search value.
- **Proposed titles, not applied:**

| Page | EN | RU | ES |
|---|---|---|---|
| `markdown` (#668) | Obsidian and Markdown notes MCP server for AI
agents | MCP-сервер для заметок Obsidian и Markdown | Servidor MCP para
notas de Obsidian y Markdown |
| `ydisk` (#668) | Yandex Disk MCP server: search your files with AI |
MCP-сервер Яндекс Диска: поиск по файлам для ИИ-агента | Servidor MCP de
Yandex Disk para tu agente de IA |
| `people` | People in your Telegram and MAX chats | Люди в ваших чатах
Telegram и MAX | Personas en tus chats de Telegram y MAX |
| `tasks` | Tasks and promises from your chats | Задачи и обещания из
ваших чатов | Tareas y promesas de tus chats |
| `first-tasks` | First tasks to ask your AI agent | Первые задачи для
ИИ-агента | Primeras tareas para tu agente de IA |

people, tasks and first-tasks were left as they are because a retitle
makes `docs:opening` check the whole page, and these need a contents
list and wording fixes first.

## Checks

Local: `pnpm lint`, `pnpm typecheck`, `pnpm exec vitest run scripts lib`
(520 passed), `pnpm docs:check`, `pnpm check:links --source`. `next
build` was not run locally (memory limit on this machine). The browser
specs did not run locally because the dev server would not start, so CI
runs them.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
leemour and others added 5 commits November 17, 2026 18:39
…n (EN/RU/ES)

The sidebar gets a "Documents & files" group under "Connect a source", built the same way
as "Meetings & Calls" and "CRM" (toolGroups in lib/docs-sidebar-tree.tsx, labels in
lib/words.ts for EN/RU/ES). It holds Google Drive, Notion and a new Markdown page. No URL
changes, so no redirect stubs.

- markdown.mdx (EN/RU/ES): a site-owned page for Markdown folders and Obsidian vaults. There
  is no separate Markdown tool: memo reads folders of notes, so the page follows the Google
  Meet page's shape (benefit, what the agent tells you, "On this page", short version, then
  the rest). Every command and limit is from cli-memo v0.135.0, the release pinned in
  tools.json (docs/notes.md and docs/commands.md there). Example paths are a labelled
  ~/Notes, not placeholders (WC-DOC-12).
- Google Drive gets a portal start page (translations/overviews/drive.*.md), as Notion
  already has. It opens with what the reader gets, a table of contents and the two ideas a
  newcomer needs (profile, local copy), then the connection steps and the reference tables.
  Facts are from drive-cli v0.65.0 (docs/index.md, installation.md, usage.md, commands.md).
- Inbound links from the start page ("Which tool do I need") and the installation page.
- A navigation test pins the group, its order and its labels.

Yandex Disk is left out: ydisk has no release yet (package version 0.0.0, not on npm), so
the install a page would give does not work. It joins the group with its first release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…es (EN/RU/ES)

Brings in the Yandex Disk page and the Notion start page's "How it works" section from
PR #669, so the Documents & files section ships as one PR.

- ydisk.mdx (EN/RU/ES): a site page for Yandex Disk, before ydisk's first release. The owner
  decided that unreleased tools may be documented. A "Coming soon" lead-in, as agents.mdx
  uses for planned work, says the npm package is not out yet; the install command stays as
  it will work after the release. Commands and options checked against ydisk-cli main
  (552e53d, docs/commands.md and src/commands/files.ts).
- Yandex Disk joins the sidebar group (between Notion and Markdown), meta.json in every
  language, the start page's "Which tool do I need" table and the docs index.
- Notion's start page gets "How it works" right after its contents list: the copy, the
  token, the profile, the sync and the agent.
- cspell words from #669, and the navigation test covers the new page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…folder browsing

tests/drive-docs.spec.ts expects the Drive start page to say where the copy lives (SQLite)
and to link the offline folder browsing section of the usage guide. The released start page
did both; the new portal start page now does too, in EN/RU/ES. Full validation failed on
these three checks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…0.5.0 added

The "What it does not do yet" list said notion had no ready write commands. Since 0.3.0 it
creates, changes, deletes and restores pages, and since 0.4.0 it reads and writes comments
and uploads files (notion-cli v0.5.0 docs/commands.md and docs/configuration.md). The page
now lists writing under "What you get" in EN/RU/ES, with the read-only switch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…the runner has

next build hung in CI at random (4 of 9 builds on this branch, and it can hit main too).
Measured on ubuntu-latest (16 GB RAM) by running the build in a systemd cgroup that reports
its memory peak:

- main: 14.4 GB of RAM plus 2.1 to 2.9 GB of swap, about 17 GB in all.
- this branch: 14.2 GB plus 1.4 GB of swap; with no swap allowed, both main and this
  branch are killed at 13 GB and at 15.5 GB.
- some runners have 3 GB of swap and some have none. With none, the build cannot fit,
  and the machine stalls instead of failing (a watchdog in the same job stopped running).
- the extra pages here add about 1% of the content; they do not change the peak in a
  way the measurement can tell apart from main.
- turbopackPluginRuntimeStrategy: "workerThreads" did not help (14.8 GB, then killed).
- an 8 GB swap file: 2 of 2 builds passed in 3.7 minutes (peak 14.2 to 14.3 GB plus 2 to
  3.1 GB of swap).

So the check, search-playground and Deploy build jobs add the swap file before next build.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour force-pushed the docs/documents-files branch from 98e14ba to 714cfe5 Compare November 17, 2026 17:47
@leemour
leemour merged commit a523227 into main Nov 17, 2026
8 checks passed
@leemour
leemour deleted the docs/documents-files branch November 17, 2026 18:01
leemour added a commit that referenced this pull request Nov 17, 2026
…dits until a fix ships (#678)

## Task
Unblock deploys. Every Deploy run since 17:40 UTC (44139609605,
44143423852, 44148152583) failed in `security / dependencies` and
`security / resolved-dependencies` on picomatch
[GHSA-fc5q-39xc-vjpf](GHSA-fc5q-39xc-vjpf)
(ReDoS through attacker-written extglob patterns). No fixed version
exists: every picomatch up to 4.0.7, the latest, is affected. #675,
#676, #668 and #677 are merged but not live.

## Why it is safe to skip
- Chain (`pnpm why picomatch --prod`): `picomatch@4.0.7` ← `fdir@6.5.0`
← `tinyglobby@0.2.17` ← `fumadocs-core@16.17.8` / `fumadocs-mdx@15.4.10`
← cli-docs. fumadocs uses it to find content files at build time, with
the site's own patterns.
- The site is a static export (`output: "export"`), and visitors do not
download picomatch. The 16:50 deploy (7b75117) has the same lockfile,
package.json, pnpm-workspace.yaml and next.config.mjs as main. In its 39
JS chunks (12 pages, with runtime chunk references followed),
picomatch's error strings, `POSIX_REGEX_SOURCE`, `picomatch`,
`tinyglobby` and `fdir` occur 0 times. The same strings are found in the
picomatch package itself, and fumadocs' own client code is in 4 of those
chunks.

## What
- `pnpm-workspace.yaml`: `audit.ignore` lists only this advisory, with
why and "remove when picomatch ships a fix".
- `.github/workflows/audit.yml` (new): the two dependency audits of
cli-base's `release-checks.yml`. The npm audit of the packed site is
filtered with jq to skip only this advisory, and fails on any other high
or critical one or on a missing report. npm has no per-advisory ignore,
and the shared workflow has no ignore input in any version up to main.
- `deploy.yml`, `monthly.yml`, `security-release.yml`: the shared check
runs with `dependencies: false`, and `audit.yml` runs beside it (in
deploy, `build` waits for it). In `security-release.yml`,
`security-events: write` moves from the workflow onto the shared job, so
the new job stays read-only.
- `docs/dev/BACKLOG_LATER.md`: DOCS-14 removes all of this once
picomatch is fixed or `release-checks.yml` takes an ignore input.

## Testing
- `pnpm audit --prod --audit-level high`: exit 0 ("1 ignored: 1 high", 2
moderate below the gate).
- The shared npm step replayed locally on the packed site: 8
vulnerabilities (7 high), and every high one is this advisory. The jq
filter passes on that report. It fails on the same report with Next's
GHSA-mfr8-8qww-v76h raised to high, and on an error report.
- zizmor: no medium or high findings in `.github/workflows`. `pnpm
lint`, `standards:check`, markdownlint, vitest (49 files, 525 tests).
- A local production build was killed for lack of memory twice (the
deploy notes it needs about 8 GB of swap), so the export check used the
identical live deploy.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant