0.76.0

Changed — may break callers

• Without a terminal, the login QR code is printed as text for an agent to paste into the chat; --qr-file is
  gone. An agent wrote a PNG and opened it in an image viewer, a window you can lose. Now tg <profile> session start qr and setup print the code on stderr as plain text (half blocks, no colours, drawn for a dark terminal
  theme), then tell the agent to paste it as a code block, exactly as printed, and to paste a renewed one and say the
  old one expired. With --json each code is also one stderr line,
  {"event":"qr","qr":{"text","expires_at","scan"}}. In a terminal the code is drawn as before. --qr-file is
  removed from session start and setup. Without a terminal a login still needs stored app keys and no 2FA, and
  is refused before it opens a browser; a phone login needs a terminal. Login stays off MCP: run the command
  (when an agent runs the login).

Added

• store clear --left names the chats it deletes (cli-core 0.353.0): the refusal without --allow-dangerous
  lists the first 20, --dry-run lists them all, and the answer carries a left list (id, title, messages).

Fixed

• From cli-core 0.351.0–0.362.0: chats leave and chats join update the store, and chats show finds a chat
  you left; a sent message is saved in the chat Telegram answered; a re-keyed chat keeps the stricter privacy of its
  two halves; a chat hidden from search stays out of every search that does not name it; a failed scheduled run's
  last.json keeps an error code, never a chat title; the first serve after an upgrade re-keys chats in short
  passes instead of locking the store.
• messages forward answers, and saves, the forwarded copy in the chat it went to. It took the first new message
  in Telegram's answer, which can belong to another chat; now it takes the one its send id names, in the target chat.
  Creating a forum topic reads its first message the same way.