@codyswann/lisa 2.147.6 → 2.147.7

package/package.json

@@ -84,7 +84,7 @@
     "lodash": ">=4.18.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {

package/plugins/lisa/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "AWS CDK-specific Lisa plugin.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cdk-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "NestJS-specific skills and migration write-protection hooks.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/skills/lisa-openclaw-connect-repo-topic/SKILL.md

@@ -110,6 +110,11 @@ root-only route can validate while the actual bot still ignores the topic-level
 `agentId`, and prompt. When in doubt, mirror the route under the owning account and keep any existing
 root group route only as a fallback/documentation shape.
 
+Account-scoped topic `agentId` routes also require an OpenClaw runtime that treats the topic agent as
+an explicit group route for non-default Telegram accounts. If the self-test logs
+`drop non-default account requires explicit binding`, update or rebuild OpenClaw before adding config
+workarounds; do not create persistent ACP bindings solely to bypass that guard.
+
 Keep allowlist policy, and add `allowFrom` only when membership must be narrower than the group.
 Leave the topic-level `requireMention = false` (the default) so the agent activates on any message —
 the topic is bound 1:1 to this dispatcher, so an @mention carries no routing information and is pure
@@ -137,11 +142,14 @@ Then from the target topic, send a plain message with **no** @mention (the defau
 `requireMention = false` means the agent must activate without one) asking for an exact-token reply
 with **no** file changes, commits, PRs, or merges, e.g. `reply with exactly TELEGRAM-ROUTE-OK`.
 Confirm the visible reply, that the dispatcher spawned the worker, and that the worker ran in the
-intended repo. If the topic was deliberately left at `requireMention = true`, mention the bot instead
-(`<bot-handle> reply with exactly TELEGRAM-ROUTE-OK`) and additionally confirm that an un-mentioned
-message is **ignored**. For folder-scoped topics, also send a request that implies but doesn't name a
-repo and confirm the dispatcher asks for confirmation before proceeding. Do **not** treat `openclaw agent --agent
-<id> ...` as proof a topic route works — use the visible topic reply.
+intended repo. If there is no dispatcher session, inspect `/tmp/openclaw/openclaw-YYYY-MM-DD.log`;
+`drop non-default account requires explicit binding` means the OpenClaw runtime is too old for
+account-scoped topic-agent routing. If the topic was deliberately left at `requireMention = true`,
+mention the bot instead (`<bot-handle> reply with exactly TELEGRAM-ROUTE-OK`) and additionally
+confirm that an un-mentioned message is **ignored**. For folder-scoped topics, also send a request
+that implies but doesn't name a repo and confirm the dispatcher asks for confirmation before
+proceeding. Do **not** treat `openclaw agent --agent <id> ...` as proof a topic route works — use the
+visible topic reply.
 
 ## Output standard
 

package/plugins/lisa-openclaw/skills/lisa-openclaw-connect-repo-topic/references/repo-topic-config.md

@@ -75,6 +75,12 @@ Use `channels.telegram.groups` for a single-account Telegram setup. If
 `channels.telegram.accounts.<account-id>.groups.<group-id>`. Account-scoped Telegram configs do not
 inherit root `channels.telegram.groups` routes.
 
+Account-scoped topic `agentId` routes require an OpenClaw runtime that treats the topic agent as an
+explicit group route for non-default Telegram accounts. If a real topic self-test is delivered to the
+bot but the logs show `drop non-default account requires explicit binding`, update or rebuild
+OpenClaw. Do not add a persistent ACP binding as a workaround; the configured topic `agentId` is the
+intended route.
+
 ### Single-account route
 
 ```json5

package/plugins/lisa-openclaw/skills/lisa-openclaw-connect-staff/references/platform-routing.md

@@ -19,6 +19,11 @@ Use `channels.telegram.groups` for a single-account Telegram setup. If the OpenC
 `channels.telegram.accounts.<account-id>.groups.<telegram-supergroup-id>`; account-scoped Telegram
 configs do not inherit root group routes.
 
+Account-scoped topic `agentId` routes require an OpenClaw runtime that treats the topic agent as an
+explicit group route for non-default Telegram accounts. If a real Telegram topic test reaches the bot
+but logs `drop non-default account requires explicit binding`, update or rebuild OpenClaw before
+adding config workarounds; the topic `agentId` is the intended route.
+
 ### Single-account route
 
 ```json5

package/plugins/lisa-openclaw/skills/lisa-openclaw-setup/SKILL.md

@@ -83,6 +83,9 @@ loudly, do not silently proceed) if any is missing:
   root (Slack channel + root `thread_ts`; Telegram supergroup + forum topic + root `message_id`), and
   replies in that thread continue the same session, so concurrent threads don't share short-term
   context.
+- **Account-scoped Telegram topic agents** — in multi-account Telegram configs,
+  `channels.telegram.accounts.<account-id>.groups.<group-id>.topics.<topic-id>.agentId` routes group
+  messages as an explicit topic route instead of dropping them as a non-default account fallback.
 - **`NO_REPLY` sentinel** — after an agent sends a message with the platform message tool, returning
   exactly `NO_REPLY` as its assistant final prevents the gateway from posting a duplicate loose
   message.

package/plugins/lisa-openclaw-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-agy/skills/lisa-openclaw-connect-repo-topic/SKILL.md

@@ -110,6 +110,11 @@ root-only route can validate while the actual bot still ignores the topic-level
 `agentId`, and prompt. When in doubt, mirror the route under the owning account and keep any existing
 root group route only as a fallback/documentation shape.
 
+Account-scoped topic `agentId` routes also require an OpenClaw runtime that treats the topic agent as
+an explicit group route for non-default Telegram accounts. If the self-test logs
+`drop non-default account requires explicit binding`, update or rebuild OpenClaw before adding config
+workarounds; do not create persistent ACP bindings solely to bypass that guard.
+
 Keep allowlist policy, and add `allowFrom` only when membership must be narrower than the group.
 Leave the topic-level `requireMention = false` (the default) so the agent activates on any message —
 the topic is bound 1:1 to this dispatcher, so an @mention carries no routing information and is pure
@@ -137,11 +142,14 @@ Then from the target topic, send a plain message with **no** @mention (the defau
 `requireMention = false` means the agent must activate without one) asking for an exact-token reply
 with **no** file changes, commits, PRs, or merges, e.g. `reply with exactly TELEGRAM-ROUTE-OK`.
 Confirm the visible reply, that the dispatcher spawned the worker, and that the worker ran in the
-intended repo. If the topic was deliberately left at `requireMention = true`, mention the bot instead
-(`<bot-handle> reply with exactly TELEGRAM-ROUTE-OK`) and additionally confirm that an un-mentioned
-message is **ignored**. For folder-scoped topics, also send a request that implies but doesn't name a
-repo and confirm the dispatcher asks for confirmation before proceeding. Do **not** treat `openclaw agent --agent
-<id> ...` as proof a topic route works — use the visible topic reply.
+intended repo. If there is no dispatcher session, inspect `/tmp/openclaw/openclaw-YYYY-MM-DD.log`;
+`drop non-default account requires explicit binding` means the OpenClaw runtime is too old for
+account-scoped topic-agent routing. If the topic was deliberately left at `requireMention = true`,
+mention the bot instead (`<bot-handle> reply with exactly TELEGRAM-ROUTE-OK`) and additionally
+confirm that an un-mentioned message is **ignored**. For folder-scoped topics, also send a request
+that implies but doesn't name a repo and confirm the dispatcher asks for confirmation before
+proceeding. Do **not** treat `openclaw agent --agent <id> ...` as proof a topic route works — use the
+visible topic reply.
 
 ## Output standard
 

package/plugins/lisa-openclaw-agy/skills/lisa-openclaw-connect-repo-topic/references/repo-topic-config.md

@@ -75,6 +75,12 @@ Use `channels.telegram.groups` for a single-account Telegram setup. If
 `channels.telegram.accounts.<account-id>.groups.<group-id>`. Account-scoped Telegram configs do not
 inherit root `channels.telegram.groups` routes.
 
+Account-scoped topic `agentId` routes require an OpenClaw runtime that treats the topic agent as an
+explicit group route for non-default Telegram accounts. If a real topic self-test is delivered to the
+bot but the logs show `drop non-default account requires explicit binding`, update or rebuild
+OpenClaw. Do not add a persistent ACP binding as a workaround; the configured topic `agentId` is the
+intended route.
+
 ### Single-account route
 
 ```json5

package/plugins/lisa-openclaw-agy/skills/lisa-openclaw-connect-staff/references/platform-routing.md

@@ -19,6 +19,11 @@ Use `channels.telegram.groups` for a single-account Telegram setup. If the OpenC
 `channels.telegram.accounts.<account-id>.groups.<telegram-supergroup-id>`; account-scoped Telegram
 configs do not inherit root group routes.
 
+Account-scoped topic `agentId` routes require an OpenClaw runtime that treats the topic agent as an
+explicit group route for non-default Telegram accounts. If a real Telegram topic test reaches the bot
+but logs `drop non-default account requires explicit binding`, update or rebuild OpenClaw before
+adding config workarounds; the topic `agentId` is the intended route.
+
 ### Single-account route
 
 ```json5

package/plugins/lisa-openclaw-agy/skills/lisa-openclaw-setup/SKILL.md

@@ -83,6 +83,9 @@ loudly, do not silently proceed) if any is missing:
   root (Slack channel + root `thread_ts`; Telegram supergroup + forum topic + root `message_id`), and
   replies in that thread continue the same session, so concurrent threads don't share short-term
   context.
+- **Account-scoped Telegram topic agents** — in multi-account Telegram configs,
+  `channels.telegram.accounts.<account-id>.groups.<group-id>.topics.<topic-id>.agentId` routes group
+  messages as an explicit topic route instead of dropping them as a non-default account fallback.
 - **`NO_REPLY` sentinel** — after an agent sends a message with the platform message tool, returning
   exactly `NO_REPLY` as its assistant final prevents the gateway from posting a duplicate loose
   message.

package/plugins/lisa-openclaw-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-copilot/skills/lisa-openclaw-connect-repo-topic/SKILL.md

@@ -110,6 +110,11 @@ root-only route can validate while the actual bot still ignores the topic-level
 `agentId`, and prompt. When in doubt, mirror the route under the owning account and keep any existing
 root group route only as a fallback/documentation shape.
 
+Account-scoped topic `agentId` routes also require an OpenClaw runtime that treats the topic agent as
+an explicit group route for non-default Telegram accounts. If the self-test logs
+`drop non-default account requires explicit binding`, update or rebuild OpenClaw before adding config
+workarounds; do not create persistent ACP bindings solely to bypass that guard.
+
 Keep allowlist policy, and add `allowFrom` only when membership must be narrower than the group.
 Leave the topic-level `requireMention = false` (the default) so the agent activates on any message —
 the topic is bound 1:1 to this dispatcher, so an @mention carries no routing information and is pure
@@ -137,11 +142,14 @@ Then from the target topic, send a plain message with **no** @mention (the defau
 `requireMention = false` means the agent must activate without one) asking for an exact-token reply
 with **no** file changes, commits, PRs, or merges, e.g. `reply with exactly TELEGRAM-ROUTE-OK`.
 Confirm the visible reply, that the dispatcher spawned the worker, and that the worker ran in the
-intended repo. If the topic was deliberately left at `requireMention = true`, mention the bot instead
-(`<bot-handle> reply with exactly TELEGRAM-ROUTE-OK`) and additionally confirm that an un-mentioned
-message is **ignored**. For folder-scoped topics, also send a request that implies but doesn't name a
-repo and confirm the dispatcher asks for confirmation before proceeding. Do **not** treat `openclaw agent --agent
-<id> ...` as proof a topic route works — use the visible topic reply.
+intended repo. If there is no dispatcher session, inspect `/tmp/openclaw/openclaw-YYYY-MM-DD.log`;
+`drop non-default account requires explicit binding` means the OpenClaw runtime is too old for
+account-scoped topic-agent routing. If the topic was deliberately left at `requireMention = true`,
+mention the bot instead (`<bot-handle> reply with exactly TELEGRAM-ROUTE-OK`) and additionally
+confirm that an un-mentioned message is **ignored**. For folder-scoped topics, also send a request
+that implies but doesn't name a repo and confirm the dispatcher asks for confirmation before
+proceeding. Do **not** treat `openclaw agent --agent <id> ...` as proof a topic route works — use the
+visible topic reply.
 
 ## Output standard
 

package/plugins/lisa-openclaw-copilot/skills/lisa-openclaw-connect-repo-topic/references/repo-topic-config.md

@@ -75,6 +75,12 @@ Use `channels.telegram.groups` for a single-account Telegram setup. If
 `channels.telegram.accounts.<account-id>.groups.<group-id>`. Account-scoped Telegram configs do not
 inherit root `channels.telegram.groups` routes.
 
+Account-scoped topic `agentId` routes require an OpenClaw runtime that treats the topic agent as an
+explicit group route for non-default Telegram accounts. If a real topic self-test is delivered to the
+bot but the logs show `drop non-default account requires explicit binding`, update or rebuild
+OpenClaw. Do not add a persistent ACP binding as a workaround; the configured topic `agentId` is the
+intended route.
+
 ### Single-account route
 
 ```json5

package/plugins/lisa-openclaw-copilot/skills/lisa-openclaw-connect-staff/references/platform-routing.md

@@ -19,6 +19,11 @@ Use `channels.telegram.groups` for a single-account Telegram setup. If the OpenC
 `channels.telegram.accounts.<account-id>.groups.<telegram-supergroup-id>`; account-scoped Telegram
 configs do not inherit root group routes.
 
+Account-scoped topic `agentId` routes require an OpenClaw runtime that treats the topic agent as an
+explicit group route for non-default Telegram accounts. If a real Telegram topic test reaches the bot
+but logs `drop non-default account requires explicit binding`, update or rebuild OpenClaw before
+adding config workarounds; the topic `agentId` is the intended route.
+
 ### Single-account route
 
 ```json5

package/plugins/lisa-openclaw-copilot/skills/lisa-openclaw-setup/SKILL.md

@@ -83,6 +83,9 @@ loudly, do not silently proceed) if any is missing:
   root (Slack channel + root `thread_ts`; Telegram supergroup + forum topic + root `message_id`), and
   replies in that thread continue the same session, so concurrent threads don't share short-term
   context.
+- **Account-scoped Telegram topic agents** — in multi-account Telegram configs,
+  `channels.telegram.accounts.<account-id>.groups.<group-id>.topics.<topic-id>.agentId` routes group
+  messages as an explicit topic route instead of dropping them as a non-default account fallback.
 - **`NO_REPLY` sentinel** — after an agent sends a message with the platform message tool, returning
   exactly `NO_REPLY` as its assistant final prevents the gateway from posting a duplicate loose
   message.

package/plugins/lisa-openclaw-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-cursor/skills/lisa-openclaw-connect-repo-topic/SKILL.md

@@ -110,6 +110,11 @@ root-only route can validate while the actual bot still ignores the topic-level
 `agentId`, and prompt. When in doubt, mirror the route under the owning account and keep any existing
 root group route only as a fallback/documentation shape.
 
+Account-scoped topic `agentId` routes also require an OpenClaw runtime that treats the topic agent as
+an explicit group route for non-default Telegram accounts. If the self-test logs
+`drop non-default account requires explicit binding`, update or rebuild OpenClaw before adding config
+workarounds; do not create persistent ACP bindings solely to bypass that guard.
+
 Keep allowlist policy, and add `allowFrom` only when membership must be narrower than the group.
 Leave the topic-level `requireMention = false` (the default) so the agent activates on any message —
 the topic is bound 1:1 to this dispatcher, so an @mention carries no routing information and is pure
@@ -137,11 +142,14 @@ Then from the target topic, send a plain message with **no** @mention (the defau
 `requireMention = false` means the agent must activate without one) asking for an exact-token reply
 with **no** file changes, commits, PRs, or merges, e.g. `reply with exactly TELEGRAM-ROUTE-OK`.
 Confirm the visible reply, that the dispatcher spawned the worker, and that the worker ran in the
-intended repo. If the topic was deliberately left at `requireMention = true`, mention the bot instead
-(`<bot-handle> reply with exactly TELEGRAM-ROUTE-OK`) and additionally confirm that an un-mentioned
-message is **ignored**. For folder-scoped topics, also send a request that implies but doesn't name a
-repo and confirm the dispatcher asks for confirmation before proceeding. Do **not** treat `openclaw agent --agent
-<id> ...` as proof a topic route works — use the visible topic reply.
+intended repo. If there is no dispatcher session, inspect `/tmp/openclaw/openclaw-YYYY-MM-DD.log`;
+`drop non-default account requires explicit binding` means the OpenClaw runtime is too old for
+account-scoped topic-agent routing. If the topic was deliberately left at `requireMention = true`,
+mention the bot instead (`<bot-handle> reply with exactly TELEGRAM-ROUTE-OK`) and additionally
+confirm that an un-mentioned message is **ignored**. For folder-scoped topics, also send a request
+that implies but doesn't name a repo and confirm the dispatcher asks for confirmation before
+proceeding. Do **not** treat `openclaw agent --agent <id> ...` as proof a topic route works — use the
+visible topic reply.
 
 ## Output standard
 

package/plugins/lisa-openclaw-cursor/skills/lisa-openclaw-connect-repo-topic/references/repo-topic-config.md

@@ -75,6 +75,12 @@ Use `channels.telegram.groups` for a single-account Telegram setup. If
 `channels.telegram.accounts.<account-id>.groups.<group-id>`. Account-scoped Telegram configs do not
 inherit root `channels.telegram.groups` routes.
 
+Account-scoped topic `agentId` routes require an OpenClaw runtime that treats the topic agent as an
+explicit group route for non-default Telegram accounts. If a real topic self-test is delivered to the
+bot but the logs show `drop non-default account requires explicit binding`, update or rebuild
+OpenClaw. Do not add a persistent ACP binding as a workaround; the configured topic `agentId` is the
+intended route.
+
 ### Single-account route
 
 ```json5

package/plugins/lisa-openclaw-cursor/skills/lisa-openclaw-connect-staff/references/platform-routing.md

@@ -19,6 +19,11 @@ Use `channels.telegram.groups` for a single-account Telegram setup. If the OpenC
 `channels.telegram.accounts.<account-id>.groups.<telegram-supergroup-id>`; account-scoped Telegram
 configs do not inherit root group routes.
 
+Account-scoped topic `agentId` routes require an OpenClaw runtime that treats the topic agent as an
+explicit group route for non-default Telegram accounts. If a real Telegram topic test reaches the bot
+but logs `drop non-default account requires explicit binding`, update or rebuild OpenClaw before
+adding config workarounds; the topic `agentId` is the intended route.
+
 ### Single-account route
 
 ```json5

package/plugins/lisa-openclaw-cursor/skills/lisa-openclaw-setup/SKILL.md

@@ -83,6 +83,9 @@ loudly, do not silently proceed) if any is missing:
   root (Slack channel + root `thread_ts`; Telegram supergroup + forum topic + root `message_id`), and
   replies in that thread continue the same session, so concurrent threads don't share short-term
   context.
+- **Account-scoped Telegram topic agents** — in multi-account Telegram configs,
+  `channels.telegram.accounts.<account-id>.groups.<group-id>.topics.<topic-id>.agentId` routes group
+  messages as an explicit topic route instead of dropping them as a non-default account fallback.
 - **`NO_REPLY` sentinel** — after an agent sends a message with the platform message tool, returning
   exactly `NO_REPLY` as its assistant final prevents the gateway from posting a duplicate loose
   message.

package/plugins/lisa-rails/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/scripts/ingest_slack_channel.py

@@ -57,12 +57,12 @@ TOKEN_PATTERNS = [
 
 
 def utc_now() -> dt.datetime:
-    return dt.datetime.now(dt.UTC).replace(microsecond=0)
+    return dt.datetime.now(dt.timezone.utc).replace(microsecond=0)
 
 
 def iso_from_ts(ts: str) -> str:
     seconds = float(ts)
-    return dt.datetime.fromtimestamp(seconds, dt.UTC).replace(microsecond=0).isoformat().replace("+00:00", "Z")
+    return dt.datetime.fromtimestamp(seconds, dt.timezone.utc).replace(microsecond=0).isoformat().replace("+00:00", "Z")
 
 
 def ts_from_input(value: str | None) -> str | None:

package/plugins/lisa-wiki-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-agy/scripts/ingest_slack_channel.py

@@ -57,12 +57,12 @@ TOKEN_PATTERNS = [
 
 
 def utc_now() -> dt.datetime:
-    return dt.datetime.now(dt.UTC).replace(microsecond=0)
+    return dt.datetime.now(dt.timezone.utc).replace(microsecond=0)
 
 
 def iso_from_ts(ts: str) -> str:
     seconds = float(ts)
-    return dt.datetime.fromtimestamp(seconds, dt.UTC).replace(microsecond=0).isoformat().replace("+00:00", "Z")
+    return dt.datetime.fromtimestamp(seconds, dt.timezone.utc).replace(microsecond=0).isoformat().replace("+00:00", "Z")
 
 
 def ts_from_input(value: str | None) -> str | None:

package/plugins/lisa-wiki-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-copilot/scripts/ingest_slack_channel.py

@@ -57,12 +57,12 @@ TOKEN_PATTERNS = [
 
 
 def utc_now() -> dt.datetime:
-    return dt.datetime.now(dt.UTC).replace(microsecond=0)
+    return dt.datetime.now(dt.timezone.utc).replace(microsecond=0)
 
 
 def iso_from_ts(ts: str) -> str:
     seconds = float(ts)
-    return dt.datetime.fromtimestamp(seconds, dt.UTC).replace(microsecond=0).isoformat().replace("+00:00", "Z")
+    return dt.datetime.fromtimestamp(seconds, dt.timezone.utc).replace(microsecond=0).isoformat().replace("+00:00", "Z")
 
 
 def ts_from_input(value: str | None) -> str | None:

package/plugins/lisa-wiki-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.147.6",
+  "version": "2.147.7",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-cursor/scripts/ingest_slack_channel.py

@@ -57,12 +57,12 @@ TOKEN_PATTERNS = [
 
 
 def utc_now() -> dt.datetime:
-    return dt.datetime.now(dt.UTC).replace(microsecond=0)
+    return dt.datetime.now(dt.timezone.utc).replace(microsecond=0)
 
 
 def iso_from_ts(ts: str) -> str:
     seconds = float(ts)
-    return dt.datetime.fromtimestamp(seconds, dt.UTC).replace(microsecond=0).isoformat().replace("+00:00", "Z")
+    return dt.datetime.fromtimestamp(seconds, dt.timezone.utc).replace(microsecond=0).isoformat().replace("+00:00", "Z")
 
 
 def ts_from_input(value: str | None) -> str | None:

package/plugins/src/openclaw/skills/lisa-openclaw-connect-repo-topic/SKILL.md

@@ -110,6 +110,11 @@ root-only route can validate while the actual bot still ignores the topic-level
 `agentId`, and prompt. When in doubt, mirror the route under the owning account and keep any existing
 root group route only as a fallback/documentation shape.
 
+Account-scoped topic `agentId` routes also require an OpenClaw runtime that treats the topic agent as
+an explicit group route for non-default Telegram accounts. If the self-test logs
+`drop non-default account requires explicit binding`, update or rebuild OpenClaw before adding config
+workarounds; do not create persistent ACP bindings solely to bypass that guard.
+
 Keep allowlist policy, and add `allowFrom` only when membership must be narrower than the group.
 Leave the topic-level `requireMention = false` (the default) so the agent activates on any message —
 the topic is bound 1:1 to this dispatcher, so an @mention carries no routing information and is pure
@@ -137,11 +142,14 @@ Then from the target topic, send a plain message with **no** @mention (the defau
 `requireMention = false` means the agent must activate without one) asking for an exact-token reply
 with **no** file changes, commits, PRs, or merges, e.g. `reply with exactly TELEGRAM-ROUTE-OK`.
 Confirm the visible reply, that the dispatcher spawned the worker, and that the worker ran in the
-intended repo. If the topic was deliberately left at `requireMention = true`, mention the bot instead
-(`<bot-handle> reply with exactly TELEGRAM-ROUTE-OK`) and additionally confirm that an un-mentioned
-message is **ignored**. For folder-scoped topics, also send a request that implies but doesn't name a
-repo and confirm the dispatcher asks for confirmation before proceeding. Do **not** treat `openclaw agent --agent
-<id> ...` as proof a topic route works — use the visible topic reply.
+intended repo. If there is no dispatcher session, inspect `/tmp/openclaw/openclaw-YYYY-MM-DD.log`;
+`drop non-default account requires explicit binding` means the OpenClaw runtime is too old for
+account-scoped topic-agent routing. If the topic was deliberately left at `requireMention = true`,
+mention the bot instead (`<bot-handle> reply with exactly TELEGRAM-ROUTE-OK`) and additionally
+confirm that an un-mentioned message is **ignored**. For folder-scoped topics, also send a request
+that implies but doesn't name a repo and confirm the dispatcher asks for confirmation before
+proceeding. Do **not** treat `openclaw agent --agent <id> ...` as proof a topic route works — use the
+visible topic reply.
 
 ## Output standard
 

package/plugins/src/openclaw/skills/lisa-openclaw-connect-repo-topic/references/repo-topic-config.md

@@ -75,6 +75,12 @@ Use `channels.telegram.groups` for a single-account Telegram setup. If
 `channels.telegram.accounts.<account-id>.groups.<group-id>`. Account-scoped Telegram configs do not
 inherit root `channels.telegram.groups` routes.
 
+Account-scoped topic `agentId` routes require an OpenClaw runtime that treats the topic agent as an
+explicit group route for non-default Telegram accounts. If a real topic self-test is delivered to the
+bot but the logs show `drop non-default account requires explicit binding`, update or rebuild
+OpenClaw. Do not add a persistent ACP binding as a workaround; the configured topic `agentId` is the
+intended route.
+
 ### Single-account route
 
 ```json5

package/plugins/src/openclaw/skills/lisa-openclaw-connect-staff/references/platform-routing.md

@@ -19,6 +19,11 @@ Use `channels.telegram.groups` for a single-account Telegram setup. If the OpenC
 `channels.telegram.accounts.<account-id>.groups.<telegram-supergroup-id>`; account-scoped Telegram
 configs do not inherit root group routes.
 
+Account-scoped topic `agentId` routes require an OpenClaw runtime that treats the topic agent as an
+explicit group route for non-default Telegram accounts. If a real Telegram topic test reaches the bot
+but logs `drop non-default account requires explicit binding`, update or rebuild OpenClaw before
+adding config workarounds; the topic `agentId` is the intended route.
+
 ### Single-account route
 
 ```json5

package/plugins/src/openclaw/skills/lisa-openclaw-setup/SKILL.md

@@ -83,6 +83,9 @@ loudly, do not silently proceed) if any is missing:
   root (Slack channel + root `thread_ts`; Telegram supergroup + forum topic + root `message_id`), and
   replies in that thread continue the same session, so concurrent threads don't share short-term
   context.
+- **Account-scoped Telegram topic agents** — in multi-account Telegram configs,
+  `channels.telegram.accounts.<account-id>.groups.<group-id>.topics.<topic-id>.agentId` routes group
+  messages as an explicit topic route instead of dropping them as a non-default account fallback.
 - **`NO_REPLY` sentinel** — after an agent sends a message with the platform message tool, returning
   exactly `NO_REPLY` as its assistant final prevents the gateway from posting a duplicate loose
   message.

package/plugins/src/wiki/scripts/ingest_slack_channel.py

@@ -57,12 +57,12 @@ TOKEN_PATTERNS = [
 
 
 def utc_now() -> dt.datetime:
-    return dt.datetime.now(dt.UTC).replace(microsecond=0)
+    return dt.datetime.now(dt.timezone.utc).replace(microsecond=0)
 
 
 def iso_from_ts(ts: str) -> str:
     seconds = float(ts)
-    return dt.datetime.fromtimestamp(seconds, dt.UTC).replace(microsecond=0).isoformat().replace("+00:00", "Z")
+    return dt.datetime.fromtimestamp(seconds, dt.timezone.utc).replace(microsecond=0).isoformat().replace("+00:00", "Z")
 
 
 def ts_from_input(value: str | None) -> str | None: