/help <command> — per-command detailed help

[amayer1983]

Requested by @famewolf in #2:

"/help could be used to get more specific parameter usage if you don't want all this in the general /help command."

Current behaviour

/help lists every command on a single message — good as overview, sparse on per-command details (parameters, examples).

Proposed

/help <command> — return a detailed help block for that one command, including:

• Synopsis (/cleanup — no args)
• What it does
• Parameters with type / accepted values
• Examples (≤ 3)
• Side effects (e.g. "rate-limited to 1 per minute", "writes to update_history.json")

Helps power users discover capabilities without scrolling through the README.

Implementation sketch

i18n-heavy: each command needs a per-command help block in 16 languages. Easiest: just write EN + DE, the fallback layer handles the rest like with every other i18n key.

/help cleanup

*/cleanup* — Remove unused Docker images

Removes images older than CLEANUP_GRACE_HOURS (default 24h) that no
running container references. Optionally backs up locally-built images
as tarballs first if CLEANUP_BACKUP_LOCAL_ONLY is set.

Side effects:
• Writes a notification to all configured channels
• Frees disk; check disk usage before/after with /status

Open questions

• Fuzzy match on the command? /help statu → /status? Probably not for v1 — exact match keeps it predictable.
• Wrong arg: /help nope → "no such command — try /help for the list" or list all? Probably the former.

Target

v1.18.0 alongside other small UX polish.

[amayer1983]

Update on the design — while building command-discovery for v1.18.2 I went with a different approach and want to capture the reasoning here.

Shipped in v1.18.2:

• All 19 commands registered with Telegram via setMyCommands on startup. Users get the native / autocomplete picker with one-line descriptions — the industry-standard Telegram bot UX.
• One-line tip at the top of /help points users at the / picker. Docs-link footer points at the README.

My take on /help <command>:

I think the native picker plus the README link probably makes /help <command> unnecessary in practice:

• Users who forgot a command name type / → picker shows everything with descriptions
• Users wanting deep details go to the README / docs
• The implementation cost (per-command help prose × 16 languages × 19 commands ≈ ~300 i18n strings to write and maintain) is high relative to the actual usage I'd expect

But — I'm leaving this issue open rather than closing as "won't fix".

If real usage shows the /-picker isn't enough — you find yourself wishing for paragraph-level help inside the chat rather than just a one-liner — drop a comment here and we'll revisit. Concrete examples ("I wanted to know what /maintenance accepts as arguments and the picker only said Pause auto-updates") are gold for deciding whether this is worth the effort.

Pull v1.18.2, give the picker a few days of actual use, and tell me whether it works for you.