fix(cli): mark commands that change only this computer as local writes

[leemour]

Task

tg-cli's command page says "Changes something in Telegram" under commands that change only local files. (max-cli builds its own versions of these commands and never showed the label; it gets its own fix.)

Why

mutates: true was on commands that write to the messenger and on ones that write only the config file, the group-rules file, the recipient lists or the keyring.

What

Every mutates: true in src/ classified. These 12 change only this computer and now carry local: true (cli-core 0.15.0, leemour/cli-core#37):

• config set, config unset — the config file
• chats rules set, chats rules unset — the group-rules file (src/moderation/rules.ts)
• recipients add|remove|clear — the recipient list file (add reads the messenger to resolve the chat, changes nothing there)
• bot auth set|remove — the keyring (auth set checks the token with the messenger, a read)
• bot recipients add|remove|clear — the bot's recipient list

Every other one stays a messenger write, including chats moderate (deletes messages, removes people).

mutates stays on all of them, so commands --json keeps writes: yes. cli-core devDependency 0.15.0; peer range widened to <0.16.0 (an older cli-core ignores local and shows the old line).

Decision: a second annotation (local) instead of dropping mutates — agents read writes to tell reads from writes, and a local write is still a write.

Not released: under ## Unreleased, per the one-release-a-day rule (0.97.0 shipped today).

Testing

pnpm lint && pnpm typecheck && pnpm test && pnpm docs:check — all pass. Checked against tg-cli with a local build of this branch: pnpm generate swaps exactly these 12 labels to "Changes something on this computer only."; chats moderate and session end keep the Telegram line; commands --json shows all 12 with mutates: true; pnpm parity:check passes.

🤖 Generated with Claude Code