@linxiraos/pi-channels 1.3.2 → 1.4.1

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 ## [Unreleased]
 
+## [1.4.1] - 2026-10-23
+
+- Version alignment with the 1.4.1 release line (no behavioral changes).
+
+## [1.4.0] - 2026-10-21
+
+- Feishu and Telegram log in with credentials as well as the WeChat QR: credentials are validated before they are written (Feishu tenant token plus bot info, Telegram `getMe`), secrets are masked in errors, and unbinding clears exactly the fields that channel owns
+
+- Channel config writes go through a read-modify-write under one file lock with a shared reader, and the runtime lock is published atomically (temp file + link), so concurrent `login`/`serve`/settings writers no longer drop keys
+- `channels.reportPolicy` is read from settings instead of being inert, and a session-only route mapping is cleaned up when its session ends
+
 ## [1.3.2] - 2026-10-19
 
 - Version line moves to 1.3.2 with the rest of the suite; no user-visible change in this package.

package/dist/types/index.d.ts

@@ -1,14 +1,15 @@
 /**
- * Channel bootstrapping for `zetacode serve` (web/desktop mode only).
+ * Channel bootstrapping shared by `zetacode serve` and normal CLI/TUI
+ * sessions.
  *
  * Enables every channel marked `enabled` in the web config and routes its
- * inbound messages into the coordinator session through `ChannelHost`.
- * Channels missing required credentials are skipped with a warning — a
- * misconfigured channel must never prevent the server from starting.
+ * inbound messages into the host session through `ChannelHost`. Channels
+ * missing required credentials are skipped with a warning — a misconfigured
+ * channel must never prevent the host from starting.
  *
- * The CLI never imports this module: `zeta`/`zeta --interactive` sessions
- * don't create a ZetaServer, so no channel listeners exist there and
- * `channel_send`/`workspace_run` stay unavailable.
+ * The runtime is transport-agnostic: it needs only the `ChannelSession`
+ * contract, so `zetacode` (interactive or `--print`) hosts it directly when a
+ * channel is enabled, and `channel_send` becomes available there too.
  */
 import type { ChannelId, ChatChannel, ChatImage } from "./channel.js";
 import { ChannelHost } from "./host.js";

package/package.json

@@ -22,15 +22,15 @@
 		"bun": ">=1.3.14"
 	},
 	"peerDependencies": {
-		"@linxiraos/pi-ai": "1.3.2"
+		"@linxiraos/pi-ai": "1.4.1"
 	},
 	"devDependencies": {
 		"@types/bun": "1.4.3",
-		"@linxiraos/pi-ai": "1.3.2"
+		"@linxiraos/pi-ai": "1.4.1"
 	},
 	"dependencies": {
 		"@larksuiteoapi/node-sdk": "^1.71.1",
-		"@linxiraos/pi-utils": "1.3.2"
+		"@linxiraos/pi-utils": "1.4.1"
 	},
 	"scripts": {
 		"test": "bun test --parallel",
@@ -62,6 +62,6 @@
 	"homepage": "https://linxira-os.github.io/zeta/",
 	"description": "IM channel adapters for Zeta (WeChat / Feishu / Telegram)",
 	"type": "module",
-	"version": "1.3.2",
+	"version": "1.4.1",
 	"name": "@linxiraos/pi-channels"
 }

package/src/index.ts

@@ -1,14 +1,15 @@
 /**
- * Channel bootstrapping for `zetacode serve` (web/desktop mode only).
+ * Channel bootstrapping shared by `zetacode serve` and normal CLI/TUI
+ * sessions.
  *
  * Enables every channel marked `enabled` in the web config and routes its
- * inbound messages into the coordinator session through `ChannelHost`.
- * Channels missing required credentials are skipped with a warning — a
- * misconfigured channel must never prevent the server from starting.
+ * inbound messages into the host session through `ChannelHost`. Channels
+ * missing required credentials are skipped with a warning — a misconfigured
+ * channel must never prevent the host from starting.
  *
- * The CLI never imports this module: `zeta`/`zeta --interactive` sessions
- * don't create a ZetaServer, so no channel listeners exist there and
- * `channel_send`/`workspace_run` stay unavailable.
+ * The runtime is transport-agnostic: it needs only the `ChannelSession`
+ * contract, so `zetacode` (interactive or `--print`) hosts it directly when a
+ * channel is enabled, and `channel_send` becomes available there too.
  */
 
 import { logger } from "@linxiraos/pi-utils";