dsh-telegram-connector 0.13.0 → 0.14.0

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## 0.14.0
+
+- **`/menu` is the front door.** `/menu` (and `/start` in the bot chat) posts a
+  control card with Status, Workspaces, Web link, Help, Update setup, Restart,
+  Plugins and Components. The buttons run the same handlers as the typed
+  commands; deployment buttons stay admin-only.
+- **One command per action.** `/plugin` is now `/plugins` with subcommands
+  (`/plugins add`, `info`, `remove`, `enable`, `disable`, `confirm`, `cancel`,
+  `approve`); `/system components` is now `/components`; `/status` in the bot
+  chat is `/system status`. The alias table (`/start`/`/?`/`/man`,
+  `/plugin list|install|rm|del`, `/list`, `/workspace rm`) is gone.
+- **`/man` removed.** `/help` and `<command> --help` remain; `/help <command>`
+  shows the same detail.
+- **`/dashboard` keeps its topic role** (claim an empty topic); the control card
+  is `/menu`.
+- The help registry, README, COMMANDS.md and the tests follow the new surface.
+
+## 0.13.1
+
+- **`/system status` probes the advertised address.** The setup binds the LAN
+  address (for example `192.168.2.98`), so the old hardcoded
+  `127.0.0.1:4310` check reported `answered unreachable` while the Web UI was
+  serving. The probe now tries the URL the web app advertises and falls back to
+  loopback only when there is no advertised URL.
+
 ## 0.13.0
 
 - **npm distribution.** The package is published as

package/COMPATIBILITY.md

@@ -6,6 +6,8 @@ every release.
 
 | Connector | DSH | Status | Notes |
 |---|---|---|---|
+| 0.14.0 | `0.2.1-rc.5` | needs UAT | one command surface: `/menu` card, `/plugins` subcommands, `/components`; aliases and `/man` removed |
+| 0.13.1 | `0.2.1-rc.5` | needs UAT | `/system status` probes the advertised web address, so a LAN-only bind no longer reports loopback as unreachable |
 | 0.13.0 | `0.2.1-rc.5` | needs UAT | independent semver; `/system update connector` resolves and installs the newest compatible connector tag; `/system update penpot` and `/system update plugin <name>` update bundles through the plugin manager; standalone mode documented |
 | 0.2.1-rc.5-0.12.11 | `0.2.1-rc.5` | tested | maintenance: setup keeps the Penpot token in both env files |
 | 0.2.1-rc.5-0.12.10 | `0.2.1-rc.5` | previous | maintenance: setup pins API-only penpot plugin 0.2.0 |

package/README.md

@@ -19,7 +19,7 @@ group "landing-page"             another workspace
 ```
 
 The full command reference is [`docs/COMMANDS.md`](docs/COMMANDS.md) — the bot's
-`/man` prints the same text, and every command accepts `--help`. The reasoning
+`/help <command>` prints the same text, and every command accepts `--help`. The reasoning
 behind the mapping is in [`docs/DESIGN.md`](docs/DESIGN.md); supported DSH
 versions are in [`COMPATIBILITY.md`](COMPATIBILITY.md).
 
@@ -73,17 +73,17 @@ versions are in [`COMPATIBILITY.md`](COMPATIBILITY.md).
   code block or a bullet list on the way out (see above).
 - **Commands live in one place.** A dashboard topic holds `/new`, `/sync`,
   `/close`, `/rename`, `/model` and friends; session topics accept plain text.
-- **Plugins from the chat.** `/plugins` lists the profile's bundles, `/plugin add`
+- **Plugins from the chat.** `/plugins` lists the profile's bundles, `/plugins add`
   inspects a spec before anything runs and asks for a confirmation, and
   `enable`/`disable`/`remove` work without opening a terminal.
 - **Channel-aware prompts.** A Telegram prompt reaches the agent with a
   `[via Telegram]` marker, so the answer can use chat steps instead of host
   commands. Web UI prompts are unmarked; the marker is in the session, not in
   the Telegram message.
-- **Dashboard card.** `/dashboard` posts the common actions as inline buttons:
-  new session, sync, status and sessions in a group; status, web link, update,
-  restart, plugins and components in the bot chat. Deployment buttons are
-  admin-only, exactly like the typed commands.
+- **Menu card.** `/menu` (and `/start` in the bot chat) posts the common actions
+  as inline buttons: status, workspaces, web link, help, update, restart, plugins
+  and components. Deployment buttons are admin-only, exactly like the typed
+  commands. `/dashboard` in a group still claims an empty topic as the dashboard.
 - **Host-free after install.** The runtime runs under a
   supervisor: every plugin confirmation opens a rollback window (live under HMR,
   or around a restart), and `/system update connector` resolves and installs the
@@ -154,7 +154,7 @@ install without the setup.
 The connector is published to npm as an exact version:
 
 ```sh
-dsh plugin --profile web add dsh-telegram-connector@0.13.0
+dsh plugin --profile web add dsh-telegram-connector@0.13.1
 export DSH_TELEGRAM_BOT_TOKEN='123456:ABC…'
 ```
 
@@ -170,7 +170,7 @@ cat >> "$DSH_HOME/profiles/web/pnpm-workspace.yaml" <<'YAML'
 allowBuilds:
   dsh-telegram-connector@https://github.com/vladtsvirko/dsh-telegram-connector.git: true
 YAML
-dsh plugin --profile web add github:vladtsvirko/dsh-telegram-connector#v0.13.0
+dsh plugin --profile web add github:vladtsvirko/dsh-telegram-connector#v0.13.1
 ```
 
 That path runs the package's `prepare` build; pnpm ≥ 10 refuses it until the
@@ -246,9 +246,9 @@ allowlisted user; `provider`/`model` → the profile default; `workspaceRoot`
 
 ## Commands
 
-The bot is self-documenting: `/help` lists the commands for the current chat,
-`/man` prints the full manual, and `<command> --help` explains one command
-(including subcommands: `/plugin add --help`). The same text is in
+The bot is self-documenting: `/help` lists the commands for the current chat
+and `<command> --help` explains one command
+(including subcommands: `/plugins add --help`). The same text is in
 [`docs/COMMANDS.md`](docs/COMMANDS.md). A `<session>` argument accepts a full
 session id, an id prefix, or the topic title.
 
@@ -261,12 +261,12 @@ session id, an id prefix, or the topic title.
 | `/workspace link <name>` | print the group link again |
 | `/workspace remove <name>` | preview the topics, confirm, then unregister from DSH and delete the group's session topics (files and sessions are untouched) |
 | `/plugins` | list the profile's bundles: enabled, disabled, available |
-| `/plugin info <name>` | version, source, rows, overrides and any error |
-| `/plugin add <spec>` | inspect a package, then install it after **Confirm** (or `/plugin confirm`) |
-| `/plugin enable <name>` · `/plugin disable <name>` | select or deselect a bundle (confirmed like the rest) |
-| `/plugin remove <name>` | uninstall a bundle (asks for confirmation) |
-| `/plugin confirm` · `/plugin cancel` | finish or drop a pending install/removal (the card has the same buttons) |
-| `/plugin approve` | allow the install scripts pnpm blocked, and retry |
+| `/plugins info <name>` | version, source, rows, overrides and any error |
+| `/plugins add <spec>` | inspect a package, then install it after **Confirm** (or `/plugins confirm`) |
+| `/plugins enable <name>` · `/plugins disable <name>` | select or deselect a bundle (confirmed like the rest) |
+| `/plugins remove <name>` | uninstall a bundle (asks for confirmation) |
+| `/plugins confirm` · `/plugins cancel` | finish or drop a pending install/removal (the card has the same buttons) |
+| `/plugins approve` | allow the install scripts pnpm blocked, and retry |
 | `/system restart` | restart into a trial: the new state is live, with a rollback window |
 | `/system restart now` | restart without a trial; the current state becomes the rollback point |
 | `/system update connector [to <version>] [now]` | move the connector to its newest compatible version, in a trial |
@@ -276,16 +276,16 @@ session id, an id prefix, or the topic title.
 | `/system confirm` | commit the running trial (or press **Commit**) |
 | `/system rollback` | restore the last committed state and restart |
 | `/system cancel` | abandon a pending update and unblock the bot; after acceptance it stops the updater job |
-| `/system components` | optional components (e.g. the design stack): a card with Enable/Disable/Port buttons |
+| `/components` | optional components (e.g. the design stack): a card with Enable/Disable/Port buttons |
 | `/system status` | versions, supervisor, open trial, web/key/registry probes |
 | `/system takechat` | make this chat the control chat (notices and update reports follow it) |
 | `/firewall` | native only: whether ufw lets the web UI through, and the `/firewall allow <port>` fix |
 | `/web` | a signed link into the web UI for the same sessions |
 | `/timezone [zone]` | IANA zone used to read times you type (default `$DSH_TIMEZONE` or UTC) |
 | `/reactions …` | read/streaming/staged reactions: show, set, `on`/`off`, `reset`, `allowed` |
-| `/status` | model route, counts, poller, timezone, supervisor and probe lines |
 | `/system status` | connector, runtime and updater state |
-| `/help` · `/man` | index, or the full manual |
+| `/menu` · `/start` | the control card with buttons for the common actions |
+| `/help [command]` | the command index, or one command |
 
 Plugin commands run in the private chat because they change the whole profile,
 not one workspace. `/schedules` is still a stub.
@@ -317,7 +317,7 @@ not one workspace. `/schedules` is still a stub.
 | `/run <command> [args]` | run a host command even when a connector name wins |
 | `/skill <name> [args]` | load a skill even when a host command owns the name |
 | `//text` | send a prompt that literally starts with `/` |
-| `/help` · `/man` | the session command manual |
+| `/help` | the session command manual |
 
 Management lives in the dashboard: `/new`, `/sessions`, `/status`, `/dashboard`,
 `/sync`, `/archived`, `/unarchive`, `/rename`, `/model`, `/close`,
@@ -490,7 +490,7 @@ session it has open.
 | nothing happens after adding the plugin | token is empty — the connector logs a warning and stays idle |
 | group title never follows a rename | bot lacks *Change Info* in that group |
 | `this runtime exposes no plugin manager` | the profile is not base-backed, or `@deepseek-ai/dsh-plugin-manager` is not mounted |
-| `/plugin add` says *already installed* | updates are a removal plus an install; use the host CLI, or remove first |
+| `/plugins add` says *already installed* | updates are a removal plus an install; use the host CLI, or remove first |
 | a plugin change says *restart required* | this runtime has no HMR — `/system restart`, then `/system confirm` if it works |
 | `/system restart` says *not running under the supervisor* | the runtime was started directly (no container), so restart it from the host |
 
@@ -504,8 +504,8 @@ session it has open.
 - The bot token comes from the environment; `cordis.patch.yml` never carries it.
 - The bot is an admin of its groups and can delete topics. `/dangerous cleanup`
   requires an explicit `confirm`; `/forget` never deletes anything.
-- **Plugins execute host code.** `/plugin add` inspects first and installs only
-  after **Confirm** (or `/plugin confirm`); blocked install scripts need `/plugin approve`, which
+- **Plugins execute host code.** `/plugins add` inspects first and installs only
+  after **Confirm** (or `/plugins confirm`); blocked install scripts need `/plugins approve`, which
   names exactly the packages allowed. The connector refuses to remove or disable
   itself, since that would cut the line mid-command.
 - `bindings.json` contains chat ids and session ids, not message contents.
@@ -520,7 +520,7 @@ npm run typecheck
 ```
 
 `src/index.ts` is the plugin (routing, commands, streaming); `help.ts` is the
-command registry behind `/help`, `/man` and the Telegram command menu;
+command registry behind `/help` and the Telegram command menu;
 `telegram.ts` is the typed Bot API client; `render.ts` normalises rich Markdown
 and splits; `outbox.ts` owns the per-group queue and publishers; `bindings.ts`
 persists the mapping; `sessions.ts` owns the topic key model; `bridge.ts` is the

package/docs/COMMANDS.md

@@ -1,7 +1,7 @@
 # Commands
 
 The bot has three surfaces. Each has its own command set, and each answers
-`/help`, `/man` and `<command> --help` from the same registry the bot uses.
+`/help` and `<command> --help` from the same registry the bot uses.
 
 ```
 private chat with the bot        control plane   workspaces, plugins, restarts, updates
@@ -13,20 +13,18 @@ group "web-app"                  workspace
 Conventions:
 
 - `<required>`, `[optional]`, `<a|b>` means choose one.
-- Every command accepts `--help`; `/help <command>` and `/man [command]` show the
-  same text. The one exception is `/commands`, which lists the live host catalog
-  instead of its own help.
-- Aliases: `/start` = `/help`, `/?` = `/help`, `/plugin list` = `/plugins`,
-  `/plugin install` = `/plugin add`, `/plugin rm` = `/plugin del` =
-  `/plugin remove`, `/workspace rm` = `/workspace remove`. `/plugin` with no
-  subcommand lists the bundles, like `/plugins`.
+- Every command accepts `--help`; `/help <command>` shows the same text. The one
+  exception is `/commands`, which lists the live host catalog instead of its own
+  help.
+- `/start` and `/menu` post the control card in the bot chat. In a group,
+  `/start` is the `startgroup` deep link that binds the workspace.
 - Admin-only (the `adminUserId` account, or the control-chat owner when unset):
   `/workspace new|link|remove`, every `/system` subcommand except `status`,
-  `/plugin add|remove|enable|disable|confirm|cancel|approve`, `/bind`,
-  `/system takechat`, `/firewall allow`, `/unbind`, `/dashboard`,
+  `/components`, `/plugins add|remove|enable|disable|confirm|cancel|approve`,
+  `/bind`, `/system takechat`, `/firewall allow`, `/unbind`, `/dashboard`,
   `/dangerous cleanup`. The inline buttons that do the same things — trial
-  Commit/Roll back, the component card, the update card's **Cancel**, Take over, the
-  deployment buttons on the dashboard card — are admin-only too.
+  Commit/Roll back, the component card, the update card's **Cancel**, Take over,
+  the deployment buttons on the menu card — are admin-only too.
 - A `<session>` argument accepts the full session id, an id prefix, or the topic title.
 - You can only use a command on the surface it belongs to; elsewhere the bot
   tells you where it lives.
@@ -56,17 +54,17 @@ dashboard.
 | Command | What it does |
 |---|---|
 | `/plugins` | bundles of this profile: enabled, disabled, available |
-| `/plugin info <name>` | version, source, rows, overrides, errors |
-| `/plugin add <spec>` | inspect a package, then install it after confirmation |
-| `/plugin remove <name>` | uninstall a bundle after confirmation |
-| `/plugin enable <name>` | select a bundle after confirmation |
-| `/plugin disable <name>` | deselect a bundle, keeping the package installed |
-| `/plugin confirm` | run the pending action |
-| `/plugin cancel` | drop the pending action |
-| `/plugin approve` | allow the install scripts pnpm blocked, then retry |
+| `/plugins info <name>` | version, source, rows, overrides, errors |
+| `/plugins add <spec>` | inspect a package, then install it after confirmation |
+| `/plugins remove <name>` | uninstall a bundle after confirmation |
+| `/plugins enable <name>` | select a bundle after confirmation |
+| `/plugins disable <name>` | deselect a bundle, keeping the package installed |
+| `/plugins confirm` | run the pending action |
+| `/plugins cancel` | drop the pending action |
+| `/plugins approve` | allow the install scripts pnpm blocked, then retry |
 
 A spec is a registry name (`pkg`, `pkg@1.2`), `github:owner/repo`, an absolute
-path, or a tarball URL. `/plugin add` never mutates before you press **Confirm** (or send `/plugin confirm`);
+path, or a tarball URL. `/plugins add` never mutates before you press **Confirm** (or send `/plugins confirm`);
 the pending action expires after ten minutes and is bound to its author.
 
 Every confirmed plugin action opens a **trial** first: under HMR the change is
@@ -75,6 +73,13 @@ Commit with `/system confirm`, revert with `/system rollback`, or let the window
 failed install/removal closes the trial without touching the profile. The
 connector refuses to disable or remove itself.
 
+### Menu
+
+| Command | What it does |
+|---|---|
+| `/menu` | post the control card: Status · Workspaces · Web link · Help · Update setup · Restart · Plugins · Components |
+| `/start` | the welcome card in the bot chat; the `startgroup` deep link in a group |
+
 ### System
 
 | Command | What it does |
@@ -88,11 +93,9 @@ connector refuses to disable or remove itself.
 | `/system update setup [--i-know-versions-are-incompatible]` | show a card with the target, DSH change, recent commit subjects and running sessions, then drain and update through the updater service; a cross-line jump gets a second **Cross anyway** confirmation |
 | `/system confirm` | commit the open trial (also the **Commit** button) |
 | `/system rollback` | restore the last committed state and restart (also **Roll back**) |
-| `/system components [<component> <enable\|disable\|port> [<port>]]` | optional components: a card with Enable/Disable/Port buttons, or the text form. The Port button offers three presets (8090/8091/8092); use the text form for anything else |
+| `/components [<component> <enable\|disable\|port> [<port>]]` | optional components: a card with Enable/Disable/Port buttons, or the text form. The Port button offers three presets (8090/8091/8092); use the text form for anything else |
 | `/system cancel` | abandon a pending update and unblock the bot (same as the card's **Cancel**); after acceptance it stops the running updater job |
 | `/system takechat` | make this private chat the control chat; notices, update reports and failure cards move here |
-| `/status` | model route, workspace/session counts, poller, timezone, supervisor |
-| `/dashboard` | post the control card: status, web link, update, restart, plugins, components |
 | `/firewall` | whether ufw lets the web UI through, and the exact `/firewall allow <port>` to fix it |
 | `/firewall allow <port>` | admin only; asks the updater to allow that served port from the LAN |
 | `/web` | a signed link into the web UI for the same sessions (bot chat only) |
@@ -175,7 +178,7 @@ button runs the same command you could type, so permissions are identical:
 | Card | Buttons |
 |---|---|
 | group dashboard (`/dashboard`) | New session · Sync · Status · Sessions |
-| bot chat (`/dashboard`) | Status · Web link · Update setup · Restart · Plugins · Components |
+| bot chat (`/menu`) | Status · Workspaces · Web link · Help · Update setup · Restart · Plugins · Components |
 
 The **flow cards** are confirmation prompts: trial Commit/Roll back, the update
 card's **Cancel** (while draining), component Enable/Disable/Port, and Take over (confirmed; restarts dsh) for a
@@ -186,7 +189,7 @@ remove`, `/unbind`, `/dangerous cleanup`, plugin add/remove/enable/disable and
 the dashboard **Restart** button. Each press answers with a toast
 (`deleting…` / `cancelled`), and the card is edited to the result. The typed
 fallback remains: `/workspace remove <name> confirm`, `/unbind confirm`,
-`/dangerous cleanup confirm` and `/plugin confirm`.
+`/dangerous cleanup confirm` and `/plugins confirm`.
 
 ## Icons and marks
 
@@ -262,7 +265,7 @@ topic is always one session, and a topic is never re-assigned.
 | `/run <command> [args]` | run a host command even when a connector command owns the name |
 | `/skill <name> [args]` | load a skill even when a host command owns the name |
 | `//text` | send a prompt that literally starts with `/` |
-| `/help`, `/man` | the session command manual |
+| `/help`, `/help` | the session command manual |
 
 Host commands (for example `/compact`, `/goal` or a command from a newly
 installed plugin) run against the session without creating a model message.
@@ -293,8 +296,8 @@ A topic created by hand becomes a session on its first message.
 # adopt what the web UI already has
 /sync                                     (General)
 # install a plugin safely
-/plugin add github:owner/repo             (bot chat)
-/plugin confirm                           → trial or live window
+/plugins add github:owner/repo             (bot chat)
+/plugins confirm                           → trial or live window
 /system confirm                          (or the Commit button)
 # ship a new connector
 /system update connector                   → newest compatible version → trial → /system confirm

package/docs/DESIGN.md

@@ -108,17 +108,17 @@ message, never a retry storm.
 
 ## 5. Commands
 
-The full reference is [COMMANDS.md](COMMANDS.md) (and `/man` in the bot); the
+The full reference is [COMMANDS.md](COMMANDS.md) (and `/help` in the bot); the
 shape is what matters here.
 
 - **Control chat** — `/workspaces`, `/workspace new|link|rm`, `/plugins`,
-  `/plugin info|add|enable|disable|remove|confirm|cancel|approve`, `/status`,
+  `/plugins info|add|enable|disable|remove|confirm|cancel|approve`, `/status`,
   `/system status`, `/timezone`, `/reactions`, `/web`, `/firewall`, `/system …`,
   `/schedules` (stub).
 - **Dashboard** — `/new`, `/sessions`, `/status`, `/dashboard`, `/sync`,
   `/archived`, `/unarchive`, `/rename`, `/model`, `/close`, `/reopen`,
   `/forget`, `/unbind`, `/dangerous cleanup`.
-- **Session topic** — plain text is a turn. `/help`, `/man`, `/commands`,
+- **Session topic** — plain text is a turn. `/help`, `/help`, `/commands`,
   `/skills`, `/<skill>`, `/run`, `/skill` and host commands are accepted;
   management commands take the session as an argument in the dashboard, so a
   conversation never has to be command-aware.
@@ -135,12 +135,12 @@ a workspace topic, and it rides on the host's `pluginManager` service:
 | Step | Host call |
 |---|---|
 | `/plugins` | `listBundles()` |
-| `/plugin info <name>` | `listBundles()`, matched by name, title or scope-less name |
-| `/plugin add <spec>` | `inspect(spec)` — no mutation |
-| **Confirm** button or `/plugin confirm` | `installBundle(spec)` |
-| `/plugin approve` | `installBundle(spec, { approvedBuilds })` |
-| `/plugin enable\|disable <name>` | `setBundleEnabled(name, boolean)` |
-| `/plugin remove <name>` | `removeBundle(name)` |
+| `/plugins info <name>` | `listBundles()`, matched by name, title or scope-less name |
+| `/plugins add <spec>` | `inspect(spec)` — no mutation |
+| **Confirm** button or `/plugins confirm` | `installBundle(spec)` |
+| `/plugins approve` | `installBundle(spec, { approvedBuilds })` |
+| `/plugins enable\|disable <name>` | `setBundleEnabled(name, boolean)` |
+| `/plugins remove <name>` | `removeBundle(name)` |
 
 The confirmation gate is deliberate: a plugin runs in-process with the
 runtime's permissions, so the preview lists what the spec names and the
@@ -151,7 +151,7 @@ disabling a bundle goes through the same confirmation for that reason. When the
 manager reports `restart-required`, the connector does not hand the restart back
 to the user — it starts the trial itself, and the trial message is the second
 confirmation.
-pnpm's blocked install scripts are named, and only `/plugin approve` allows the
+pnpm's blocked install scripts are named, and only `/plugins approve` allows the
 exact packages the failed run reported. The connector refuses to disable or
 remove its own bundle, because the in-flight reply would be cut off. A missing
 manager is reported, never assumed.
@@ -320,9 +320,9 @@ and directories.
 - The bot is a group admin and can delete topics: `/dangerous cleanup` requires
   an explicit `confirm`, and `/forget` never deletes anything.
 - Plugin mutations are the highest-risk surface: a bundle's code and install
-  scripts run with the runtime's permissions. `/plugin add` inspects first and
-  installs only after an explicit confirmation (the card's **Confirm** or `/plugin confirm`); blocked install scripts are
-  named and only `/plugin approve` allows exactly those names; `/plugin remove`
+  scripts run with the runtime's permissions. `/plugins add` inspects first and
+  installs only after an explicit confirmation (the card's **Confirm** or `/plugins confirm`); blocked install scripts are
+  named and only `/plugins approve` allows exactly those names; `/plugins remove`
   confirms too. Enable/disable is confirmed like the rest, and reversible. The
   connector refuses to disable or remove its own bundle.
 
@@ -371,7 +371,7 @@ a rollback, which is what makes the swap cheap and safe.
 |---|---|---|
 | `/system restart` (default) | connector → `POST /restart {trial:true}` | supervisor persists the trial, then restarts `dsh` |
 | `/system restart now` | connector → `POST /restart {trial:false}` | supervisor snapshots the current profile, then restarts |
-| plugin confirmation (**Confirm** / `/plugin confirm`) | connector → `POST /trial/open` | trial opens *before* the change, without restarting |
+| plugin confirmation (**Confirm** / `/plugins confirm`) | connector → `POST /trial/open` | trial opens *before* the change, without restarting |
 | change applied live | connector | keeps the trial; the message is the confirmation |
 | change needs a restart | connector → abandon + `/system restart` | the live trial is closed and a restart trial opened |
 | `/system update connector` | connector → `POST /update {trial:true}` | supervisor stops the runtime, runs `dsh-entrypoint reset-plugin`, starts a trial |
@@ -400,7 +400,7 @@ deserves the same window. The connector therefore opens the trial *before* the
 manager runs the operation:
 
 ```
-Confirm / /plugin confirm ─► POST /trial/open ─► mutation ─┬─ applied        ─► keep trial, announce
+Confirm / /plugins confirm ─► POST /trial/open ─► mutation ─┬─ applied        ─► keep trial, announce
                                                  ├─ restart-required ─► abandon, restart trial
                                                  └─ failed         ─► abandon
 ```

package/docs/STANDALONE.md

@@ -64,10 +64,10 @@ feature silently disappears.
 | Feature | Setup | Standalone |
 |---|---|---|
 | Sessions, topics, workspace dashboard, media, reactions | yes | yes |
-| `/plugins`, `/plugin add|remove|enable|disable` | yes, DSH plugin manager | yes, if the profile is base-backed with `pluginManager`; otherwise the commands explain that it is absent |
+| `/plugins`, `/plugins add|remove|enable|disable` | yes, DSH plugin manager | yes, if the profile is base-backed with `pluginManager`; otherwise the commands explain that it is absent |
 | `/system update penpot`, `/system update plugin <name>` | yes, wrapped in a supervisor trial | yes through the plugin manager; without a supervisor there is no automatic rollback |
 | `/system update connector` | yes: newest compatible npm version, installed by the supervisor | no: update from the host with the two `dsh plugin` commands below |
-| `/system update setup`, `/system components`, `/firewall` | yes, through the updater service | no: the updater is not present, and the commands say so |
+| `/system update setup`, `/components`, `/firewall` | yes, through the updater service | no: the updater is not present, and the commands say so |
 | `/system restart`, `/system rollback` | supervisor trial | restart the runtime yourself; no trial |
 | `/system status` | versions, supervisor, registry, data directory | the same lines, with absent components marked |
 

package/lib/help.d.ts

@@ -1,7 +1,7 @@
 /**
  * The command manual.
  *
- * One registry drives `/help`, `/man` and `<command> --help` on all three
+ * One registry drives `/help` and `<command> --help` on all three
  * surfaces (the bot chat, the workspace dashboard, a session topic), so the
  * text cannot drift between the index, the detail view and the README.
  *
@@ -11,7 +11,7 @@ export type Surface = 'control' | 'dashboard' | 'session';
 export interface CommandDoc {
     /** Command path without a slash, e.g. `plugin add`. */
     path: string;
-    /** Canonical invocation, e.g. `/plugin add <spec>`. */
+    /** Canonical invocation, e.g. `/plugins add <spec>`. */
     usage: string;
     summary: string;
     details?: string;
@@ -25,7 +25,7 @@ export interface CommandDoc {
 export declare const COMMANDS: CommandDoc[];
 /** `/help`: commands grouped by area, with one line each. */
 export declare function indexText(surface: Surface): string;
-/** `/man`: the same registry with details and examples. */
+/** The manual: the same registry with details and examples. */
 export declare function manualText(surface: Surface, only?: string): string;
 /** `/help <command>` and `<command> --help`. */
 export declare function lookupText(raw: string, surface: Surface): string | undefined;