@codyswann/lisa 4.77.0 → 4.77.1

package/package.json

@@ -189,7 +189,7 @@
     "qs": "^6.16.0"
   },
   "name": "@codyswann/lisa",
-  "version": "4.77.0",
+  "version": "4.77.1",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {
@@ -345,7 +345,7 @@
     "test": "tests"
   },
   "types": "./dist/index.d.ts",
-  "lisaReleaseCommit": "8e3b35a3acc33f287d0cb0488e9ae64f81c3a94d",
-  "gitHead": "8e3b35a3acc33f287d0cb0488e9ae64f81c3a94d",
-  "lisaReleaseTag": "v4.77.0"
+  "lisaReleaseCommit": "4d5646b9bff5fa86841ed13540b52359ec877758",
+  "gitHead": "4d5646b9bff5fa86841ed13540b52359ec877758",
+  "lisaReleaseTag": "v4.77.1"
 }

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

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

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

@@ -25,6 +25,18 @@ create them; invoke the runtime's automation tool with the spec below.
   automation. Do not point recurring automations at hashed scratch worktrees or a checkout whose Git
   metadata is broken.
 - **Claude** → use **`/schedule`** to create local recurring routines, one per automation below.
+- **Devin CLI** → there is no native scheduler (documented gap, CodySwannGT/lisa#4283 — decided
+  as a documented manual trigger, not a polyfill). State that Devin cannot schedule the loops and
+  stop without creating anything. Then tell the operator their two working options:
+  1. **Run a loop by hand.** For example `devin -p -- "/lisa:lisa-intake <queue>"`. The same
+     command can go in the operator's own cron, which then owns the clock.
+  2. **Run the loops unattended** through `scheduler: "github-actions"` with `executionEnv`
+     (next section). GitHub Actions only owns the clock: the loop itself runs on whichever
+     supported remote surface `executionEnv` names (for example `claude-web` or
+     `codex-cloud`). That surface is not Devin, and there is no Devin remote surface.
+
+  Devin runs Lisa's skills from the `lisa-devin` plugin, so each loop's prompt is the same skill
+  invocation a scheduled run would make.
 - **Other runtimes** → use the runtime's native recurring-task mechanism. If the runtime has none,
   state that scheduling is unavailable and stop.
 

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

@@ -23,6 +23,18 @@ create them; invoke the runtime's automation tool with the spec below.
   automation. Do not point recurring automations at hashed scratch worktrees or a checkout whose Git
   metadata is broken.
 - **Claude** → use **`/schedule`** to create local recurring routines, one per automation below.
+- **Devin CLI** → there is no native scheduler (documented gap, CodySwannGT/lisa#4283 — decided
+  as a documented manual trigger, not a polyfill). State that Devin cannot schedule the loops and
+  stop without creating anything. Then tell the operator their two working options:
+  1. **Run a loop by hand.** For example `devin -p -- "/lisa:lisa-intake <queue>"`. The same
+     command can go in the operator's own cron, which then owns the clock.
+  2. **Run the loops unattended** through `scheduler: "github-actions"` with `executionEnv`
+     (next section). GitHub Actions only owns the clock: the loop itself runs on whichever
+     supported remote surface `executionEnv` names (for example `claude-web` or
+     `codex-cloud`). That surface is not Devin, and there is no Devin remote surface.
+
+  Devin runs Lisa's skills from the `lisa-devin` plugin, so each loop's prompt is the same skill
+  invocation a scheduled run would make.
 - **Other runtimes** → use the runtime's native recurring-task mechanism. If the runtime has none,
   state that scheduling is unavailable and stop.
 

package/plugins/lisa-agy/plugin.json

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

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

@@ -23,6 +23,18 @@ create them; invoke the runtime's automation tool with the spec below.
   automation. Do not point recurring automations at hashed scratch worktrees or a checkout whose Git
   metadata is broken.
 - **Claude** → use **`/schedule`** to create local recurring routines, one per automation below.
+- **Devin CLI** → there is no native scheduler (documented gap, CodySwannGT/lisa#4283 — decided
+  as a documented manual trigger, not a polyfill). State that Devin cannot schedule the loops and
+  stop without creating anything. Then tell the operator their two working options:
+  1. **Run a loop by hand.** For example `devin -p -- "/lisa:lisa-intake <queue>"`. The same
+     command can go in the operator's own cron, which then owns the clock.
+  2. **Run the loops unattended** through `scheduler: "github-actions"` with `executionEnv`
+     (next section). GitHub Actions only owns the clock: the loop itself runs on whichever
+     supported remote surface `executionEnv` names (for example `claude-web` or
+     `codex-cloud`). That surface is not Devin, and there is no Devin remote surface.
+
+  Devin runs Lisa's skills from the `lisa-devin` plugin, so each loop's prompt is the same skill
+  invocation a scheduled run would make.
 - **Other runtimes** → use the runtime's native recurring-task mechanism. If the runtime has none,
   state that scheduling is unavailable and stop.
 

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.1",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

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

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

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

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

@@ -23,6 +23,18 @@ create them; invoke the runtime's automation tool with the spec below.
   automation. Do not point recurring automations at hashed scratch worktrees or a checkout whose Git
   metadata is broken.
 - **Claude** → use **`/schedule`** to create local recurring routines, one per automation below.
+- **Devin CLI** → there is no native scheduler (documented gap, CodySwannGT/lisa#4283 — decided
+  as a documented manual trigger, not a polyfill). State that Devin cannot schedule the loops and
+  stop without creating anything. Then tell the operator their two working options:
+  1. **Run a loop by hand.** For example `devin -p -- "/lisa:lisa-intake <queue>"`. The same
+     command can go in the operator's own cron, which then owns the clock.
+  2. **Run the loops unattended** through `scheduler: "github-actions"` with `executionEnv`
+     (next section). GitHub Actions only owns the clock: the loop itself runs on whichever
+     supported remote surface `executionEnv` names (for example `claude-web` or
+     `codex-cloud`). That surface is not Devin, and there is no Devin remote surface.
+
+  Devin runs Lisa's skills from the `lisa-devin` plugin, so each loop's prompt is the same skill
+  invocation a scheduled run would make.
 - **Other runtimes** → use the runtime's native recurring-task mechanism. If the runtime has none,
   state that scheduling is unavailable and stop.
 

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

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

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

@@ -23,6 +23,18 @@ create them; invoke the runtime's automation tool with the spec below.
   automation. Do not point recurring automations at hashed scratch worktrees or a checkout whose Git
   metadata is broken.
 - **Claude** → use **`/schedule`** to create local recurring routines, one per automation below.
+- **Devin CLI** → there is no native scheduler (documented gap, CodySwannGT/lisa#4283 — decided
+  as a documented manual trigger, not a polyfill). State that Devin cannot schedule the loops and
+  stop without creating anything. Then tell the operator their two working options:
+  1. **Run a loop by hand.** For example `devin -p -- "/lisa:lisa-intake <queue>"`. The same
+     command can go in the operator's own cron, which then owns the clock.
+  2. **Run the loops unattended** through `scheduler: "github-actions"` with `executionEnv`
+     (next section). GitHub Actions only owns the clock: the loop itself runs on whichever
+     supported remote surface `executionEnv` names (for example `claude-web` or
+     `codex-cloud`). That surface is not Devin, and there is no Devin remote surface.
+
+  Devin runs Lisa's skills from the `lisa-devin` plugin, so each loop's prompt is the same skill
+  invocation a scheduled run would make.
 - **Other runtimes** → use the runtime's native recurring-task mechanism. If the runtime has none,
   state that scheduling is unavailable and stop.
 

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

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

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

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

package/plugins/lisa-devin/skills/lisa-setup-automations/SKILL.md

@@ -23,6 +23,18 @@ create them; invoke the runtime's automation tool with the spec below.
   automation. Do not point recurring automations at hashed scratch worktrees or a checkout whose Git
   metadata is broken.
 - **Claude** → use **`/schedule`** to create local recurring routines, one per automation below.
+- **Devin CLI** → there is no native scheduler (documented gap, CodySwannGT/lisa#4283 — decided
+  as a documented manual trigger, not a polyfill). State that Devin cannot schedule the loops and
+  stop without creating anything. Then tell the operator their two working options:
+  1. **Run a loop by hand.** For example `devin -p -- "/lisa:lisa-intake <queue>"`. The same
+     command can go in the operator's own cron, which then owns the clock.
+  2. **Run the loops unattended** through `scheduler: "github-actions"` with `executionEnv`
+     (next section). GitHub Actions only owns the clock: the loop itself runs on whichever
+     supported remote surface `executionEnv` names (for example `claude-web` or
+     `codex-cloud`). That surface is not Devin, and there is no Devin remote surface.
+
+  Devin runs Lisa's skills from the `lisa-devin` plugin, so each loop's prompt is the same skill
+  invocation a scheduled run would make.
 - **Other runtimes** → use the runtime's native recurring-task mechanism. If the runtime has none,
   state that scheduling is unavailable and stop.
 

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.1",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.1",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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-devin/.claude-plugin/plugin.json

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.1",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.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": "4.77.0",
+  "version": "4.77.1",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"