@codyswann/lisa 2.189.7 → 2.189.9

package/plugins/lisa-expo-agy/skills/e2e-coverage-gaps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: e2e-coverage-gaps
-description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa:tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the exploratory-qa skill instead.
+description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.
 ---
 
 # E2E Coverage Gaps
@@ -14,7 +14,7 @@ is real and reachable, then file each gap as a **build-ready missing-test work i
 Lisa lifecycle.
 
 This skill is purely about **automated-coverage gaps**. It does not judge whether the UI is confusing
-or pretty — for human usability findings, use the `exploratory-qa` skill.
+or pretty — for human usability findings, use the `lisa-exploratory-qa` skill.
 
 ## Parameters
 
@@ -67,7 +67,7 @@ Map routes/flows against existing coverage and classify each gap:
 
 ### 6. File One Ticket Per Gap
 
-Each confirmed gap becomes a leaf **missing-test** work item created via `lisa:tracker-write` (the
+Each confirmed gap becomes a leaf **missing-test** work item created via `lisa-tracker-write` (the
 vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never
 call a vendor `*-write-*` skill directly), `issue_type: Task`, **build-ready per the `ready` flag
 (default `true`)**. Pass `build_ready` explicitly on every create. Each ticket MUST specify:
@@ -101,5 +101,5 @@ No report file. Emit a concise in-session summary:
 - Every ticket must stand alone for an implementer who was not in the session and must be concretely
   automatable (named route, behavior, and stable hook).
 - Do not refile gaps already covered or already ticketed (marker check).
-- This skill is about automated coverage only — route human usability issues to `exploratory-qa`.
+- This skill is about automated coverage only — route human usability issues to `lisa-exploratory-qa`.
 - Preserve unrelated repo changes.

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

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

package/plugins/lisa-expo-copilot/skills/e2e-coverage-gaps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: e2e-coverage-gaps
-description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa:tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the exploratory-qa skill instead.
+description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.
 ---
 
 # E2E Coverage Gaps
@@ -14,7 +14,7 @@ is real and reachable, then file each gap as a **build-ready missing-test work i
 Lisa lifecycle.
 
 This skill is purely about **automated-coverage gaps**. It does not judge whether the UI is confusing
-or pretty — for human usability findings, use the `exploratory-qa` skill.
+or pretty — for human usability findings, use the `lisa-exploratory-qa` skill.
 
 ## Parameters
 
@@ -67,7 +67,7 @@ Map routes/flows against existing coverage and classify each gap:
 
 ### 6. File One Ticket Per Gap
 
-Each confirmed gap becomes a leaf **missing-test** work item created via `lisa:tracker-write` (the
+Each confirmed gap becomes a leaf **missing-test** work item created via `lisa-tracker-write` (the
 vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never
 call a vendor `*-write-*` skill directly), `issue_type: Task`, **build-ready per the `ready` flag
 (default `true`)**. Pass `build_ready` explicitly on every create. Each ticket MUST specify:
@@ -101,5 +101,5 @@ No report file. Emit a concise in-session summary:
 - Every ticket must stand alone for an implementer who was not in the session and must be concretely
   automatable (named route, behavior, and stable hook).
 - Do not refile gaps already covered or already ticketed (marker check).
-- This skill is about automated coverage only — route human usability issues to `exploratory-qa`.
+- This skill is about automated coverage only — route human usability issues to `lisa-exploratory-qa`.
 - Preserve unrelated repo changes.

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

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

package/plugins/lisa-expo-cursor/skills/e2e-coverage-gaps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: e2e-coverage-gaps
-description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa:tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the exploratory-qa skill instead.
+description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.
 ---
 
 # E2E Coverage Gaps
@@ -14,7 +14,7 @@ is real and reachable, then file each gap as a **build-ready missing-test work i
 Lisa lifecycle.
 
 This skill is purely about **automated-coverage gaps**. It does not judge whether the UI is confusing
-or pretty — for human usability findings, use the `exploratory-qa` skill.
+or pretty — for human usability findings, use the `lisa-exploratory-qa` skill.
 
 ## Parameters
 
@@ -67,7 +67,7 @@ Map routes/flows against existing coverage and classify each gap:
 
 ### 6. File One Ticket Per Gap
 
-Each confirmed gap becomes a leaf **missing-test** work item created via `lisa:tracker-write` (the
+Each confirmed gap becomes a leaf **missing-test** work item created via `lisa-tracker-write` (the
 vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never
 call a vendor `*-write-*` skill directly), `issue_type: Task`, **build-ready per the `ready` flag
 (default `true`)**. Pass `build_ready` explicitly on every create. Each ticket MUST specify:
@@ -101,5 +101,5 @@ No report file. Emit a concise in-session summary:
 - Every ticket must stand alone for an implementer who was not in the session and must be concretely
   automatable (named route, behavior, and stable hook).
 - Do not refile gaps already covered or already ticketed (marker check).
-- This skill is about automated coverage only — route human usability issues to `exploratory-qa`.
+- This skill is about automated coverage only — route human usability issues to `lisa-exploratory-qa`.
 - Preserve unrelated repo changes.

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.189.7",
+  "version": "2.189.9",
   "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.189.7",
+  "version": "2.189.9",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/skills/e2e-coverage-gaps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: e2e-coverage-gaps
-description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa:tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the exploratory-qa skill instead.
+description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.
 ---
 
 # E2E Coverage Gaps
@@ -14,7 +14,7 @@ is real and reachable, then file each gap as a **build-ready missing-test work i
 Lisa lifecycle.
 
 This skill is purely about **automated-coverage gaps**. It does not judge whether the UI is confusing
-or pretty — for human usability findings, use the `exploratory-qa` skill.
+or pretty — for human usability findings, use the `lisa-exploratory-qa` skill.
 
 ## Parameters
 
@@ -67,7 +67,7 @@ Map routes/flows against existing coverage and classify each gap:
 
 ### 6. File One Ticket Per Gap
 
-Each confirmed gap becomes a leaf **missing-test** work item created via `lisa:tracker-write` (the
+Each confirmed gap becomes a leaf **missing-test** work item created via `lisa-tracker-write` (the
 vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never
 call a vendor `*-write-*` skill directly), `issue_type: Task`, **build-ready per the `ready` flag
 (default `true`)**. Pass `build_ready` explicitly on every create. Each ticket MUST specify:
@@ -101,5 +101,5 @@ No report file. Emit a concise in-session summary:
 - Every ticket must stand alone for an implementer who was not in the session and must be concretely
   automatable (named route, behavior, and stable hook).
 - Do not refile gaps already covered or already ticketed (marker check).
-- This skill is about automated coverage only — route human usability issues to `exploratory-qa`.
+- This skill is about automated coverage only — route human usability issues to `lisa-exploratory-qa`.
 - Preserve unrelated repo changes.

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

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

package/plugins/lisa-harper-fabric-agy/skills/e2e-coverage-gaps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: e2e-coverage-gaps
-description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa:tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the exploratory-qa skill instead.
+description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.
 ---
 
 # E2E Coverage Gaps
@@ -14,7 +14,7 @@ is real and reachable, then file each gap as a **build-ready missing-test work i
 Lisa lifecycle.
 
 This skill is purely about **automated-coverage gaps**. It does not judge whether the UI is confusing
-or pretty — for human usability findings, use the `exploratory-qa` skill.
+or pretty — for human usability findings, use the `lisa-exploratory-qa` skill.
 
 ## Parameters
 
@@ -67,7 +67,7 @@ Map routes/flows against existing coverage and classify each gap:
 
 ### 6. File One Ticket Per Gap
 
-Each confirmed gap becomes a leaf **missing-test** work item created via `lisa:tracker-write` (the
+Each confirmed gap becomes a leaf **missing-test** work item created via `lisa-tracker-write` (the
 vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never
 call a vendor `*-write-*` skill directly), `issue_type: Task`, **build-ready per the `ready` flag
 (default `true`)**. Pass `build_ready` explicitly on every create. Each ticket MUST specify:
@@ -101,5 +101,5 @@ No report file. Emit a concise in-session summary:
 - Every ticket must stand alone for an implementer who was not in the session and must be concretely
   automatable (named route, behavior, and stable hook).
 - Do not refile gaps already covered or already ticketed (marker check).
-- This skill is about automated coverage only — route human usability issues to `exploratory-qa`.
+- This skill is about automated coverage only — route human usability issues to `lisa-exploratory-qa`.
 - Preserve unrelated repo changes.

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

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

package/plugins/lisa-harper-fabric-copilot/skills/e2e-coverage-gaps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: e2e-coverage-gaps
-description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa:tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the exploratory-qa skill instead.
+description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.
 ---
 
 # E2E Coverage Gaps
@@ -14,7 +14,7 @@ is real and reachable, then file each gap as a **build-ready missing-test work i
 Lisa lifecycle.
 
 This skill is purely about **automated-coverage gaps**. It does not judge whether the UI is confusing
-or pretty — for human usability findings, use the `exploratory-qa` skill.
+or pretty — for human usability findings, use the `lisa-exploratory-qa` skill.
 
 ## Parameters
 
@@ -67,7 +67,7 @@ Map routes/flows against existing coverage and classify each gap:
 
 ### 6. File One Ticket Per Gap
 
-Each confirmed gap becomes a leaf **missing-test** work item created via `lisa:tracker-write` (the
+Each confirmed gap becomes a leaf **missing-test** work item created via `lisa-tracker-write` (the
 vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never
 call a vendor `*-write-*` skill directly), `issue_type: Task`, **build-ready per the `ready` flag
 (default `true`)**. Pass `build_ready` explicitly on every create. Each ticket MUST specify:
@@ -101,5 +101,5 @@ No report file. Emit a concise in-session summary:
 - Every ticket must stand alone for an implementer who was not in the session and must be concretely
   automatable (named route, behavior, and stable hook).
 - Do not refile gaps already covered or already ticketed (marker check).
-- This skill is about automated coverage only — route human usability issues to `exploratory-qa`.
+- This skill is about automated coverage only — route human usability issues to `lisa-exploratory-qa`.
 - Preserve unrelated repo changes.

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

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

package/plugins/lisa-harper-fabric-cursor/skills/e2e-coverage-gaps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: e2e-coverage-gaps
-description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa:tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the exploratory-qa skill instead.
+description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.
 ---
 
 # E2E Coverage Gaps
@@ -14,7 +14,7 @@ is real and reachable, then file each gap as a **build-ready missing-test work i
 Lisa lifecycle.
 
 This skill is purely about **automated-coverage gaps**. It does not judge whether the UI is confusing
-or pretty — for human usability findings, use the `exploratory-qa` skill.
+or pretty — for human usability findings, use the `lisa-exploratory-qa` skill.
 
 ## Parameters
 
@@ -67,7 +67,7 @@ Map routes/flows against existing coverage and classify each gap:
 
 ### 6. File One Ticket Per Gap
 
-Each confirmed gap becomes a leaf **missing-test** work item created via `lisa:tracker-write` (the
+Each confirmed gap becomes a leaf **missing-test** work item created via `lisa-tracker-write` (the
 vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never
 call a vendor `*-write-*` skill directly), `issue_type: Task`, **build-ready per the `ready` flag
 (default `true`)**. Pass `build_ready` explicitly on every create. Each ticket MUST specify:
@@ -101,5 +101,5 @@ No report file. Emit a concise in-session summary:
 - Every ticket must stand alone for an implementer who was not in the session and must be concretely
   automatable (named route, behavior, and stable hook).
 - Do not refile gaps already covered or already ticketed (marker check).
-- This skill is about automated coverage only — route human usability issues to `exploratory-qa`.
+- This skill is about automated coverage only — route human usability issues to `lisa-exploratory-qa`.
 - Preserve unrelated repo changes.

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.189.7",
+  "version": "2.189.9",
   "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.189.7",
+  "version": "2.189.9",
   "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.189.7",
+  "version": "2.189.9",
   "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.189.7",
+  "version": "2.189.9",
   "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.189.7",
+  "version": "2.189.9",
   "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.189.7",
+  "version": "2.189.9",
   "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.189.7",
+  "version": "2.189.9",
   "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/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "Lisa Openclaw Connect Repo Topic"
+display_name: "Openclaw Connect Repo Topic"
 short_description: "Bind a Telegram forum topic to an OpenClaw dispatcher+worker agent pair that runs a coding CLI against a repo, so you can drive code work…"
 default_prompt:
   - "Use $lisa-openclaw-connect-repo-topic: Bind a Telegram forum topic to an OpenClaw dispatcher+worker agent pair that runs a coding CLI against a repo, so you can drive code work…."

package/plugins/lisa-openclaw/skills/lisa-openclaw-connect-staff/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "Lisa Openclaw Connect Staff"
+display_name: "Openclaw Connect Staff"
 short_description: "Connect staff roles to a human chat surface (Telegram or Slack) via OpenClaw using a facilitator/specialist hub-and-spoke model"
 default_prompt:
   - "Use $lisa-openclaw-connect-staff: Connect staff roles to a human chat surface (Telegram or Slack) via OpenClaw using a facilitator/specialist hub-and-spoke model."

package/plugins/lisa-openclaw/skills/lisa-openclaw-setup/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "Lisa Openclaw Setup"
+display_name: "Openclaw Setup"
 short_description: "Set up OpenClaw as the chat-surface runtime for this project's staff roles"
 default_prompt:
   - "Use $lisa-openclaw-setup: Set up OpenClaw as the chat-surface runtime for this project's staff roles."

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.189.7",
+  "version": "2.189.9",
   "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/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.189.7",
+  "version": "2.189.9",
   "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/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.189.7",
+  "version": "2.189.9",
   "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-phaser/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.189.7",
+  "version": "2.189.9",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.189.7",
+  "version": "2.189.9",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.189.7",
+  "version": "2.189.9",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.189.7",
+  "version": "2.189.9",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.189.7",
+  "version": "2.189.9",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.189.7",
+  "version": "2.189.9",
   "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.189.7",
+  "version": "2.189.9",
   "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/skills/e2e-coverage-gaps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: e2e-coverage-gaps
-description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa:tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the exploratory-qa skill instead.
+description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.
 ---
 
 # E2E Coverage Gaps
@@ -14,7 +14,7 @@ is real and reachable, then file each gap as a **build-ready missing-test work i
 Lisa lifecycle.
 
 This skill is purely about **automated-coverage gaps**. It does not judge whether the UI is confusing
-or pretty — for human usability findings, use the `exploratory-qa` skill.
+or pretty — for human usability findings, use the `lisa-exploratory-qa` skill.
 
 ## Parameters
 
@@ -67,7 +67,7 @@ Map routes/flows against existing coverage and classify each gap:
 
 ### 6. File One Ticket Per Gap
 
-Each confirmed gap becomes a leaf **missing-test** work item created via `lisa:tracker-write` (the
+Each confirmed gap becomes a leaf **missing-test** work item created via `lisa-tracker-write` (the
 vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never
 call a vendor `*-write-*` skill directly), `issue_type: Task`, **build-ready per the `ready` flag
 (default `true`)**. Pass `build_ready` explicitly on every create. Each ticket MUST specify:
@@ -101,5 +101,5 @@ No report file. Emit a concise in-session summary:
 - Every ticket must stand alone for an implementer who was not in the session and must be concretely
   automatable (named route, behavior, and stable hook).
 - Do not refile gaps already covered or already ticketed (marker check).
-- This skill is about automated coverage only — route human usability issues to `exploratory-qa`.
+- This skill is about automated coverage only — route human usability issues to `lisa-exploratory-qa`.
 - Preserve unrelated repo changes.

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

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

package/plugins/lisa-rails-agy/skills/e2e-coverage-gaps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: e2e-coverage-gaps
-description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa:tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the exploratory-qa skill instead.
+description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.
 ---
 
 # E2E Coverage Gaps
@@ -14,7 +14,7 @@ is real and reachable, then file each gap as a **build-ready missing-test work i
 Lisa lifecycle.
 
 This skill is purely about **automated-coverage gaps**. It does not judge whether the UI is confusing
-or pretty — for human usability findings, use the `exploratory-qa` skill.
+or pretty — for human usability findings, use the `lisa-exploratory-qa` skill.
 
 ## Parameters
 
@@ -67,7 +67,7 @@ Map routes/flows against existing coverage and classify each gap:
 
 ### 6. File One Ticket Per Gap
 
-Each confirmed gap becomes a leaf **missing-test** work item created via `lisa:tracker-write` (the
+Each confirmed gap becomes a leaf **missing-test** work item created via `lisa-tracker-write` (the
 vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never
 call a vendor `*-write-*` skill directly), `issue_type: Task`, **build-ready per the `ready` flag
 (default `true`)**. Pass `build_ready` explicitly on every create. Each ticket MUST specify:
@@ -101,5 +101,5 @@ No report file. Emit a concise in-session summary:
 - Every ticket must stand alone for an implementer who was not in the session and must be concretely
   automatable (named route, behavior, and stable hook).
 - Do not refile gaps already covered or already ticketed (marker check).
-- This skill is about automated coverage only — route human usability issues to `exploratory-qa`.
+- This skill is about automated coverage only — route human usability issues to `lisa-exploratory-qa`.
 - Preserve unrelated repo changes.

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

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

package/plugins/lisa-rails-copilot/skills/e2e-coverage-gaps/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: e2e-coverage-gaps
-description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa:tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the exploratory-qa skill instead.
+description: Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files one build-ready missing-test ticket per gap via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.
 ---
 
 # E2E Coverage Gaps
@@ -14,7 +14,7 @@ is real and reachable, then file each gap as a **build-ready missing-test work i
 Lisa lifecycle.
 
 This skill is purely about **automated-coverage gaps**. It does not judge whether the UI is confusing
-or pretty — for human usability findings, use the `exploratory-qa` skill.
+or pretty — for human usability findings, use the `lisa-exploratory-qa` skill.
 
 ## Parameters
 
@@ -67,7 +67,7 @@ Map routes/flows against existing coverage and classify each gap:
 
 ### 6. File One Ticket Per Gap
 
-Each confirmed gap becomes a leaf **missing-test** work item created via `lisa:tracker-write` (the
+Each confirmed gap becomes a leaf **missing-test** work item created via `lisa-tracker-write` (the
 vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never
 call a vendor `*-write-*` skill directly), `issue_type: Task`, **build-ready per the `ready` flag
 (default `true`)**. Pass `build_ready` explicitly on every create. Each ticket MUST specify:
@@ -101,5 +101,5 @@ No report file. Emit a concise in-session summary:
 - Every ticket must stand alone for an implementer who was not in the session and must be concretely
   automatable (named route, behavior, and stable hook).
 - Do not refile gaps already covered or already ticketed (marker check).
-- This skill is about automated coverage only — route human usability issues to `exploratory-qa`.
+- This skill is about automated coverage only — route human usability issues to `lisa-exploratory-qa`.
 - Preserve unrelated repo changes.

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

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