Skip to content

docs(mail): register Mail (@wirecat/mail-cli) on the site - #463

Merged
leemour merged 8 commits into
mainfrom
docs/add-mail-cli
Nov 1, 2026
Merged

leemour merged 8 commits into
mainfrom
docs/add-mail-cli

Conversation

@leemour

@leemour leemour commented Oct 31, 2026

Copy link
Copy Markdown
Collaborator

What

Adds Mail (mail, @wirecat/mail-cli, WireCatLabs/mail-cli) to the docs site in EN, RU and ES. Mail syncs a mailbox over IMAP, read only, into the shared WireCat store so memo and agents can search it offline. It works with Yandex, Gmail, iCloud, Mail.ru, Fastmail and any provider found by server discovery, and has an MCP server. Outlook and Microsoft 365 are not supported yet (OAuth only). It does not send mail.

Changes

  • tools.json entry, docsRef: v0.1.0
  • Sidebar: tool list in meta, meta.ru, meta.es; icon; overview link
  • lib/mail-descriptions.ts and lib/seo.ts
  • translations/mail/: ru and es for index, installation, usage, providers, configuration, troubleshooting, security, commands; fingerprints in translations/sources.json
  • translations/pages/mail/compare.en.md (compares only with Memo, no claims about other projects)
  • Overview title correction in scripts/docs-corrections.json
  • Rows in docs start, installation, features, skills, MCP, configuration and roadmap pages (EN/RU/ES)

Blocked until mail-cli publishes v0.1.0 (do not merge before)

  • pnpm sync reads docs/ from the tag v0.1.0, which does not exist yet.
  • Changelog ru/es translations and docs/release-notes-review.json need the released changelog (today it says "Unreleased"). Not included.
  • pnpm docs:contracts installs the npm package.
  • mail-cli docs/ (index, usage, installation, commands) use a real personal address in examples. Replace it with me@example.com before tagging; the translations here already use me@example.com, so fingerprints match only after that fix.
  • The global roadmaps link ./mail/roadmap.md (a navigation test requires it for every tool), but mail-cli has no docs/roadmap.md or meta entry yet.
  • Landing editorial exports and lib/words.ts are not touched.

Checked

pnpm lint, pnpm ci:quick, pnpm standards:check, pnpm docs:lint, pnpm typecheck pass. pnpm docs:translation check is structure ok for all 16 pages. pnpm sync --tool mail --ref main fails only on the missing changelog translations and the address issue above.

🤖 Generated with Claude Code

leemour and others added 6 commits October 31, 2026 04:53
…ES pages

Add mail-cli to tools.json (docsRef v0.1.0, not tagged yet), the sidebar
(tool list in the three meta files, icon, overview link), reviewed page
descriptions, an English comparison page, Russian and Spanish translations
of seven pages and the command reference with their source fingerprints,
an overview title correction, and rows in the docs start, installation,
features, skills, MCP, configuration and roadmap lists.

The site builds only after mail-cli publishes v0.1.0: sync reads the docs
from that tag, and changelog translations and the release notes review
need the released changelog.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Compare mail with Himalaya, mu, gog, Google Workspace MCP and Microsoft 365 MCP
in 22 task rows grouped by use, with an Agents and safety group, a short Setup
group and a section on where another tool fits better. mail marks come from the
docs and source on 31 October 2026; competitor marks keep their sources.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- translations/mail: RU/ES changelog and roadmap; commands, index, providers,
  security, troubleshooting and usage brought up to the released docs
  (session list, doctor --online, --credential-storage, the keyring file
  fallback, the domain lookups); fingerprints accepted.
- docs/release-notes-review.json: mail v0.1.0, roadmap fingerprint from the
  released roadmap (--wcat-describe is no longer in Later).
- compare page: marks checked against the first release.
- docs-quality: memo's own `mail delete|restore|inspect` are not mail commands.

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

- compare: search rows are ❌ with "memo does this"; the keyring row is 🟡 with the
  private-file fallback; four "fits better" scenarios; footnote and read-only
  note say memo mail delete moves Gmail mail to Trash.
- tools.json and mail descriptions name memo as the search.
- docs/tasks.json maps every mail command group.
- ru: Яндекс everywhere, "связка ключей" for the keyring, "хранилище" for the
  store, no "в запросе" for a prompt; es: "terminal" is feminine.
- scripts/docs-quality.ts: the memo skip is reverted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
leemour and others added 2 commits November 1, 2026 01:21
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pin mail to v0.1.1 and memo to v0.131.2, re-sync the source, and carry the
changes into the Russian and Spanish pages. Record the roadmap reviews for
both releases. Merge origin/main.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour merged commit 767f46d into main Nov 1, 2026
2 checks passed
leemour added a commit that referenced this pull request Nov 1, 2026
…#473)

Deploy run 41257419609 (#463) failed in browser shards 1 and 2; nothing
was published.

- Shard 2: the remote Memo guide test looked for `memo mcp --revoke
--json` and `memo mcp --http`. Memo 0.131.2 documents `memo mcp revoke
--json` and `memo mcp serve --http`. The test now follows the docs.
- Shard 1: the tg command reference entry has 3002 elements (en, ru, es)
since the mail pages joined the sidebar, against a ceiling of 3000. The
ceiling only separates the small entry page from the full reference, so
it moves to 3500, as in #354.

I could not run the two specs locally (the dev server did not start
within the 60 s limit); the deploy run is the check.

🤖 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