@codyswann/lisa 2.147.3 → 2.147.5

package/plugins/src/base/skills/github-validate-issue/SKILL.md

@@ -147,7 +147,7 @@ When `issue_type = Spike`, body must include:
 
 #### S7 — Parent sub-issue declared
 
-When `issue_type ∉ {Bug, Epic}`, `parent_ref` must be set. The native sub-issue link is set by `lisa:github-write-issue` Phase 6 step 3. (Validity of the parent is checked in feasibility gate F2.)
+When `issue_type ∉ {Bug, Epic}`, `parent_ref` must be set — **except for a build-ready leaf work unit**, which may stand alone. A flat `Task` / `Improvement`, or a childless `Story` / `Spike` (no open child work) with `build_ready = true`, is an independently claimable leaf per `leaf-only-lifecycle`, which states such leaves "must not be stranded"; for these a missing parent is `N/A`, not a FAIL. This mirrors the leaf carve-out already in S10/S15. A `Sub-task` is exempt from this exception — it always requires a parent. When a parent IS declared, the native sub-issue link is set by `lisa:github-write-issue` Phase 6 step 3. (Validity of a declared parent is checked in feasibility gate F2.)
 
 #### S8 — Target Backend Environment
 

package/plugins/src/base/skills/jira-validate-ticket/SKILL.md

@@ -148,7 +148,7 @@ When `issue_type = Spike`, description must include:
 
 #### S7 — Epic parent declared
 
-When `issue_type ∉ {Bug, Epic}`, `parent_key` must be set. (Validity of the key is checked in feasibility gates.)
+When `issue_type ∉ {Bug, Epic}`, `parent_key` must be set — **except for a build-ready leaf work unit**, which may stand alone. A flat `Task` / `Improvement`, or a childless `Story` / `Spike` (no open child work) with `build_ready = true`, is an independently claimable leaf per `leaf-only-lifecycle`, which states such leaves "must not be stranded"; for these a missing parent is `N/A`, not a FAIL. This mirrors the leaf carve-out already in S10/S15. A `Sub-task` is exempt from this exception — it always requires a parent. (Validity of a declared parent key is checked in feasibility gates.)
 
 #### S8 — Target Backend Environment
 

package/plugins/src/base/skills/linear-validate-issue/SKILL.md

@@ -153,6 +153,8 @@ When `issue_type ∈ {Story, Task, Improvement}` AND the item is part of an Epic
 
 For top-level Bug / Spike not under an Epic, this gate is N/A.
 
+A **build-ready leaf work unit** that is not part of an Epic context stands alone: a flat `Task` / `Improvement`, or a childless `Story` / `Spike` (no open child work) with `build_ready = true`, is an independently claimable leaf per `leaf-only-lifecycle` ("must not be stranded"), so a missing `parent_project_id` is `N/A`, not a FAIL. A `Sub-task` is exempt from this exception — it always requires `parent_issue_id`. This mirrors the leaf carve-out already in S10/S15.
+
 #### S8 — Target Backend Environment
 
 When `runtime_behavior_change = true`, description must contain `## Target Backend Environment` with one of `dev`, `staging`, `prod`. Skipped for doc-only / config-only / type-only / Epic.

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

@@ -101,18 +101,28 @@ The worker prepares the safe target and launches the CLI; it does not edit files
 
 ### 6. Bind the topic
 
-Route the topic to the dispatcher: set
-`channels.telegram.groups.<group-id>.topics.<topic-id>.agentId = <topic-slug>-dispatch`, 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 friction.
-Set it to `true` only for a shared-workspace topic where humans also coordinate with each other and
-you don't want every line to spawn a run; the group-level `requireMention` stays `true` regardless.
-See "Mention gating" in [references/repo-topic-config.md](references/repo-topic-config.md) for the
-tradeoff. The topic `systemPrompt` must state the scope mode, treat each native-reply
-root as an independent request context, confirm repo selection only in folder-scoped mode, spawn the
-worker with an explicit repo path, and return the worker result to the topic. Back up
-`~/.openclaw/openclaw.json` before editing and preserve unrelated routes.
+Route the topic to the dispatcher. In single-account Telegram configs, set
+`channels.telegram.groups.<group-id>.topics.<topic-id>.agentId = <topic-slug>-dispatch`. In
+multi-account Telegram configs, set the same route under the owning bot account:
+`channels.telegram.accounts.<account-id>.groups.<group-id>.topics.<topic-id>.agentId =
+<topic-slug>-dispatch`. Account configs do not inherit root `channels.telegram.groups` routes, so a
+root-only route can validate while the actual bot still ignores the topic-level `requireMention`,
+`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.
+
+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
+friction. Set it to `true` only for a shared-workspace topic where humans also coordinate with each
+other and you don't want every line to spawn a run; the group-level `requireMention` stays `true`
+regardless. See "Mention gating" in [references/repo-topic-config.md](references/repo-topic-config.md)
+for the tradeoff. The topic `systemPrompt` must state the scope mode, treat each native-reply root as
+an independent request context, confirm repo selection only in folder-scoped mode, spawn the worker
+with an explicit repo path, and return the worker result to the topic. If the route may return
+generated files, the prompt must also say to write or copy returnable artifacts under
+`~/.openclaw/media` before calling `message(action="send")`, because outbound local media delivery
+rejects arbitrary `/tmp` paths. Back up `~/.openclaw/openclaw.json` before editing and preserve
+unrelated routes.
 
 ### 7. Validate + self-test
 

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

@@ -70,6 +70,13 @@ repos:
 
 ## Topic route
 
+Use `channels.telegram.groups` for a single-account Telegram setup. If
+`channels.telegram.accounts` is configured, bind the route under the owning bot account instead:
+`channels.telegram.accounts.<account-id>.groups.<group-id>`. Account-scoped Telegram configs do not
+inherit root `channels.telegram.groups` routes.
+
+### Single-account route
+
 ```json5
 {
   "channels": {
@@ -99,6 +106,41 @@ repos:
 }
 ```
 
+### Multi-account route
+
+```json5
+{
+  "channels": {
+    "telegram": {
+      "accounts": {
+        "<account-id>": {
+          "groups": {
+            "<group-id>": {
+              "groupPolicy": "allowlist",
+              "requireMention": true,
+              "allowFrom": ["<telegram-user-id>"],
+              "topics": {
+                "<topic-id>": {
+                  "agentId": "<topic-slug>-dispatch",
+                  "requireMention": false,
+                  "systemPrompt": "Use the topic's configured scope mode. For single-repo, pass the fixed repo path to <topic-slug>-codex. For folder-scoped, confirm the inferred repo or repo set unless the user already named it explicitly, then pass the explicit repo path(s) to <topic-slug>-codex. Treat each native reply root as an independent request context. If generated files need to be returned as Telegram attachments, write or copy them under ~/.openclaw/media before calling message(action=\"send\"), because outbound local media delivery rejects arbitrary /tmp paths."
+                }
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+## File return path
+
+When a repo-topic agent returns generated files to Telegram, use the OpenClaw `message` tool with
+real local file paths. Write or copy returnable artifacts under `~/.openclaw/media` before sending;
+outbound local media delivery rejects arbitrary `/tmp` paths even when the file exists.
+
 ## Mention gating
 
 `requireMention` controls whether a message must @-mention the bot before the agent activates. It is

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

@@ -14,6 +14,13 @@ all unrelated agents, channels, routes, and tokens.
 
 ## Telegram — facilitator topic route
 
+Use `channels.telegram.groups` for a single-account Telegram setup. If the OpenClaw config has
+`channels.telegram.accounts`, put the route under the owning bot account at
+`channels.telegram.accounts.<account-id>.groups.<telegram-supergroup-id>`; account-scoped Telegram
+configs do not inherit root group routes.
+
+### Single-account route
+
 ```json5
 {
   "channels": {
@@ -36,6 +43,34 @@ all unrelated agents, channels, routes, and tokens.
 }
 ```
 
+### Multi-account route
+
+```json5
+{
+  "channels": {
+    "telegram": {
+      "accounts": {
+        "<account-id>": {
+          "groups": {
+            "<telegram-supergroup-id>": {
+              "groupPolicy": "allowlist",
+              "requireMention": true,
+              "allowFrom": ["<telegram-user-id>"],
+              "topics": {
+                "<facilitator-topic-id>": {
+                  "agentId": "<facilitator-agent-id>",
+                  "requireMention": true
+                }
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
 ## Slack — facilitator channel route
 
 ```json5