@codyswann/lisa 2.203.0 → 2.204.1

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

@@ -249,12 +249,81 @@ jobs:
           bun-version: '1.3.8'
       - name: Install dependencies
         run: bun install
+      - name: Materialize dotenv env file
+        if: ${{ vars.DOTENV_ENV_MATERIALIZATION_KEYS != '' }}
+        shell: bash
+        env:
+          DOTENV_ENV_MATERIALIZATION_KEYS: ${{ vars.DOTENV_ENV_MATERIALIZATION_KEYS }}
+          DOTENV_ENV_FILE: ${{ vars.DOTENV_ENV_FILE || '.env.local' }}
+          # Optional project mapping for serverless-dotenv-plugin projects:
+          # DOTENV_ENV_MATERIALIZATION_KEYS="API_URL JWT_SECRET"
+          # API_URL: ${{ vars.API_URL }}
+          # JWT_SECRET: ${{ secrets.JWT_SECRET }}
+        run: |
+          set -euo pipefail
+          : > "$DOTENV_ENV_FILE"
+          wrote_any=false
+
+          for key in $DOTENV_ENV_MATERIALIZATION_KEYS; do
+            value="${!key:-}"
+            if [ -z "$value" ]; then
+              echo "::notice::Skipping empty dotenv key: $key"
+              continue
+            fi
+            printf '%s=%s\n' "$key" "$value" >> "$DOTENV_ENV_FILE"
+            wrote_any=true
+          done
+
+          if [ "$wrote_any" != "true" ]; then
+            rm -f "$DOTENV_ENV_FILE"
+            echo "::notice::No dotenv values were materialized"
+          fi
       - name: serverless deploy
         run: |
           bun run serverless deploy --stage ${{ github.ref_name != 'main' && github.ref_name || 'production' }}
         env:
           SERVERLESS_ACCESS_KEY: ${{ secrets.SERVERLESS_ACCESS_KEY }}
           AWS_PROFILE: '' # Override serverless.yml profile with empty string for CI
+      - name: Post-deploy health smoke
+        if: ${{ vars.POST_DEPLOY_HEALTH_CHECK_ENABLED == 'true' }}
+        shell: bash
+        env:
+          SERVERLESS_ACCESS_KEY: ${{ secrets.SERVERLESS_ACCESS_KEY }}
+          AWS_PROFILE: ''
+          HEALTH_OUTPUT_KEY: ${{ vars.POST_DEPLOY_HEALTH_OUTPUT_KEY || 'HttpApiUrl' }}
+          HEALTH_PATH: ${{ vars.POST_DEPLOY_HEALTH_PATH || '/health' }}
+          HEALTH_EXPECTED_BODY: ${{ vars.POST_DEPLOY_HEALTH_EXPECTED_BODY }}
+          SERVERLESS_STACK_NAME: ${{ vars.SERVERLESS_STACK_NAME }}
+          STAGE: ${{ github.ref_name != 'main' && github.ref_name || 'production' }}
+        run: |
+          set -euo pipefail
+
+          stack_name="$SERVERLESS_STACK_NAME"
+          if [ -z "$stack_name" ]; then
+            service_name=$(bun run serverless print --stage "$STAGE" --format json | jq -r '.service // empty')
+            if [ -z "$service_name" ]; then
+              echo "::error::Set SERVERLESS_STACK_NAME or make serverless print expose .service"
+              exit 1
+            fi
+            stack_name="${service_name}-${STAGE}"
+          fi
+
+          base_url=$(aws cloudformation describe-stacks \
+            --stack-name "$stack_name" \
+            --query "Stacks[0].Outputs[?OutputKey=='${HEALTH_OUTPUT_KEY}'].OutputValue | [0]" \
+            --output text)
+          if [ -z "$base_url" ] || [ "$base_url" = "None" ]; then
+            echo "::error::CloudFormation output ${HEALTH_OUTPUT_KEY} was not found on ${stack_name}"
+            exit 1
+          fi
+
+          health_url="${base_url%/}/${HEALTH_PATH#/}"
+          body=$(curl --fail --silent --show-error --max-time 20 "$health_url")
+          if [ -n "$HEALTH_EXPECTED_BODY" ] && ! grep -Fq "$HEALTH_EXPECTED_BODY" <<< "$body"; then
+            echo "::error::Health check response did not contain expected body"
+            exit 1
+          fi
+          echo "Health check passed: $health_url"
 
       - 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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "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.203.0",
+  "version": "2.204.1",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

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

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

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

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

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

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

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

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.203.0",
+  "version": "2.204.1",
   "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

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

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