@codyswann/lisa 2.204.0 → 2.204.2

package/expo/create-only/.github/workflows/deploy.yml

@@ -47,6 +47,8 @@ jobs:
     name: 🌍 Determine Environment
     runs-on: ubuntu-latest
     timeout-minutes: 5
+    permissions:
+      contents: read
     outputs:
       environment: ${{ steps.env.outputs.environment }}
       approval_environment: ${{ steps.approval.outputs.approval_environment }}
@@ -88,6 +90,9 @@ jobs:
     # Reference to the quality checks workflow
     uses: CodySwannGT/lisa/.github/workflows/release.yml@main
     needs: [determine_environment]
+    permissions:
+      contents: write
+      pull-requests: read
     with:
       environment: ${{ needs.determine_environment.outputs.environment }}
       release_strategy: 'standard-version'
@@ -114,6 +119,8 @@ jobs:
     name: Check EAS Setup
     runs-on: ubuntu-latest
     needs: [determine_environment]
+    permissions:
+      contents: read
     outputs:
       has_eas_setup: ${{ steps.check.outputs.has_eas_setup }}
     steps:
@@ -132,6 +139,8 @@ jobs:
     name: Check App Config Changes
     runs-on: ubuntu-latest
     needs: [determine_environment]
+    permissions:
+      contents: read
     outputs:
       app_config_changed: ${{ steps.check_changes.outputs.app_config_changed }}
     steps:
@@ -157,6 +166,8 @@ jobs:
     needs: [determine_environment, check_eas_setup, check_app_config_changes]
     if: needs.check_eas_setup.outputs.has_eas_setup == 'true' && (needs.check_app_config_changes.outputs.app_config_changed == 'true' || inputs.force_build == true)
     uses: CodySwannGT/lisa/.github/workflows/build.yml@main
+    permissions:
+      contents: read
     with:
       environment: ${{ needs.determine_environment.outputs.environment }}
     secrets:
@@ -178,6 +189,8 @@ jobs:
       always() && 
       needs.check_eas_setup.outputs.has_eas_setup == 'true' &&
       needs.release.result == 'success'
+    permissions:
+      contents: read
     steps:
       - name: Checkout repository
         uses: actions/checkout@v6

package/nestjs/create-only/.github/workflows/deploy.yml

@@ -40,6 +40,8 @@ jobs:
     name: 🌍 Determine Environment
     runs-on: ubuntu-latest
     timeout-minutes: 5
+    permissions:
+      contents: read
     outputs:
       environment: ${{ steps.env.outputs.environment }}
       approval_environment: ${{ steps.approval.outputs.approval_environment }}
@@ -81,6 +83,9 @@ jobs:
     name: 📦 Release
     uses: CodySwannGT/lisa/.github/workflows/release.yml@main
     needs: [determine_environment]
+    permissions:
+      contents: write
+      pull-requests: read
     with:
       environment: ${{ needs.determine_environment.outputs.environment }}
       release_strategy: 'standard-version'
@@ -105,6 +110,8 @@ jobs:
     name: Verify AWS Credentials
     runs-on: ubuntu-latest
     needs: [release]
+    permissions:
+      contents: read
     outputs:
       has_aws_credentials: ${{ steps.check.outputs.has_aws_credentials }}
     steps:
@@ -129,6 +136,8 @@ jobs:
     runs-on: ubuntu-latest
     needs: [release, verify_aws_credentials]
     if: needs.verify_aws_credentials.outputs.has_aws_credentials == 'true'
+    permissions:
+      contents: read
     outputs:
       requires_migration: ${{ steps.check.outputs.requires_migration }}
     steps:
@@ -144,13 +153,14 @@ jobs:
         shell: bash
         env:
           SKIP_MIGRATIONS: ${{ vars.SKIP_MIGRATIONS }}
-          GITHUB_OUTPUT: ${{ github.output }}
 
   verify_vpn:
     name: Verify VPN
     runs-on: ubuntu-latest
     needs: [check_migration_required]
     if: always() && needs.check_migration_required.outputs.requires_migration == 'true'
+    permissions:
+      contents: read
     outputs:
       has_vpn_setup: ${{ steps.check.outputs.has_vpn_setup }}
     steps:
@@ -168,7 +178,6 @@ jobs:
           fi
         env:
           OVPN_CONFIG: ${{ secrets[env.OVPN_CONFIG_NAME] }}
-          GITHUB_OUTPUT: ${{ github.output }}
   migrate:
     name: Schema Migrations
     runs-on: ubuntu-latest
@@ -217,13 +226,27 @@ jobs:
           SERVERLESS_ACCESS_KEY: ${{ secrets.SERVERLESS_ACCESS_KEY }}
           AWS_PROFILE: '' # Override serverless.yml profile with empty string for CI
   deploy:
-    needs: [migrate, verify_aws_credentials]
+    needs:
+      [
+        determine_environment,
+        release,
+        check_migration_required,
+        migrate,
+        verify_aws_credentials,
+      ]
     if: |
       always() &&
       needs.verify_aws_credentials.outputs.has_aws_credentials == 'true' &&
-      (needs.migrate.result == 'success' || needs.migrate.result == 'skipped')
+      needs.check_migration_required.result == 'success' &&
+      (
+        needs.migrate.result == 'success' ||
+        (needs.check_migration_required.outputs.requires_migration != 'true' && needs.migrate.result == 'skipped')
+      )
     name: Deploy
     runs-on: ubuntu-latest
+    outputs:
+      environment_url: ${{ steps.deployment_outputs.outputs.environment_url }}
+      deployment_status: ${{ steps.deployment_outputs.outputs.deployment_status }}
     permissions:
       id-token: write # needed to interact with GitHub's OIDC Token endpoint
       contents: read
@@ -325,6 +348,43 @@ jobs:
           fi
           echo "Health check passed: $health_url"
 
+      - name: Resolve deployment outputs
+        id: deployment_outputs
+        shell: bash
+        env:
+          SERVERLESS_ACCESS_KEY: ${{ secrets.SERVERLESS_ACCESS_KEY }}
+          AWS_PROFILE: ''
+          DEPLOYMENT_URL: ${{ vars.DEPLOYMENT_URL }}
+          HEALTH_OUTPUT_KEY: ${{ vars.POST_DEPLOY_HEALTH_OUTPUT_KEY || 'HttpApiUrl' }}
+          SERVERLESS_STACK_NAME: ${{ vars.SERVERLESS_STACK_NAME }}
+          STAGE: ${{ github.ref_name != 'main' && github.ref_name || 'production' }}
+        run: |
+          set -euo pipefail
+          environment_url="$DEPLOYMENT_URL"
+
+          if [ -z "$environment_url" ]; then
+            stack_name="$SERVERLESS_STACK_NAME"
+            if [ -z "$stack_name" ]; then
+              service_name=$(bun run serverless print --stage "$STAGE" --format json | jq -r '.service // empty' 2>/dev/null || true)
+              if [ -n "$service_name" ]; then
+                stack_name="${service_name}-${STAGE}"
+              fi
+            fi
+
+            if [ -n "$stack_name" ]; then
+              environment_url=$(aws cloudformation describe-stacks \
+                --stack-name "$stack_name" \
+                --query "Stacks[0].Outputs[?OutputKey=='${HEALTH_OUTPUT_KEY}'].OutputValue | [0]" \
+                --output text 2>/dev/null || true)
+              if [ "$environment_url" = "None" ]; then
+                environment_url=""
+              fi
+            fi
+          fi
+
+          echo "environment_url=$environment_url" >> "$GITHUB_OUTPUT"
+          echo "deployment_status=success" >> "$GITHUB_OUTPUT"
+
       - name: 📢 Notify on success
         run: echo "Successfully deployed version ${{ needs.release.outputs.version }} to ${{ needs.determine_environment.outputs.environment }}"
 

package/package.json

@@ -95,7 +95,7 @@
     "ws": ">=8.20.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/.codex-plugin/skills/lisa-parity-skill-creator/SKILL.md

@@ -58,9 +58,11 @@ first:
   `name`: `lisa-implement`, `lisa-git-commit`, `lisa-tracker-write`. No spaces,
   no camelCase, no underscores.
 - The directory name and the frontmatter `name` must match exactly.
-- Commands live under `commands/lisa/` and map to colon-separated slash names:
-  `commands/lisa/git/commit.md` → `/lisa:git:commit`;
-  `commands/lisa/implement.md` → `/lisa:implement`.
+- Commands live flat under `commands/` — Claude Code prefixes plugin commands
+  with the plugin name, so `commands/git/commit.md` → `/lisa:git:commit` and
+  `commands/implement.md` → `/lisa:implement`. (Per-agent variant generators
+  nest them under `commands/lisa/` for harnesses without plugin-name
+  namespacing; never author that nesting in source.)
 - **Commands** surface as `/lisa:*` (colon). **Skills** surface as `/lisa-*`
   (hyphen). Never share a bare name like `implement` across both surfaces.
 
@@ -112,15 +114,15 @@ carries the actual logic. Keep the two descriptions consistent.
 1. **Decide placement** — downstream (`plugins/src/base`) vs. Lisa-only
    (`.claude`). For base, both a skill and a command directory entry are needed.
 2. **Pick the name** — `lisa-<slug>`, hyphenated, unique. Check it does not collide:
-   `ls plugins/src/base/skills/` and `ls plugins/src/base/commands/lisa/`.
+   `ls plugins/src/base/skills/` and `ls plugins/src/base/commands/`.
 3. **Create the skill** at
    `plugins/src/base/skills/lisa-<name>/SKILL.md` with the frontmatter above and a
    body that follows house style — see `plugins/src/base/skills/lisa-quality-review/SKILL.md`
    for the canonical shape (title, "When to use", numbered checklist/steps,
    explicit "Rules"/"Output" sections). Write real, actionable guidance, not
    TODOs.
-4. **Create the command** at `plugins/src/base/commands/lisa/<name>.md` (or a nested
-   `commands/lisa/<namespace>/<name>.md` for a colon-namespaced command) using the
+4. **Create the command** at `plugins/src/base/commands/<name>.md` (or a nested
+   `commands/<namespace>/<name>.md` for a colon-namespaced command) using the
    pass-through template.
 5. **Rebuild the artifacts** so the generated plugins match source:
    ```bash

package/plugins/lisa/skills/lisa-parity-skill-creator/SKILL.md

@@ -58,9 +58,11 @@ first:
   `name`: `lisa-implement`, `lisa-git-commit`, `lisa-tracker-write`. No spaces,
   no camelCase, no underscores.
 - The directory name and the frontmatter `name` must match exactly.
-- Commands live under `commands/lisa/` and map to colon-separated slash names:
-  `commands/lisa/git/commit.md` → `/lisa:git:commit`;
-  `commands/lisa/implement.md` → `/lisa:implement`.
+- Commands live flat under `commands/` — Claude Code prefixes plugin commands
+  with the plugin name, so `commands/git/commit.md` → `/lisa:git:commit` and
+  `commands/implement.md` → `/lisa:implement`. (Per-agent variant generators
+  nest them under `commands/lisa/` for harnesses without plugin-name
+  namespacing; never author that nesting in source.)
 - **Commands** surface as `/lisa:*` (colon). **Skills** surface as `/lisa-*`
   (hyphen). Never share a bare name like `implement` across both surfaces.
 
@@ -112,15 +114,15 @@ carries the actual logic. Keep the two descriptions consistent.
 1. **Decide placement** — downstream (`plugins/src/base`) vs. Lisa-only
    (`.claude`). For base, both a skill and a command directory entry are needed.
 2. **Pick the name** — `lisa-<slug>`, hyphenated, unique. Check it does not collide:
-   `ls plugins/src/base/skills/` and `ls plugins/src/base/commands/lisa/`.
+   `ls plugins/src/base/skills/` and `ls plugins/src/base/commands/`.
 3. **Create the skill** at
    `plugins/src/base/skills/lisa-<name>/SKILL.md` with the frontmatter above and a
    body that follows house style — see `plugins/src/base/skills/lisa-quality-review/SKILL.md`
    for the canonical shape (title, "When to use", numbered checklist/steps,
    explicit "Rules"/"Output" sections). Write real, actionable guidance, not
    TODOs.
-4. **Create the command** at `plugins/src/base/commands/lisa/<name>.md` (or a nested
-   `commands/lisa/<namespace>/<name>.md` for a colon-namespaced command) using the
+4. **Create the command** at `plugins/src/base/commands/<name>.md` (or a nested
+   `commands/<namespace>/<name>.md` for a colon-namespaced command) using the
    pass-through template.
 5. **Rebuild the artifacts** so the generated plugins match source:
    ```bash

package/plugins/lisa-agy/plugin.json

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

package/plugins/lisa-agy/skills/lisa-parity-skill-creator/SKILL.md

@@ -58,9 +58,11 @@ first:
   `name`: `lisa-implement`, `lisa-git-commit`, `lisa-tracker-write`. No spaces,
   no camelCase, no underscores.
 - The directory name and the frontmatter `name` must match exactly.
-- Commands live under `commands/lisa/` and map to colon-separated slash names:
-  `commands/lisa/git/commit.md` → `/lisa:git:commit`;
-  `commands/lisa/implement.md` → `/lisa:implement`.
+- Commands live flat under `commands/` — Claude Code prefixes plugin commands
+  with the plugin name, so `commands/git/commit.md` → `/lisa:git:commit` and
+  `commands/implement.md` → `/lisa:implement`. (Per-agent variant generators
+  nest them under `commands/lisa/` for harnesses without plugin-name
+  namespacing; never author that nesting in source.)
 - **Commands** surface as `/lisa:*` (colon). **Skills** surface as `/lisa-*`
   (hyphen). Never share a bare name like `implement` across both surfaces.
 
@@ -112,15 +114,15 @@ carries the actual logic. Keep the two descriptions consistent.
 1. **Decide placement** — downstream (`plugins/src/base`) vs. Lisa-only
    (`.claude`). For base, both a skill and a command directory entry are needed.
 2. **Pick the name** — `lisa-<slug>`, hyphenated, unique. Check it does not collide:
-   `ls plugins/src/base/skills/` and `ls plugins/src/base/commands/lisa/`.
+   `ls plugins/src/base/skills/` and `ls plugins/src/base/commands/`.
 3. **Create the skill** at
    `plugins/src/base/skills/lisa-<name>/SKILL.md` with the frontmatter above and a
    body that follows house style — see `plugins/src/base/skills/lisa-quality-review/SKILL.md`
    for the canonical shape (title, "When to use", numbered checklist/steps,
    explicit "Rules"/"Output" sections). Write real, actionable guidance, not
    TODOs.
-4. **Create the command** at `plugins/src/base/commands/lisa/<name>.md` (or a nested
-   `commands/lisa/<namespace>/<name>.md` for a colon-namespaced command) using the
+4. **Create the command** at `plugins/src/base/commands/<name>.md` (or a nested
+   `commands/<namespace>/<name>.md` for a colon-namespaced command) using the
    pass-through template.
 5. **Rebuild the artifacts** so the generated plugins match source:
    ```bash

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

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

package/plugins/lisa-copilot/skills/lisa-parity-skill-creator/SKILL.md

@@ -58,9 +58,11 @@ first:
   `name`: `lisa-implement`, `lisa-git-commit`, `lisa-tracker-write`. No spaces,
   no camelCase, no underscores.
 - The directory name and the frontmatter `name` must match exactly.
-- Commands live under `commands/lisa/` and map to colon-separated slash names:
-  `commands/lisa/git/commit.md` → `/lisa:git:commit`;
-  `commands/lisa/implement.md` → `/lisa:implement`.
+- Commands live flat under `commands/` — Claude Code prefixes plugin commands
+  with the plugin name, so `commands/git/commit.md` → `/lisa:git:commit` and
+  `commands/implement.md` → `/lisa:implement`. (Per-agent variant generators
+  nest them under `commands/lisa/` for harnesses without plugin-name
+  namespacing; never author that nesting in source.)
 - **Commands** surface as `/lisa:*` (colon). **Skills** surface as `/lisa-*`
   (hyphen). Never share a bare name like `implement` across both surfaces.
 
@@ -112,15 +114,15 @@ carries the actual logic. Keep the two descriptions consistent.
 1. **Decide placement** — downstream (`plugins/src/base`) vs. Lisa-only
    (`.claude`). For base, both a skill and a command directory entry are needed.
 2. **Pick the name** — `lisa-<slug>`, hyphenated, unique. Check it does not collide:
-   `ls plugins/src/base/skills/` and `ls plugins/src/base/commands/lisa/`.
+   `ls plugins/src/base/skills/` and `ls plugins/src/base/commands/`.
 3. **Create the skill** at
    `plugins/src/base/skills/lisa-<name>/SKILL.md` with the frontmatter above and a
    body that follows house style — see `plugins/src/base/skills/lisa-quality-review/SKILL.md`
    for the canonical shape (title, "When to use", numbered checklist/steps,
    explicit "Rules"/"Output" sections). Write real, actionable guidance, not
    TODOs.
-4. **Create the command** at `plugins/src/base/commands/lisa/<name>.md` (or a nested
-   `commands/lisa/<namespace>/<name>.md` for a colon-namespaced command) using the
+4. **Create the command** at `plugins/src/base/commands/<name>.md` (or a nested
+   `commands/<namespace>/<name>.md` for a colon-namespaced command) using the
    pass-through template.
 5. **Rebuild the artifacts** so the generated plugins match source:
    ```bash

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

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

package/plugins/lisa-cursor/skills/lisa-parity-skill-creator/SKILL.md

@@ -58,9 +58,11 @@ first:
   `name`: `lisa-implement`, `lisa-git-commit`, `lisa-tracker-write`. No spaces,
   no camelCase, no underscores.
 - The directory name and the frontmatter `name` must match exactly.
-- Commands live under `commands/lisa/` and map to colon-separated slash names:
-  `commands/lisa/git/commit.md` → `/lisa:git:commit`;
-  `commands/lisa/implement.md` → `/lisa:implement`.
+- Commands live flat under `commands/` — Claude Code prefixes plugin commands
+  with the plugin name, so `commands/git/commit.md` → `/lisa:git:commit` and
+  `commands/implement.md` → `/lisa:implement`. (Per-agent variant generators
+  nest them under `commands/lisa/` for harnesses without plugin-name
+  namespacing; never author that nesting in source.)
 - **Commands** surface as `/lisa:*` (colon). **Skills** surface as `/lisa-*`
   (hyphen). Never share a bare name like `implement` across both surfaces.
 
@@ -112,15 +114,15 @@ carries the actual logic. Keep the two descriptions consistent.
 1. **Decide placement** — downstream (`plugins/src/base`) vs. Lisa-only
    (`.claude`). For base, both a skill and a command directory entry are needed.
 2. **Pick the name** — `lisa-<slug>`, hyphenated, unique. Check it does not collide:
-   `ls plugins/src/base/skills/` and `ls plugins/src/base/commands/lisa/`.
+   `ls plugins/src/base/skills/` and `ls plugins/src/base/commands/`.
 3. **Create the skill** at
    `plugins/src/base/skills/lisa-<name>/SKILL.md` with the frontmatter above and a
    body that follows house style — see `plugins/src/base/skills/lisa-quality-review/SKILL.md`
    for the canonical shape (title, "When to use", numbered checklist/steps,
    explicit "Rules"/"Output" sections). Write real, actionable guidance, not
    TODOs.
-4. **Create the command** at `plugins/src/base/commands/lisa/<name>.md` (or a nested
-   `commands/lisa/<namespace>/<name>.md` for a colon-namespaced command) using the
+4. **Create the command** at `plugins/src/base/commands/<name>.md` (or a nested
+   `commands/<namespace>/<name>.md` for a colon-namespaced command) using the
    pass-through template.
 5. **Rebuild the artifacts** so the generated plugins match source:
    ```bash

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.204.0",
+  "version": "2.204.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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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.204.0",
+  "version": "2.204.2",
   "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"