@llblab/pi-telegram 0.42.2 → 0.42.3
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
CHANGED
|
@@ -2,6 +2,11 @@
|
|
|
2
2
|
|
|
3
3
|
> Each release keeps at most 8 outcome records of at most 512 characters.
|
|
4
4
|
|
|
5
|
+
## 0.42.3: Agent Diagnostics Hotfix
|
|
6
|
+
|
|
7
|
+
- `Agent Diagnostics`: Identifies `/telegram-status` as a Pi TUI command and routes agents without command access directly to the redacted diagnostic files instead of attempting a shell executable; runtime behavior and STT fallback remain unchanged.
|
|
8
|
+
- `Local Architecture Guidance`: Consolidates the repository-local Domain DAG Skill around canonical protocols and removes redundant self-validation configuration and a legacy recipe wrapper; the validator remains available, and this development-only Skill is not included in the npm package.
|
|
9
|
+
|
|
5
10
|
## 0.42.2: Telegram Comment Membrane
|
|
6
11
|
|
|
7
12
|
- `Transport-Private HTML Comments`: Removes every assistant-authored `<!-- … -->` block from Telegram previews, active-turn finals, connected companion projections, direct sends, and Guest Mode regardless of Markdown position or owning extension; only recognized top-level comments activate actions, unclosed tails stay hidden, comment-only text plans send nothing, and the Pi terminal transcript remains unchanged.
|
package/package.json
CHANGED
|
@@ -4,11 +4,13 @@ Read this reference only when diagnosing Telegram bridge health or delivery fail
|
|
|
4
4
|
|
|
5
5
|
Inspect in this order:
|
|
6
6
|
|
|
7
|
-
1.
|
|
8
|
-
2.
|
|
7
|
+
1. `/telegram-status` for compact health in the Pi TUI.
|
|
8
|
+
2. `/telegram-status --debug` for bounded human-readable diagnostics in the Pi TUI.
|
|
9
9
|
3. `~/.pi/agent/tmp/telegram/state.json` and `logs.jsonl` for default-profile redacted evidence.
|
|
10
10
|
4. `state.<profile>.json` and `logs.<profile>.jsonl` for a named profile.
|
|
11
11
|
|
|
12
|
+
These slash commands are registered Pi commands, not shell executables or agent tools. If the agent cannot invoke them through a supported Pi surface, read the diagnostic files directly; do not run them in Bash or inject terminal input.
|
|
13
|
+
|
|
12
14
|
When `PI_CODING_AGENT_DIR` selects another compatible runtime, resolve its equivalent `tmp/telegram` directory.
|
|
13
15
|
|
|
14
16
|
Do not mutate ownership files, bridge state, journals, bindings, or locks to force recovery. Use supported commands and preserve exact profile, target, transport, and session authority. Never claim successful delivery without transport evidence.
|