Command descriptions in the command registry are hardcoded English and do not follow the browser locale

[MoTingFeng]

Summary

The slash-command menu (e.g. /compact, /goal, /plan, /export, /permission, /feedback, /model) shows descriptions registered on the host side, which are hardcoded English strings. Everything else in the command UI is localized through dsh-client-locale (the t() seat). There is no clean path for a non-English user to localize these descriptions without patching node_modules or shadow-registering duplicate commands in an agent preset.

Evidence

1. The official README acknowledges the gap. packages/client/locale/README.md, under "Known Limitations": "Registry-held text reads its translation once — copy captured at registration time outside the slot render path (e.g. the /model command description in the command registry) keeps the language it was registered under until re-registration; slot-rendered copy follows switches live."

2. The command popup localizes everything except the descriptions. In packages/client/ui-commands (built dsh-client-ui-commands/lib/client.js), the popup renders t("overlay.aria"), t("search.placeholder"), t("retry"), t("status.*") (L947-991), while descriptions come verbatim from remote.commands.list(sessionId) (L511).

3. Host command packages hardcode English descriptions, e.g.:

   • packages/goal/command-goal/src/index.ts: 'set or view the goal for a long-running task'
   • packages/compaction/command-compact/src/index.ts: 'Compact older conversation history'
   • dsh-plan-mode, dsh-permission-presets, dsh-command-feedback, dsh-session-log-export: same hardcoded pattern.

4. The official e2e golden snapshot expects exactly this: apps/web/tests/snapshots/lifecycle-chrome/command-menu.expected.md lists all seven entries with English descriptions — compact Compact older conversation history, goal set or view the goal for a long-running task, plan Enter or leave plan mode, permission Switch the permission preset (sandbox mode + approval policy), feedback record feedback about this session, export Download this Session log as a ZIP archive, model Select the model for this conversation.

Proposal

1. Allow description (and optionally input.hint) in ctx.commands.register(...) to be either a string (backwards compatible) or a per-locale object, e.g. { zh: "压缩较早的对话历史", en: "Compact older conversation history" }; and/or
2. Register command descriptions into the locale registry (locale.register(ns, { zh, en })) keyed by command name, and render via the t() seat so descriptions follow live locale switches.

Either way, remote.commands.list should return the description for the current locale.

Impact

• Removes the need for users to patch node_modules or shadow-register commands in agent presets purely to localize descriptions.
• Fixes the acknowledged limitation that registry-held copy does not follow locale switches.
• Small blast radius: commands service + client render + 7 registration sites.

Environment

• dsh v0.1.0-rc.6 (Web UI)
• Windows 11, Chrome/Edge