@codyswann/lisa 2.147.5 → 2.147.7

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

@@ -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: