@codyswann/lisa 3.56.0 → 3.58.0

package/expo/copy-overwrite/scripts/bdd/baseline.mjs

@@ -41,9 +41,6 @@ const defect = (code, message) => ({ code, message });
 /** Defect / evidence code, named once. */
 const SCENARIO_DELETED = "scenario-deleted";
 
-/** The maintainer-applied PR label that authorizes giving coverage back. */
-export const BASELINE_LABEL = "bdd-floor-baseline";
-
 /**
  * Fixed absolute locations git is installed at, tried before anything on PATH.
  *
@@ -301,15 +298,23 @@ const RETIREMENT_FIELDS = ["reason", "ticket", "approvedBy", "recordedAt"];
 
 /**
  * Whether a scenario has been retired the way the contract requires: a
- * complete `retirements` record AND the maintainer-applied label. Either alone
- * is not an authorization — that is the whole point of asking for two
- * artifacts one author cannot produce by editing one file.
+ * COMPLETE `retirements` record.
+ *
+ * This used to also demand a maintainer-applied PR label, on the reasoning that
+ * two artifacts one author cannot produce alone is a stronger guarantee than
+ * one. The label was dropped because it guarantees the wrong thing: it verifies
+ * that a second person clicked, not that the behavior is actually gone, and it
+ * stalls the case it was most needed for — an agent retiring coverage for a
+ * feature the product genuinely no longer has.
+ *
+ * The record is the part that carries information. It still owes every field in
+ * {@link RETIREMENT_FIELDS}, is still refused when incomplete, and still lands
+ * in the diff where it can be read and challenged.
  * @param {object|undefined} record - The retirements entry, if any.
- * @param {readonly string[]} labels - PR labels.
- * @returns {boolean} True when the retirement is authorized and complete.
+ * @returns {boolean} True when the retirement is complete.
  */
-function isRetired(record, labels) {
-  if (!record || !labels.includes(BASELINE_LABEL)) return false;
+function isRetired(record) {
+  if (!record) return false;
   return RETIREMENT_FIELDS.every(field => Boolean(record[field]));
 }
 
@@ -324,15 +329,10 @@ function isRetired(record, labels) {
  * Keys whose scenario disappeared from the contract entirely are left to
  * {@link checkDeletions}, which names that act precisely; reporting both would
  * describe one deletion as two different failures.
- * @param {object} input - Baseline, head contract and scenarios, and PR labels.
+ * @param {object} input - Baseline, and head contract and scenarios.
  * @returns {object[]} Defects found.
  */
-export function checkCoverageRegression({
-  baseline,
-  contract,
-  scenarios,
-  labels,
-}) {
+export function checkCoverageRegression({ baseline, contract, scenarios }) {
   const before = acceptedKeys(baseline.scenarios, baseline.contract);
   const after = acceptedKeys(scenarios, contract);
   const present = new Set(scenarios.map(scenario => scenario.id));
@@ -343,42 +343,42 @@ export function checkCoverageRegression({
   return [...before]
     .filter(key => !after.has(key) && present.has(partsOf(key).scenario))
     .sort(byCodeUnit)
-    .flatMap(key => regressionDefect(key, { retired, waived, labels }));
+    .flatMap(key => regressionDefect(key, { retired, waived }));
 }
 
 /**
  * The defect for one obligation whose accepted coverage disappeared, or none
  * when it left the denominator through an authorized route.
  * @param {string} key - The `SCENARIO:platform` key.
- * @param {object} input - Retirement records, waived keys, and PR labels.
+ * @param {object} input - Retirement records and waived keys.
  * @returns {object[]} Zero or one defect.
  */
-function regressionDefect(key, { retired, waived, labels }) {
+function regressionDefect(key, { retired, waived }) {
   const { scenario, platform } = partsOf(key);
-  if (isRetired(retired.get(scenario), labels)) return [];
-  if (waived.has(key) && labels.includes(BASELINE_LABEL)) return [];
+  if (isRetired(retired.get(scenario))) return [];
+  if (waived.has(key)) return [];
   return [
     defect(
       "coverage-regression",
-      `${scenario}:${platform} was covered at the base revision and is not covered here. Coverage this repository already accepted cannot be handed back quietly. Restore the mapping, or take one of the two recorded routes out — a retirements record (${RETIREMENT_FIELDS.join(", ")}) for a behavior the product no longer has, or a platformWaivers entry for a runner that cannot decide it — and get the maintainer-applied "${BASELINE_LABEL}" label on this pull request. ${routeTaken(key, { retired, waived, labels })}`
+      `${scenario}:${platform} was covered at the base revision and is not covered here. Coverage this repository already accepted cannot be handed back quietly. Restore the mapping, or take one of the two recorded routes out — a retirements record (${RETIREMENT_FIELDS.join(", ")}) for a behavior the product no longer has, or a platformWaivers entry for a runner that cannot decide it. ${routeTaken(key, { retired })}`
     ),
   ];
 }
 
 /**
- * Say which half of the authorization is missing, so the operator is told what
- * to do rather than only what went wrong.
+ * Say what is missing from the authorization, so the operator is told what to
+ * do rather than only what went wrong.
+ *
+ * Only reached for a key that took NEITHER route: {@link regressionDefect}
+ * returns early for a waived one, so the waiver set cannot inform this
+ * sentence and is not passed.
  * @param {string} key - The `SCENARIO:platform` key.
- * @param {object} input - Retirement records, waived keys, labels, contract.
+ * @param {object} input - Retirement records.
  * @returns {string} A one-sentence next step.
  */
-function routeTaken(key, { retired, waived, labels }) {
+function routeTaken(key, { retired }) {
   const { scenario } = partsOf(key);
   const record = retired.get(scenario);
-  const authorized = labels.includes(BASELINE_LABEL);
-  if ((record || waived.has(key)) && !authorized) {
-    return `A record is present but the "${BASELINE_LABEL}" label is not: recording a reduction in the same pull request that makes it is not an authorization.`;
-  }
   if (record) {
     const missing = RETIREMENT_FIELDS.filter(field => !record[field]);
     return `Its retirements record is incomplete (no ${missing.join(", no ")}).`;
@@ -419,10 +419,10 @@ export function checkNewObligations({ baseline, contract, scenarios }) {
  * The contract's answer to a retired behavior is `@superseded`, which keeps
  * the audit trail. Deleting the scenario instead makes coverage look better
  * by describing less of the product.
- * @param {object} input - Base IDs, head scenarios, and the PR labels.
+ * @param {object} input - Base IDs and head scenarios.
  * @returns {object[]} Defects found.
  */
-export function checkDeletions({ baseIds, scenarios, contract, labels }) {
+export function checkDeletions({ baseIds, scenarios, contract }) {
   const present = new Set(scenarios.map(scenario => scenario.id));
   const retired = new Map(
     (contract.retirements ?? []).map(entry => [entry.scenario, entry])
@@ -430,22 +430,21 @@ export function checkDeletions({ baseIds, scenarios, contract, labels }) {
   return [...baseIds]
     .filter(id => !present.has(id))
     .sort(byCodeUnit)
-    .flatMap(id => deletionDefects(id, retired.get(id), labels));
+    .flatMap(id => deletionDefects(id, retired.get(id)));
 }
 
 /**
  * Defects for one deleted scenario.
  * @param {string} id - The scenario ID that disappeared.
  * @param {object|undefined} record - Its retirement record, if any.
- * @param {readonly string[]} labels - PR labels.
  * @returns {object[]} Defects found.
  */
-function deletionDefects(id, record, labels) {
+function deletionDefects(id, record) {
   if (!record) {
     return [
       defect(
         SCENARIO_DELETED,
-        `${id} was deleted from the contract. Retiring a behavior is @superseded, not deletion — deleting it shrinks the denominator instead of the gap. A genuine removal needs a retirements record and the "${BASELINE_LABEL}" label.`
+        `${id} was deleted from the contract. Retiring a behavior is @superseded, not deletion — deleting it shrinks the denominator instead of the gap. A genuine removal needs a complete retirements record (${RETIREMENT_FIELDS.join(", ")}).`
       ),
     ];
   }
@@ -453,13 +452,5 @@ function deletionDefects(id, record, labels) {
   const defects = missing.map(field =>
     defect(SCENARIO_DELETED, `${id}: retirements record has no ${field}`)
   );
-  if (!labels.includes(BASELINE_LABEL)) {
-    defects.push(
-      defect(
-        SCENARIO_DELETED,
-        `${id}: a retirement needs the maintainer-applied "${BASELINE_LABEL}" label`
-      )
-    );
-  }
   return defects;
 }

package/expo/copy-overwrite/scripts/bdd/render.mjs

@@ -208,7 +208,7 @@ ${executionSection(report)}
 
 ## Coverage floor
 
-The committed floor is an absolute bar — "is this platform below it right now" — and nothing else. It is **not** a ratchet and nobody has to nudge it upward: what protects coverage already earned is a separate, per-obligation check. Coverage accepted at the base revision cannot disappear, and behavior that is new must arrive mapped or waived; either reduction takes a recorded route (a \`retirements\` record or a \`platformWaivers\` entry) plus the maintainer-applied \`bdd-floor-baseline\` label — two artifacts one author cannot produce alone.
+The committed floor is an absolute bar — "is this platform below it right now" — and nothing else. It is **not** a ratchet and nobody has to nudge it upward: what protects coverage already earned is a separate, per-obligation check. Coverage accepted at the base revision cannot disappear, and behavior that is new must arrive mapped or waived; either reduction takes a recorded route — a complete \`retirements\` record or a \`platformWaivers\` entry — which lands in the diff where it can be read and challenged.
 
 ${floorTable(report)}
 

package/expo/copy-overwrite/scripts/check-bdd-coverage.mjs

@@ -312,14 +312,12 @@ function validateAll({
       baseline,
       contract,
       scenarios,
-      labels: options.labels,
     }),
     ...checkNewObligations({ baseline, contract, scenarios }),
     ...checkDeletions({
       baseIds: baseline.scenarioIds,
       scenarios,
       contract,
-      labels: options.labels,
     }),
   ];
 }
@@ -679,10 +677,6 @@ export function parseArgs(argv, env) {
     report: argv.includes("--report"),
     resultFiles,
     baseSha: env.BDD_BASE_SHA || null,
-    labels: (env.BDD_PR_LABELS ?? "")
-      .split(",")
-      .map(item => item.trim())
-      .filter(Boolean),
     today: env.BDD_TODAY || new Date().toISOString().slice(0, 10),
   };
 }

package/package.json

@@ -141,7 +141,7 @@
     "zod-validation-error": "^4.0.0"
   },
   "name": "@codyswann/lisa",
-  "version": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.0",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/skills/lisa-setup-sonar/SKILL.md

@@ -12,7 +12,7 @@ unattended factories run. It replaces Lisa's former hand-rolled SonarCloud REST
 access with the vendor's official token-authed MCP, which is Lisa's single Sonar
 substrate on both developer machines and headless cloud routines.
 
-This does **not** touch the CI SonarCloud SAST job in `quality.yml` or its
+This does **not** touch the CI static-security job in `quality.yml` or its
 `SONAR_TOKEN` secret — that enforcement gate is separate and stays as-is.
 
 ## Supported agents

package/plugins/lisa/rules/reference/bdd-e2e-coverage.md

@@ -145,9 +145,9 @@ forces it upward, and lowering it needs no ceremony.
 
 What stops coverage sliding backwards is checked directly, per obligation, against the base
 revision — **an obligation that was mapped may not stop being mapped, and new behavior arrives
-mapped or waived**. Giving coverage back is legitimate but takes two artifacts one author cannot
-produce alone: a recorded route (a `retirements` record or a `platformWaivers` entry) plus the
-maintainer-applied `bdd-floor-baseline` label. Gaps that predate the change are burndown, never a
+mapped or waived**. Giving coverage back is legitimate but takes a recorded route: a complete `retirements`
+record (for a behavior the product no longer has) or a `platformWaivers` entry (for a runner
+that cannot decide it). Gaps that predate the change are burndown, never a
 gate failure — which is what lets a brownfield project adopt `enforced` without first backfilling
 its whole history.
 

package/plugins/lisa/skills/lisa-setup-sonar/SKILL.md

@@ -12,7 +12,7 @@ unattended factories run. It replaces Lisa's former hand-rolled SonarCloud REST
 access with the vendor's official token-authed MCP, which is Lisa's single Sonar
 substrate on both developer machines and headless cloud routines.
 
-This does **not** touch the CI SonarCloud SAST job in `quality.yml` or its
+This does **not** touch the CI static-security job in `quality.yml` or its
 `SONAR_TOKEN` secret — that enforcement gate is separate and stays as-is.
 
 ## Supported agents

package/plugins/lisa-agy/plugin.json

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

package/plugins/lisa-agy/skills/lisa-setup-sonar/SKILL.md

@@ -12,7 +12,7 @@ unattended factories run. It replaces Lisa's former hand-rolled SonarCloud REST
 access with the vendor's official token-authed MCP, which is Lisa's single Sonar
 substrate on both developer machines and headless cloud routines.
 
-This does **not** touch the CI SonarCloud SAST job in `quality.yml` or its
+This does **not** touch the CI static-security job in `quality.yml` or its
 `SONAR_TOKEN` secret — that enforcement gate is separate and stays as-is.
 
 ## Supported agents

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.0",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-copilot/rules/reference/bdd-e2e-coverage.md

@@ -145,9 +145,9 @@ forces it upward, and lowering it needs no ceremony.
 
 What stops coverage sliding backwards is checked directly, per obligation, against the base
 revision — **an obligation that was mapped may not stop being mapped, and new behavior arrives
-mapped or waived**. Giving coverage back is legitimate but takes two artifacts one author cannot
-produce alone: a recorded route (a `retirements` record or a `platformWaivers` entry) plus the
-maintainer-applied `bdd-floor-baseline` label. Gaps that predate the change are burndown, never a
+mapped or waived**. Giving coverage back is legitimate but takes a recorded route: a complete `retirements`
+record (for a behavior the product no longer has) or a `platformWaivers` entry (for a runner
+that cannot decide it). Gaps that predate the change are burndown, never a
 gate failure — which is what lets a brownfield project adopt `enforced` without first backfilling
 its whole history.
 

package/plugins/lisa-copilot/skills/lisa-setup-sonar/SKILL.md

@@ -12,7 +12,7 @@ unattended factories run. It replaces Lisa's former hand-rolled SonarCloud REST
 access with the vendor's official token-authed MCP, which is Lisa's single Sonar
 substrate on both developer machines and headless cloud routines.
 
-This does **not** touch the CI SonarCloud SAST job in `quality.yml` or its
+This does **not** touch the CI static-security job in `quality.yml` or its
 `SONAR_TOKEN` secret — that enforcement gate is separate and stays as-is.
 
 ## Supported agents

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

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

package/plugins/lisa-cursor/rules/bdd-e2e-coverage-reference.mdc

@@ -150,9 +150,9 @@ forces it upward, and lowering it needs no ceremony.
 
 What stops coverage sliding backwards is checked directly, per obligation, against the base
 revision — **an obligation that was mapped may not stop being mapped, and new behavior arrives
-mapped or waived**. Giving coverage back is legitimate but takes two artifacts one author cannot
-produce alone: a recorded route (a `retirements` record or a `platformWaivers` entry) plus the
-maintainer-applied `bdd-floor-baseline` label. Gaps that predate the change are burndown, never a
+mapped or waived**. Giving coverage back is legitimate but takes a recorded route: a complete `retirements`
+record (for a behavior the product no longer has) or a `platformWaivers` entry (for a runner
+that cannot decide it). Gaps that predate the change are burndown, never a
 gate failure — which is what lets a brownfield project adopt `enforced` without first backfilling
 its whole history.
 

package/plugins/lisa-cursor/skills/lisa-setup-sonar/SKILL.md

@@ -12,7 +12,7 @@ unattended factories run. It replaces Lisa's former hand-rolled SonarCloud REST
 access with the vendor's official token-authed MCP, which is Lisa's single Sonar
 substrate on both developer machines and headless cloud routines.
 
-This does **not** touch the CI SonarCloud SAST job in `quality.yml` or its
+This does **not** touch the CI static-security job in `quality.yml` or its
 `SONAR_TOKEN` secret — that enforcement gate is separate and stays as-is.
 
 ## Supported agents

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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": "3.56.0",
+  "version": "3.58.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-agy/plugin.json

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "3.56.0",
+  "version": "3.58.0",
   "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": "3.56.0",
+  "version": "3.58.0",
   "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": "3.56.0",
+  "version": "3.58.0",
   "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": "3.56.0",
+  "version": "3.58.0",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"