Tier 3: implement bot self-configuration methods (setMyName/Description/ShortDescription, default admin rights)

[windkh]

Tier 3 — Bot profile / self-configuration methods (low effort, one-time value)

From the V18 coverage analysis (#453). "Configure my bot from a flow" conveniences. Low individual value but cheap to add as a bundle, and none fit the passthrough (no chatId), so they need explicit handling.

Method(s)	Bot API	Purpose
setMyName, getMyName	6.7	Bot display name.
setMyDescription, getMyDescription	6.6	"What can this bot do?" description.
setMyShortDescription, getMyShortDescription	6.6	Profile-page short description.
setMyDefaultAdministratorRights, getMyDefaultAdministratorRights	6.0	Default admin rights requested when added to groups/channels.

Note

Best bundled with setMyCommands (Tier 1, #459) since they share the "no chatId, bot-level config" shape.

Related: #453, #448.

[windkh]

On hold pending #501 — do not implement this against the v1 API surface.

node-telegram-bot-api@2.0.0 is released and describes itself as "a from-scratch redesign with no backward compatibility" with the v1 TelegramBot surface. Among other things it replaces positional arguments with params objects under a uniform bot.api.* namespace, and covers Bot API 10.2 natively.

This issue was written on 2026-06-17 against v1. Two things about it are now uncertain:

• Whether the work is still needed. Methods listed here may already be reachable through v2's bot.api.* surface, in which case the remaining work is exposing them in the nodes, not implementing them.
• Whether the tiering still holds. v2 changes the effort profile, so the split across Tier 1–4 may need re-cutting rather than the tiers being worked in order.

Anything implemented against v1 in the meantime would very likely be thrown away in the port.

Action: this issue is re-checked as part of #501, after the breaking-change analysis it requires. It stays open until then — no assumption either way. Kept as-is on purpose: it records what users asked for, and that need survives the library change even if the implementation does not.