@codyswann/lisa 2.128.1 → 2.129.2

package/plugins/lisa-copilot/scripts/doctor-report.mjs

@@ -6,6 +6,11 @@
  * repo adds real readiness probes. Keep this file dependency-free so future
  * doctor scripts can reuse it from plugin distributions and downstream repos.
  */
+import { existsSync } from "node:fs";
+import path from "node:path";
+import process from "node:process";
+
+import { getPluginSyncResult } from "./plugin-sync-explain.mjs";
 
 export const DOCTOR_STATUSES = ["PASS", "WARN", "FAIL", "SKIP"];
 export const DOCTOR_VERDICTS = ["READY", "READY_WITH_WARNINGS", "NOT_READY"];
@@ -34,6 +39,85 @@ export const DOCTOR_VERDICTS = ["READY", "READY_WITH_WARNINGS", "NOT_READY"];
  * }} DoctorReportInput
  */
 
+/**
+ * @param {string} root
+ * @returns {DoctorGroup}
+ */
+export function createPluginSyncDoctorGroup(root = process.cwd()) {
+  const repoRoot = path.resolve(root);
+  if (
+    !existsSync(path.join(repoRoot, "plugins", "src")) &&
+    !existsSync(path.join(repoRoot, "plugins"))
+  ) {
+    return {
+      id: "plugin-sync",
+      title: "Plugin source/generated sync",
+      checks: [
+        {
+          id: "plugin-sync",
+          status: "SKIP",
+          summary: "plugin sync check is not applicable",
+          observed:
+            "No plugins/ or plugins/src/ directory was found in this repository.",
+        },
+      ],
+    };
+  }
+
+  try {
+    const result = getPluginSyncResult(repoRoot);
+    if (!result.readOnly) {
+      return {
+        id: "plugin-sync",
+        title: "Plugin source/generated sync",
+        checks: [
+          {
+            id: "plugin-sync",
+            status: "FAIL",
+            summary: "plugin sync readiness check mutated the working tree",
+            observed:
+              "Git status changed while collecting plugin sync evidence.",
+            remediation:
+              "Run `git status --short`, inspect the unexpected changes, and fix plugin-sync-explain before trusting doctor output.",
+          },
+        ],
+      };
+    }
+
+    return {
+      id: "plugin-sync",
+      title: "Plugin source/generated sync",
+      checks: [
+        {
+          id: "plugin-sync",
+          status: result.verdict,
+          summary:
+            result.verdict === "PASS"
+              ? "plugin source and generated artifacts are in sync"
+              : `plugin sync drift detected: ${result.driftClass}`,
+          observed: renderPluginSyncObserved(result),
+          remediation: renderPluginSyncRemediation(result),
+        },
+      ],
+    };
+  } catch (error) {
+    return {
+      id: "plugin-sync",
+      title: "Plugin source/generated sync",
+      checks: [
+        {
+          id: "plugin-sync",
+          status: "FAIL",
+          summary: "plugin sync readiness check failed",
+          observed: error instanceof Error ? error.message : String(error),
+          remediation:
+            "Run `/lisa:plugin-sync-explain` or `bun run check:plugins` to inspect plugin sync health directly.",
+        },
+      ],
+    };
+  }
+}
+
 /**
  * @param {readonly DoctorGroup[]} groups
  * @returns {DoctorVerdict}
@@ -141,3 +225,55 @@ function normalizeCheck(check) {
     status: normalizedStatus,
   };
 }
+
+/**
+ * @param {import("./plugin-sync-explain.mjs").PluginSyncResult} result
+ * @returns {string}
+ */
+function renderPluginSyncObserved(result) {
+  if (result.verdict === "PASS") {
+    return "Drift class IN_SYNC; plugin sync evidence was collected read-only.";
+  }
+  const paths = result.affectedPaths.length
+    ? result.affectedPaths.join(", ")
+    : "none";
+  return `Drift class ${result.driftClass}; affected paths: ${paths}.`;
+}
+
+/**
+ * @param {import("./plugin-sync-explain.mjs").PluginSyncResult} result
+ * @returns {string | undefined}
+ */
+function renderPluginSyncRemediation(result) {
+  if (result.verdict === "PASS") {
+    return undefined;
+  }
+
+  const nextAction = pluginSyncNextAction(result.driftClass);
+  const details = result.remediations
+    .map(item => `${item.path}: ${item.nextAction}`)
+    .join(" ");
+  const explain =
+    "Run `/lisa:plugin-sync-explain` or `bun run check:plugins` for the detailed drift report.";
+
+  return [nextAction, details, explain].filter(Boolean).join(" ");
+}
+
+/**
+ * @param {string} driftClass
+ * @returns {string}
+ */
+function pluginSyncNextAction(driftClass) {
+  switch (driftClass) {
+    case "SOURCE_NOT_BUILT":
+      return "Next action: run `bun run build:plugins && bun run check:plugins`, then commit source plus regenerated plugin artifacts.";
+    case "OUT_OF_SYNC":
+      return "Next action: review source and generated plugin changes, keep `plugins/src` authoritative, then run `bun run build:plugins && bun run check:plugins`.";
+    case "GENERATED_ONLY":
+      return "Next action: move generated-only edits upstream to `plugins/src`, or remove the generated artifact drift if it should not ship.";
+    case "MARKETPLACE_REGISTRATION_DRIFT":
+      return "Next action: align marketplace registration with the built plugin manifests, or remove stale marketplace entries.";
+    default:
+      return `Next action: inspect plugin sync drift class ${driftClass}.`;
+  }
+}

package/plugins/lisa-copilot/scripts/plugin-sync-explain.mjs

@@ -50,6 +50,25 @@ const GIT_BIN = "/usr/bin/git";
  *   readonly readOnly: boolean
  *   readonly text: string
  * }} PluginSyncReport
+ *
+ * @typedef {{
+ *   readonly path: string
+ *   readonly counterpart?: string
+ *   readonly classification: string
+ *   readonly nextAction: string
+ * }} PluginSyncRemediation
+ *
+ * @typedef {{
+ *   readonly root: string
+ *   readonly verdict: "PASS" | "WARN"
+ *   readonly driftClass: string
+ *   readonly affectedPaths: readonly string[]
+ *   readonly remediations: readonly PluginSyncRemediation[]
+ *   readonly findings: readonly PluginSyncFinding[]
+ *   readonly statusBefore: string
+ *   readonly statusAfter: string
+ *   readonly readOnly: boolean
+ * }} PluginSyncResult
  */
 
 /**
@@ -57,6 +76,25 @@ const GIT_BIN = "/usr/bin/git";
  * @returns {PluginSyncReport}
  */
 export function explainPluginSync(root = process.cwd()) {
+  const result = getPluginSyncResult(root);
+
+  return {
+    root: result.root,
+    findings: result.findings,
+    statusBefore: result.statusBefore,
+    statusAfter: result.statusAfter,
+    readOnly: result.readOnly,
+    text: renderPluginSyncReport(result),
+  };
+}
+
+/**
+ * Return a structured, read-only plugin sync result for readiness surfaces such
+ * as doctor. CLI callers should still render this through renderPluginSyncReport.
+ * @param {string} root
+ * @returns {PluginSyncResult}
+ */
+export function getPluginSyncResult(root = process.cwd()) {
   const repoRoot = path.resolve(root);
   const statusBefore = gitStatus(repoRoot);
   const statusEntries = parseGitStatus(statusBefore);
@@ -71,20 +109,23 @@ export function explainPluginSync(root = process.cwd()) {
   ];
   const statusAfter = gitStatus(repoRoot);
   const readOnly = statusAfter === statusBefore;
+  const driftClass = highestClassification(findings);
 
   return {
     root: repoRoot,
+    verdict: findings.length === 0 ? "PASS" : "WARN",
+    driftClass,
+    affectedPaths: affectedPaths(findings),
+    remediations: findings.map(finding => ({
+      path: finding.path,
+      counterpart: finding.counterpart,
+      classification: finding.classification,
+      nextAction: finding.nextAction,
+    })),
     findings,
     statusBefore,
     statusAfter,
     readOnly,
-    text: renderPluginSyncReport({
-      root: repoRoot,
-      findings,
-      statusBefore,
-      statusAfter,
-      readOnly,
-    }),
   };
 }
 
@@ -142,6 +183,22 @@ function highestClassification(findings) {
   return "IN_SYNC";
 }
 
+/**
+ * @param {readonly PluginSyncFinding[]} findings
+ * @returns {string[]}
+ */
+function affectedPaths(findings) {
+  return [
+    ...new Set(
+      findings.flatMap(finding =>
+        [finding.path, finding.counterpart].filter(
+          pathValue => typeof pathValue === "string" && pathValue.length > 0
+        )
+      )
+    ),
+  ];
+}
+
 /**
  * @param {readonly { readonly code: string, readonly file: string }[]} entries
  * @param {ReadonlyMap<string, Buffer> | undefined} expectedGeneratedFiles

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "2.128.1",
+  "version": "2.129.2",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cursor/scripts/doctor-report.mjs

@@ -6,6 +6,11 @@
  * repo adds real readiness probes. Keep this file dependency-free so future
  * doctor scripts can reuse it from plugin distributions and downstream repos.
  */
+import { existsSync } from "node:fs";
+import path from "node:path";
+import process from "node:process";
+
+import { getPluginSyncResult } from "./plugin-sync-explain.mjs";
 
 export const DOCTOR_STATUSES = ["PASS", "WARN", "FAIL", "SKIP"];
 export const DOCTOR_VERDICTS = ["READY", "READY_WITH_WARNINGS", "NOT_READY"];
@@ -34,6 +39,85 @@ export const DOCTOR_VERDICTS = ["READY", "READY_WITH_WARNINGS", "NOT_READY"];
  * }} DoctorReportInput
  */
 
+/**
+ * @param {string} root
+ * @returns {DoctorGroup}
+ */
+export function createPluginSyncDoctorGroup(root = process.cwd()) {
+  const repoRoot = path.resolve(root);
+  if (
+    !existsSync(path.join(repoRoot, "plugins", "src")) &&
+    !existsSync(path.join(repoRoot, "plugins"))
+  ) {
+    return {
+      id: "plugin-sync",
+      title: "Plugin source/generated sync",
+      checks: [
+        {
+          id: "plugin-sync",
+          status: "SKIP",
+          summary: "plugin sync check is not applicable",
+          observed:
+            "No plugins/ or plugins/src/ directory was found in this repository.",
+        },
+      ],
+    };
+  }
+
+  try {
+    const result = getPluginSyncResult(repoRoot);
+    if (!result.readOnly) {
+      return {
+        id: "plugin-sync",
+        title: "Plugin source/generated sync",
+        checks: [
+          {
+            id: "plugin-sync",
+            status: "FAIL",
+            summary: "plugin sync readiness check mutated the working tree",
+            observed:
+              "Git status changed while collecting plugin sync evidence.",
+            remediation:
+              "Run `git status --short`, inspect the unexpected changes, and fix plugin-sync-explain before trusting doctor output.",
+          },
+        ],
+      };
+    }
+
+    return {
+      id: "plugin-sync",
+      title: "Plugin source/generated sync",
+      checks: [
+        {
+          id: "plugin-sync",
+          status: result.verdict,
+          summary:
+            result.verdict === "PASS"
+              ? "plugin source and generated artifacts are in sync"
+              : `plugin sync drift detected: ${result.driftClass}`,
+          observed: renderPluginSyncObserved(result),
+          remediation: renderPluginSyncRemediation(result),
+        },
+      ],
+    };
+  } catch (error) {
+    return {
+      id: "plugin-sync",
+      title: "Plugin source/generated sync",
+      checks: [
+        {
+          id: "plugin-sync",
+          status: "FAIL",
+          summary: "plugin sync readiness check failed",
+          observed: error instanceof Error ? error.message : String(error),
+          remediation:
+            "Run `/lisa:plugin-sync-explain` or `bun run check:plugins` to inspect plugin sync health directly.",
+        },
+      ],
+    };
+  }
+}
+
 /**
  * @param {readonly DoctorGroup[]} groups
  * @returns {DoctorVerdict}
@@ -141,3 +225,55 @@ function normalizeCheck(check) {
     status: normalizedStatus,
   };
 }
+
+/**
+ * @param {import("./plugin-sync-explain.mjs").PluginSyncResult} result
+ * @returns {string}
+ */
+function renderPluginSyncObserved(result) {
+  if (result.verdict === "PASS") {
+    return "Drift class IN_SYNC; plugin sync evidence was collected read-only.";
+  }
+  const paths = result.affectedPaths.length
+    ? result.affectedPaths.join(", ")
+    : "none";
+  return `Drift class ${result.driftClass}; affected paths: ${paths}.`;
+}
+
+/**
+ * @param {import("./plugin-sync-explain.mjs").PluginSyncResult} result
+ * @returns {string | undefined}
+ */
+function renderPluginSyncRemediation(result) {
+  if (result.verdict === "PASS") {
+    return undefined;
+  }
+
+  const nextAction = pluginSyncNextAction(result.driftClass);
+  const details = result.remediations
+    .map(item => `${item.path}: ${item.nextAction}`)
+    .join(" ");
+  const explain =
+    "Run `/lisa:plugin-sync-explain` or `bun run check:plugins` for the detailed drift report.";
+
+  return [nextAction, details, explain].filter(Boolean).join(" ");
+}
+
+/**
+ * @param {string} driftClass
+ * @returns {string}
+ */
+function pluginSyncNextAction(driftClass) {
+  switch (driftClass) {
+    case "SOURCE_NOT_BUILT":
+      return "Next action: run `bun run build:plugins && bun run check:plugins`, then commit source plus regenerated plugin artifacts.";
+    case "OUT_OF_SYNC":
+      return "Next action: review source and generated plugin changes, keep `plugins/src` authoritative, then run `bun run build:plugins && bun run check:plugins`.";
+    case "GENERATED_ONLY":
+      return "Next action: move generated-only edits upstream to `plugins/src`, or remove the generated artifact drift if it should not ship.";
+    case "MARKETPLACE_REGISTRATION_DRIFT":
+      return "Next action: align marketplace registration with the built plugin manifests, or remove stale marketplace entries.";
+    default:
+      return `Next action: inspect plugin sync drift class ${driftClass}.`;
+  }
+}

package/plugins/lisa-cursor/scripts/plugin-sync-explain.mjs

@@ -50,6 +50,25 @@ const GIT_BIN = "/usr/bin/git";
  *   readonly readOnly: boolean
  *   readonly text: string
  * }} PluginSyncReport
+ *
+ * @typedef {{
+ *   readonly path: string
+ *   readonly counterpart?: string
+ *   readonly classification: string
+ *   readonly nextAction: string
+ * }} PluginSyncRemediation
+ *
+ * @typedef {{
+ *   readonly root: string
+ *   readonly verdict: "PASS" | "WARN"
+ *   readonly driftClass: string
+ *   readonly affectedPaths: readonly string[]
+ *   readonly remediations: readonly PluginSyncRemediation[]
+ *   readonly findings: readonly PluginSyncFinding[]
+ *   readonly statusBefore: string
+ *   readonly statusAfter: string
+ *   readonly readOnly: boolean
+ * }} PluginSyncResult
  */
 
 /**
@@ -57,6 +76,25 @@ const GIT_BIN = "/usr/bin/git";
  * @returns {PluginSyncReport}
  */
 export function explainPluginSync(root = process.cwd()) {
+  const result = getPluginSyncResult(root);
+
+  return {
+    root: result.root,
+    findings: result.findings,
+    statusBefore: result.statusBefore,
+    statusAfter: result.statusAfter,
+    readOnly: result.readOnly,
+    text: renderPluginSyncReport(result),
+  };
+}
+
+/**
+ * Return a structured, read-only plugin sync result for readiness surfaces such
+ * as doctor. CLI callers should still render this through renderPluginSyncReport.
+ * @param {string} root
+ * @returns {PluginSyncResult}
+ */
+export function getPluginSyncResult(root = process.cwd()) {
   const repoRoot = path.resolve(root);
   const statusBefore = gitStatus(repoRoot);
   const statusEntries = parseGitStatus(statusBefore);
@@ -71,20 +109,23 @@ export function explainPluginSync(root = process.cwd()) {
   ];
   const statusAfter = gitStatus(repoRoot);
   const readOnly = statusAfter === statusBefore;
+  const driftClass = highestClassification(findings);
 
   return {
     root: repoRoot,
+    verdict: findings.length === 0 ? "PASS" : "WARN",
+    driftClass,
+    affectedPaths: affectedPaths(findings),
+    remediations: findings.map(finding => ({
+      path: finding.path,
+      counterpart: finding.counterpart,
+      classification: finding.classification,
+      nextAction: finding.nextAction,
+    })),
     findings,
     statusBefore,
     statusAfter,
     readOnly,
-    text: renderPluginSyncReport({
-      root: repoRoot,
-      findings,
-      statusBefore,
-      statusAfter,
-      readOnly,
-    }),
   };
 }
 
@@ -142,6 +183,22 @@ function highestClassification(findings) {
   return "IN_SYNC";
 }
 
+/**
+ * @param {readonly PluginSyncFinding[]} findings
+ * @returns {string[]}
+ */
+function affectedPaths(findings) {
+  return [
+    ...new Set(
+      findings.flatMap(finding =>
+        [finding.path, finding.counterpart].filter(
+          pathValue => typeof pathValue === "string" && pathValue.length > 0
+        )
+      )
+    ),
+  ];
+}
+
 /**
  * @param {readonly { readonly code: string, readonly file: string }[]} entries
  * @param {ReadonlyMap<string, Buffer> | undefined} expectedGeneratedFiles

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.128.1",
+  "version": "2.129.2",
   "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.128.1",
+  "version": "2.129.2",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/commands/exploratory-qa.md

@@ -1,5 +1,5 @@
 ---
-description: "Run a first-time-user exploratory QA walkthrough: experience the app like a brand-new human user, clicking through to find anything confusing, broken, or hard to understand (machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent UX, awkward scroll behavior) across all breakpoints, and file each finding (bug or usability issue) as a tracked work item via lisa:tracker-write. The optional ready flag marks tickets build-ready (auto-picked-up by lisa:intake) or leaves them in the backlog for human triage (default). For gaps in the automated Playwright suite, use e2e-coverage-gaps instead."
+description: "Run a first-time-user exploratory QA walkthrough: experience the app like a brand-new human user, clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent UX, awkward scroll behavior) across all breakpoints, and file each finding (bug or usability issue) as a tracked work item via lisa:tracker-write. The optional ready flag marks tickets build-ready (auto-picked-up by lisa:intake) or leaves them in the backlog for human triage (default). For gaps in the automated Playwright suite, use e2e-coverage-gaps instead."
 allowed-tools: ["Skill"]
 argument-hint: "[target-url | env] [ready=true|false]"
 ---

package/plugins/lisa-expo/skills/exploratory-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: exploratory-qa
-description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
+description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
 ---
 
 # Exploratory QA
@@ -49,9 +49,12 @@ filed as a tracked work item so it enters the Lisa lifecycle — no static repor
 Click through the visible paths and actually attempt real tasks — a first-time user explores, makes
 mistakes, and tries the obvious thing. Cover at least these dimensions unless the user narrows scope:
 
-- **Comprehension & labeling:** machine-style or developer labels shown to users (raw IDs, enum keys,
-  `snake_case`, `null`/`undefined`, untranslated i18n keys), jargon, unclear button/menu names, icons
-  with no discernible meaning.
+- **Comprehension & labeling:** human-facing copy must sound like something a normal first-time user
+  would understand. Flag machine-style or developer labels shown to users (raw IDs, enum keys,
+  `snake_case`, `null`/`undefined`, untranslated i18n keys), admin/database terms such as
+  "metadata", implementation identifiers such as slugs, unexplained domain jargon, unclear
+  button/menu names, and icons with no discernible meaning. If a heading, label, or field would make a
+  non-technical user ask "what does that mean?", file a usability/clarity ticket with plainer wording.
 - **Navigation clarity:** is it obvious how to get somewhere and back? Dead ends, hidden entry points,
   surprising redirects, broken links, no clear "home".
 - **Visual/layout quality:** cut-off or truncated text, overlap, cramped/crowded density, offscreen or

package/plugins/lisa-expo-agy/commands/exploratory-qa.md

@@ -1,5 +1,5 @@
 ---
-description: "Run a first-time-user exploratory QA walkthrough: experience the app like a brand-new human user, clicking through to find anything confusing, broken, or hard to understand (machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent UX, awkward scroll behavior) across all breakpoints, and file each finding (bug or usability issue) as a tracked work item via lisa:tracker-write. The optional ready flag marks tickets build-ready (auto-picked-up by lisa:intake) or leaves them in the backlog for human triage (default). For gaps in the automated Playwright suite, use e2e-coverage-gaps instead."
+description: "Run a first-time-user exploratory QA walkthrough: experience the app like a brand-new human user, clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent UX, awkward scroll behavior) across all breakpoints, and file each finding (bug or usability issue) as a tracked work item via lisa:tracker-write. The optional ready flag marks tickets build-ready (auto-picked-up by lisa:intake) or leaves them in the backlog for human triage (default). For gaps in the automated Playwright suite, use e2e-coverage-gaps instead."
 allowed-tools: ["Skill"]
 argument-hint: "[target-url | env] [ready=true|false]"
 ---

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

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

package/plugins/lisa-expo-agy/skills/exploratory-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: exploratory-qa
-description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
+description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
 ---
 
 # Exploratory QA
@@ -49,9 +49,12 @@ filed as a tracked work item so it enters the Lisa lifecycle — no static repor
 Click through the visible paths and actually attempt real tasks — a first-time user explores, makes
 mistakes, and tries the obvious thing. Cover at least these dimensions unless the user narrows scope:
 
-- **Comprehension & labeling:** machine-style or developer labels shown to users (raw IDs, enum keys,
-  `snake_case`, `null`/`undefined`, untranslated i18n keys), jargon, unclear button/menu names, icons
-  with no discernible meaning.
+- **Comprehension & labeling:** human-facing copy must sound like something a normal first-time user
+  would understand. Flag machine-style or developer labels shown to users (raw IDs, enum keys,
+  `snake_case`, `null`/`undefined`, untranslated i18n keys), admin/database terms such as
+  "metadata", implementation identifiers such as slugs, unexplained domain jargon, unclear
+  button/menu names, and icons with no discernible meaning. If a heading, label, or field would make a
+  non-technical user ask "what does that mean?", file a usability/clarity ticket with plainer wording.
 - **Navigation clarity:** is it obvious how to get somewhere and back? Dead ends, hidden entry points,
   surprising redirects, broken links, no clear "home".
 - **Visual/layout quality:** cut-off or truncated text, overlap, cramped/crowded density, offscreen or

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

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

package/plugins/lisa-expo-copilot/commands/exploratory-qa.md

@@ -1,5 +1,5 @@
 ---
-description: "Run a first-time-user exploratory QA walkthrough: experience the app like a brand-new human user, clicking through to find anything confusing, broken, or hard to understand (machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent UX, awkward scroll behavior) across all breakpoints, and file each finding (bug or usability issue) as a tracked work item via lisa:tracker-write. The optional ready flag marks tickets build-ready (auto-picked-up by lisa:intake) or leaves them in the backlog for human triage (default). For gaps in the automated Playwright suite, use e2e-coverage-gaps instead."
+description: "Run a first-time-user exploratory QA walkthrough: experience the app like a brand-new human user, clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent UX, awkward scroll behavior) across all breakpoints, and file each finding (bug or usability issue) as a tracked work item via lisa:tracker-write. The optional ready flag marks tickets build-ready (auto-picked-up by lisa:intake) or leaves them in the backlog for human triage (default). For gaps in the automated Playwright suite, use e2e-coverage-gaps instead."
 allowed-tools: ["Skill"]
 argument-hint: "[target-url | env] [ready=true|false]"
 ---

package/plugins/lisa-expo-copilot/skills/exploratory-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: exploratory-qa
-description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
+description: First-time-user exploratory QA walkthrough for web apps that FEEDS THE LIFECYCLE. Use when asked to experience an app the way a brand-new human user would — landing cold on the home page and clicking through to find anything confusing, broken, or hard to understand (human-facing jargon, machine-style labels, slow or unclear loads, cramped or cut-off UI, inconsistent/non-standard UX, awkward scroll behavior, unclear affordances) across all breakpoints. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write (bugs and usability/UX issues). A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated Playwright test suite, use the e2e-coverage-gaps skill instead.
 ---
 
 # Exploratory QA
@@ -49,9 +49,12 @@ filed as a tracked work item so it enters the Lisa lifecycle — no static repor
 Click through the visible paths and actually attempt real tasks — a first-time user explores, makes
 mistakes, and tries the obvious thing. Cover at least these dimensions unless the user narrows scope:
 
-- **Comprehension & labeling:** machine-style or developer labels shown to users (raw IDs, enum keys,
-  `snake_case`, `null`/`undefined`, untranslated i18n keys), jargon, unclear button/menu names, icons
-  with no discernible meaning.
+- **Comprehension & labeling:** human-facing copy must sound like something a normal first-time user
+  would understand. Flag machine-style or developer labels shown to users (raw IDs, enum keys,
+  `snake_case`, `null`/`undefined`, untranslated i18n keys), admin/database terms such as
+  "metadata", implementation identifiers such as slugs, unexplained domain jargon, unclear
+  button/menu names, and icons with no discernible meaning. If a heading, label, or field would make a
+  non-technical user ask "what does that mean?", file a usability/clarity ticket with plainer wording.
 - **Navigation clarity:** is it obvious how to get somewhere and back? Dead ends, hidden entry points,
   surprising redirects, broken links, no clear "home".
 - **Visual/layout quality:** cut-off or truncated text, overlap, cramped/crowded density, offscreen or