@agfpd/iapeer 0.4.22 → 0.4.23

package/CHANGELOG.md

@@ -10,6 +10,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.4.23] - 2026-06-22
+
+### Added
+
+- **`iapeer enable telegram <peer>`** — a discoverability alias for `iapeer connect telegram
+  <peer>` (give an existing peer a Telegram bot face). A layperson reaches for "enable
+  telegram", not "connect"; both now work and route through the same flow (bot add →
+  interface → router restart; asks only the token). telegram is a CHANNEL, not a marketplace
+  plugin, so the alias routes to the connect flow, not `enableCapability`. The `connect`
+  help line documents the alias. No telegram-runtime change (the mechanism already worked) —
+  purely CLI discoverability.
+
 ## [0.4.22] - 2026-06-22
 
 ### Added
@@ -340,7 +352,8 @@ Initial public release — the foundation core of the iapeer multi-agent ecosyst
 - **Heterogeneous peers** — AI agents (Claude, Codex), humans (Telegram), and services
   (timer = cron, watcher = event) are all first-class and addressed the same way.
 
-[Unreleased]: https://github.com/agfpd/iapeer/compare/v0.4.22...HEAD
+[Unreleased]: https://github.com/agfpd/iapeer/compare/v0.4.23...HEAD
+[0.4.23]: https://github.com/agfpd/iapeer/compare/v0.4.22...v0.4.23
 [0.4.22]: https://github.com/agfpd/iapeer/compare/v0.4.21...v0.4.22
 [0.4.21]: https://github.com/agfpd/iapeer/compare/v0.4.20...v0.4.21
 [0.4.20]: https://github.com/agfpd/iapeer/compare/v0.4.19...v0.4.20

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agfpd/iapeer",
-  "version": "0.4.22",
+  "version": "0.4.23",
   "description": "Foundation core for the iapeer multi-agent ecosystem: identity, registry, storage, codec.",
   "license": "Apache-2.0",
   "author": "agfpd",

package/src/cli/index.ts

@@ -875,6 +875,41 @@ export async function removePeerCli(
   }
 }
 
+/**
+ * `connect telegram <peer>` core — give a peer a Telegram bot face (interfaces.telegram).
+ * Shared by the `connect telegram` verb AND the `enable telegram <peer>` discoverability
+ * alias (telegram is a CHANNEL, not a marketplace plugin, so both route here, not through
+ * enableCapability). Returns the process exit code. The human owes only the token (prompted
+ * when omitted on a tty); the system does bot-add → interface → router restart.
+ */
+async function connectTelegramVerb(
+  peer: string,
+  token: string | undefined,
+  env: NodeJS.ProcessEnv,
+  out: (s: string) => void,
+  errOut: (s: string) => void,
+): Promise<number> {
+  const { connectTelegram } = await import('../connect/index.ts')
+  const r = await connectTelegram({ peer, token, env })
+  if (r.state === 'noop-same-token') {
+    out(`connect telegram ${r.peer}: ${r.detail}\n`)
+    return 0
+  }
+  if (r.state !== 'connected') {
+    errOut(`connect telegram ${r.peer}: ${r.state}${r.detail ? ` — ${r.detail}` : ''}\n`)
+    return 1
+  }
+  const rs = r.restart!
+  out(`bot ${r.username ?? `for "${r.peer}"`} added + interfaced to "${r.peer}"\n`)
+  out(
+    rs.state === 'restarted'
+      ? `router restarted — credentials loaded\n`
+      : `router restart ${rs.state}${rs.detail ? ` — ${rs.detail}` : ''} (the channel stays dead until the router restarts)\n`,
+  )
+  out(`activation: send the bot ${r.username ?? '(see @BotFather)'} its FIRST message — Telegram does not let a bot start the chat\n`)
+  return rs.state === 'restarted' ? 0 : 1
+}
+
 // ─────────────────────────────────────────────────────────────────────────────
 // rename — first-class peer-identity rename (parity with remove/create). Wraps
 // renamePeer (registry + per-cwd profile, atomic, inside the lock) and KEEPS the
@@ -1168,7 +1203,7 @@ const VERBS: ReadonlyArray<{ sig: string; desc: string }> = [
     desc: 'manual IAP send (fallback)',
   },
   { sig: '<runtime>', desc: "launch the cwd's peer FRESH; on a TTY drop into it (like attach), else detached" },
-  { sig: 'connect telegram <peer> [--token <t>]', desc: 'attach a telegram bot to a peer (bot add → interface → router restart; asks only the token)' },
+  { sig: 'connect telegram <peer> [--token <t>]', desc: 'attach a telegram bot to a peer (bot add → interface → router restart; asks only the token). Alias: `iapeer enable telegram <peer>`' },
   { sig: 'enable <plugin> [peer] [--no-setup]', desc: 'install + enable an agfpd capability for a peer' },
   {
     sig: 'new <peer> [runtime]',
@@ -2287,31 +2322,16 @@ export async function runCli(argv: string[], env: NodeJS.ProcessEnv = process.en
         // alias/bot-add/interface/router-restart are resolved by the system. The
         // FIRST message from the human to the bot activates the chat (platform rule).
         if (positionals[0] !== 'telegram' || !positionals[1]) return argErr(errOut, 'connect needs "telegram <peer>" — usage: iapeer connect telegram <peer> [--token <t>] (e.g. iapeer connect telegram boris)')
-        const { connectTelegram } = await import('../connect/index.ts')
-        const r = await connectTelegram({
-          peer: positionals[1],
-          token: typeof flags.token === 'string' ? flags.token : undefined,
-          env,
-        })
-        if (r.state === 'noop-same-token') {
-          out(`connect telegram ${r.peer}: ${r.detail}\n`)
-          return 0
-        }
-        if (r.state !== 'connected') {
-          errOut(`connect telegram ${r.peer}: ${r.state}${r.detail ? ` — ${r.detail}` : ''}\n`)
-          return 1
-        }
-        const rs = r.restart!
-        out(`bot ${r.username ?? `for "${r.peer}"`} added + interfaced to "${r.peer}"\n`)
-        out(
-          rs.state === 'restarted'
-            ? `router restarted — credentials loaded\n`
-            : `router restart ${rs.state}${rs.detail ? ` — ${rs.detail}` : ''} (the channel stays dead until the router restarts)\n`,
-        )
-        out(`activation: send the bot ${r.username ?? '(see @BotFather)'} its FIRST message — Telegram does not let a bot start the chat\n`)
-        return rs.state === 'restarted' ? 0 : 1
+        return await connectTelegramVerb(positionals[1], typeof flags.token === 'string' ? flags.token : undefined, env, out, errOut)
       }
       case 'enable': {
+        // DISCOVERABILITY ALIAS: `enable telegram <peer>` → `connect telegram <peer>`
+        // (a layperson reaches for "enable telegram"; telegram is a CHANNEL, not a
+        // marketplace plugin, so it routes to the connect flow, NOT enableCapability).
+        if (positionals[0] === 'telegram') {
+          if (!positionals[1]) return argErr(errOut, 'enable telegram needs a peer — usage: iapeer enable telegram <peer> [--token <t>] (alias of `iapeer connect telegram <peer>`)')
+          return await connectTelegramVerb(positionals[1], typeof flags.token === 'string' ? flags.token : undefined, env, out, errOut)
+        }
         // Per-peer capability install (contract Установка §3): install <plugin>@agfpd
         // per-runtime (claude project-scope IN the peer cwd / codex global) + enable +
         // call the plugin's `setup` ONLY if its iapeer.json declares it. Idempotent and