[leemour]

Task

Prepare max 0.111.0: #953 (cli-core 0.638.0 → 0.641.0) and #954 (keyring hint, cli-core 0.641.0 → 0.642.0).

Do not merge yet. The live check of messages sync --all waits for the owner, and the changelog waits for his yes.

Why

• The headline fix is progress after every page in messages sync --all: WireCat Desktop showed «Чат 1 из 36 · 0»
  for minutes. Each progress line is now also a sync.progress event in runs show.
• A daily or one-off schedule that gets rate_limited waits up to 6 h and runs once more.
• 0.111.0, a minor: the section has entries under «Изменено — может сломать скрипты». npm's latest is 0.110.0.

What

• package.json and src/version.ts at 0.111.0.
• CHANGELOG.md: ## 0.111.0 — 12.11.2026, the changes/ fragments collected as bin/release does, the two
  cli-core lines merged into one (0.638.0 → 0.642.0; the store stays at version 66). Completed from cli-core
  0.640.0–0.642.0 with what a max command shows: name patterns and more candidates, *part* limits, a word's start
  in transcripts and file text, plain http refused for remote embeddings, list: refused, test people hidden.
• The schedule entry now says daily and one-off only. Dropped the voice-order sentence: max has no MAX speech service,
  it always transcribes on this computer.
• docs/troubleshooting.md: a token that does not read is first a keyring locked after boot, as the error says now.
• docs/commands.md regenerated with no change.

Testing

• pnpm release:check on this branch: all 15 checks ok (exit 0), started 2026-11-11T23:00:10Z at ce5db99. A first run at 58ad42d failed only tree unchanged — the docs fix made while it ran.
• Live, waiting for the owner (read-only, default profile, the release build through bin/max):
  1. bin/max default messages sync --all --since-time 2d --no-catch-up --json (ends by itself). On stderr, a
     {"event":"progress","step":"sync",...} line after every page, 5–10 s apart, with fetched growing inside a chat
     before chats_done moves on.
  2. bin/max default runs list --limit 10 --json: take the sync run's run_id.
  3. bin/max default runs show <run_id> --json: sync.progress events with counts.
• smoke:live not needed: no write path changed. The release report in cli-private has the proposed one-word script.

🤖 Generated with Claude Code