0.21.1: Runtime And Session Semantics Hotfix

[llblab]

Summary

This hotfix clarifies how Telegram destinations, Pi instances, active sessions, session files, and model context relate in pi-telegram.

It also documents the current small transient prompt guidance plus on-demand telegram_help design, distinguishes Pi session JSONL from shared bridge runtime logs, and corrects the queue-dispatch description to the current normal sendUserMessage(content) path.

Why

Issue #127 exposed a reasonable but inaccurate mental model: a Telegram destination can look permanently bound to one Pi session, and a large shared JSONL can look like merged model history. In reality, Telegram follows an assigned Pi instance and routes into its current session; bridge logs and Pi session files have separate roles. The previous wording also did not explain that ordinary Telegram prompts inherit normal Pi session context and token economics.

User-visible behavior

• README and architecture now state that Telegram targets follow Pi instances and their active sessions, not immutable session identities.
• Telegram's session-control boundary is explicit: compaction exists; new/resume/fork/tree/switch/reload do not yet have safe public Pi APIs.
• Token-cost guidance distinguishes normal active context from small Telegram metadata and current on-demand help.
• Pi session JSONL and profile-scoped pi-telegram logs*.jsonl are explicitly separated.
• Hidden/headless process creation is ruled out; explicitly launched long-lived Pi processes still follow normal lock ownership.

Changed areas

• README.md: operator-facing runtime/session/token-cost model.
• docs/architecture.md: instance/session ownership, process behavior, JSONL identity, current prompt guidance, and normal dispatch semantics.
• docs/public-api.md: stable session-control and target-identity boundary.
• CHANGELOG.md, package metadata: 0.21.1 hotfix release notes and version.

Risk Notes

Documentation and package metadata only; no runtime code or configuration migration.

Validation

• npm run validate — 1,138 tests; 1,137 passed, 1 platform skip; typecheck passed; audit clean; pack dry-run produced llblab-pi-telegram-0.21.1.tgz.
• Domain DAG validator — passed with 0 errors and 0 warnings.
• ABCd context validator — passed with 0 errors and 0 warnings.