@codyswann/lisa 2.155.2 → 2.155.3

package/package.json

@@ -84,7 +84,7 @@
     "lodash": ">=4.18.1"
   },
   "name": "@codyswann/lisa",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa/rules/reference/config-resolution.md

@@ -404,9 +404,15 @@ Rules:
 
 - **Single-environment projects** (one entry in `deploy.branches`) may omit
   `deploy.order`; the derived chain is empty and the back-sync no-ops.
-- **Multi-environment projects MUST set `deploy.order`** for config-driven
-  back-sync. If it is absent, the Action fails rather than guessing the rank
-  (or the workflow wrapper must pass an explicit `chain`, which always wins).
+- **Projects whose environments all map to the same branch** (e.g.
+  `dev`/`staging`/`production` all → `main`) may also omit `deploy.order`: the
+  branches resolve to a single distinct branch, so there is nothing to back-sync
+  and the derived chain is the empty no-op. `deploy.order` is only required when
+  `deploy.branches` resolves to **more than one distinct branch**.
+- **Multi-branch projects MUST set `deploy.order`** for config-driven back-sync.
+  If `deploy.branches` resolves to more than one distinct branch and `deploy.order`
+  is absent, the Action fails rather than guessing the rank (or the workflow
+  wrapper must pass an explicit `chain`, which always wins).
 - The env-name set of `deploy.order` and `deploy.branches` **must match exactly**
   — every env in one appears in the other. A mismatch is a config error.
 
@@ -475,9 +481,12 @@ Doctor must validate config in three layers:
      and `deploy.branches`.
 
 4. **Deploy env-order correctness**
-   - When `deploy.branches` defines more than one environment but `deploy.order` is absent, `WARN`:
-     config-driven back-sync cannot derive a chain without the ranking (the wrapper must add
-     `deploy.order` or pass an explicit `chain`).
+   - When `deploy.branches` resolves to more than one **distinct** branch but `deploy.order` is
+     absent, `WARN`: config-driven back-sync cannot derive a chain without the ranking (the wrapper
+     must add `deploy.order` or pass an explicit `chain`).
+   - When `deploy.branches` defines multiple environments that all map to the **same** branch (e.g.
+     `dev`/`staging`/`production` all → `main`), `deploy.order` is **not** required — the chain is the
+     empty no-op. Do not `WARN` in this case.
    - When `deploy.order` is present but its env names do not exactly match the `deploy.branches`
      keys, `FAIL` — the derived sync-down chain would be wrong or empty.
 

package/plugins/lisa/skills/doctor/SKILL.md

@@ -104,8 +104,12 @@ this order:
 6. **Deploy env-order audit** (only when `deploy.branches` is present)
    - `PASS` (or skip) when `deploy.branches` defines a single environment — `deploy.order` is
      optional and the back-sync chain is empty.
-   - `WARN` when `deploy.branches` defines **more than one** environment but `deploy.order` is
-     absent. Config-driven back-sync (`reusable-claude-sync-down-branches.yml`) cannot derive a
+   - `PASS` (or skip) when `deploy.branches` defines multiple environments that all map to the
+     **same** branch (e.g. `dev`/`staging`/`production` all → `main`). The branches resolve to a
+     single distinct branch, so there is nothing to back-sync, the chain is the empty no-op, and
+     `deploy.order` is not required. Do not WARN.
+   - `WARN` when `deploy.branches` resolves to **more than one distinct** branch but `deploy.order`
+     is absent. Config-driven back-sync (`reusable-claude-sync-down-branches.yml`) cannot derive a
      source→target chain without the env ranking; the repo must either add `deploy.order`
      (low→high, e.g. `["dev","staging","production"]`) or pass an explicit `chain` in its
      `claude-sync-down-branches.yml` wrapper. WARN not FAIL because the explicit-chain override is

package/plugins/lisa/skills/sync-down/SKILL.md

@@ -44,6 +44,7 @@ CHAIN=$(jq -e -r '
   | ($b | keys | sort) as $bk
   | ($o | sort) as $ok
   | if ($b | length) <= 1 then "{}"
+    elif (($b | [.[]] | unique | length) <= 1) then "{}"
     elif ($o | length) == 0 then "ERR_NO_ORDER"
     elif ($bk != $ok) then "ERR_MISMATCH"
     else ($o | reverse) as $hl
@@ -53,12 +54,16 @@ CHAIN=$(jq -e -r '
 ' .lisa.config.json)
 ```
 
-- `ERR_NO_ORDER` → stop: `deploy.branches` has multiple environments but
-  `deploy.order` is missing. Tell the user to add `deploy.order` (low→high, e.g.
-  `["dev","staging","production"]`). Do not guess the ranking.
+- `ERR_NO_ORDER` → stop: `deploy.branches` has multiple environments mapped to
+  more than one distinct branch but `deploy.order` is missing. Tell the user to
+  add `deploy.order` (low→high, e.g. `["dev","staging","production"]`). Do not
+  guess the ranking.
 - `ERR_MISMATCH` → stop: `deploy.order` and `deploy.branches` name different
   environments. They must match exactly.
-- `{}` (single-environment project) → nothing to sync; report and exit cleanly.
+- `{}` → nothing to sync; report and exit cleanly. This covers both a
+  single-environment project and a multi-environment project whose branches all
+  resolve to the **same** branch (e.g. dev/staging/production all → `main`), where
+  `deploy.order` is not required.
 
 ### 2. Resolve the source branch
 

package/plugins/lisa-agy/plugin.json

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

package/plugins/lisa-agy/skills/doctor/SKILL.md

@@ -104,8 +104,12 @@ this order:
 6. **Deploy env-order audit** (only when `deploy.branches` is present)
    - `PASS` (or skip) when `deploy.branches` defines a single environment — `deploy.order` is
      optional and the back-sync chain is empty.
-   - `WARN` when `deploy.branches` defines **more than one** environment but `deploy.order` is
-     absent. Config-driven back-sync (`reusable-claude-sync-down-branches.yml`) cannot derive a
+   - `PASS` (or skip) when `deploy.branches` defines multiple environments that all map to the
+     **same** branch (e.g. `dev`/`staging`/`production` all → `main`). The branches resolve to a
+     single distinct branch, so there is nothing to back-sync, the chain is the empty no-op, and
+     `deploy.order` is not required. Do not WARN.
+   - `WARN` when `deploy.branches` resolves to **more than one distinct** branch but `deploy.order`
+     is absent. Config-driven back-sync (`reusable-claude-sync-down-branches.yml`) cannot derive a
      source→target chain without the env ranking; the repo must either add `deploy.order`
      (low→high, e.g. `["dev","staging","production"]`) or pass an explicit `chain` in its
      `claude-sync-down-branches.yml` wrapper. WARN not FAIL because the explicit-chain override is

package/plugins/lisa-agy/skills/sync-down/SKILL.md

@@ -44,6 +44,7 @@ CHAIN=$(jq -e -r '
   | ($b | keys | sort) as $bk
   | ($o | sort) as $ok
   | if ($b | length) <= 1 then "{}"
+    elif (($b | [.[]] | unique | length) <= 1) then "{}"
     elif ($o | length) == 0 then "ERR_NO_ORDER"
     elif ($bk != $ok) then "ERR_MISMATCH"
     else ($o | reverse) as $hl
@@ -53,12 +54,16 @@ CHAIN=$(jq -e -r '
 ' .lisa.config.json)
 ```
 
-- `ERR_NO_ORDER` → stop: `deploy.branches` has multiple environments but
-  `deploy.order` is missing. Tell the user to add `deploy.order` (low→high, e.g.
-  `["dev","staging","production"]`). Do not guess the ranking.
+- `ERR_NO_ORDER` → stop: `deploy.branches` has multiple environments mapped to
+  more than one distinct branch but `deploy.order` is missing. Tell the user to
+  add `deploy.order` (low→high, e.g. `["dev","staging","production"]`). Do not
+  guess the ranking.
 - `ERR_MISMATCH` → stop: `deploy.order` and `deploy.branches` name different
   environments. They must match exactly.
-- `{}` (single-environment project) → nothing to sync; report and exit cleanly.
+- `{}` → nothing to sync; report and exit cleanly. This covers both a
+  single-environment project and a multi-environment project whose branches all
+  resolve to the **same** branch (e.g. dev/staging/production all → `main`), where
+  `deploy.order` is not required.
 
 ### 2. Resolve the source branch
 

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

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

package/plugins/lisa-copilot/rules/reference/config-resolution.md

@@ -404,9 +404,15 @@ Rules:
 
 - **Single-environment projects** (one entry in `deploy.branches`) may omit
   `deploy.order`; the derived chain is empty and the back-sync no-ops.
-- **Multi-environment projects MUST set `deploy.order`** for config-driven
-  back-sync. If it is absent, the Action fails rather than guessing the rank
-  (or the workflow wrapper must pass an explicit `chain`, which always wins).
+- **Projects whose environments all map to the same branch** (e.g.
+  `dev`/`staging`/`production` all → `main`) may also omit `deploy.order`: the
+  branches resolve to a single distinct branch, so there is nothing to back-sync
+  and the derived chain is the empty no-op. `deploy.order` is only required when
+  `deploy.branches` resolves to **more than one distinct branch**.
+- **Multi-branch projects MUST set `deploy.order`** for config-driven back-sync.
+  If `deploy.branches` resolves to more than one distinct branch and `deploy.order`
+  is absent, the Action fails rather than guessing the rank (or the workflow
+  wrapper must pass an explicit `chain`, which always wins).
 - The env-name set of `deploy.order` and `deploy.branches` **must match exactly**
   — every env in one appears in the other. A mismatch is a config error.
 
@@ -475,9 +481,12 @@ Doctor must validate config in three layers:
      and `deploy.branches`.
 
 4. **Deploy env-order correctness**
-   - When `deploy.branches` defines more than one environment but `deploy.order` is absent, `WARN`:
-     config-driven back-sync cannot derive a chain without the ranking (the wrapper must add
-     `deploy.order` or pass an explicit `chain`).
+   - When `deploy.branches` resolves to more than one **distinct** branch but `deploy.order` is
+     absent, `WARN`: config-driven back-sync cannot derive a chain without the ranking (the wrapper
+     must add `deploy.order` or pass an explicit `chain`).
+   - When `deploy.branches` defines multiple environments that all map to the **same** branch (e.g.
+     `dev`/`staging`/`production` all → `main`), `deploy.order` is **not** required — the chain is the
+     empty no-op. Do not `WARN` in this case.
    - When `deploy.order` is present but its env names do not exactly match the `deploy.branches`
      keys, `FAIL` — the derived sync-down chain would be wrong or empty.
 

package/plugins/lisa-copilot/skills/doctor/SKILL.md

@@ -104,8 +104,12 @@ this order:
 6. **Deploy env-order audit** (only when `deploy.branches` is present)
    - `PASS` (or skip) when `deploy.branches` defines a single environment — `deploy.order` is
      optional and the back-sync chain is empty.
-   - `WARN` when `deploy.branches` defines **more than one** environment but `deploy.order` is
-     absent. Config-driven back-sync (`reusable-claude-sync-down-branches.yml`) cannot derive a
+   - `PASS` (or skip) when `deploy.branches` defines multiple environments that all map to the
+     **same** branch (e.g. `dev`/`staging`/`production` all → `main`). The branches resolve to a
+     single distinct branch, so there is nothing to back-sync, the chain is the empty no-op, and
+     `deploy.order` is not required. Do not WARN.
+   - `WARN` when `deploy.branches` resolves to **more than one distinct** branch but `deploy.order`
+     is absent. Config-driven back-sync (`reusable-claude-sync-down-branches.yml`) cannot derive a
      source→target chain without the env ranking; the repo must either add `deploy.order`
      (low→high, e.g. `["dev","staging","production"]`) or pass an explicit `chain` in its
      `claude-sync-down-branches.yml` wrapper. WARN not FAIL because the explicit-chain override is

package/plugins/lisa-copilot/skills/sync-down/SKILL.md

@@ -44,6 +44,7 @@ CHAIN=$(jq -e -r '
   | ($b | keys | sort) as $bk
   | ($o | sort) as $ok
   | if ($b | length) <= 1 then "{}"
+    elif (($b | [.[]] | unique | length) <= 1) then "{}"
     elif ($o | length) == 0 then "ERR_NO_ORDER"
     elif ($bk != $ok) then "ERR_MISMATCH"
     else ($o | reverse) as $hl
@@ -53,12 +54,16 @@ CHAIN=$(jq -e -r '
 ' .lisa.config.json)
 ```
 
-- `ERR_NO_ORDER` → stop: `deploy.branches` has multiple environments but
-  `deploy.order` is missing. Tell the user to add `deploy.order` (low→high, e.g.
-  `["dev","staging","production"]`). Do not guess the ranking.
+- `ERR_NO_ORDER` → stop: `deploy.branches` has multiple environments mapped to
+  more than one distinct branch but `deploy.order` is missing. Tell the user to
+  add `deploy.order` (low→high, e.g. `["dev","staging","production"]`). Do not
+  guess the ranking.
 - `ERR_MISMATCH` → stop: `deploy.order` and `deploy.branches` name different
   environments. They must match exactly.
-- `{}` (single-environment project) → nothing to sync; report and exit cleanly.
+- `{}` → nothing to sync; report and exit cleanly. This covers both a
+  single-environment project and a multi-environment project whose branches all
+  resolve to the **same** branch (e.g. dev/staging/production all → `main`), where
+  `deploy.order` is not required.
 
 ### 2. Resolve the source branch
 

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

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

package/plugins/lisa-cursor/rules/config-resolution-reference.mdc

@@ -409,9 +409,15 @@ Rules:
 
 - **Single-environment projects** (one entry in `deploy.branches`) may omit
   `deploy.order`; the derived chain is empty and the back-sync no-ops.
-- **Multi-environment projects MUST set `deploy.order`** for config-driven
-  back-sync. If it is absent, the Action fails rather than guessing the rank
-  (or the workflow wrapper must pass an explicit `chain`, which always wins).
+- **Projects whose environments all map to the same branch** (e.g.
+  `dev`/`staging`/`production` all → `main`) may also omit `deploy.order`: the
+  branches resolve to a single distinct branch, so there is nothing to back-sync
+  and the derived chain is the empty no-op. `deploy.order` is only required when
+  `deploy.branches` resolves to **more than one distinct branch**.
+- **Multi-branch projects MUST set `deploy.order`** for config-driven back-sync.
+  If `deploy.branches` resolves to more than one distinct branch and `deploy.order`
+  is absent, the Action fails rather than guessing the rank (or the workflow
+  wrapper must pass an explicit `chain`, which always wins).
 - The env-name set of `deploy.order` and `deploy.branches` **must match exactly**
   — every env in one appears in the other. A mismatch is a config error.
 
@@ -480,9 +486,12 @@ Doctor must validate config in three layers:
      and `deploy.branches`.
 
 4. **Deploy env-order correctness**
-   - When `deploy.branches` defines more than one environment but `deploy.order` is absent, `WARN`:
-     config-driven back-sync cannot derive a chain without the ranking (the wrapper must add
-     `deploy.order` or pass an explicit `chain`).
+   - When `deploy.branches` resolves to more than one **distinct** branch but `deploy.order` is
+     absent, `WARN`: config-driven back-sync cannot derive a chain without the ranking (the wrapper
+     must add `deploy.order` or pass an explicit `chain`).
+   - When `deploy.branches` defines multiple environments that all map to the **same** branch (e.g.
+     `dev`/`staging`/`production` all → `main`), `deploy.order` is **not** required — the chain is the
+     empty no-op. Do not `WARN` in this case.
    - When `deploy.order` is present but its env names do not exactly match the `deploy.branches`
      keys, `FAIL` — the derived sync-down chain would be wrong or empty.
 

package/plugins/lisa-cursor/skills/doctor/SKILL.md

@@ -104,8 +104,12 @@ this order:
 6. **Deploy env-order audit** (only when `deploy.branches` is present)
    - `PASS` (or skip) when `deploy.branches` defines a single environment — `deploy.order` is
      optional and the back-sync chain is empty.
-   - `WARN` when `deploy.branches` defines **more than one** environment but `deploy.order` is
-     absent. Config-driven back-sync (`reusable-claude-sync-down-branches.yml`) cannot derive a
+   - `PASS` (or skip) when `deploy.branches` defines multiple environments that all map to the
+     **same** branch (e.g. `dev`/`staging`/`production` all → `main`). The branches resolve to a
+     single distinct branch, so there is nothing to back-sync, the chain is the empty no-op, and
+     `deploy.order` is not required. Do not WARN.
+   - `WARN` when `deploy.branches` resolves to **more than one distinct** branch but `deploy.order`
+     is absent. Config-driven back-sync (`reusable-claude-sync-down-branches.yml`) cannot derive a
      source→target chain without the env ranking; the repo must either add `deploy.order`
      (low→high, e.g. `["dev","staging","production"]`) or pass an explicit `chain` in its
      `claude-sync-down-branches.yml` wrapper. WARN not FAIL because the explicit-chain override is

package/plugins/lisa-cursor/skills/sync-down/SKILL.md

@@ -44,6 +44,7 @@ CHAIN=$(jq -e -r '
   | ($b | keys | sort) as $bk
   | ($o | sort) as $ok
   | if ($b | length) <= 1 then "{}"
+    elif (($b | [.[]] | unique | length) <= 1) then "{}"
     elif ($o | length) == 0 then "ERR_NO_ORDER"
     elif ($bk != $ok) then "ERR_MISMATCH"
     else ($o | reverse) as $hl
@@ -53,12 +54,16 @@ CHAIN=$(jq -e -r '
 ' .lisa.config.json)
 ```
 
-- `ERR_NO_ORDER` → stop: `deploy.branches` has multiple environments but
-  `deploy.order` is missing. Tell the user to add `deploy.order` (low→high, e.g.
-  `["dev","staging","production"]`). Do not guess the ranking.
+- `ERR_NO_ORDER` → stop: `deploy.branches` has multiple environments mapped to
+  more than one distinct branch but `deploy.order` is missing. Tell the user to
+  add `deploy.order` (low→high, e.g. `["dev","staging","production"]`). Do not
+  guess the ranking.
 - `ERR_MISMATCH` → stop: `deploy.order` and `deploy.branches` name different
   environments. They must match exactly.
-- `{}` (single-environment project) → nothing to sync; report and exit cleanly.
+- `{}` → nothing to sync; report and exit cleanly. This covers both a
+  single-environment project and a multi-environment project whose branches all
+  resolve to the **same** branch (e.g. dev/staging/production all → `main`), where
+  `deploy.order` is not required.
 
 ### 2. Resolve the source branch
 

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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.155.2",
+  "version": "2.155.3",
   "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-rails/.claude-plugin/plugin.json

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

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.155.2",
+  "version": "2.155.3",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/src/base/rules/reference/config-resolution.md

@@ -404,9 +404,15 @@ Rules:
 
 - **Single-environment projects** (one entry in `deploy.branches`) may omit
   `deploy.order`; the derived chain is empty and the back-sync no-ops.
-- **Multi-environment projects MUST set `deploy.order`** for config-driven
-  back-sync. If it is absent, the Action fails rather than guessing the rank
-  (or the workflow wrapper must pass an explicit `chain`, which always wins).
+- **Projects whose environments all map to the same branch** (e.g.
+  `dev`/`staging`/`production` all → `main`) may also omit `deploy.order`: the
+  branches resolve to a single distinct branch, so there is nothing to back-sync
+  and the derived chain is the empty no-op. `deploy.order` is only required when
+  `deploy.branches` resolves to **more than one distinct branch**.
+- **Multi-branch projects MUST set `deploy.order`** for config-driven back-sync.
+  If `deploy.branches` resolves to more than one distinct branch and `deploy.order`
+  is absent, the Action fails rather than guessing the rank (or the workflow
+  wrapper must pass an explicit `chain`, which always wins).
 - The env-name set of `deploy.order` and `deploy.branches` **must match exactly**
   — every env in one appears in the other. A mismatch is a config error.
 
@@ -475,9 +481,12 @@ Doctor must validate config in three layers:
      and `deploy.branches`.
 
 4. **Deploy env-order correctness**
-   - When `deploy.branches` defines more than one environment but `deploy.order` is absent, `WARN`:
-     config-driven back-sync cannot derive a chain without the ranking (the wrapper must add
-     `deploy.order` or pass an explicit `chain`).
+   - When `deploy.branches` resolves to more than one **distinct** branch but `deploy.order` is
+     absent, `WARN`: config-driven back-sync cannot derive a chain without the ranking (the wrapper
+     must add `deploy.order` or pass an explicit `chain`).
+   - When `deploy.branches` defines multiple environments that all map to the **same** branch (e.g.
+     `dev`/`staging`/`production` all → `main`), `deploy.order` is **not** required — the chain is the
+     empty no-op. Do not `WARN` in this case.
    - When `deploy.order` is present but its env names do not exactly match the `deploy.branches`
      keys, `FAIL` — the derived sync-down chain would be wrong or empty.
 

package/plugins/src/base/skills/doctor/SKILL.md

@@ -104,8 +104,12 @@ this order:
 6. **Deploy env-order audit** (only when `deploy.branches` is present)
    - `PASS` (or skip) when `deploy.branches` defines a single environment — `deploy.order` is
      optional and the back-sync chain is empty.
-   - `WARN` when `deploy.branches` defines **more than one** environment but `deploy.order` is
-     absent. Config-driven back-sync (`reusable-claude-sync-down-branches.yml`) cannot derive a
+   - `PASS` (or skip) when `deploy.branches` defines multiple environments that all map to the
+     **same** branch (e.g. `dev`/`staging`/`production` all → `main`). The branches resolve to a
+     single distinct branch, so there is nothing to back-sync, the chain is the empty no-op, and
+     `deploy.order` is not required. Do not WARN.
+   - `WARN` when `deploy.branches` resolves to **more than one distinct** branch but `deploy.order`
+     is absent. Config-driven back-sync (`reusable-claude-sync-down-branches.yml`) cannot derive a
      source→target chain without the env ranking; the repo must either add `deploy.order`
      (low→high, e.g. `["dev","staging","production"]`) or pass an explicit `chain` in its
      `claude-sync-down-branches.yml` wrapper. WARN not FAIL because the explicit-chain override is

package/plugins/src/base/skills/sync-down/SKILL.md

@@ -44,6 +44,7 @@ CHAIN=$(jq -e -r '
   | ($b | keys | sort) as $bk
   | ($o | sort) as $ok
   | if ($b | length) <= 1 then "{}"
+    elif (($b | [.[]] | unique | length) <= 1) then "{}"
     elif ($o | length) == 0 then "ERR_NO_ORDER"
     elif ($bk != $ok) then "ERR_MISMATCH"
     else ($o | reverse) as $hl
@@ -53,12 +54,16 @@ CHAIN=$(jq -e -r '
 ' .lisa.config.json)
 ```
 
-- `ERR_NO_ORDER` → stop: `deploy.branches` has multiple environments but
-  `deploy.order` is missing. Tell the user to add `deploy.order` (low→high, e.g.
-  `["dev","staging","production"]`). Do not guess the ranking.
+- `ERR_NO_ORDER` → stop: `deploy.branches` has multiple environments mapped to
+  more than one distinct branch but `deploy.order` is missing. Tell the user to
+  add `deploy.order` (low→high, e.g. `["dev","staging","production"]`). Do not
+  guess the ranking.
 - `ERR_MISMATCH` → stop: `deploy.order` and `deploy.branches` name different
   environments. They must match exactly.
-- `{}` (single-environment project) → nothing to sync; report and exit cleanly.
+- `{}` → nothing to sync; report and exit cleanly. This covers both a
+  single-environment project and a multi-environment project whose branches all
+  resolve to the **same** branch (e.g. dev/staging/production all → `main`), where
+  `deploy.order` is not required.
 
 ### 2. Resolve the source branch
 

package/scripts/migrate-deploy-order.sh

@@ -76,7 +76,9 @@ derive_chain() {
   jq -e -r '
     (.deploy.branches // {}) as $b | (.deploy.order // []) as $o
     | ($b|keys|sort) as $bk | ($o|sort) as $ok
-    | if ($b|length)<=1 then "{}" elif ($o|length)==0 then "ERR_NO_ORDER"
+    | if ($b|length)<=1 then "{}"
+      elif (($b|[.[]]|unique|length)<=1) then "{}"
+      elif ($o|length)==0 then "ERR_NO_ORDER"
       elif ($bk!=$ok) then "ERR_MISMATCH"
       else ($o|reverse) as $hl
         | [ range(0;($hl|length)-1) | {($b[$hl[.]]):$b[$hl[.+1]]} ] | add | tojson end