@codyswann/lisa 2.346.0 → 2.349.0

package/expo/create-only/.github/workflows/nightly-e2e-bypass-reaper.yml

@@ -0,0 +1,83 @@
+name: 🧹 Nightly E2E Bypass Reaper
+
+# Removes a used `nightly-e2e-bypass` label when its pull request closes.
+#
+# ## Why removal happens on CLOSE and not on USE
+#
+# The obvious implementation — have the gate strip the label as soon as it
+# honours it — is wrong, and wrong in a way that is easy to ship and hard to
+# diagnose. Removing the label fires `unlabeled`, which re-runs the gate, which
+# now sees no bypass and goes RED. The PR is blocked again by the very mechanism
+# meant to unblock it, and the only way out is to re-apply the label, which the
+# gate then strips again. So the gate itself never writes; this single-purpose
+# workflow does the cleanup once the PR can no longer be affected by it.
+#
+# Expiry is the belt to this suspenders. Even where this reaper is not
+# installed, a bypass stops working `bypass_max_hours` after the label was
+# applied (default 24, hard ceiling 72). The reaper keeps the label list honest;
+# it is not what bounds the waiver's lifetime.
+#
+# ## Why the audit survives removal
+#
+# The audit record lives in the gate's job summary, its `::notice::` annotation
+# and its `audit_json` output on the run that honoured the bypass — none of which
+# this workflow touches. Removing the label removes the REQUEST, never the
+# RECORD.
+
+on:
+  pull_request_target:
+    types: [closed]
+
+permissions:
+  contents: read
+  # The one write in the whole nightly-gate standard, scoped to removing one
+  # label from an already-closed PR.
+  pull-requests: write
+
+concurrency:
+  group: nightly-e2e-bypass-reaper-${{ github.event.pull_request.number }}
+  cancel-in-progress: false
+
+jobs:
+  reap:
+    name: 🧹 Remove used bypass label
+    # `pull_request_target` runs with a writable token against the BASE repo, so
+    # this job must never check out or execute pull-request code. It does not:
+    # there is no checkout step and the only command is a `gh` API call.
+    if: contains(github.event.pull_request.labels.*.name, 'nightly-e2e-bypass')
+    runs-on: ubuntu-latest
+    timeout-minutes: 5
+    steps:
+      - name: 🧹 Strip the bypass label
+        env:
+          GH_TOKEN: ${{ github.token }}
+          REPO: ${{ github.repository }}
+          PR: ${{ github.event.pull_request.number }}
+          LABEL: nightly-e2e-bypass
+        run: |
+          set -euo pipefail
+          echo "Removing '$LABEL' from $REPO#$PR (state: ${{ github.event.pull_request.merged && 'merged' || 'closed' }})."
+          # ONE delete. Someone removing the label between the event and this
+          # run is the desired end state, not a failure — but a permission or
+          # API problem must NEVER look like a successful reap, or the label
+          # list quietly stops being trustworthy.
+          #
+          # `set -e` is disabled around the call so a non-zero exit is inspected
+          # rather than killing the step, and the outcome is then decided by
+          # asking whether the label is actually gone. Reading the status out of
+          # `--include` does not work: `--silent` suppresses the output that
+          # would carry it.
+          set +e
+          gh api -X DELETE "repos/$REPO/issues/$PR/labels/$LABEL" --silent 2>/dev/null
+          deleted=$?
+          set -e
+          if [[ $deleted -eq 0 ]]; then
+            echo "::notice title=Nightly E2E bypass label removed::'$LABEL' cleared from #$PR after close. The audit record on the gate run that honoured it is unaffected."
+            exit 0
+          fi
+          if gh api "repos/$REPO/issues/$PR/labels" --jq '.[].name' 2>/dev/null \
+            | grep -qxF "$LABEL"; then
+            echo "::error title=Nightly E2E bypass label NOT removed::'$LABEL' is still on #$PR and the delete failed. Check that this workflow's token carries \`pull-requests: write\`."
+            exit 1
+          fi
+          echo "::notice title=Nightly E2E bypass label already gone::'$LABEL' was not on #$PR by the time the reaper ran. Nothing to do."

package/expo/create-only/.github/workflows/nightly-e2e-health.yml

@@ -0,0 +1,140 @@
+name: 🌙 Nightly E2E Health
+
+# The blocking half of the nightly e2e standard.
+#
+# The e2e suites are too slow to gate a pull request, so they run on a schedule
+# against the integration branch. That trade buys fast PRs and pays for them
+# with a signal nobody is obliged to read: a nightly can go red and merges
+# continue on top of it for days, so the suite ends up measuring accumulated
+# damage rather than the change that caused it. This workflow closes the loop —
+# it runs no e2e itself, it reads the verdict the nightlies already produced, so
+# it costs seconds and adds nothing to PR latency.
+#
+# All the logic lives in Lisa's reusable `nightly-e2e-health.yml` plus the
+# Lisa-shipped guard `scripts/check-nightly-e2e-health.mjs`. The contract —
+# including the 25-row fail-closed truth table and the bypass rules — is
+# `docs/nightly-e2e-gate.md` in Lisa. This caller owns only the project-specific
+# values: which suites, which branch, and where the gate is required.
+#
+# ## Wiring this up, in order
+#
+#   1. Fill in `suites` below with YOUR workflow file names and job names. The
+#      job name for a suite reached through a nested reusable workflow is
+#      reported by the API as `<caller job name> / <called job name>` — copy it
+#      from a real run, do not guess it.
+#   2. Leave `bootstrap_until` set to a date ~2 weeks out while you burn the
+#      suite down. Missing evidence will report but not block, with the expiry
+#      visible on every PR. A red suite still blocks. When the date passes the
+#      gate arms itself with no further action.
+#   3. Add the required status check to the ruleset for the branch below. The
+#      context is `🌙 Nightly E2E Health / 🌙 Gate` — the composite of THIS
+#      job's name and the reusable's job name, byte for byte, emoji included.
+#      `expo/github-rulesets/nightly-e2e-health.json` in Lisa is the template.
+#   4. Add the context-pinning test (see the ruleset template's header) so a
+#      rename of either half cannot silently disarm the gate.
+#   5. Install `nightly-e2e-bypass-reaper.yml` so a used bypass label is removed
+#      when the PR closes.
+#
+# ## Scoped to PRs targeting the integration branch, on purpose
+#
+# `branches:` filters by BASE branch, and it must pair with where the context is
+# required. Two reasons, each load-bearing:
+#
+#   1. A required context whose workflow never runs on that branch is a DEADLOCK,
+#      not a gate — the check is never reported, so the PR can never go green.
+#   2. Release and hotfix branches receive promotion PRs. Blocking a hotfix to
+#      production because last night's dev suite was red blocks the fix for the
+#      failure, which inverts the point of the gate.
+#
+# So: required where the work lands, absent where the releases go.
+
+on:
+  pull_request:
+    # Set this to your integration branch (the one the nightlies run against).
+    branches: [dev]
+    # No `paths:` filter, deliberately. A required context that a path filter
+    # can suppress never reports on a docs-only PR, which blocks that PR
+    # forever. This job takes seconds; it always runs.
+    #
+    # `labeled` / `unlabeled` ride on top of the defaults so applying (or
+    # removing) the bypass label re-evaluates the gate immediately instead of
+    # requiring an empty push to re-trigger `synchronize`.
+    types: [opened, synchronize, reopened, labeled, unlabeled]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  # The whole job is Actions-API reads. Nothing here writes.
+  actions: read
+  # Only needed on a PRIVATE repository, and only for the bypass path (reading
+  # the PR timeline to attribute the label). Harmless to keep on a public repo.
+  pull-requests: read
+
+concurrency:
+  # Per-PR and CANCELLING: this job holds no external state and writes to
+  # nothing, so a superseded run is pure waste. Note the fail-closed
+  # interaction: a cancelled gate run reports NO check, which leaves the
+  # required context unreported and the PR blocked until the newer run reports.
+  group: nightly-e2e-health-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  # This job's `name:` is HALF of the required status-check context; the other
+  # half is the reusable's job name (`🌙 Gate`). GitHub composes them as
+  # `🌙 Nightly E2E Health / 🌙 Gate`. Renaming either half silently stops the
+  # gate reporting, which DEADLOCKS every PR into the protected branch until
+  # someone edits the ruleset. Pin both strings in a test.
+  health:
+    name: 🌙 Nightly E2E Health
+    # PIN AN IMMUTABLE REF. `@main` is not a supported pin for a merge gate: the
+    # thing that decides whether code may merge must not change under you
+    # between two runs of the same PR. Better still, pin the tag's commit SHA
+    # and keep the tag in a trailing comment.
+    uses: CodySwannGT/lisa/.github/workflows/nightly-e2e-health.yml@v2.345.1
+    with:
+      branch: dev
+      # Structured JSON, schema-validated before any API call. Duplicated
+      # labels, unanchored regexes, unknown keys and zero-match patterns are all
+      # rejected rather than silently gating less than you wrote.
+      #
+      # Prefer `{"mode":"run"}` (the whole workflow IS the suite) or
+      # `{"mode":"job","name":"…"}` (an exact, published job name). Use
+      # `{"mode":"job_pattern","pattern":"^…$"}` only for matrix job names that
+      # no single string can cover.
+      #
+      # ONLY `maestro-e2e.yml` by default, because that is the only nightly
+      # suite this template actually ships. Naming a workflow file that does not
+      # exist is truth-table row 11 — a HARD failure, not missing evidence —
+      # since the API cannot tell "renamed out from under the gate" apart from
+      # "never existed". A default that red-walls a fresh fork would teach the
+      # first adopter to delete the gate.
+      #
+      # Add your browser suite here once you have one. If Playwright runs inside
+      # `ci.yml`'s scheduled arm rather than its own workflow, use `mode: "job"`
+      # with the job name copied from a REAL run — for a job inside a nested
+      # reusable workflow the API reports `<caller job> / <called job>`:
+      #
+      #   {
+      #     "label": "Playwright browser e2e",
+      #     "workflow": "ci.yml",
+      #     "match": {
+      #       "mode": "job",
+      #       "name": "🔍 Quality Checks / 🎭 Playwright E2E Tests"
+      #     }
+      #   }
+      #
+      # Do NOT add a suite whose job `ci.yml` skips — a skipped job never
+      # reports, and the gate would read it as missing evidence forever.
+      suites: |
+        [
+          {
+            "label": "Maestro native e2e",
+            "workflow": "maestro-e2e.yml",
+            "match": { "mode": "run" }
+          }
+        ]
+      # A TIME-BOXED grace period. While this is in the future, MISSING evidence
+      # reports but does not block, and every PR shows the expiry. A red suite
+      # blocks inside the window too. Set it, do not remove it — and do not push
+      # it out repeatedly, which is how a bootstrap becomes permanent.
+      bootstrap_until: ''

package/expo/create-only/bdd/coverage-map.json

@@ -0,0 +1,38 @@
+{
+  "_comment": "BDD behavior contract, machine-readable half. See the Lisa rule `bdd-e2e-coverage` and docs/bdd-coverage-schema.md. Seeded in the `not-adopted` state: the gate reports and exits 0, and the BDD check MUST NOT be a required ruleset context until adoption.state is `enforced`. Adopt in one operation: set adoption.state, pass the matching bdd_mode from ci.yml, and add the ruleset context together.",
+  "schemaVersion": 2,
+  "asOf": "1970-01-01",
+  "adoption": {
+    "_comment": "not-adopted | bootstrap | enforced. Must equal the bdd_mode this repo's ci.yml passes to Lisa's quality.yml. bootstrap additionally requires `owner` (a named person) and `expiresAt` (an ISO date) — a bootstrap with no time-box never ends.",
+    "state": "not-adopted",
+    "owner": null,
+    "expiresAt": null
+  },
+  "runnerPlatforms": {
+    "_comment": "The ONLY place a test runner is named authoritatively. Declare each runner this project has and the platforms it covers, e.g. {\"playwright\": [\"web\"], \"maestro\": [\"ios\", \"android\"]}. Platform vocabulary is this project's own.",
+    "playwright": ["web"],
+    "maestro": ["ios", "android"]
+  },
+  "coverageFloor": {
+    "_comment": "Committed traceability floor per platform. A ratchet: may rise, may never fall. Seeded at 0 so adopting on a brownfield app never red-gates CI before any scenario exists. Lowering one requires a coverageFloorBaseline record naming the exact change AND the maintainer-applied `bdd-floor-baseline` pull-request label.",
+    "web": 0,
+    "ios": 0,
+    "android": 0
+  },
+  "coverageFloorBaseline": [],
+  "retirements": [],
+  "trackers": {
+    "_comment": "Tracker-tag grammar is portfolio-wide; the allowed keys and repos are per-repo. Key style: @TUN-123, @SE-6833. Repo-issue style: @gh-2394 (this repo) or @gh-wiki-124 (a sibling repo). Tags are validated for syntax and membership only — the gate never contacts a tracker, so an unreachable issue can never block a merge.",
+    "required": false,
+    "keys": [],
+    "keyUrlTemplate": null,
+    "github": {
+      "org": null,
+      "defaultRepo": null,
+      "repos": []
+    }
+  },
+  "platformWaivers": [],
+  "mappings": [],
+  "exclusions": []
+}

package/expo/create-only/bdd/features/.keep

@@ -0,0 +1,5 @@
+# Gherkin behavior contract lives here as *.feature files.
+#
+# Each scenario carries one stable @BDD-<DOMAIN>-<NNN> id, the platforms it
+# requires, @figma-*/@ratified-* provenance, and a tracker tag (@TUN-123,
+# @SE-6833, @gh-2394, @gh-wiki-124). See the Lisa rule bdd-e2e-coverage.

package/expo/github-rulesets/{playwright.json → bdd-coverage.json}

@@ -1,11 +1,11 @@
 {
-  "name": "playwright",
+  "name": "bdd-behavior-contract",
   "target": "branch",
   "enforcement": "active",
   "conditions": {
     "ref_name": {
       "exclude": [],
-      "include": ["refs/heads/staging"]
+      "include": ["~DEFAULT_BRANCH"]
     }
   },
   "bypass_actors": [
@@ -13,11 +13,6 @@
       "actor_id": null,
       "actor_type": "DeployKey",
       "bypass_mode": "always"
-    },
-    {
-      "actor_id": 5,
-      "actor_type": "RepositoryRole",
-      "bypass_mode": "always"
     }
   ],
   "rules": [
@@ -28,7 +23,7 @@
         "do_not_enforce_on_create": true,
         "required_status_checks": [
           {
-            "context": "🔍 Quality Checks / 🎭 Playwright E2E Tests",
+            "context": "🔍 Quality Checks / 🧾 BDD Behavior Contract",
             "integration_id": 15368
           }
         ]

package/expo/github-rulesets/nightly-e2e-health.json

@@ -0,0 +1,33 @@
+{
+  "name": "nightly e2e health",
+  "target": "branch",
+  "enforcement": "active",
+  "conditions": {
+    "ref_name": {
+      "exclude": [],
+      "include": ["refs/heads/dev"]
+    }
+  },
+  "bypass_actors": [
+    {
+      "actor_id": null,
+      "actor_type": "DeployKey",
+      "bypass_mode": "always"
+    }
+  ],
+  "rules": [
+    {
+      "type": "required_status_checks",
+      "parameters": {
+        "strict_required_status_checks_policy": false,
+        "do_not_enforce_on_create": true,
+        "required_status_checks": [
+          {
+            "context": "🌙 Nightly E2E Health / 🌙 Gate",
+            "integration_id": 15368
+          }
+        ]
+      }
+    }
+  ]
+}

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

@@ -11,6 +11,9 @@
       "maestro:test:android": "maestro test -p android .maestro/flows",
       "maestro:test:smoke": "maestro test -p ios --include-tags=smoke .maestro/flows",
       "maestro:studio": "maestro studio",
+      "bdd:coverage": "node scripts/check-bdd-coverage.mjs",
+      "bdd:coverage:write": "node scripts/check-bdd-coverage.mjs --write",
+      "bdd:matrix": "node scripts/bdd-matrix.mjs --write",
       "start:local": "cp .env.localhost .env.local && STAGE=local expo start",
       "start:dev": "cp .env.development .env.local && STAGE=development expo start",
       "start:staging": "cp .env.staging .env.local && STAGE=staging expo start",

package/package.json

@@ -120,7 +120,7 @@
     }
   },
   "name": "@codyswann/lisa",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {

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

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

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

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

package/plugins/lisa-agy/plugin.json

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "AWS CDK-specific Lisa plugin.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "NestJS-specific skills and migration write-protection hooks.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.346.0",
+  "version": "2.349.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.346.0",
+  "version": "2.349.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": "2.346.0",
+  "version": "2.349.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": "2.346.0",
+  "version": "2.349.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": "2.346.0",
+  "version": "2.349.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"