@llblab/pi-telegram 0.17.4 → 0.17.5

package/BACKLOG.md

@@ -5,6 +5,11 @@
   - Done when: each confirmed sequence has a conservative normalization or safe-degradation rule covered by tests.
   - Done when: unconfirmed speculative rewrites remain out of the delivery path.
 
+- [ ] Evaluate Rich Draft placeholder heartbeat for long unsafe preview gaps.
+  - Done when: live/client evidence confirms whether `RichBlockThinking` / `<tg-thinking>` prevents Telegram draft expiry while assistant output is still streaming but no safe Markdown prefix is available.
+  - Done when: the behavior is compared against the existing typing keepalive lifecycle so Telegram chat action and Rich Draft placeholder states do not fight each other.
+  - Done when: abort/clear behavior is tested so placeholder drafts do not create the transient confusing block observed after abort.
+
 - [ ] Track a public Pi session-replacement hook before adding Telegram `/new`.
   - [ ] Wait for a safe public Pi API.
     - Done when: Pi exposes an API that invokes the same session-replacement path as terminal `/new`.

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 0.17.5: Screenshot Refresh
+
+- `[Docs]` Refreshed the package screenshot.
+
 ## 0.17.4: Native Rich Markdown Splitter Hotfix
 
 - `[Rich Markdown]` Rewrap oversized fenced code, display-math, and fully wrapped inline-formatting blocks when splitting native Rich Markdown at Telegram transport limits. Impact: very long structured Markdown blocks no longer produce invalid partial Rich Markdown chunks, so final assistant replies can stay native without losing long code/math/formatted output.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@llblab/pi-telegram",
-  "version": "0.17.4",
+  "version": "0.17.5",
   "private": false,
   "publishConfig": {
     "access": "public"