@codyswann/lisa 4.74.5 → 4.74.6

package/dist/core/nightly-e2e-guard-behavior-certificate.js

@@ -41,9 +41,9 @@ export const NIGHTLY_E2E_GUARD_BEHAVIOR_CERTIFICATES = Object.freeze({
     }),
     d1b26caeaf65950e3b60ff41964d234c032c50470072e7643310b1f6722e34e6: Object.freeze({
         contractVersion: "1.9.0",
-        packageVersions: Object.freeze(["4.74.5"]),
+        packageVersions: Object.freeze(["4.74.6"]),
         provenances: Object.freeze([
-            "workspace package @codyswann/lisa@4.74.5 (typescript/copy-overwrite/scripts/check-nightly-e2e-health.mjs)",
+            "workspace package @codyswann/lisa@4.74.6 (typescript/copy-overwrite/scripts/check-nightly-e2e-health.mjs)",
         ]),
     }),
     dfd2fef680de5ef03e63075e8a61c62ca4d95cdfdff6201939b79c748d3397f6: Object.freeze({

package/dist/core/upstream-evidence-manifest.js

@@ -815,7 +815,7 @@ export const UPSTREAM_EVIDENCE_MANIFEST = Object.freeze({
     "plugins/src/base/skills/lisa-setup-automations/SKILL.md": "520dbf5c1735c038ef6607eafefb6914e4e24a434c6abb2b057c6065efbf6bb6",
     "plugins/src/base/skills/lisa-setup-automations/scripts/generate-workflow.mjs": "c13e287c8beb6f847b03c93298b8a3fb211e65ce897e63692933377f8c4303f1",
     "plugins/src/base/skills/lisa-setup-confluence/SKILL.md": "e92d762dbdaeae671c3e52dfe8e10d40a10b606b5e050589181a3898649faedc",
-    "plugins/src/base/skills/lisa-setup-github-repo/SKILL.md": "91302b0cd254e6402b1a70b37794960575f7113d27376f30e267eb8ac7799149",
+    "plugins/src/base/skills/lisa-setup-github-repo/SKILL.md": "bc9232d0609a27c66a1267221f6da33b50850145532da760f5501d37addd2cb0",
     "plugins/src/base/skills/lisa-setup-github/SKILL.md": "75435e81130abd21c678d302b7a220da95a19868d122ca93168278628b200666",
     "plugins/src/base/skills/lisa-setup-jira/SKILL.md": "261acaeb2923cc9238f468dcf986a0e1323a67e1e51d175b2c1b700dacab2fb8",
     "plugins/src/base/skills/lisa-setup-kane/SKILL.md": "fe50024a4f896af01716f2435f57227b1f8de61803e80bf3e3c3247ec179b103",
@@ -1327,7 +1327,7 @@ export const UPSTREAM_EVIDENCE_MANIFEST = Object.freeze({
     "scripts/lisa-github-environments.sh": "0a76e92f108519abaf3e29991299ec3b0db20ea533e69e6d2a53d802dba9c370",
     "scripts/lisa-github-repo-settings.sh": "4afbccdfb08c62ba13afee42ec8561a28facf87c61f6f4b80000115328364d54",
     "scripts/lisa-github-repo-setup.sh": "4717873e339b3e615d0bf22b4cb290b3575df5aba8c3639dc0d3bebc23abf651",
-    "scripts/lisa-github-rulesets.sh": "1818492ed1d5489030c959438bd1ab34379c261ba398ebeae1b851c1ab357a09",
+    "scripts/lisa-github-rulesets.sh": "183e3f80b09c3189c131e5b31b21d9349c17d1eded5d42742f49e91f058c75de",
     "scripts/lisa-mutation.mjs": "74603e61f493d700318feb862f61ee1653430700b5edf232e70241ccdedac587",
     "scripts/lisa-remote-env/materialized-env-authority.mjs": "2844475d7b407c4dccce4e0f500a3aaf5412f9f315c9173dd0ca22dd24497049",
     "scripts/lisa-remote-env/session-start.sh": "2b40873f39b38e00b50285ca2c4c705ea018285fa457c3e1a985adbeaad6c26b",

package/package.json

@@ -189,7 +189,7 @@
     "qs": "^6.16.0"
   },
   "name": "@codyswann/lisa",
-  "version": "4.74.5",
+  "version": "4.74.6",
   "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": "ef8f7f2dc99790e757388c1836738c538a5aacef",
-  "gitHead": "ef8f7f2dc99790e757388c1836738c538a5aacef",
-  "lisaReleaseTag": "v4.74.5"
+  "lisaReleaseCommit": "00b41544bab8ef052550f94becac99518ccecb32",
+  "gitHead": "00b41544bab8ef052550f94becac99518ccecb32",
+  "lisaReleaseTag": "v4.74.6"
 }

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

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

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

@@ -32,6 +32,7 @@ Apply the fleet-standard GitHub repository configuration to this project's repo.
    - Repos without `.github/workflows/` get only app-based required checks — an Actions check that can never report would block every PR forever
    - **A template change never reaches an already-configured repo on its own** — re-running this step is the migration. Each context the run newly makes blocking is printed as `+ now required: <context>`, and a ruleset that already satisfies its template reports `nothing to do` and is not sent at all, so a second run is visibly a no-op
    - **Declaring a ruleset's required list makes it declarative.** By default a live-only required context is preserved, never dropped — including on the generated `base`, which gets no exemption: removing a protection by default, on a script invoked with `--yes`, is not something an operator ever opted into. Name a ruleset in `github.rulesets.requiredChecks` and the live list stops being unioned in, so removing an entry actually stops requiring it — printed as `- no longer required: <context>`. Dropping an `await` without that opt-in leaves the live context in place; `lisa-reconcile-policy.mjs` then reports it as EXTRA, and `--prune` is where the removal is asked for. The retired `addRequiredChecks` is still read and could only ever add
+   - **Bypass actors follow the same contract.** By default a live bypass actor the template does not name (e.g. an admin `RepositoryRole` someone added on purpose) is kept, the template's actors are added beside it, and a live actor's `bypass_mode` is never widened back to the template's. Declaring a ruleset's list — `github.rulesets.bypassActors.<ruleset name>` for a template ruleset, `policy.ruleset.bypass_actors` for the generated `base` — makes it exactly that list, which is the only way to remove one. Every change is printed by name, dry run included: `+ bypass actor added: <type> [<id>] (<mode>)`, a warning `- bypass actor removed: …`, and `~ bypass actor mode changed: <type> [<id>] (<old> -> <new>)`
 3. **Deploy key** (`scripts/setup-deploy-key.sh --yes`) — write-access deploy key + `DEPLOY_KEY` secret, skipped when already configured. The `base` ruleset's `DeployKey: always` bypass is what lets CI version-bump pushes through protected branches.
 4. **Deployment environments** (`scripts/lisa-github-environments.sh`) — entirely optional; only runs when `.lisa.config.json` declares environments:
    ```json

package/plugins/lisa/skills/lisa-setup-github-repo/SKILL.md

@@ -30,6 +30,7 @@ Apply the fleet-standard GitHub repository configuration to this project's repo.
    - Repos without `.github/workflows/` get only app-based required checks — an Actions check that can never report would block every PR forever
    - **A template change never reaches an already-configured repo on its own** — re-running this step is the migration. Each context the run newly makes blocking is printed as `+ now required: <context>`, and a ruleset that already satisfies its template reports `nothing to do` and is not sent at all, so a second run is visibly a no-op
    - **Declaring a ruleset's required list makes it declarative.** By default a live-only required context is preserved, never dropped — including on the generated `base`, which gets no exemption: removing a protection by default, on a script invoked with `--yes`, is not something an operator ever opted into. Name a ruleset in `github.rulesets.requiredChecks` and the live list stops being unioned in, so removing an entry actually stops requiring it — printed as `- no longer required: <context>`. Dropping an `await` without that opt-in leaves the live context in place; `lisa-reconcile-policy.mjs` then reports it as EXTRA, and `--prune` is where the removal is asked for. The retired `addRequiredChecks` is still read and could only ever add
+   - **Bypass actors follow the same contract.** By default a live bypass actor the template does not name (e.g. an admin `RepositoryRole` someone added on purpose) is kept, the template's actors are added beside it, and a live actor's `bypass_mode` is never widened back to the template's. Declaring a ruleset's list — `github.rulesets.bypassActors.<ruleset name>` for a template ruleset, `policy.ruleset.bypass_actors` for the generated `base` — makes it exactly that list, which is the only way to remove one. Every change is printed by name, dry run included: `+ bypass actor added: <type> [<id>] (<mode>)`, a warning `- bypass actor removed: …`, and `~ bypass actor mode changed: <type> [<id>] (<old> -> <new>)`
 3. **Deploy key** (`scripts/setup-deploy-key.sh --yes`) — write-access deploy key + `DEPLOY_KEY` secret, skipped when already configured. The `base` ruleset's `DeployKey: always` bypass is what lets CI version-bump pushes through protected branches.
 4. **Deployment environments** (`scripts/lisa-github-environments.sh`) — entirely optional; only runs when `.lisa.config.json` declares environments:
    ```json

package/plugins/lisa-agy/plugin.json

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

package/plugins/lisa-agy/skills/lisa-setup-github-repo/SKILL.md

@@ -30,6 +30,7 @@ Apply the fleet-standard GitHub repository configuration to this project's repo.
    - Repos without `.github/workflows/` get only app-based required checks — an Actions check that can never report would block every PR forever
    - **A template change never reaches an already-configured repo on its own** — re-running this step is the migration. Each context the run newly makes blocking is printed as `+ now required: <context>`, and a ruleset that already satisfies its template reports `nothing to do` and is not sent at all, so a second run is visibly a no-op
    - **Declaring a ruleset's required list makes it declarative.** By default a live-only required context is preserved, never dropped — including on the generated `base`, which gets no exemption: removing a protection by default, on a script invoked with `--yes`, is not something an operator ever opted into. Name a ruleset in `github.rulesets.requiredChecks` and the live list stops being unioned in, so removing an entry actually stops requiring it — printed as `- no longer required: <context>`. Dropping an `await` without that opt-in leaves the live context in place; `lisa-reconcile-policy.mjs` then reports it as EXTRA, and `--prune` is where the removal is asked for. The retired `addRequiredChecks` is still read and could only ever add
+   - **Bypass actors follow the same contract.** By default a live bypass actor the template does not name (e.g. an admin `RepositoryRole` someone added on purpose) is kept, the template's actors are added beside it, and a live actor's `bypass_mode` is never widened back to the template's. Declaring a ruleset's list — `github.rulesets.bypassActors.<ruleset name>` for a template ruleset, `policy.ruleset.bypass_actors` for the generated `base` — makes it exactly that list, which is the only way to remove one. Every change is printed by name, dry run included: `+ bypass actor added: <type> [<id>] (<mode>)`, a warning `- bypass actor removed: …`, and `~ bypass actor mode changed: <type> [<id>] (<old> -> <new>)`
 3. **Deploy key** (`scripts/setup-deploy-key.sh --yes`) — write-access deploy key + `DEPLOY_KEY` secret, skipped when already configured. The `base` ruleset's `DeployKey: always` bypass is what lets CI version-bump pushes through protected branches.
 4. **Deployment environments** (`scripts/lisa-github-environments.sh`) — entirely optional; only runs when `.lisa.config.json` declares environments:
    ```json

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

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

package/plugins/lisa-copilot/skills/lisa-setup-github-repo/SKILL.md

@@ -30,6 +30,7 @@ Apply the fleet-standard GitHub repository configuration to this project's repo.
    - Repos without `.github/workflows/` get only app-based required checks — an Actions check that can never report would block every PR forever
    - **A template change never reaches an already-configured repo on its own** — re-running this step is the migration. Each context the run newly makes blocking is printed as `+ now required: <context>`, and a ruleset that already satisfies its template reports `nothing to do` and is not sent at all, so a second run is visibly a no-op
    - **Declaring a ruleset's required list makes it declarative.** By default a live-only required context is preserved, never dropped — including on the generated `base`, which gets no exemption: removing a protection by default, on a script invoked with `--yes`, is not something an operator ever opted into. Name a ruleset in `github.rulesets.requiredChecks` and the live list stops being unioned in, so removing an entry actually stops requiring it — printed as `- no longer required: <context>`. Dropping an `await` without that opt-in leaves the live context in place; `lisa-reconcile-policy.mjs` then reports it as EXTRA, and `--prune` is where the removal is asked for. The retired `addRequiredChecks` is still read and could only ever add
+   - **Bypass actors follow the same contract.** By default a live bypass actor the template does not name (e.g. an admin `RepositoryRole` someone added on purpose) is kept, the template's actors are added beside it, and a live actor's `bypass_mode` is never widened back to the template's. Declaring a ruleset's list — `github.rulesets.bypassActors.<ruleset name>` for a template ruleset, `policy.ruleset.bypass_actors` for the generated `base` — makes it exactly that list, which is the only way to remove one. Every change is printed by name, dry run included: `+ bypass actor added: <type> [<id>] (<mode>)`, a warning `- bypass actor removed: …`, and `~ bypass actor mode changed: <type> [<id>] (<old> -> <new>)`
 3. **Deploy key** (`scripts/setup-deploy-key.sh --yes`) — write-access deploy key + `DEPLOY_KEY` secret, skipped when already configured. The `base` ruleset's `DeployKey: always` bypass is what lets CI version-bump pushes through protected branches.
 4. **Deployment environments** (`scripts/lisa-github-environments.sh`) — entirely optional; only runs when `.lisa.config.json` declares environments:
    ```json

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

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

package/plugins/lisa-cursor/skills/lisa-setup-github-repo/SKILL.md

@@ -30,6 +30,7 @@ Apply the fleet-standard GitHub repository configuration to this project's repo.
    - Repos without `.github/workflows/` get only app-based required checks — an Actions check that can never report would block every PR forever
    - **A template change never reaches an already-configured repo on its own** — re-running this step is the migration. Each context the run newly makes blocking is printed as `+ now required: <context>`, and a ruleset that already satisfies its template reports `nothing to do` and is not sent at all, so a second run is visibly a no-op
    - **Declaring a ruleset's required list makes it declarative.** By default a live-only required context is preserved, never dropped — including on the generated `base`, which gets no exemption: removing a protection by default, on a script invoked with `--yes`, is not something an operator ever opted into. Name a ruleset in `github.rulesets.requiredChecks` and the live list stops being unioned in, so removing an entry actually stops requiring it — printed as `- no longer required: <context>`. Dropping an `await` without that opt-in leaves the live context in place; `lisa-reconcile-policy.mjs` then reports it as EXTRA, and `--prune` is where the removal is asked for. The retired `addRequiredChecks` is still read and could only ever add
+   - **Bypass actors follow the same contract.** By default a live bypass actor the template does not name (e.g. an admin `RepositoryRole` someone added on purpose) is kept, the template's actors are added beside it, and a live actor's `bypass_mode` is never widened back to the template's. Declaring a ruleset's list — `github.rulesets.bypassActors.<ruleset name>` for a template ruleset, `policy.ruleset.bypass_actors` for the generated `base` — makes it exactly that list, which is the only way to remove one. Every change is printed by name, dry run included: `+ bypass actor added: <type> [<id>] (<mode>)`, a warning `- bypass actor removed: …`, and `~ bypass actor mode changed: <type> [<id>] (<old> -> <new>)`
 3. **Deploy key** (`scripts/setup-deploy-key.sh --yes`) — write-access deploy key + `DEPLOY_KEY` secret, skipped when already configured. The `base` ruleset's `DeployKey: always` bypass is what lets CI version-bump pushes through protected branches.
 4. **Deployment environments** (`scripts/lisa-github-environments.sh`) — entirely optional; only runs when `.lisa.config.json` declares environments:
    ```json

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "4.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "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": "4.74.5",
+  "version": "4.74.6",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/src/base/skills/lisa-setup-github-repo/SKILL.md

@@ -30,6 +30,7 @@ Apply the fleet-standard GitHub repository configuration to this project's repo.
    - Repos without `.github/workflows/` get only app-based required checks — an Actions check that can never report would block every PR forever
    - **A template change never reaches an already-configured repo on its own** — re-running this step is the migration. Each context the run newly makes blocking is printed as `+ now required: <context>`, and a ruleset that already satisfies its template reports `nothing to do` and is not sent at all, so a second run is visibly a no-op
    - **Declaring a ruleset's required list makes it declarative.** By default a live-only required context is preserved, never dropped — including on the generated `base`, which gets no exemption: removing a protection by default, on a script invoked with `--yes`, is not something an operator ever opted into. Name a ruleset in `github.rulesets.requiredChecks` and the live list stops being unioned in, so removing an entry actually stops requiring it — printed as `- no longer required: <context>`. Dropping an `await` without that opt-in leaves the live context in place; `lisa-reconcile-policy.mjs` then reports it as EXTRA, and `--prune` is where the removal is asked for. The retired `addRequiredChecks` is still read and could only ever add
+   - **Bypass actors follow the same contract.** By default a live bypass actor the template does not name (e.g. an admin `RepositoryRole` someone added on purpose) is kept, the template's actors are added beside it, and a live actor's `bypass_mode` is never widened back to the template's. Declaring a ruleset's list — `github.rulesets.bypassActors.<ruleset name>` for a template ruleset, `policy.ruleset.bypass_actors` for the generated `base` — makes it exactly that list, which is the only way to remove one. Every change is printed by name, dry run included: `+ bypass actor added: <type> [<id>] (<mode>)`, a warning `- bypass actor removed: …`, and `~ bypass actor mode changed: <type> [<id>] (<old> -> <new>)`
 3. **Deploy key** (`scripts/setup-deploy-key.sh --yes`) — write-access deploy key + `DEPLOY_KEY` secret, skipped when already configured. The `base` ruleset's `DeployKey: always` bypass is what lets CI version-bump pushes through protected branches.
 4. **Deployment environments** (`scripts/lisa-github-environments.sh`) — entirely optional; only runs when `.lisa.config.json` declares environments:
    ```json

package/scripts/lisa-github-rulesets.sh

@@ -724,6 +724,209 @@ report_removed_contexts() {
   done < <(ruleset_removed_contexts "$live" "$payload")
 }
 
+##############################################################################
+# Bypass Actors
+##############################################################################
+
+# Bypass actors follow the same contract as required checks (#4297).
+#
+# The applier used to send each template's `bypass_actors` as the whole list,
+# and GitHub REPLACES the list on update. So a bypass a consumer added on
+# purpose — measured: an admin RepositoryRole on `nightly e2e health` — was
+# deleted by every apply, reported as a routine "Applied", and no config key
+# could keep it. Losing a bypass is not a tightening anyone asked for either:
+# it can strand the only actor allowed to land an emergency fix.
+#
+# So, exactly like the required list:
+#   - by default the LIVE bypass list is preserved and the template's entries
+#     are added to it;
+#   - a ruleset whose bypass list is DECLARED gets precisely that list, which
+#     is the only way to remove an actor;
+#   - every actor added or removed, and every bypass_mode changed, is printed
+#     by name, on a dry run too; an undeclared live entry keeps its own mode.
+#
+# Declared per ruleset under `github.rulesets.bypassActors`:
+#   { "github": { "rulesets": { "bypassActors": {
+#       "nightly e2e health": [
+#         { "actor_type": "DeployKey", "actor_id": null, "bypass_mode": "always" }
+#       ] } } } }
+#
+# The generated `base` ruleset already has a declaration surface —
+# `policy.ruleset.bypass_actors`, which lisa-ruleset-payload.mjs builds it
+# from — so that is what makes base declarative. A second key for the same
+# field would recreate the two-writers problem the generator exists to end.
+
+# The declared bypass list for one ruleset, or "null" when none is declared.
+config_bypass_actors() {
+  local project_path="$1"
+  local ruleset_name="$2"
+  local config="$project_path/.lisa.config.json"
+
+  if [[ ! -f "$config" ]]; then
+    echo "null"
+    return 0
+  fi
+
+  local filter='.github.rulesets.bypassActors[$name] // null'
+  if [[ "$ruleset_name" == "base" ]]; then
+    if jq -e '.github.rulesets.bypassActors.base != null' "$config" &> /dev/null; then
+      log_warning "github.rulesets.bypassActors.base is ignored — declare base's bypass list as policy.ruleset.bypass_actors" >&2
+    fi
+    filter='.policy.ruleset.bypass_actors // null'
+  fi
+
+  # An omitted bypass_mode is GitHub's default, `always`, and an omitted
+  # actor_id is null (DeployKey). Filled in here so a declaration that leaves
+  # them out compares equal to what GitHub stores, rather than reporting a
+  # change that never happens.
+  local declared
+  if ! declared=$(jq -c --arg name "$ruleset_name" \
+    "($filter) | if type == \"array\" then map(. + {actor_id: (.actor_id // null), bypass_mode: (.bypass_mode // \"always\")}) else null end" \
+    "$config" 2>/dev/null); then
+    log_warning ".lisa.config.json could not be parsed — ignoring github.rulesets overrides" >&2
+    echo "null"
+    return 0
+  fi
+  echo "$declared"
+}
+
+# Print why this ruleset's bypass declaration is unusable, or nothing when it
+# is absent or well-formed. A malformed declaration must stop the ruleset: read
+# as "nothing declared" it would quietly PRESERVE the actors the operator tried
+# to remove, and the run would still report success.
+bypass_declaration_error() {
+  local project_path="$1"
+  local ruleset_name="$2"
+  local config="$project_path/.lisa.config.json"
+
+  [[ -f "$config" ]] || return 0
+
+  local key="github.rulesets.bypassActors[\"$ruleset_name\"]"
+  local filter='.github.rulesets.bypassActors[$name]?'
+  if [[ "$ruleset_name" == "base" ]]; then
+    key="policy.ruleset.bypass_actors"
+    filter='.policy.ruleset.bypass_actors?'
+  fi
+
+  jq -r --arg name "$ruleset_name" --arg key "$key" "
+    ($filter) as \$declared
+    | if \$declared == null then empty
+      elif (\$declared | type) != \"array\" then
+        \"\(\$key) must be a list of bypass actors, got \(\$declared | type)\"
+      elif any(\$declared[]; type != \"object\" or (.actor_type | type) != \"string\") then
+        \"\(\$key) has an entry without a string actor_type\"
+      elif any(\$declared[]; .actor_id != null and ((.actor_id | type) != \"number\" or .actor_id != (.actor_id | floor))) then
+        \"\(\$key) has an actor_id that is neither an integer nor null\"
+      elif any(\$declared[]; .bypass_mode as \$mode | \$mode != null and ([\"always\", \"pull_request\", \"exempt\"] | index(\$mode)) == null) then
+        \"\(\$key) has a bypass_mode other than always, pull_request or exempt\"
+      else empty end" "$config" 2>/dev/null \
+    || echo "$key could not be validated — refusing to apply a declaration nobody checked"
+}
+
+# Replace a template's bypass list with the declared one, when there is one.
+# `base` is skipped: its payload is already built from its declaration.
+apply_config_bypass_actors() {
+  local json="$1"
+  local project_path="$2"
+  local ruleset_name="$3"
+
+  local declared
+  declared=$(config_bypass_actors "$project_path" "$ruleset_name")
+  if [[ "$declared" == "null" || "$ruleset_name" == "base" ]]; then
+    echo "$json"
+    return 0
+  fi
+  echo "$json" | jq --argjson declared "$declared" '.bypass_actors = $declared'
+}
+
+# Union the live bypass list back into the payload. Live entries are kept
+# verbatim and in live order, so a ruleset that needs no change compares equal
+# and nothing is sent; template-only actors are appended. A live entry the
+# template also names keeps its LIVE bypass_mode: an operator who narrowed the
+# admin bypass from `always` to `pull_request` made the same deliberate choice
+# as one who added it, and taking the template's mode would widen it back
+# without a word. Changing a mode, like removing an actor, needs a declaration.
+preserve_live_bypass_actors() {
+  local live="$1"
+  local json="$2"
+
+  if [[ -z "$live" ]] || ! echo "$live" | jq -e 'has("bypass_actors")' &> /dev/null; then
+    echo "$json"
+    return 0
+  fi
+
+  echo "$json" | jq --argjson live "$live" '
+    def actor_key: [.actor_type, .actor_id];
+    (.bypass_actors // []) as $want
+    | ($live.bypass_actors // []) as $have
+    | .bypass_actors = (
+        $have
+        + [ $want[]
+          | . as $entry
+          | select([ $have[] | actor_key ] | index([$entry | actor_key]) | not) ]
+      )'
+}
+
+# One line per bypass actor in $1's list that $2's list lacks, keyed by
+# actor type and id. Formatted `<type> [<id>] (<bypass_mode>)`.
+bypass_actors_missing_from() {
+  local from="$1"
+  local against="$2"
+
+  jq -r -n --argjson from "${from:-null}" --argjson against "${against:-null}" '
+    def actor_key: [.actor_type, .actor_id];
+    def actors: if . == null then [] else (.bypass_actors // []) end;
+    ($against | actors | map(actor_key)) as $keys
+    | ($from | actors)[]
+    | select(actor_key as $k | ($keys | index([$k])) | not)
+    | "\(.actor_type)\(if .actor_id == null then "" else " \(.actor_id)" end) (\(.bypass_mode))"'
+}
+
+# One line per actor present in both lists whose bypass_mode differs,
+# formatted `<type> [<id>] (<live mode> -> <payload mode>)`.
+bypass_actor_mode_changes() {
+  local live="$1"
+  local payload="$2"
+
+  jq -r -n --argjson live "${live:-null}" --argjson want "${payload:-null}" '
+    def actor_key: [.actor_type, .actor_id];
+    def actors: if . == null then [] else (.bypass_actors // []) end;
+    ($live | actors) as $have
+    | ($want | actors)[]
+    | . as $entry
+    | ([ $have[] | select(actor_key == ($entry | actor_key)) ] | first) as $old
+    | select($old != null and $old.bypass_mode != $entry.bypass_mode)
+    | "\(.actor_type)\(if .actor_id == null then "" else " \(.actor_id)" end) (\($old.bypass_mode) -> \(.bypass_mode))"'
+}
+
+# Name every bypass actor this run adds and removes. A removal is a warning:
+# it can only happen when config declared the list, and it should still never
+# read in the audit log as a routine reconciliation.
+report_bypass_actor_changes() {
+  local live="$1"
+  local payload="$2"
+
+  # A live ruleset that does not disclose its bypass list cannot be preserved,
+  # and the payload's list will replace whatever is there.
+  if [[ -n "$live" ]] \
+    && ! echo "$live" | jq -e 'has("bypass_actors")' &> /dev/null \
+    && echo "$payload" | jq -e 'has("bypass_actors")' &> /dev/null; then
+    log_warning "  GitHub did not disclose this ruleset's bypass actors — any it has will be replaced by the list sent (the token needs repository admin to read them)"
+    return 0
+  fi
+
+  local actor
+  while IFS= read -r actor; do
+    [[ -n "$actor" ]] && log_info "  + bypass actor added: $actor"
+  done < <(bypass_actors_missing_from "$payload" "$live")
+  while IFS= read -r actor; do
+    [[ -n "$actor" ]] && log_warning "  - bypass actor removed: $actor (the declared bypass list does not name it)"
+  done < <(bypass_actors_missing_from "$live" "$payload")
+  while IFS= read -r actor; do
+    [[ -n "$actor" ]] && log_warning "  ~ bypass actor mode changed: $actor (the declared bypass list sets it)"
+  done < <(bypass_actor_mode_changes "$live" "$payload")
+}
+
 apply_ruleset() {
   local repo="$1"
   local template_file="$2"
@@ -736,12 +939,20 @@ apply_ruleset() {
   local ruleset_name
   ruleset_name=$(echo "$template_content" | jq -r '.name')
 
+  local bypass_error
+  bypass_error=$(bypass_declaration_error "$project_path" "$ruleset_name")
+  if [[ -n "$bypass_error" ]]; then
+    log_error "Not applying ruleset '$ruleset_name': $bypass_error"
+    return 1
+  fi
+
   local clean_template
   clean_template=$(strip_readonly_fields "$template_content")
   clean_template=$(add_derived_run_gate_checks "$clean_template" "$project_path" "$ruleset_name")
   clean_template=$(add_config_required_checks "$clean_template" "$project_path" "$ruleset_name")
   clean_template=$(strip_actions_checks_if_no_workflows "$clean_template" "$project_path")
   clean_template=$(strip_config_dropped_checks "$clean_template" "$project_path")
+  clean_template=$(apply_config_bypass_actors "$clean_template" "$project_path" "$ruleset_name")
 
   # A template whose rules were entirely stripped has nothing to enforce here.
   if [[ $(echo "$clean_template" | jq '(.rules // [1]) | length') -eq 0 ]]; then
@@ -779,6 +990,12 @@ apply_ruleset() {
     else
       clean_template=$(preserve_live_required_checks "$live" "$clean_template")
     fi
+    # The same opt-in, for the bypass list: preserved unless declared.
+    if [[ "$(config_bypass_actors "$project_path" "$ruleset_name")" == "null" ]]; then
+      clean_template=$(preserve_live_bypass_actors "$live" "$clean_template")
+    else
+      log_verbose "Bypass actors for '$ruleset_name' are declared in .lisa.config.json — the live list is not preserved"
+    fi
   fi
 
   # Idempotence: a run that would change nothing must say so and send nothing,
@@ -797,6 +1014,7 @@ apply_ruleset() {
     fi
     report_added_contexts "$live" "$clean_template"
     report_removed_contexts "$live" "$clean_template"
+    report_bypass_actor_changes "$live" "$clean_template"
     log_verbose "Template: $template_file"
     return 0
   fi
@@ -811,6 +1029,7 @@ apply_ruleset() {
   if apply_with_integration_fallback "$repo" "$ruleset_name" "$clean_template" "$existing_id"; then
     report_added_contexts "$live" "${APPLIED_PAYLOAD:-$clean_template}"
     report_removed_contexts "$live" "${APPLIED_PAYLOAD:-$clean_template}"
+    report_bypass_actor_changes "$live" "${APPLIED_PAYLOAD:-$clean_template}"
     return 0
   fi
   log_error "Failed to apply ruleset '$ruleset_name'"