@codyswann/lisa 2.147.4 → 2.147.6

package/plugins/lisa-openclaw-cursor/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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.147.4",
+  "version": "2.147.6",
   "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.4",
+  "version": "2.147.6",
   "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.4",
+  "version": "2.147.6",
   "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.4",
+  "version": "2.147.6",
   "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.4",
+  "version": "2.147.6",
   "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.4",
+  "version": "2.147.6",
   "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.4",
+  "version": "2.147.6",
   "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.4",
+  "version": "2.147.6",
   "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.4",
+  "version": "2.147.6",
   "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.4",
+  "version": "2.147.6",
   "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.4",
+  "version": "2.147.6",
   "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.4",
+  "version": "2.147.6",
   "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-agy/plugin.json

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

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

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

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

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

package/plugins/src/base/skills/repair-intake/SKILL.md

@@ -49,11 +49,15 @@ close-out** roles and moves work *unstuck* or *fully closed*:
   lifecycle label. repair-intake classifies it as a PRD or build ticket and adds the configured
   `ready` label (`prd-ready` for a PRD, build `status:ready` for a ticket) so normal intake can see
   it; if the later intake/implement gate finds the item incomplete, it moves the item to `blocked`.
-- **Missing PRD child link drift** — a GitHub PRD in `ticketed` (or another open non-product-owned
-  PRD role) has a generated-work section/comment that names top-level generated work, but the PRD's
-  native sub-issue list is missing one or more of those top-level children. repair-intake replays the
-  `prd-backlink` native-linking contract and attaches the missing same-repo top-level children
-  idempotently, so PRD rollup can rely on the native graph again.
+- **Missing native child link drift** — a GitHub parent (a `ticketed`/other open non-product-owned
+  PRD, **or a build Epic/Story container**) whose children are discoverable — from the generated-work
+  section/comment for a PRD, or from body parentage (`Parent: #<n>` / `Parent Epic: #<n>`) for a build
+  container resolved via the documented hierarchy fallback — but whose native sub-issue list is missing
+  one or more of those children. This is the common shape when children were created by an external
+  generator (e.g. Codex) or an older write path that recorded parentage only in prose and never called
+  `addSubIssue`. repair-intake replays the `prd-backlink` / `github-write-issue` native-linking contract
+  and attaches the missing same-repo children idempotently, so rollup and the GitHub UI can rely on the
+  native graph again.
 
 This skill is the symmetric counterpart to `lisa:intake`. It reuses the same queue-detection,
 the same agent-team orchestration, the same "don't ask, just run" confirmation policy, and the
@@ -467,7 +471,21 @@ left in a status it should not carry, including a stale build-ready `ready`).
 
 1. Read the child set using the vendor-native hierarchy first (GitHub sub-issues, JIRA
    Epic/parent/sub-task hierarchy, Linear project/parent/sub-issues), with the same fallbacks the
-   vendor read/sync skills document.
+   vendor read/sync skills document. **Record which children were resolved natively vs. only via the
+   prose/body-parentage fallback** — the gap between the two sets is repairable native-link drift.
+1a. **Heal native child links before rolling up (GitHub).** Whenever the resolved child set
+   contains same-repo children that are *not* in the parent's native `subIssues` graph — the typical
+   case when the children carry `Parent: #<n>` / `Parent Epic: #<n>` in prose but were never attached
+   (external generators like Codex, or an older write path) — attach each missing same-repo child as a
+   native sub-issue using the identical idempotent `addSubIssue` contract the "GitHub PRD missing child
+   links" path documents below: dedupe by `owner/repo#number`, treat "already linked" as success, keep
+   cross-repo/cross-vendor children documented-only with a warning, and on `subIssues`/`addSubIssue`
+   unavailability record a capability warning and continue. A build parent attaches the children
+   resolved by its hierarchy (its Stories/Sub-tasks), not only empty-parent-token top-level work — the
+   PRD top-level-only restriction is a PRD rule, not a build one. Record repaired refs in the rollup
+   state fingerprint so repeated cycles do not re-post. Do this even when step 2 derives `unchanged`:
+   the native graph is what the GitHub UI rollup and progress bar depend on, independently of the
+   parent's status.
 2. **Compute the derived parent state** bottom-up per the `leaf-only-lifecycle` **Parent status
    rollup** state machine, evaluated over the env ladder `in-progress < dev < staging <
    production` (the ordered keys of the env-keyed `done` map): any required child blocked →
@@ -754,9 +772,11 @@ It MAY:
   applies only to containers, never to leaves.
 - Move a PRD with fully terminal generated work to `shipped` and close/archive the source artifact
   where the source vendor supports native close-out, per `prd-lifecycle-rollup`.
-- Repair missing native GitHub PRD child links from the generated-work fallback by replaying the
-  `prd-backlink` top-level-only, same-repo, idempotent `addSubIssue` contract. This repairs
-  structure only; it does not ship or verify the PRD.
+- Repair missing native GitHub child links by replaying the same-repo, idempotent `addSubIssue`
+  contract — for a **PRD** from the generated-work fallback (top-level-only), and for a **build
+  Epic/Story container** from its hierarchy/body-parentage children — so rollup and the GitHub UI can
+  rely on the native graph. This repairs structure only; it does not ship, transition, or verify the
+  parent.
 - Normalize a GitHub issue with no configured lifecycle label by adding the configured PRD or build
   `ready` label after classifying the issue. This is a visibility repair, not a claim; the item
   remains open and unclaimed for normal intake.
@@ -779,13 +799,16 @@ It MUST NOT:
 1. **Resolve the queue** — detect vendor/lifecycle (Source dispatch); resolve stuck role names
    from config. For JIRA, confirm the needed transitions are reachable; stop on misconfig.
 2. **Enumerate repair candidates** — query in-progress role(s), `blocked` role(s), terminal/open
-   items, GitHub PRDs whose generated-work fallback names top-level children missing from native
-   sub-issues, rollup parents/PRDs with child work, **containers carrying the `ready` role** (a
+   items, GitHub parents (PRDs **and build Epic/Story containers**) whose discoverable children —
+   generated-work fallback for a PRD, hierarchy/body-parentage for a build container — are missing from
+   their native sub-issue graph, rollup parents/PRDs with child work, **containers carrying the `ready`
+   role** (a
    leaf-only-invariant violation to reconcile), and GitHub issues with no configured lifecycle label,
    for the detected lifecycle(s), up to `max_candidates`, via the Access layer reads.
 3. **Order deterministically**, highest repair-confidence first:
    1. terminal-labeled items that only need native close / complete / resolve,
-   2. GitHub PRDs missing native links for generated top-level work (structure-only repair),
+   2. GitHub parents (PRDs missing native links for generated top-level work, or build Epic/Story
+      containers missing native links for prose/hierarchy children) needing structure-only repair,
    3. rollup parents/PRDs whose child sets are all terminal (close-out),
    4. rollup parents whose children have advanced to an intermediate env, or stale-`ready`
       containers, that need their derived state applied (status-only reconciliation, no native
@@ -826,8 +849,8 @@ Report outcomes in these buckets:
 - `rolled_up` — parent/container/PRD rollups advanced to their derived state: an intermediate env
   (e.g. all children at `On Stg` → parent `On Stg`), a fully-terminal close-out, or a stale-`ready`
   container reconciled from its children.
-- `relinked` — GitHub PRDs whose missing native sub-issue links were repaired from the
-  generated-work fallback.
+- `relinked` — GitHub parents (PRDs from the generated-work fallback, or build Epic/Story containers
+  from hierarchy/body-parentage) whose missing native sub-issue links were attached.
 - `normalized_ready` — GitHub issues missing official lifecycle labels that were classified and
   given the configured PRD/build `ready` label so normal intake can claim them.
 - `still_blocked` — examined and intentionally left `blocked`, with the active reason.

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