@llblab/pi-telegram 0.16.0 → 0.16.2
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.
- package/CHANGELOG.md +10 -0
- package/lib/status.ts +6 -6
- package/package.json +1 -1
- package/screenshot.png +0 -0
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,16 @@
|
|
|
2
2
|
|
|
3
3
|
## Unreleased
|
|
4
4
|
|
|
5
|
+
No open changes.
|
|
6
|
+
|
|
7
|
+
## 0.16.2: Screenshot Refresh Hotfix
|
|
8
|
+
|
|
9
|
+
- `[Docs]` Refreshed the package screenshot. Impact: npm and repository previews show the current Telegram bridge UI without changing runtime behavior.
|
|
10
|
+
|
|
11
|
+
## 0.16.1: Disconnected Queue Status Hotfix
|
|
12
|
+
|
|
13
|
+
- `[Status]` Keep showing the local Telegram queue count in the TUI status bar when polling ownership moves to another Pi instance and the bridge reads as disconnected. Impact: the singleton Telegram control lock can move without hiding pending session-local Telegram prompt work from the original agent.
|
|
14
|
+
|
|
5
15
|
## 0.16.0: Telegram Extension Commands
|
|
6
16
|
|
|
7
17
|
- `[API]` Added `registerTelegramCommand()` on the public `/commands` subpath so companion extensions can explicitly provide Telegram-native slash commands without adding workflow-specific commands to core. Built-in bridge commands stay reserved, extension command names must be Bot API safe, duplicate extension names are rejected, commands stay hidden unless `showInMenu` is enabled, visible commands must provide an emoji used in `/start` help and Bot API descriptions, extension-command descriptions are shown in `/start`, visible extension commands are inserted after `/compact` before queue-control commands, prompt-template commands remain separated in `/start`, handler failures are isolated with runtime diagnostics, and routing precedence is built-ins → extension commands → prompt-template aliases. Impact: commands such as fresh-session controls can live in companion extensions while `pi-telegram` remains a lightweight Telegram shell.
|
package/lib/status.ts
CHANGED
|
@@ -529,15 +529,15 @@ export function buildTelegramStatusBarText(
|
|
|
529
529
|
if (state.error) {
|
|
530
530
|
return `${label} ${theme.fg("error", "error")} ${theme.fg("muted", state.error)}`;
|
|
531
531
|
}
|
|
532
|
-
if (!state.hasBotToken)
|
|
533
|
-
return `${label} ${theme.fg("muted", "not configured")}`;
|
|
534
|
-
if (!state.pollingActive)
|
|
535
|
-
return `${label} ${theme.fg("muted", "disconnected")}`;
|
|
536
|
-
if (!state.paired)
|
|
537
|
-
return `${label} ${theme.fg("warning", "awaiting pairing")}`;
|
|
538
532
|
const queued = state.queuedStatus
|
|
539
533
|
? theme.fg("success", state.queuedStatus)
|
|
540
534
|
: "";
|
|
535
|
+
if (!state.hasBotToken)
|
|
536
|
+
return `${label} ${theme.fg("muted", "not configured")}${queued}`;
|
|
537
|
+
if (!state.pollingActive)
|
|
538
|
+
return `${label} ${theme.fg("muted", "disconnected")}${queued}`;
|
|
539
|
+
if (!state.paired)
|
|
540
|
+
return `${label} ${theme.fg("warning", "awaiting pairing")}${queued}`;
|
|
541
541
|
if (state.compactionInProgress) {
|
|
542
542
|
return `${label} ${theme.fg("warning", "compacting")}${queued}`;
|
|
543
543
|
}
|
package/package.json
CHANGED
package/screenshot.png
CHANGED
|
Binary file
|