@codyswann/lisa 2.147.6 → 2.148.0

package/dist/migrations/ensure-jest-rn-mock-accessibility-manager.d.ts

@@ -0,0 +1,38 @@
+import type { Migration, MigrationContext, MigrationResult } from "./migration.interface.js";
+/**
+ * Migration: add the RN 0.85 `AccessibilityManager` TurboModule mock to an
+ * existing project's `jest.config.react-native-mock.js`.
+ *
+ * That file is create-only, so Lisa never overwrites it once a project has been
+ * scaffolded. Projects created before the AccessibilityManager mock was added to
+ * the template therefore keep a stale copy. After the Expo SDK 56 / React Native
+ * 0.85 upgrade, `AccessibilityInfo` eagerly reads the `AccessibilityManager`
+ * TurboModule; without the mock it resolves to null and every test suite that
+ * touches accessibility crashes the Jest worker with
+ * "NativeAccessibilityManagerIOS is not available".
+ *
+ * Idempotent and conservative: only acts on Expo projects whose mock file exists,
+ * still exposes the `module.exports = {` registry anchor, and does not already
+ * define `AccessibilityManager`. The block is inserted as the first registry
+ * entry so it is unaffected by any project-specific module mocks that follow.
+ */
+export declare class EnsureJestRnMockAccessibilityManagerMigration implements Migration {
+    readonly name = "ensure-jest-rn-mock-accessibility-manager";
+    readonly description = "Add the RN 0.85 AccessibilityManager TurboModule mock to jest.config.react-native-mock.js";
+    /**
+     * Applies to Expo projects whose create-only mock file exists, exposes the
+     * registry anchor, and does not already define the AccessibilityManager mock.
+     * @param ctx - Migration context
+     * @returns True when the mock is missing and can be safely inserted
+     */
+    applies(ctx: MigrationContext): Promise<boolean>;
+    /**
+     * Insert the AccessibilityManager mock block immediately after the
+     * `module.exports = {` anchor. Re-checks the marker so the operation is
+     * idempotent even if `applies` and `apply` are called out of step.
+     * @param ctx - Migration context
+     * @returns Result describing the action taken
+     */
+    apply(ctx: MigrationContext): Promise<MigrationResult>;
+}
+//# sourceMappingURL=ensure-jest-rn-mock-accessibility-manager.d.ts.map

package/dist/migrations/ensure-jest-rn-mock-accessibility-manager.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"ensure-jest-rn-mock-accessibility-manager.d.ts","sourceRoot":"","sources":["../../src/migrations/ensure-jest-rn-mock-accessibility-manager.ts"],"names":[],"mappings":"AAEA,OAAO,KAAK,EACV,SAAS,EACT,gBAAgB,EAChB,eAAe,EAChB,MAAM,0BAA0B,CAAC;AAuClC;;;;;;;;;;;;;;;;GAgBG;AACH,qBAAa,6CAA8C,YAAW,SAAS;IAC7E,QAAQ,CAAC,IAAI,+CAA+C;IAC5D,QAAQ,CAAC,WAAW,+FAC0E;IAE9F;;;;;OAKG;IACG,OAAO,CAAC,GAAG,EAAE,gBAAgB,GAAG,OAAO,CAAC,OAAO,CAAC;IAYtD;;;;;;OAMG;IACG,KAAK,CAAC,GAAG,EAAE,gBAAgB,GAAG,OAAO,CAAC,eAAe,CAAC;CAqC7D"}

package/dist/migrations/ensure-jest-rn-mock-accessibility-manager.js

@@ -0,0 +1,110 @@
+import * as path from "node:path";
+import * as fse from "fs-extra";
+const MOCK_FILE = "jest.config.react-native-mock.js";
+/** Anchor marking the start of the mocked TurboModule registry object */
+const ANCHOR = "module.exports = {\n";
+/** Presence of this key means the AccessibilityManager mock is already wired */
+const MARKER = "AccessibilityManager:";
+/**
+ * The AccessibilityManager TurboModule mock block, inserted as the first entry
+ * of the mocked module registry. Kept byte-for-byte in sync with the
+ * `expo/create-only/jest.config.react-native-mock.js` template.
+ */
+const ACCESSIBILITY_MANAGER_BLOCK = `  // SDK 56 / RN 0.85: AccessibilityInfo eagerly reads the AccessibilityManager
+  // TurboModule. Without a mock the module resolves to null and AccessibilityInfo
+  // methods reject with "NativeAccessibilityManagerIOS is not available", which
+  // the unhandledRejection handler escalates into a Jest worker crash that takes
+  // down every suite touching accessibility.
+  AccessibilityManager: {
+    getCurrentBoldTextState: onSuccess => onSuccess(false),
+    getCurrentGrayscaleState: onSuccess => onSuccess(false),
+    getCurrentInvertColorsState: onSuccess => onSuccess(false),
+    getCurrentReduceMotionState: onSuccess => onSuccess(false),
+    getCurrentDarkerSystemColorsState: onSuccess => onSuccess(false),
+    getCurrentPrefersCrossFadeTransitionsState: onSuccess => onSuccess(false),
+    getCurrentReduceTransparencyState: onSuccess => onSuccess(false),
+    getCurrentVoiceOverState: onSuccess => onSuccess(false),
+    setAccessibilityContentSizeMultipliers: () => {},
+    setAccessibilityFocus: () => {},
+    announceForAccessibility: () => {},
+    announceForAccessibilityWithOptions: () => {},
+    addListener: () => {},
+    removeListeners: () => {},
+    getConstants: () => ({}),
+  },
+`;
+/**
+ * Migration: add the RN 0.85 `AccessibilityManager` TurboModule mock to an
+ * existing project's `jest.config.react-native-mock.js`.
+ *
+ * That file is create-only, so Lisa never overwrites it once a project has been
+ * scaffolded. Projects created before the AccessibilityManager mock was added to
+ * the template therefore keep a stale copy. After the Expo SDK 56 / React Native
+ * 0.85 upgrade, `AccessibilityInfo` eagerly reads the `AccessibilityManager`
+ * TurboModule; without the mock it resolves to null and every test suite that
+ * touches accessibility crashes the Jest worker with
+ * "NativeAccessibilityManagerIOS is not available".
+ *
+ * Idempotent and conservative: only acts on Expo projects whose mock file exists,
+ * still exposes the `module.exports = {` registry anchor, and does not already
+ * define `AccessibilityManager`. The block is inserted as the first registry
+ * entry so it is unaffected by any project-specific module mocks that follow.
+ */
+export class EnsureJestRnMockAccessibilityManagerMigration {
+    name = "ensure-jest-rn-mock-accessibility-manager";
+    description = "Add the RN 0.85 AccessibilityManager TurboModule mock to jest.config.react-native-mock.js";
+    /**
+     * Applies to Expo projects whose create-only mock file exists, exposes the
+     * registry anchor, and does not already define the AccessibilityManager mock.
+     * @param ctx - Migration context
+     * @returns True when the mock is missing and can be safely inserted
+     */
+    async applies(ctx) {
+        if (!ctx.detectedTypes.includes("expo")) {
+            return false;
+        }
+        const mockPath = path.join(ctx.projectDir, MOCK_FILE);
+        if (!(await fse.pathExists(mockPath))) {
+            return false;
+        }
+        const content = await fse.readFile(mockPath, "utf8");
+        return content.includes(ANCHOR) && !content.includes(MARKER);
+    }
+    /**
+     * Insert the AccessibilityManager mock block immediately after the
+     * `module.exports = {` anchor. Re-checks the marker so the operation is
+     * idempotent even if `applies` and `apply` are called out of step.
+     * @param ctx - Migration context
+     * @returns Result describing the action taken
+     */
+    async apply(ctx) {
+        const mockPath = path.join(ctx.projectDir, MOCK_FILE);
+        if (!(await fse.pathExists(mockPath))) {
+            return { name: this.name, action: "noop" };
+        }
+        const content = await fse.readFile(mockPath, "utf8");
+        if (content.includes(MARKER) || !content.includes(ANCHOR)) {
+            return { name: this.name, action: "noop" };
+        }
+        const updated = content.replace(ANCHOR, ANCHOR + ACCESSIBILITY_MANAGER_BLOCK);
+        const message = `Added AccessibilityManager TurboModule mock to ${MOCK_FILE}`;
+        if (ctx.dryRun) {
+            ctx.logger.dry(`Would add AccessibilityManager mock to ${MOCK_FILE}`);
+            return {
+                name: this.name,
+                action: "applied",
+                changedFiles: [MOCK_FILE],
+                message,
+            };
+        }
+        await fse.writeFile(mockPath, updated);
+        ctx.logger.success(message);
+        return {
+            name: this.name,
+            action: "applied",
+            changedFiles: [MOCK_FILE],
+            message,
+        };
+    }
+}
+//# sourceMappingURL=ensure-jest-rn-mock-accessibility-manager.js.map

package/dist/migrations/ensure-jest-rn-mock-accessibility-manager.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"ensure-jest-rn-mock-accessibility-manager.js","sourceRoot":"","sources":["../../src/migrations/ensure-jest-rn-mock-accessibility-manager.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,IAAI,MAAM,WAAW,CAAC;AAClC,OAAO,KAAK,GAAG,MAAM,UAAU,CAAC;AAOhC,MAAM,SAAS,GAAG,kCAAkC,CAAC;AAErD,yEAAyE;AACzE,MAAM,MAAM,GAAG,sBAAsB,CAAC;AAEtC,gFAAgF;AAChF,MAAM,MAAM,GAAG,uBAAuB,CAAC;AAEvC;;;;GAIG;AACH,MAAM,2BAA2B,GAAG;;;;;;;;;;;;;;;;;;;;;;CAsBnC,CAAC;AAEF;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,OAAO,6CAA6C;IAC/C,IAAI,GAAG,2CAA2C,CAAC;IACnD,WAAW,GAClB,2FAA2F,CAAC;IAE9F;;;;;OAKG;IACH,KAAK,CAAC,OAAO,CAAC,GAAqB;QACjC,IAAI,CAAC,GAAG,CAAC,aAAa,CAAC,QAAQ,CAAC,MAAM,CAAC,EAAE,CAAC;YACxC,OAAO,KAAK,CAAC;QACf,CAAC;QACD,MAAM,QAAQ,GAAG,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,UAAU,EAAE,SAAS,CAAC,CAAC;QACtD,IAAI,CAAC,CAAC,MAAM,GAAG,CAAC,UAAU,CAAC,QAAQ,CAAC,CAAC,EAAE,CAAC;YACtC,OAAO,KAAK,CAAC;QACf,CAAC;QACD,MAAM,OAAO,GAAG,MAAM,GAAG,CAAC,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC,CAAC;QACrD,OAAO,OAAO,CAAC,QAAQ,CAAC,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC;IAC/D,CAAC;IAED;;;;;;OAMG;IACH,KAAK,CAAC,KAAK,CAAC,GAAqB;QAC/B,MAAM,QAAQ,GAAG,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,UAAU,EAAE,SAAS,CAAC,CAAC;QAEtD,IAAI,CAAC,CAAC,MAAM,GAAG,CAAC,UAAU,CAAC,QAAQ,CAAC,CAAC,EAAE,CAAC;YACtC,OAAO,EAAE,IAAI,EAAE,IAAI,CAAC,IAAI,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC;QAC7C,CAAC;QAED,MAAM,OAAO,GAAG,MAAM,GAAG,CAAC,QAAQ,CAAC,QAAQ,EAAE,MAAM,CAAC,CAAC;QACrD,IAAI,OAAO,CAAC,QAAQ,CAAC,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,QAAQ,CAAC,MAAM,CAAC,EAAE,CAAC;YAC1D,OAAO,EAAE,IAAI,EAAE,IAAI,CAAC,IAAI,EAAE,MAAM,EAAE,MAAM,EAAE,CAAC;QAC7C,CAAC;QAED,MAAM,OAAO,GAAG,OAAO,CAAC,OAAO,CAC7B,MAAM,EACN,MAAM,GAAG,2BAA2B,CACrC,CAAC;QACF,MAAM,OAAO,GAAG,kDAAkD,SAAS,EAAE,CAAC;QAE9E,IAAI,GAAG,CAAC,MAAM,EAAE,CAAC;YACf,GAAG,CAAC,MAAM,CAAC,GAAG,CAAC,0CAA0C,SAAS,EAAE,CAAC,CAAC;YACtE,OAAO;gBACL,IAAI,EAAE,IAAI,CAAC,IAAI;gBACf,MAAM,EAAE,SAAS;gBACjB,YAAY,EAAE,CAAC,SAAS,CAAC;gBACzB,OAAO;aACR,CAAC;QACJ,CAAC;QAED,MAAM,GAAG,CAAC,SAAS,CAAC,QAAQ,EAAE,OAAO,CAAC,CAAC;QACvC,GAAG,CAAC,MAAM,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;QAC5B,OAAO;YACL,IAAI,EAAE,IAAI,CAAC,IAAI;YACf,MAAM,EAAE,SAAS;YACjB,YAAY,EAAE,CAAC,SAAS,CAAC;YACzB,OAAO;SACR,CAAC;IACJ,CAAC;CACF"}

package/dist/migrations/index.d.ts

@@ -1,6 +1,7 @@
 import type { Migration, MigrationContext, MigrationResult } from "./migration.interface.js";
 export type { Migration, MigrationAction, MigrationContext, MigrationResult, } from "./migration.interface.js";
 export { EnsureAuditIgnoreLocalExclusionsMigration } from "./ensure-audit-ignore-local-exclusions.js";
+export { EnsureJestRnMockAccessibilityManagerMigration } from "./ensure-jest-rn-mock-accessibility-manager.js";
 export { EnsureLisaPostinstallMigration } from "./ensure-lisa-postinstall.js";
 export { EnsureTsconfigLocalFilesFallbackMigration } from "./ensure-tsconfig-local-files-fallback.js";
 export { EnsureTsconfigLocalIncludesMigration } from "./ensure-tsconfig-local-includes.js";

package/dist/migrations/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/migrations/index.ts"],"names":[],"mappings":"AAIA,OAAO,KAAK,EACV,SAAS,EACT,gBAAgB,EAChB,eAAe,EAChB,MAAM,0BAA0B,CAAC;AAElC,YAAY,EACV,SAAS,EACT,eAAe,EACf,gBAAgB,EAChB,eAAe,GAChB,MAAM,0BAA0B,CAAC;AAClC,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,8BAA8B,EAAE,MAAM,8BAA8B,CAAC;AAC9E,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,oCAAoC,EAAE,MAAM,qCAAqC,CAAC;AAE3F;;GAEG;AACH,qBAAa,iBAAiB;IAC5B,OAAO,CAAC,QAAQ,CAAC,UAAU,CAAuB;IAElD;;;OAGG;gBACS,UAAU,CAAC,EAAE,SAAS,SAAS,EAAE;IAS7C;;;OAGG;IACH,MAAM,IAAI,SAAS,SAAS,EAAE;IAI9B;;;;OAIG;IACG,mBAAmB,CAAC,GAAG,EAAE,gBAAgB,GAAG,OAAO,CAAC,IAAI,CAAC;IAQ/D;;;;OAIG;IACG,MAAM,CAAC,GAAG,EAAE,gBAAgB,GAAG,OAAO,CAAC,SAAS,eAAe,EAAE,CAAC;CAazE;AAED;;;GAGG;AACH,wBAAgB,uBAAuB,IAAI,iBAAiB,CAE3D"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/migrations/index.ts"],"names":[],"mappings":"AAKA,OAAO,KAAK,EACV,SAAS,EACT,gBAAgB,EAChB,eAAe,EAChB,MAAM,0BAA0B,CAAC;AAElC,YAAY,EACV,SAAS,EACT,eAAe,EACf,gBAAgB,EAChB,eAAe,GAChB,MAAM,0BAA0B,CAAC;AAClC,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,6CAA6C,EAAE,MAAM,gDAAgD,CAAC;AAC/G,OAAO,EAAE,8BAA8B,EAAE,MAAM,8BAA8B,CAAC;AAC9E,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,oCAAoC,EAAE,MAAM,qCAAqC,CAAC;AAE3F;;GAEG;AACH,qBAAa,iBAAiB;IAC5B,OAAO,CAAC,QAAQ,CAAC,UAAU,CAAuB;IAElD;;;OAGG;gBACS,UAAU,CAAC,EAAE,SAAS,SAAS,EAAE;IAU7C;;;OAGG;IACH,MAAM,IAAI,SAAS,SAAS,EAAE;IAI9B;;;;OAIG;IACG,mBAAmB,CAAC,GAAG,EAAE,gBAAgB,GAAG,OAAO,CAAC,IAAI,CAAC;IAQ/D;;;;OAIG;IACG,MAAM,CAAC,GAAG,EAAE,gBAAgB,GAAG,OAAO,CAAC,SAAS,eAAe,EAAE,CAAC;CAazE;AAED;;;GAGG;AACH,wBAAgB,uBAAuB,IAAI,iBAAiB,CAE3D"}

package/dist/migrations/index.js

@@ -1,8 +1,10 @@
 import { EnsureAuditIgnoreLocalExclusionsMigration } from "./ensure-audit-ignore-local-exclusions.js";
+import { EnsureJestRnMockAccessibilityManagerMigration } from "./ensure-jest-rn-mock-accessibility-manager.js";
 import { EnsureLisaPostinstallMigration } from "./ensure-lisa-postinstall.js";
 import { EnsureTsconfigLocalFilesFallbackMigration } from "./ensure-tsconfig-local-files-fallback.js";
 import { EnsureTsconfigLocalIncludesMigration } from "./ensure-tsconfig-local-includes.js";
 export { EnsureAuditIgnoreLocalExclusionsMigration } from "./ensure-audit-ignore-local-exclusions.js";
+export { EnsureJestRnMockAccessibilityManagerMigration } from "./ensure-jest-rn-mock-accessibility-manager.js";
 export { EnsureLisaPostinstallMigration } from "./ensure-lisa-postinstall.js";
 export { EnsureTsconfigLocalFilesFallbackMigration } from "./ensure-tsconfig-local-files-fallback.js";
 export { EnsureTsconfigLocalIncludesMigration } from "./ensure-tsconfig-local-includes.js";
@@ -20,6 +22,7 @@ export class MigrationRegistry {
             new EnsureTsconfigLocalIncludesMigration(),
             new EnsureTsconfigLocalFilesFallbackMigration(),
             new EnsureAuditIgnoreLocalExclusionsMigration(),
+            new EnsureJestRnMockAccessibilityManagerMigration(),
             new EnsureLisaPostinstallMigration(),
         ];
     }

package/dist/migrations/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/migrations/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,8BAA8B,EAAE,MAAM,8BAA8B,CAAC;AAC9E,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,oCAAoC,EAAE,MAAM,qCAAqC,CAAC;AAa3F,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,8BAA8B,EAAE,MAAM,8BAA8B,CAAC;AAC9E,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,oCAAoC,EAAE,MAAM,qCAAqC,CAAC;AAE3F;;GAEG;AACH,MAAM,OAAO,iBAAiB;IACX,UAAU,CAAuB;IAElD;;;OAGG;IACH,YAAY,UAAiC;QAC3C,IAAI,CAAC,UAAU,GAAG,UAAU,IAAI;YAC9B,IAAI,oCAAoC,EAAE;YAC1C,IAAI,yCAAyC,EAAE;YAC/C,IAAI,yCAAyC,EAAE;YAC/C,IAAI,8BAA8B,EAAE;SACrC,CAAC;IACJ,CAAC;IAED;;;OAGG;IACH,MAAM;QACJ,OAAO,IAAI,CAAC,UAAU,CAAC;IACzB,CAAC;IAED;;;;OAIG;IACH,KAAK,CAAC,mBAAmB,CAAC,GAAqB;QAC7C,KAAK,MAAM,SAAS,IAAI,IAAI,CAAC,UAAU,EAAE,CAAC;YACxC,IAAI,SAAS,CAAC,gBAAgB,EAAE,CAAC;gBAC/B,MAAM,SAAS,CAAC,gBAAgB,CAAC,GAAG,CAAC,CAAC;YACxC,CAAC;QACH,CAAC;IACH,CAAC;IAED;;;;OAIG;IACH,KAAK,CAAC,MAAM,CAAC,GAAqB;QAChC,MAAM,OAAO,GAAsB,EAAE,CAAC;QACtC,KAAK,MAAM,SAAS,IAAI,IAAI,CAAC,UAAU,EAAE,CAAC;YACxC,MAAM,SAAS,GAAG,MAAM,SAAS,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC;YAC/C,IAAI,CAAC,SAAS,EAAE,CAAC;gBACf,OAAO,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,SAAS,CAAC,IAAI,EAAE,MAAM,EAAE,SAAS,EAAE,CAAC,CAAC;gBAC1D,SAAS;YACX,CAAC;YACD,MAAM,MAAM,GAAG,MAAM,SAAS,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC;YAC1C,OAAO,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;QACvB,CAAC;QACD,OAAO,OAAO,CAAC;IACjB,CAAC;CACF;AAED;;;GAGG;AACH,MAAM,UAAU,uBAAuB;IACrC,OAAO,IAAI,iBAAiB,EAAE,CAAC;AACjC,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/migrations/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,6CAA6C,EAAE,MAAM,gDAAgD,CAAC;AAC/G,OAAO,EAAE,8BAA8B,EAAE,MAAM,8BAA8B,CAAC;AAC9E,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,oCAAoC,EAAE,MAAM,qCAAqC,CAAC;AAa3F,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,6CAA6C,EAAE,MAAM,gDAAgD,CAAC;AAC/G,OAAO,EAAE,8BAA8B,EAAE,MAAM,8BAA8B,CAAC;AAC9E,OAAO,EAAE,yCAAyC,EAAE,MAAM,2CAA2C,CAAC;AACtG,OAAO,EAAE,oCAAoC,EAAE,MAAM,qCAAqC,CAAC;AAE3F;;GAEG;AACH,MAAM,OAAO,iBAAiB;IACX,UAAU,CAAuB;IAElD;;;OAGG;IACH,YAAY,UAAiC;QAC3C,IAAI,CAAC,UAAU,GAAG,UAAU,IAAI;YAC9B,IAAI,oCAAoC,EAAE;YAC1C,IAAI,yCAAyC,EAAE;YAC/C,IAAI,yCAAyC,EAAE;YAC/C,IAAI,6CAA6C,EAAE;YACnD,IAAI,8BAA8B,EAAE;SACrC,CAAC;IACJ,CAAC;IAED;;;OAGG;IACH,MAAM;QACJ,OAAO,IAAI,CAAC,UAAU,CAAC;IACzB,CAAC;IAED;;;;OAIG;IACH,KAAK,CAAC,mBAAmB,CAAC,GAAqB;QAC7C,KAAK,MAAM,SAAS,IAAI,IAAI,CAAC,UAAU,EAAE,CAAC;YACxC,IAAI,SAAS,CAAC,gBAAgB,EAAE,CAAC;gBAC/B,MAAM,SAAS,CAAC,gBAAgB,CAAC,GAAG,CAAC,CAAC;YACxC,CAAC;QACH,CAAC;IACH,CAAC;IAED;;;;OAIG;IACH,KAAK,CAAC,MAAM,CAAC,GAAqB;QAChC,MAAM,OAAO,GAAsB,EAAE,CAAC;QACtC,KAAK,MAAM,SAAS,IAAI,IAAI,CAAC,UAAU,EAAE,CAAC;YACxC,MAAM,SAAS,GAAG,MAAM,SAAS,CAAC,OAAO,CAAC,GAAG,CAAC,CAAC;YAC/C,IAAI,CAAC,SAAS,EAAE,CAAC;gBACf,OAAO,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,SAAS,CAAC,IAAI,EAAE,MAAM,EAAE,SAAS,EAAE,CAAC,CAAC;gBAC1D,SAAS;YACX,CAAC;YACD,MAAM,MAAM,GAAG,MAAM,SAAS,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC;YAC1C,OAAO,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;QACvB,CAAC;QACD,OAAO,OAAO,CAAC;IACjB,CAAC;CACF;AAED;;;GAGG;AACH,MAAM,UAAU,uBAAuB;IACrC,OAAO,IAAI,iBAAiB,EAAE,CAAC;AACjC,CAAC"}

package/expo/copy-overwrite/knip.json

@@ -118,6 +118,7 @@
     "react-hook-form",
     "react-native-element-dropdown",
     "react-native-keyboard-controller",
+    "react-native-worklets",
     "tailwind-variants",
     "tar",
     "text-encoding-polyfill",

package/expo/package-lisa/package.lisa.json

@@ -119,8 +119,6 @@
       "@legendapp/motion": "^2.4.0",
       "@react-native-async-storage/async-storage": "2.2.0",
       "@react-native-masked-view/masked-view": "^0.3.2",
-      "@react-navigation/drawer": "^7.5.0",
-      "@react-navigation/elements": "^1.3.31",
       "@sentry/react-native": "~7.11.0",
       "@shopify/flash-list": "2.0.2",
       "@shopify/react-native-skia": "2.6.2",

package/package.json

@@ -84,7 +84,7 @@
     "lodash": ">=4.18.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.147.6",
+  "version": "2.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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.148.0",
   "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: