dsh-telegram-connector 0.0.0-stage → 0.13.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (79) hide show
  1. package/CHANGELOG.md +992 -0
  2. package/COMPATIBILITY.md +170 -0
  3. package/LICENSE +21 -0
  4. package/README.md +533 -2
  5. package/cordis.patch.yml +19 -0
  6. package/docs/COMMANDS.md +305 -0
  7. package/docs/DESIGN.md +566 -0
  8. package/docs/STANDALONE.md +95 -0
  9. package/lib/about.d.ts +15 -0
  10. package/lib/about.js +42 -0
  11. package/lib/about.js.map +1 -0
  12. package/lib/bindings.d.ts +116 -0
  13. package/lib/bindings.js +163 -0
  14. package/lib/bindings.js.map +1 -0
  15. package/lib/bots.d.ts +70 -0
  16. package/lib/bots.js +157 -0
  17. package/lib/bots.js.map +1 -0
  18. package/lib/bridge.d.ts +49 -0
  19. package/lib/bridge.js +104 -0
  20. package/lib/bridge.js.map +1 -0
  21. package/lib/errors.d.ts +43 -0
  22. package/lib/errors.js +52 -0
  23. package/lib/errors.js.map +1 -0
  24. package/lib/help.d.ts +54 -0
  25. package/lib/help.js +662 -0
  26. package/lib/help.js.map +1 -0
  27. package/lib/index.d.ts +82 -0
  28. package/lib/index.js +5744 -0
  29. package/lib/index.js.map +1 -0
  30. package/lib/media.d.ts +38 -0
  31. package/lib/media.js +183 -0
  32. package/lib/media.js.map +1 -0
  33. package/lib/mirror.d.ts +71 -0
  34. package/lib/mirror.js +58 -0
  35. package/lib/mirror.js.map +1 -0
  36. package/lib/outbox.d.ts +82 -0
  37. package/lib/outbox.js +318 -0
  38. package/lib/outbox.js.map +1 -0
  39. package/lib/plugins.d.ts +121 -0
  40. package/lib/plugins.js +221 -0
  41. package/lib/plugins.js.map +1 -0
  42. package/lib/process.d.ts +42 -0
  43. package/lib/process.js +150 -0
  44. package/lib/process.js.map +1 -0
  45. package/lib/rate-limit.d.ts +36 -0
  46. package/lib/rate-limit.js +67 -0
  47. package/lib/rate-limit.js.map +1 -0
  48. package/lib/reactions.d.ts +59 -0
  49. package/lib/reactions.js +109 -0
  50. package/lib/reactions.js.map +1 -0
  51. package/lib/reference.d.ts +49 -0
  52. package/lib/reference.js +183 -0
  53. package/lib/reference.js.map +1 -0
  54. package/lib/render.d.ts +60 -0
  55. package/lib/render.js +589 -0
  56. package/lib/render.js.map +1 -0
  57. package/lib/sessions.d.ts +17 -0
  58. package/lib/sessions.js +28 -0
  59. package/lib/sessions.js.map +1 -0
  60. package/lib/slash.d.ts +41 -0
  61. package/lib/slash.js +117 -0
  62. package/lib/slash.js.map +1 -0
  63. package/lib/supervisor.d.ts +93 -0
  64. package/lib/supervisor.js +110 -0
  65. package/lib/supervisor.js.map +1 -0
  66. package/lib/telegram-prompt.d.ts +45 -0
  67. package/lib/telegram-prompt.js +93 -0
  68. package/lib/telegram-prompt.js.map +1 -0
  69. package/lib/telegram.d.ts +305 -0
  70. package/lib/telegram.js +219 -0
  71. package/lib/telegram.js.map +1 -0
  72. package/lib/time.d.ts +15 -0
  73. package/lib/time.js +33 -0
  74. package/lib/time.js.map +1 -0
  75. package/lib/updates.d.ts +110 -0
  76. package/lib/updates.js +360 -0
  77. package/lib/updates.js.map +1 -0
  78. package/package.json +69 -4
  79. package/skills/telegram-rich-text/SKILL.md +62 -0
package/CHANGELOG.md ADDED
@@ -0,0 +1,992 @@
1
+ # Changelog
2
+
3
+ ## 0.13.1
4
+
5
+ - **`/system status` probes the advertised address.** The setup binds the LAN
6
+ address (for example `192.168.2.98`), so the old hardcoded
7
+ `127.0.0.1:4310` check reported `answered unreachable` while the Web UI was
8
+ serving. The probe now tries the URL the web app advertises and falls back to
9
+ loopback only when there is no advertised URL.
10
+
11
+ ## 0.13.0
12
+
13
+ - **npm distribution.** The package is published as
14
+ `dsh-telegram-connector@<version>`; the registry tarball already contains
15
+ `lib/`, so installs no longer run a build script. The release workflow
16
+ publishes a tag with provenance, and `/system update connector` resolves npm
17
+ versions. GitHub tags remain supported for source installs and as the setup's
18
+ fallback.
19
+ - **Independent versioning.** The connector version is now plain semver
20
+ (`0.13.0`), not `<dsh>-<product>`. The DSH release it was tested against is a
21
+ row in `COMPATIBILITY.md`; a setup release no longer has to carry a matching
22
+ connector tag, and a connector release no longer needs a setup release.
23
+ - **`/system update connector` now updates.** It resolves the newest tag in the
24
+ connector repository (or `to <version>`), refuses a tag whose declared DSH
25
+ range excludes the running runtime, and asks the supervisor to install that
26
+ exact ref. Before, it only reinstalled the setup-pinned version.
27
+ - **`/system update penpot` and `/system update plugin <name>`.** Any
28
+ GitHub-installed bundle can move to its newest compatible tag through the
29
+ host plugin manager, wrapped in a rollback trial. A failed install puts the
30
+ previous version back immediately.
31
+ - **The update path is testable without a runtime.** Release discovery,
32
+ semver range checks and argument parsing live in `src/updates.ts` with unit
33
+ tests; the supervisor accepts the exact ref in the `/update` request.
34
+ - Standalone use is documented in `docs/STANDALONE.md`: the same plugin runs
35
+ without the supervisor or updater, and the commands that need them say so.
36
+ The bundle patch now reads `ALLOWED_USER_IDS`, `DSH_ADMIN_USER_ID`,
37
+ `DSH_PROVIDER` and `DSH_MODEL` from the environment, so a bare install needs
38
+ no patch edit.
39
+
40
+ ## 0.2.1-rc.5-0.12.11
41
+
42
+ Maintenance release; no connector change. Aligned with the setup fix that keeps
43
+ the Penpot access token across both .env files.
44
+
45
+ ## 0.2.1-rc.5-0.12.10
46
+
47
+ Maintenance release; no connector change. Aligned with the setup that pins the
48
+ API-only Penpot plugin 0.2.0.
49
+
50
+ ## 0.2.1-rc.5-0.12.9
51
+
52
+ Maintenance release; no connector change. Aligned with the setup fix that adds
53
+ the ufw LAN-to-bridge route for published container ports.
54
+
55
+ ## 0.2.1-rc.5-0.12.8
56
+
57
+ Maintenance release; no connector change. Aligned with the setup fix for the
58
+ Penpot database URI (credentials moved out of the URL).
59
+
60
+ ## 0.2.1-rc.5-0.12.7
61
+
62
+ Maintenance release; no connector change. Aligned with the setup fix for
63
+ ProtectHome and rootless Podman's runtime dir.
64
+
65
+ ## 0.2.1-rc.5-0.12.6
66
+
67
+ Maintenance release; no connector change. Aligned with the setup fix for the
68
+ numeric UID in the unit and the DESIGN environment override.
69
+
70
+ ## 0.2.1-rc.5-0.12.5
71
+
72
+ Maintenance release; no connector change. Aligned with the setup fix that
73
+ exposes /run/user/<uid> to the service for rootless Podman.
74
+
75
+ ## 0.2.1-rc.5-0.12.4
76
+
77
+ Maintenance release; no connector change. Aligned with the setup fix that moves
78
+ rootless Podman's runtime dir to /run/dsh.
79
+
80
+ ## 0.2.1-rc.5-0.12.3
81
+
82
+ Maintenance release; no connector change. Aligned with the setup fix that
83
+ installs `passt` (pasta) and enables lingering for rootless Podman.
84
+
85
+ ## 0.2.1-rc.5-0.12.2
86
+
87
+ Maintenance release; no connector change. Aligned with the setup fix that moves
88
+ the `dsh` home to the data directory for rootless Podman.
89
+
90
+ ## 0.2.1-rc.5-0.12.1
91
+
92
+ Maintenance release; no connector change. Aligned with the setup fix that adds
93
+ the ufw bridge rules Podman needs for the Penpot stack.
94
+
95
+ ## 0.2.1-rc.5-0.12.0
96
+
97
+ ### Changed
98
+
99
+ - **Controls are words only.** Buttons, dashboard cards, trial and update
100
+ cards, status lines, process rows and speaker markers no longer use emoji.
101
+ The first word carries the status (`committed`, `failed`, `queued`,
102
+ `waiting`); a bare exception is prefixed `error:`. Process rows read
103
+ `Read: path`, `Search: query`, `Skill: name`; task lists use `[x]` / `[ ]`.
104
+ - **Reactions are the documented exception.** Telegram only accepts emoji from
105
+ its fixed set, so `/reactions` keeps 👀, ✍ and 🙉 (and `/reactions allowed`
106
+ lists the valid set). No other surface uses them.
107
+ - The icon policy is in `docs/COMMANDS.md` and a test fails if a button label
108
+ contains an emoji.
109
+
110
+ ## 0.2.1-rc.5-0.11.1
111
+
112
+ ### Fixed
113
+
114
+ - **The typed confirmation stays available for scripts.** `/workspace remove
115
+ <name> confirm` and `/unbind confirm` execute without pressing the card;
116
+ `/dangerous cleanup confirm` and `/plugin confirm` already did. The card is
117
+ still the normal path.
118
+
119
+ ## 0.2.1-rc.5-0.11.0
120
+
121
+ ### Added
122
+
123
+ - **One confirmation card for consequential actions.** `/workspace remove`,
124
+ `/unbind`, `/dangerous cleanup`, plugin add/remove/enable/disable and the
125
+ dashboard **Restart** button now post a consequence summary with **Confirm**
126
+ and **Cancel**. Every press answers with a toast and the card is edited to the
127
+ result; the typed `confirm` forms remain as the scriptable fallback.
128
+ - **`/sync` reports progress.** It posts a live card (`checked 4/12`, `adopted 2`)
129
+ and refuses a second sync in the same group.
130
+ - **`/model` lists the runtime's models.** Without a route it queries the
131
+ runtime's model catalog, marks the current route and rejects a route outside
132
+ it.
133
+ - **Admin markers.** `/help`, `/man` and the Telegram menu mark admin-only
134
+ commands (`· admin`), with `/system status` called out as the open subcommand.
135
+ - **Release notes and a cross-version gate.** The setup-update card shows the DSH
136
+ delta, recent commit subjects and the rollback contract; a target that crosses
137
+ a DSH line or product major gets a separate **Cross anyway** confirmation.
138
+ - **Component Port sub-card.** It shows the current port, derived choices and a
139
+ **Back** button instead of the fixed 8090/8091/8092 triplet.
140
+
141
+ ### Fixed
142
+
143
+ - **`/archived` is reachable.** It was documented, listed in `/help` and never
144
+ dispatched; the only working spelling was `/list archived`. Both now work and
145
+ the menu lists `/archived`.
146
+ - **The setup-update card no longer denies `/system cancel`.** It says the
147
+ command still stops an accepted job, which is what the code does.
148
+ - **Deleting topics is previewed.** `/workspace remove` (alias `/workspace rm`)
149
+ and `/unbind` show how many topics and which ones go, then ask.
150
+ - **Canonical verbs.** `/workspace remove` is the documented form; `/plugin` with
151
+ no subcommand lists bundles like `/plugins`.
152
+ - **Actionable refusals.** A command used in the wrong topic names itself and its
153
+ home; the unauthorized reply names the fix.
154
+ - **Errors are sentences.** Updater failures no longer print raw JSON, and
155
+ truncated reports say they were truncated.
156
+ - **Copy and icons.** `/system status` uses plain labels, `/schedules` is marked
157
+ planned, and the button icon roles are documented.
158
+
159
+
160
+ ## 0.2.1-rc.5-0.11.0
161
+
162
+ Maintenance release; no connector change. Aligned with the setup fix for the
163
+ Penpot compose service names (`penpot-backend`/`penpot-exporter`).
164
+
165
+ ## 0.2.1-rc.5-0.10.6
166
+
167
+ Maintenance release; no connector change. Aligned with the setup fix for Podman
168
+ DNS (`aardvark-dns`) and `.env` ownership.
169
+
170
+ ## 0.2.1-rc.5-0.10.5
171
+
172
+ Maintenance release; no connector change. Aligned with the setup fix that reports
173
+ the deployed git manifest instead of "none".
174
+
175
+ ## 0.2.1-rc.5-0.10.4
176
+
177
+ Maintenance tag for the setup release; no connector code changed. The setup
178
+ pins this tag so the `apple-hig` skill fixes ship with a matching connector.
179
+
180
+ ## 0.2.1-rc.5-0.10.3
181
+
182
+ ### Changed
183
+
184
+ - **`/system update setup` now confirms before it does anything.** It posts a
185
+ card with the current and target version and the number of running sessions;
186
+ **Update now** starts the drain, **Cancel** closes it. A pending card expires
187
+ cleanly if dsh restarts instead of looking like a completed update.
188
+ - The card drops Cancel as soon as nothing is draining, and the accepted state
189
+ says the cancel button is gone.
190
+
191
+ ## 0.2.1-rc.5-0.10.2
192
+
193
+ ### Fixed
194
+
195
+ - **Take over no longer restarts dsh silently.** The button now asks for
196
+ confirmation and says plainly that the restart interrupts every running
197
+ session and tool call, not only the held one. Cancel is a separate button.
198
+ The API does not expose a per-session disposer to the connector, so a global
199
+ restart is still the only way to release a web UI handle.
200
+ - **An unusable publisher token names the reason.** The notice now includes
201
+ Telegram's error (for example `401: Unauthorized`), says the bot is ignored
202
+ until restart, and tells the user to check the token with @BotFather and
203
+ replace it in `DSH_TELEGRAM_PUBLISHER_TOKENS`.
204
+ - **"Delivery could not be confirmed" explains itself.** The notice now says
205
+ Telegram did not acknowledge before dsh stopped (usually a restart/update),
206
+ that the message may or may not have arrived, and to check the chat before
207
+ resending.
208
+ - **The update card loses its Cancel button before the hand-over.** When no
209
+ session is draining, the card says so and drops the keyboard immediately
210
+ instead of offering a cancel that cannot work; the accepted state says the
211
+ cancel button is gone.
212
+
213
+ ## 0.2.1-rc.5-0.10.1
214
+
215
+ Maintenance release; no connector change. Aligned with the setup 0.10.1
216
+ test-only fix.
217
+
218
+ ## 0.2.1-rc.5-0.10.0
219
+
220
+ Maintenance release; no connector code change. Aligned with the setup that
221
+ removes Docker: the agent gets rootless Podman, Penpot runs on rootful Podman.
222
+
223
+ ## 0.2.1-rc.5-0.9.5
224
+
225
+ ### Added
226
+
227
+ - **Telegram prompts carry their channel.** The prompt the agent receives starts
228
+ with `[via Telegram]`, so it can answer with chat steps instead of host
229
+ commands. Web UI prompts stay unmarked; the marker is part of the session
230
+ transcript, not of the Telegram message.
231
+
232
+ ## 0.2.1-rc.5-0.9.4
233
+
234
+ ### Fixed
235
+
236
+ - **A prompt sent while the setup update restarted is no longer discarded.**
237
+ The first Telegram batch after an update was refused wholesale with "send it
238
+ again". Plain prompts and attachments are now delivered (the session survived
239
+ the restart); only commands are refused, because a queued `/system …` or trial
240
+ confirmation refers to the state the update replaced.
241
+
242
+ ## 0.2.1-rc.5-0.9.3
243
+
244
+ Maintenance release; no connector change. Aligned with the setup cleanup of
245
+ stale `/system update all` text and the penpot 0.1.2 pin.
246
+
247
+ ## 0.2.1-rc.5-0.9.2
248
+
249
+ ### Fixed
250
+
251
+ - **Dashboard Status and Sessions were the same message.** On the dashboard
252
+ surface `/status` without a session fell through to the session list, so both
253
+ buttons printed the workspace dashboard. `/status` now reports the workspace
254
+ and runtime state (session count, model route, poller, timezone) and
255
+ `/sessions` lists the sessions.
256
+
257
+ ## 0.2.1-rc.5-0.9.1
258
+
259
+ ### Changed
260
+
261
+ - **Commands renamed, no aliases:** `/system update setup` (was `update all`),
262
+ `/system components` (was `manage`), `/dashboard` (was `/setsystem`),
263
+ `/archived` (was `/list archived`). `/about` is removed; `/system status`
264
+ prints the same state.
265
+ - **Dashboard card.** `/dashboard` posts inline buttons: in a group, New
266
+ session, Sync, Status and Sessions; in the bot chat, Status, Web link, Update
267
+ setup, Restart, Plugins and Components. Each button runs the typed command, so
268
+ permissions are identical; the deployment buttons are admin-only.
269
+ - **`/unbind`, `/dashboard` and `/dangerous cleanup` require admin**, matching
270
+ `/bind` and the rest of the deployment-wide commands.
271
+ - The "system topic" is called the dashboard throughout; help and docs use the
272
+ new names.
273
+
274
+ ## 0.2.1-rc.5-0.9.0
275
+
276
+ ### Changed
277
+
278
+ - The bot's help and error text describes the systemd deployment: `update all`
279
+ moves the setup checkout through the updater service (not an image through a
280
+ sidecar), rollback does not move the checkout or the DSH install, and the
281
+ firewall note no longer compares a published Docker port.
282
+ - A held session names the other process and says `sudo systemctl stop
283
+ dsh.service`; the no-supervisor and updater-unreachable hints point at
284
+ `journalctl -u dsh-updater.service` and `update.sh --tg-connector`.
285
+
286
+ ## 0.2.1-rc.5-0.8.2
287
+
288
+ Maintenance release; no connector change. Aligned with the setup fix that makes
289
+ DSH_PUBLIC_URL an accepted installer answer.
290
+
291
+ ## 0.2.1-rc.5-0.8.1
292
+
293
+ Maintenance release; no connector change. Aligned with the setup fix for the
294
+ native smoke workflow and the health probe's bind address.
295
+
296
+ ## 0.2.1-rc.5-0.8.0
297
+
298
+ Maintenance release; no connector change. Aligned with the setup release that
299
+ removes the Docker deployment mode and adds a CPU/RAM share to the systemd unit.
300
+
301
+ ## 0.2.1-rc.5-0.7.0
302
+
303
+ ### Fixed
304
+
305
+ - **Inline buttons now require the admin account.** Trial Commit/Roll back,
306
+ component Enable/Disable/Port, the update card's ✖ and Take over all change
307
+ the deployment for every user, but the callback handler checked only the
308
+ allowlist while the typed equivalents required `adminUserId`. Any allowlisted
309
+ member could restart the runtime or commit a rollback window. The gate now
310
+ matches `/system`: a non-admin press is answered with
311
+ "only the admin can do that" and does nothing.
312
+ - **`/commands --help` shows its help again.** The `/commands` branch ran before
313
+ the generic `--help` handler, so the flag was swallowed and the host catalog
314
+ printed instead. The handler now runs first on every surface.
315
+
316
+ ### Changed
317
+
318
+ - The accepted update card no longer says "cancelling is no longer possible": the
319
+ card's button is gone, but `/system cancel` still stops the job, and the card
320
+ now says so.
321
+ - `/workspaces` help says the startgroup link is printed only for a workspace
322
+ that has no group yet.
323
+
324
+ ## 0.2.1-rc.5-0.6.4
325
+
326
+ Aligned with the setup fix for `data/.runtime.json`, which the entrypoint wrote
327
+ without a pid (invalid JSON) after an editing slip.
328
+
329
+ ### Fixed
330
+
331
+ - **A malformed instance marker degrades to "unknown", never to a crash or a
332
+ phantom holder.** The pid is trusted only as a positive integer, so a marker
333
+ from a broken build cannot make `/system status` claim another runtime holds
334
+ the data directory, and cannot hide the real one. With the marker fixed, a
335
+ held session again distinguishes "another client in this runtime" (take-over
336
+ card) from "another process over this data directory" (stop it first).
337
+
338
+ ## 0.2.1-rc.5-0.6.3
339
+
340
+ Maintenance release; no connector change. Aligned with the setup patch that
341
+ makes the doctor fixture read the real invoking uid (CI runners are uid 1001)
342
+ and adds a test that pins the ownership mismatch itself.
343
+
344
+ ## 0.2.1-rc.5-0.6.2
345
+
346
+ Maintenance release; no connector change. Aligned with the setup patch that
347
+ removes the credential helper's YAML dependency (the setup CI has no global dsh)
348
+ and makes its new doctor test independent of the runner's Docker daemon.
349
+ Supersedes 0.2.1-rc.5-0.6.1, whose CI stayed red on the credential tests.
350
+
351
+ ## 0.2.1-rc.5-0.6.1
352
+
353
+ Maintenance release; no connector change. Aligned with the setup tag whose new
354
+ doctor test assumed a host without Docker — the CI runner has one, so the setup
355
+ released a patch with the test made deterministic.
356
+
357
+ ## 0.2.1-rc.5-0.6.0
358
+
359
+ Aligned with the setup release that adds `install.sh --doctor`, keeps the
360
+ deployed provider key on a repair run, and refuses to run two runtimes over one
361
+ data directory.
362
+
363
+ ### Fixed
364
+
365
+ - **A held session now says who holds it.** The refusal named "a web UI tab" for
366
+ every case, so a session the *bot itself* still held in another topic, or one
367
+ held by a second runtime over the same data directory, was blamed on a tab the
368
+ user did not have — and `/system restart now` could not fix either. The
369
+ connector now distinguishes the three cases: another topic (send there, or
370
+ `/forget` this binding), a live client in this runtime (a tab; restart
371
+ clears it), and another dsh process (stop it first; `./install.sh --doctor`
372
+ names it). The take-over card is only offered when a restart can deliver.
373
+ - **A refused prompt is not queued where it could never arrive.** When another
374
+ topic owns the session, replaying the prompt after a restart would hand it to
375
+ whichever topic resumed first. It is no longer journaled for that case.
376
+ - **A re-bound topic no longer keeps the previous session's handle.** `/sync`
377
+ replacing a dead binding, or a session being forgotten and re-minted in the
378
+ same topic, left a runtime that still owned the old session; the next prompt
379
+ resumed it and failed with an ownership error that pointed at a phantom tab.
380
+
381
+ ### Added
382
+
383
+ - **The runtime registry is repaired at boot.** The web UI lists the runtime's
384
+ workspace registry, while Telegram lists the connector's bindings; after a
385
+ crash or a storage reset those disagree, and the web UI shows no workspace
386
+ even though Telegram reports it and its sessions. A bound workspace whose
387
+ directory still exists is recreated, its sessions are re-attached, and the
388
+ control chat gets one notice. `/sync` does the same repair on demand instead
389
+ of answering "this composition exposes no workspace registry".
390
+ - **`/system status` shows both lists and who owns the data directory.**
391
+ `registry: N workspace(s) in the runtime · M bound to Telegram` makes the
392
+ disagreement visible before a prompt fails, and `data:` names a second live
393
+ runtime over the same directory (the one case a restart cannot clear).
394
+
395
+ ## 0.2.1-rc.5-0.5.1
396
+
397
+ Maintenance release; no connector change. Aligned with the setup tag whose CI is
398
+ green.
399
+
400
+ ## 0.2.1-rc.5-0.5.0
401
+
402
+ Maintenance release; no connector change. Aligned with the setup release that
403
+ configures git and installs Docker when the design stack needs it.
404
+
405
+ ## 0.2.1-rc.5-0.4.0
406
+
407
+ ### Added
408
+
409
+ - **`/firewall` — see and fix the ufw hole from Telegram.** A native install's
410
+ web UI is only as reachable as ufw allows, and the fix used to need SSH.
411
+ `/firewall` lists the ports the deployment serves with their networks and
412
+ marks each allowed or blocked; `/firewall allow <port>` (admin only) asks the
413
+ updater to allow it. The updater accepts only a port the deployment already
414
+ serves from its `.env` and runs the fixed `ufw allow from <network> to any
415
+ port <port> proto tcp` — never a command from the chat.
416
+ - A finished setup update now appends the same advisory to its report, so the
417
+ blocked state arrives without asking and without a `--status` command.
418
+ - Docker deployments get "nothing to do": a published port is DNATed before
419
+ ufw's `INPUT` chain sees it, so a rule there changes nothing.
420
+ ## 0.2.1-rc.5-0.3.0
421
+
422
+ Maintenance release; no connector change. Aligned with the setup release that
423
+ warns when ufw would block a native install's web UI.
424
+
425
+ ## 0.2.1-rc.5-0.2.2
426
+
427
+ Maintenance release; no connector change. Aligned with the setup fix for the design
428
+ plugin on native hosts.
429
+
430
+ ## 0.2.1-rc.5-0.2.1
431
+
432
+ Maintenance release; no connector change. Aligned with the setup fix for the
433
+ unattended install.
434
+
435
+ ## 0.2.1-rc.5-0.2.0
436
+
437
+ Maintenance release; no connector change. Aligned with the setup release that asks
438
+ for publisher bot tokens and names the downloaded checkout.
439
+
440
+ ## 0.2.1-rc.5-0.1.2
441
+
442
+ Maintenance release; no connector change. Aligned with the setup tag whose CI is
443
+ green.
444
+
445
+ ## 0.2.1-rc.5-0.1.1
446
+
447
+ Maintenance release; no connector change. Aligned with the setup fix for the
448
+ root re-run of the one-file install.
449
+
450
+ ## 0.2.1-rc.5-0.1.0
451
+
452
+ Maintenance release; no connector change. Aligned with the setup release that adds
453
+ the one-file (wget/curl) install.
454
+
455
+ ## 0.2.1-rc.5-0.0.0
456
+
457
+ Alignment release against DSH `0.2.1-rc.5`. No connector code change; the product
458
+ line restarts at `0.0.0` for the new DSH part.
459
+
460
+ ### Changed
461
+
462
+ - Rebuilt against `@deepseek-ai/dsh-agent`, `dsh-llm` and `dsh-session`
463
+ `0.2.1-rc.5`. Their published `lib/` is byte-identical to rc.2, and
464
+ `typecheck` plus 191 tests pass unchanged.
465
+ - Peer ranges left alone (`>=0.1.0-rc.6 <0.3.0-0`). rc.5 is inside them and the
466
+ loader evaluates prereleases, so the runtime needs no exact-version exemption.
467
+ - One `COMPATIBILITY.md` row added; the previous one is now `previous`.
468
+
469
+ ## 0.2.1-rc.2-0.8.0
470
+
471
+ ### Added
472
+
473
+ - **The command menu.** Telegram's menu above the input box was empty; it is now
474
+ published for the bot chat and for groups, from the same registry as `/help`,
475
+ so it cannot drift from the manual. Two calls on boot, one per scope.
476
+ - **`/system takechat`**: make the current private chat the control chat.
477
+ Notices, update reports and failure cards go there, and moving it is explicit.
478
+ - **`/bind` is documented** (`/help bind`) — it was a real command in no help.
479
+
480
+ ### Fixed
481
+
482
+ - **The control chat no longer follows the last DM.** It is claimed by the first
483
+ private chat and stays there; an allowed colleague writing to the bot could
484
+ earlier redirect someone else's notices — and the content in them — by
485
+ messaging once. Only the admin moves it, with `/system takechat`.
486
+ - **Attaching a group is administration.** `/bind` and `/workspace new|link|rm`
487
+ now need the admin: they decide what every user in a group can reach. The
488
+ first-run `?startgroup=` link still works before the bot chat is claimed, so a
489
+ fresh install cannot lock itself out.
490
+ - **A host command of the same name works in a session topic.** `/bind`,
491
+ `/cleanup` and `/archived` exist on both sides; the connector's reservation
492
+ used to refuse them outright instead of letting the host command run.
493
+ - **`agent/error` is redacted** before it reaches a group: a provider error can
494
+ quote the key it rejected.
495
+ - **A failed attachment is reported to the user**, not only to the agent in the
496
+ prompt.
497
+ - **`/plugin del` works** — it resolved in help but had no dispatcher.
498
+ - **`/unarchive` points at a command that works**: it said `/rename` "inside it",
499
+ where `/rename` is refused; it now gives the full form to run from the dashboard.
500
+ - **A hard cut never splits a surrogate pair**, so an emoji at the 4,096 boundary
501
+ stays one character.
502
+
503
+ ### Notes
504
+
505
+ - With no `DSH_ADMIN_USER_ID` and no claimed bot chat, any allowed user may
506
+ administer — otherwise a hand-written config could not bind its first group.
507
+ `/about` says which rule is in effect.
508
+ ## 0.2.1-rc.2-0.7.4
509
+
510
+ Maintenance release; no connector change. Aligned with the setup fix for the
511
+ native smoke workflow.
512
+
513
+ ## 0.2.1-rc.2-0.7.3
514
+
515
+ Maintenance release; no connector change. Aligned with the setup fix for the
516
+ native smoke workflow.
517
+
518
+ ## 0.2.1-rc.2-0.7.2
519
+
520
+ Maintenance release; no connector change. Aligned with the setup fix for the
521
+ native prepare working directory.
522
+
523
+ ## 0.2.1-rc.2-0.7.1
524
+
525
+ Maintenance release; no connector change. It exists because the setup repo ships
526
+ one aligned tag and 0.7.1 fixes that repository's native smoke workflow.
527
+
528
+ ## 0.2.1-rc.2-0.7.0
529
+
530
+ ### Added
531
+
532
+ - **One admin account.** `DSH_ADMIN_USER_ID` (connector config `adminUserId`)
533
+ names the account that may run `/system update|restart|rollback|confirm|cancel|manage`
534
+ and `/plugin add|remove|enable|disable`. Everyone in `ALLOWED_USER_IDS` keeps
535
+ full use of the agent and every session. Every allowed user could update or
536
+ roll back the deployment for everyone before this.
537
+ - **`/status` answers the two questions it could not.** `web: 127.0.0.1:<port>
538
+ answered 200|401|unreachable`, `key: set (OPENCODE_GO_API_KEY)|missing (…)`,
539
+ and the last agent error with its time. `/about` and `/system status` name the
540
+ admin and say how it was decided.
541
+ - **The bindings warning reaches the chat.** A `bindings.json` that cannot be
542
+ read is kept aside and announced once, with the recovery step, instead of
543
+ leaving every group answering "not attached" for no visible reason.
544
+
545
+ ### Fixed
546
+
547
+ - **`/system` and `/plugin` are guarded on both entry paths**, including the
548
+ inline-button callbacks.
549
+
550
+ ### Notes
551
+
552
+ - No lockout on upgrade: with no `DSH_ADMIN_USER_ID`, the owner of the bot chat
553
+ is the admin. New installs always set it (the installer defaults it to the
554
+ first allowed id).
555
+ - Native mode now runs a real install → update → uninstall in CI
556
+ (`.github/workflows/native-smoke.yml`, on every tag and weekly), and the image
557
+ is built on every release tag.
558
+
559
+ ## 0.2.1-rc.2-0.6.0
560
+
561
+ ### Fixed
562
+
563
+ - **A hung Bot API call no longer freezes a topic.** No `fetch` carried a
564
+ deadline, so one stalled connection left the topic's flush chain unsettled and
565
+ that topic stopped updating until the process restarted. Every call now has a
566
+ timeout: 60 s by default (`requestTimeoutSeconds`), the long poll extends
567
+ Telegram's own hold time, and downloads get their own
568
+ (`downloadTimeoutSeconds`, 120 s).
569
+ - **A mirrored turn survives a restart.** The answer lived only in the sink; a
570
+ restart inside the flush window lost it and the catch-up digest never saw it.
571
+ Mirrored turns are journaled and completed like Telegram turns.
572
+ - **`/system rollback` no longer promises what the supervisor refuses.** While
573
+ another operation was running the supervisor answered `200` and did nothing,
574
+ so the connector retired the card and the rollback became unreachable. The
575
+ route now answers `409` (or `202` when it accepts), `/status` reports `busy`,
576
+ and the connector checks before posting.
577
+ - **`/system cancel` stops the job, not just the card.** It asks the updater to
578
+ cancel the running `update.sh` (the sidecar also stops a job that exceeds
579
+ `DSH_UPDATE_TIMEOUT_SECONDS`, 30 minutes by default).
580
+ - **The update gate allows the recovery commands.** It matched on a prefix, so
581
+ `/system update all` slipped through while `/system restart` was blocked — the
582
+ reverse of what a stuck drain needs. The rule is now an explicit list with its
583
+ own tests.
584
+
585
+ - **A mirrored web answer arrives as its own message.** Releasing a session to
586
+ the web UI left the topic's sink in place, so the answer was appended to the
587
+ previous Telegram turn and edited into that message — which sits above the
588
+ echo, changes silently, and looks like no answer at all. A mirrored prompt now
589
+ resets the sink, and the answer is gated behind the echo so it cannot overtake
590
+ it. Covered by an integration test that drives the real plugin.
591
+ - **A reply is never dropped silently.** A refused chunk used to disappear: no
592
+ log, no retry, no notice. It is logged with Telegram's code, retried once as
593
+ plain text, and reported in the topic if that also fails.
594
+ - **A permission error no longer silences a group.** A 400 "not enough rights"
595
+ was classified as "bot is not a member", which marked the bot missing and
596
+ blocked the chat for an hour; the main bot was never re-checked. Only real
597
+ membership failures do that now.
598
+ - **Re-tapping the startgroup link no longer wipes a group.** Binding was not
599
+ idempotent: a second tap deleted every topic in the group, disposed live
600
+ agents mid-answer and dropped every binding. Re-linking the same workspace now
601
+ just prints the dashboard, a group that hosts another workspace is refused
602
+ instead of seized, and moving a workspace clears the old group's bindings
603
+ without deleting its history.
604
+ - **A prompt refused after a take-over is queued, not lost.** When the refusal
605
+ arrived as an `agent/error` (the agent already existed), the prompt was never
606
+ journaled, so the Take over button delivered nothing. It is journaled now and
607
+ the card is posted with the button.
608
+ - **`/sync` keeps a healthy topic.** Any probe error (429, 5xx, network) counted
609
+ as "topic deleted" and unbound the topic, leaked the agent and created a
610
+ duplicate. Only a definite "message thread not found" purges a binding now,
611
+ the runtime is disposed before the binding goes, and the summary counts the
612
+ ones it could not probe.
613
+ - **`/unarchive <id>` reuses the session's topic** instead of binding one session
614
+ to two topics (the mirror kept posting to the archived one).
615
+ - **A stuck `/system update all` drain can be cleared.** The update gate blocked
616
+ every message including `/system restart`; `/system cancel` and the recovery
617
+ commands now pass, and `/system cancel` is a text command, not just a button.
618
+ - **A corrupt or older `bindings.json` is kept, not overwritten.** It used to be
619
+ replaced by an empty document and then overwritten on the next save — every
620
+ binding gone, silently. It is now set aside as `bindings.json.corrupt-<ts>`
621
+ with a log line.
622
+ - **Long formatted replies stay formatted.** A chunk that fits 3,800 markdown
623
+ characters can exceed Telegram's 4,096 once converted to HTML (`/man` did), and
624
+ the whole chunk fell back to plain text. Splitting now checks the converted
625
+ length; `SAFE_LENGTH` is 3,400.
626
+
627
+ ### Added
628
+
629
+ - **`/web`** prints a signed link into the web UI for the same sessions, with
630
+ what handing a session over means. It is only available in the bot chat, so
631
+ the link never lands in a group. `/about` and `/system status` now name the web
632
+ root (without the token) and the declared peer range.
633
+ - `<command> --help` works in session topics too, as `/help` promised.
634
+
635
+ ### Tests
636
+
637
+ - `tests/binding.integration.test.ts`: re-linking a group changes nothing, a
638
+ group hosting another workspace is refused, moving a workspace clears the old
639
+ bindings, `/unarchive` reuses its topic, `/sync` keeps a topic on a 5xx.
640
+ - The harness can refuse a Bot API call (`failSend`), and `waitFor` awaits async
641
+ predicates.
642
+
643
+ ## 0.2.1-rc.2-0.4.11
644
+
645
+ - Diagnostics for the mirror: the user echo reaches Telegram but the answer does
646
+ not, and the decision points are silent. `mirror:` logs whether the topic was
647
+ claimed, and `flush:` logs every flush that actually sends. Temporary; remove
648
+ once the cause is known.
649
+
650
+ ## 0.2.1-rc.2-0.4.10
651
+
652
+ - A refused Telegram prompt is no longer lost. It is journaled and the reply
653
+ offers **Take over**: the supervisor restarts the runtime, every write handle is
654
+ released, and the boot replay delivers the queued text without a retype.
655
+ - The journal replay drops prompts older than an hour, so a take-over that was
656
+ never taken does not resurface days later.
657
+
658
+ ## 0.2.1-rc.2-0.4.9
659
+
660
+ - One delivery path for a topic. A mirrored web turn now feeds the same sink as
661
+ a Telegram turn — buffer, flush, edits, splitting, rich/HTML fallback — instead
662
+ of a second plain-text pipeline through the outbox. Net -219 lines.
663
+ - What differs is declared on the sink, not duplicated in code: the mirror echoes
664
+ the prompt (Telegram never saw it) and shows no process card (the web UI
665
+ already does).
666
+ - A session taken over by another client drops its stale agent, so the next
667
+ Telegram prompt resumes instead of reusing a handle that owns nothing.
668
+ - `MirrorQueue` and the mirror process-card machinery are gone.
669
+
670
+ ## 0.2.1-rc.2-0.4.8
671
+
672
+ - A failed Telegram prompt no longer silences the topic. The attempt created a
673
+ runtime entry before the runtime refused it, and "this topic has a runtime"
674
+ was enough to drop every web turn mirror. A topic is now claimed only by a
675
+ runtime that actually holds an agent and has not been taken over.
676
+ - The leftover entry from a failed attempt is dropped, so it cannot claim the
677
+ topic later either.
678
+
679
+ ## 0.2.1-rc.2-0.4.7
680
+
681
+ - A session held by another client now says so from both paths. The refusal came
682
+ from `resume` (the session exists on disk), which was outside the friendly
683
+ mapping, so the raw runtime error leaked to the chat.
684
+ - The advice is the one that works: the write handle is a kernel lock with no
685
+ expiry, and a closed tab does not always release it, so `/system restart now`
686
+ clears every handle. "Close the tab" was wrong when there was no tab.
687
+
688
+ ## 0.2.1-rc.2-0.4.6
689
+
690
+ - A session taken over by a web UI tab is mirrored into its topic again. The
691
+ connector used to keep streaming into an agent handle it no longer owned, so
692
+ the topic went silent while Telegram prompts failed with the ownership error
693
+ under a misleading "Process interrupted" card.
694
+ - The takeover is detected from a prompt the connector did not send, and the
695
+ session is marked foreign until a Telegram prompt lands again.
696
+ - The refusal now says what happened ("this session is open in a web UI tab,
697
+ so prompts from Telegram are refused until it closes") instead of looking
698
+ like a crash.
699
+
700
+ ## 0.2.1-rc.2-0.4.5
701
+
702
+ Maintenance release for the setup fix that reaches Penpot over the shared
703
+ network and no longer fails a component change on an unreachable probe. No
704
+ connector behavior change.
705
+
706
+ ## 0.2.1-rc.2-0.4.4
707
+
708
+ Maintenance release for the setup fix that stops a port change from starting a
709
+ stopped component. No connector behavior change.
710
+
711
+ ## 0.2.1-rc.2-0.4.3
712
+
713
+ Maintenance release for the setup change that installs the Penpot plugin when
714
+ the design component is enabled. No connector behavior change.
715
+
716
+ ## 0.2.1-rc.2-0.4.2
717
+
718
+ Maintenance release for the setup change that replaces the design MCP bridge
719
+ with the in-repo `penpot` CLI. No connector behavior change.
720
+
721
+ ## 0.2.1-rc.2-0.4.1
722
+
723
+ Maintenance release for the setup's local-build fix of the design stack. No
724
+ connector behavior change.
725
+
726
+ ## 0.2.1-rc.2-0.4.0
727
+
728
+ - `/system manage` lists the optional components the setup registers and posts a
729
+ card with Enable / Disable and Port buttons. The text form
730
+ `/system manage <component> <enable|disable|port> [<port>]` does the same
731
+ without a tap. The updater applies the change, restarts the runtime and
732
+ reports; the connector never touches Docker.
733
+
734
+ ## 0.2.1-rc.2-0.3.1
735
+
736
+ - Process cards no longer wait for a rate-limited main bot. A summary falls back
737
+ to the outbox, live-card creation is skipped instead of blocking the turn, and
738
+ a stale card is left for the next start rather than delaying shutdown or
739
+ startup for the 429 block to expire.
740
+
741
+ ## 0.2.1-rc.2-0.3.0
742
+
743
+ - `processMode: live` is the new default. One process card is created on the
744
+ first tool/command/skill row, edited during the turn, and finalised as a
745
+ collapsed `<details>` summary. `summary` still sends only the collapsed
746
+ summary after the turn; `off` hides process rows. Web-UI sessions follow the
747
+ same mode.
748
+ - Live process-card refs are persisted in bindings, closed with a warning after
749
+ a restart or graceful stop, and expired after 30 minutes of inactivity.
750
+ - Slash commands are detected only at the first non-whitespace character;
751
+ slashes later in a prompt are literal. `/commands@bot` is accepted and a
752
+ command addressed to another known bot is ignored. `//text` is a leading-only
753
+ escape.
754
+ - `/run <command> [args]` executes a host command even when a connector name
755
+ wins; `/skill <name> [args]` loads a user-invocable skill even when a host
756
+ command owns the name.
757
+ - Media sent with a skill is attached to that turn, including reply references.
758
+ Media sent with a command is staged for the next prompt instead of being
759
+ dropped; unknown slash commands stage it too. Albums are debounced as one
760
+ gesture.
761
+ - Failed command output and thrown command errors are redacted before posting;
762
+ successful command output is unchanged. Command output still stays out of the
763
+ model history, and replying to the result pulls it back in.
764
+ - `/commands` and `/skills` documentation now covers the collision escapes,
765
+ leading-only slash rule and media behaviour.
766
+
767
+ ## 0.2.1-rc.2-0.2.1
768
+
769
+ Maintenance release: ships with the setup's supervisor-test fix. No connector
770
+ behavior change.
771
+
772
+ ## 0.2.1-rc.2-0.2.0
773
+
774
+ Maintenance release aligned with the setup's two-mode installer. No connector
775
+ behavior change: the same code runs under the container and under the new native
776
+ systemd deployment.
777
+
778
+ ## 0.2.1-rc.2-0.1.19
779
+
780
+ - Tool calls, host commands and skill loads become short safe process rows.
781
+ Telegram sessions append one collapsed `<details>` summary per turn
782
+ (`processMode: summary`); web-UI-driven sessions get a live process card.
783
+ Raw tool output is never mirrored; command/path/query previews are redacted and
784
+ truncated, and credentials are masked.
785
+ - Session topics now bridge host commands dynamically with
786
+ `ctx.commands.list()` / `ctx.commands.execute()`; no allowlist means a command
787
+ from a newly installed plugin works without a connector release. The command
788
+ result is posted without creating a model message.
789
+ - `/commands` lists host commands, `/skills` lists user-invocable skills, and
790
+ `/<name>` loads a skill through the `dsh-tool-skill` gesture. Both lists are
791
+ read live from the session, so new skills also work without a connector
792
+ release.
793
+ - Connector commands keep precedence over host commands on a name collision.
794
+
795
+ ## 0.2.1-rc.2-0.1.18
796
+
797
+ - Fix the `telegram-rich-text` skill never loading: the registration omitted the
798
+ `source` field that the skills registry requires, so loading it failed with
799
+ `source must be a string`.
800
+ - Send a Markdown table as a fenced monospaced block, or as bullets when it is
801
+ too wide, instead of leaving the GFM table to the client. Clients that do not
802
+ render tables showed the raw pipe syntax; a code block and a list work
803
+ everywhere.
804
+
805
+ ## 0.2.1-rc.2-0.1.17
806
+
807
+ - Forwarded messages are now processed as their own context turn with a
808
+ `Forwarded from …` block. Forwarded rich messages are read from
809
+ `rich_message.blocks`; forwarded media is re-downloaded and attached.
810
+ - A reply to a forwarded message adds `(forwarded from …)` to the reference
811
+ block, so the model can tell that the quoted message was not written by the
812
+ current user.
813
+ - The poll filter now admits forwarded and rich messages that carry no `text`.
814
+
815
+ ## 0.2.1-rc.2-0.1.16
816
+
817
+ - Reply references now read `rich_message.blocks` as well as `text`/`caption`/
818
+ `quote`. A reply to a message the connector sent as a rich message (for
819
+ example the anchor test message) used to look like a plain prompt because
820
+ Telegram puts the content in `rich_message`, not `text`.
821
+ - The rich-block extractor flattens headings, paragraphs, tables and nested
822
+ inline text, skips layout metadata, and still truncates the quote to ~800
823
+ characters.
824
+
825
+ ## 0.2.1-rc.2-0.1.15
826
+
827
+ - Replying to an earlier message now adds it to the prompt as quoted reference
828
+ context. Same-chat replies use `reply_to_message`; cross-chat/topic replies use
829
+ `external_reply`.
830
+ - Referenced media is re-downloaded on every use (no cache), attached as
831
+ `ImageBlock`/`FileBlock`, and deduped against staged or newly sent media by
832
+ `file_id`.
833
+ - Download failures are written into the prompt, including the likely fixes
834
+ (re-upload, send as a file, grant the bot access to the source chat).
835
+ - A text reply is a normal acknowledgment turn; a media reply is an immediate
836
+ prompt with the new media as the task and the referenced media as context.
837
+ - Commands never attach referenced media.
838
+
839
+ ## 0.2.1-rc.2-0.1.14
840
+
841
+ - Photos, image documents, videos, video notes, audio, voice notes and
842
+ animations are downloaded through the Bot API and attached with DSH's
843
+ attachment service: images become `ImageBlock`s, everything else becomes a
844
+ `FileBlock` with a read-only path the agent can inspect.
845
+ - Captionless media is staged instead of starting a turn per file. Staged items
846
+ get the **🙉** reaction, and the next caption or text prompt downloads and
847
+ attaches the whole batch. The reaction is removed when the batch is used or
848
+ after 15 minutes.
849
+ - Albums are debounced by `media_group_id`, so a multi-photo upload is one
850
+ prompt, not one prompt per photo.
851
+ - `/reactions staged <emoji>` and `stagedReaction` configure the marker; the
852
+ default is 🙉.
853
+
854
+ ## 0.2.1-rc.2-0.1.13
855
+
856
+ - Every Telegram session gets a `telegram-surface` system-prompt section that
857
+ tells the model the user is reading in Telegram and that replies are sent as
858
+ rich messages. It asks for headings, lists, narrow tables, fenced code,
859
+ details, math and `<tg-time>`, and warns against MarkdownV2 escaping and
860
+ wrapping the whole answer in a code fence.
861
+ - The full formatting cheat sheet ships as `skills/telegram-rich-text/SKILL.md`
862
+ and is registered as the `telegram-rich-text` runtime skill, so it is loadable
863
+ on demand instead of inflating every prompt.
864
+ - The prompt section is installed on both newly created and resumed Telegram
865
+ agents, including sessions adopted from the web UI.
866
+
867
+ ## 0.2.1-rc.2-0.1.12
868
+
869
+ - Agent replies are sent as Telegram rich messages (Bot API 10.1+), so Markdown
870
+ tables, headings and lists render natively instead of arriving as raw source.
871
+ A rich message rejected by the API falls back to the HTML subset (a table
872
+ becomes a monospaced block or a key/value list) and finally to plain text.
873
+ - Message splitting is table-aware: a table split across messages repeats its
874
+ header and separator, so every chunk still renders as a table.
875
+ - The main bot sets a **read** reaction on an authorized prompt and a
876
+ **streaming** reaction on each reply part that may still be edited; the
877
+ streaming reaction is removed after the final flush, on agent error, and on
878
+ shutdown. Both emoji are configurable online with `/reactions` and persisted
879
+ in the bindings. Telegram's fixed reaction set is validated (`✓`, `✅` and
880
+ `⏳` are not allowed; defaults are 👀 and ✍).
881
+ - A rejected HTML payload now falls back to rendered plain text instead of
882
+ resending the Markdown source.
883
+
884
+ ## 0.2.1-rc.2-0.1.11
885
+
886
+ - A failed topic operation no longer latches topic management off for the rest
887
+ of the process. A transient 400/403 used to block `/new`, `/sync` and
888
+ `/unarchive` even after the permission or topic was fixed.
889
+ - `/new` now reports Telegram's actual error instead of only guessing that
890
+ `can_manage_topics` is missing.
891
+
892
+ ## 0.2.1-rc.2-0.1.10
893
+
894
+ Maintenance release aligned with the setup fix for the web UI bind address. No
895
+ connector behavior change.
896
+
897
+ ## 0.2.1-rc.2-0.1.9
898
+
899
+ - Mirror web-UI prompts and answers in log order; the answer used to read the
900
+ event envelope instead of `event.data.message` and was never posted.
901
+ - Do not mirror harness-injected `user/message` context (time readings, runtime
902
+ context, skill catalogs) as if the user had typed it.
903
+ - Match the claimed topic by group and thread, not thread id alone.
904
+
905
+ ## 0.2.1-rc.2-0.1.8
906
+
907
+ Maintenance target for the web-UI drain/cancel test. No behavior change.
908
+
909
+ ## 0.2.1-rc.2-0.1.7
910
+
911
+ - Boot fallback waits for a terminal update state instead of reading `applying`.
912
+ - Updater marks `reporting`/`reported`; the connector reports only if the updater
913
+ could not, and closes the update card with the final result.
914
+
915
+ ## 0.2.1-rc.2-0.1.6
916
+
917
+ - Fix the updater’s Telegram report (`fetch` option shadowed global `fetch`).
918
+ - If the updater cannot report, the booting connector sends the persisted result after 5s.
919
+ - Updater result files are written atomically.
920
+ - `/about` continues to show updater status.
921
+
922
+ ## 0.2.1-rc.2-0.1.5
923
+
924
+ - `/about` reports updater status (`ready`, `unreachable`, `disabled`, or `apply unavailable`) and the checkout tag.
925
+
926
+ ## 0.2.1-rc.2-0.1.4
927
+
928
+ Maintenance release for the self-reloading updater. No connector behavior change.
929
+
930
+ ## 0.2.1-rc.2-0.1.3
931
+
932
+ - Editable setup-update card: target, live drain blockers, and a Cancel button.
933
+ - Cancel is removed once the updater accepts; callbacks after that are refused.
934
+ - `/about`, `/help`, `/man` and `/system status` stay available while draining.
935
+ - Updater sends a “dsh is down” notice and strips ANSI from report logs.
936
+ - `/about` no longer prints the old peer-range line.
937
+
938
+ ## 0.2.1-rc.2-0.1.2
939
+
940
+ Maintenance target for the next setup-updater validation. No connector behavior
941
+ change.
942
+
943
+ ## 0.2.1-rc.2-0.1.1
944
+
945
+ Maintenance release used as the first live target for the setup updater. No
946
+ connector behavior change.
947
+
948
+ ## 0.2.1-rc.2-0.1.0
949
+
950
+ First DSH-aligned release with the updater sidecar. The DSH part matches the
951
+ tested runtime; the product part (`0.1.0`) is our compatible feature line.
952
+ Same-major updates may jump; crossing a major or DSH line requires the explicit
953
+ flag in the setup updater.
954
+
955
+ - Telegram sessions mount a DSH **agent preset** (default or `agentPreset`) on
956
+ create and the header's recorded preset on resume.
957
+ - `/system` namespace: `status`, `restart [now]`, `update connector [now]`,
958
+ `update all`, `confirm`, `rollback`; old commands removed.
959
+ - `/system update connector now` reinstalls without a trial.
960
+ - `/system update all` drains all agents (web UI included), blocks new prompts,
961
+ calls the updater sidecar, and rejects the queued downtime batch with
962
+ “update finished — send it again”.
963
+ - `/system status` lists sessions blocking a drain.
964
+
965
+ ## 0.1.0-rc.1
966
+
967
+ First release candidate for 0.1.0.
968
+
969
+ First public shape of the connector.
970
+
971
+ - Groups map to workspaces, forum topics to sessions, the private chat to the
972
+ control plane.
973
+ - Streaming replies, Markdown subset → Telegram HTML, fence-aware splitting.
974
+ - `/sync` adoption with per-session probing and history replay, paced to
975
+ Telegram's per-chat limits and announced in the system chat while waiting.
976
+ - Durable bindings; sessions are resumed, never re-minted on restart.
977
+ - Plugin surface: list, info, add/remove with inspect + confirmation,
978
+ enable/disable, build-script approval.
979
+ - Supervised restarts: `/restart` (trial), `/restart now`, `/confirm`,
980
+ `/rollback`, live trials for HMR changes, automatic rollback on crash, boot
981
+ failure, deadline or container restart.
982
+ - Self-update through the supervisor (`/update`).
983
+ - `/help`, `/man`, `<command> --help`, `/about`, `/timezone`.
984
+ - Per-group outbox: persisted FIFO with control priority, exactly-once delivery
985
+ (ambiguous outcomes are quarantined, never duplicated), queue status line, a
986
+ weekly saturation digest, and an owner notice when a message is lost so it is
987
+ never silent.
988
+ - Logical bridge: durable out/in journals for turns and prompts, with a
989
+ crash catch-up digest and prompt re-injection; the format is the boundary for
990
+ a future standalone bridge process.
991
+ - Optional publisher bots (`DSH_TELEGRAM_PUBLISHER_TOKENS`): send-only, per-bot
992
+ rate limits, proactive switching, membership checks and missing-member reports.