@codyswann/lisa 2.214.0 → 2.216.0

package/package.json

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

package/plugins/lisa/.codex-plugin/skills/lisa-drive-pr-to-merge/SKILL.md

@@ -36,6 +36,43 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
 Resolve `<owner>/<repo>` from `gh repo view --json nameWithOwner` (or the PR URL).
 Use plain `gh` + `git` so Claude and Codex execute identically.
 
+## 0. Take the babysitter lease
+
+This skill is the branch's owner while it runs. Declare that ownership so the
+CI auto-fix workflow (`reusable-claude-ci-auto-fix.yml`) stands down instead of
+pushing competing fixes to the same branch (the single-writer rule):
+
+```bash
+gh label create "lisa:babysitter-on-duty" \
+  --description "A drive-pr-to-merge session is actively driving this PR; CI auto-fix must stand down" \
+  --color FBCA04 || true  # tolerate only already-exists; check the next step
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+gh pr view <pr> --json labels \
+  --jq '[.labels[].name] | contains(["lisa:babysitter-on-duty"])'
+```
+
+Verify the final command prints `true` before driving. If the label could not
+be attached (for example, no label-write permission), retry once; if it still
+fails, surface a warning that the branch is unleased — the CI auto-fix
+workflow may engage in parallel — and watch for its `claude-auto-fix-*` PR
+per section 2f while driving.
+
+The auto-fix workflow reads freshness from the label's most recent `labeled`
+timeline event and treats stamps older than its TTL (default 90 minutes) as
+stale. **Refresh the lease** whenever more than ~30 minutes have passed since
+the last stamp while the watch loop is still running — a refresh is a
+remove + re-add (re-adding an existing label does not create a new timeline
+event):
+
+```bash
+gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+```
+
+**Release the lease** (remove the label) at every terminal state — merged,
+closed, or a hard block handed to a human. A crashed session that never
+releases is why the TTL exists; do not rely on it as the normal release path.
+
 ## 1. Enable auto-merge
 
 Before enabling auto-merge, capture the live PR head and compare it to
@@ -74,7 +111,8 @@ gh pr view <pr> --json state,mergeStateStatus,mergeable,reviewDecision,statusChe
 ```
 
 Handle every blocker class; after any fix, re-poll and continue. Do not stop while
-the PR is still open and progress is possible.
+the PR is still open and progress is possible. On each iteration, refresh the
+babysitter lease if its last stamp is older than ~30 minutes (section 0).
 
 In **`on_blocker=report`** mode, only the mechanical step (a) and auto-merge enabling
 apply; for any of (b)–(e) do not act — classify the blocker and return per the input
@@ -150,6 +188,16 @@ Some org rulesets allow 0 approvals yet a bot `CHANGES_REQUESTED` still blocks
 auto-merge — dismissing the stale review after resolving all threads is what
 unblocks it.
 
+### f. Pending auto-fix PR into this branch
+If an open PR from `claude-auto-fix-<headRefName>` targets this PR's head
+branch (the CI auto-fix workflow engaged before this session took the lease),
+adjudicate it: merge it into the head branch if the fix is correct and still
+needed, otherwise close it and delete the side branch. Never leave it dangling
+— it represents a competing writer's pending work. Merging it mutates the
+driven branch, so treat it like any other push: disarm auto-merge first,
+re-read `headRefOid`, reset `verify_commit` to the merged head, wait for that
+head's checks to start, then re-enable auto-merge (section 1).
+
 ## 3. Merge and verify it actually shipped (ancestry check)
 
 Enabling auto-merge + green checks + resolved threads is **not** proof the merge
@@ -177,3 +225,8 @@ Loop until one of:
   needs design input, or genuine unresolved human objection (not a bot gate). Stop
   and report exactly what is blocking and what was already tried — never force the
   merge or weaken a gate to get past it.
+
+At every terminal state, release the babysitter lease
+(`gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"`) so the CI
+auto-fix workflow can take over as fixer of last resort if the branch goes
+red later with nobody driving it.

package/plugins/lisa/skills/lisa-drive-pr-to-merge/SKILL.md

@@ -36,6 +36,43 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
 Resolve `<owner>/<repo>` from `gh repo view --json nameWithOwner` (or the PR URL).
 Use plain `gh` + `git` so Claude and Codex execute identically.
 
+## 0. Take the babysitter lease
+
+This skill is the branch's owner while it runs. Declare that ownership so the
+CI auto-fix workflow (`reusable-claude-ci-auto-fix.yml`) stands down instead of
+pushing competing fixes to the same branch (the single-writer rule):
+
+```bash
+gh label create "lisa:babysitter-on-duty" \
+  --description "A drive-pr-to-merge session is actively driving this PR; CI auto-fix must stand down" \
+  --color FBCA04 || true  # tolerate only already-exists; check the next step
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+gh pr view <pr> --json labels \
+  --jq '[.labels[].name] | contains(["lisa:babysitter-on-duty"])'
+```
+
+Verify the final command prints `true` before driving. If the label could not
+be attached (for example, no label-write permission), retry once; if it still
+fails, surface a warning that the branch is unleased — the CI auto-fix
+workflow may engage in parallel — and watch for its `claude-auto-fix-*` PR
+per section 2f while driving.
+
+The auto-fix workflow reads freshness from the label's most recent `labeled`
+timeline event and treats stamps older than its TTL (default 90 minutes) as
+stale. **Refresh the lease** whenever more than ~30 minutes have passed since
+the last stamp while the watch loop is still running — a refresh is a
+remove + re-add (re-adding an existing label does not create a new timeline
+event):
+
+```bash
+gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+```
+
+**Release the lease** (remove the label) at every terminal state — merged,
+closed, or a hard block handed to a human. A crashed session that never
+releases is why the TTL exists; do not rely on it as the normal release path.
+
 ## 1. Enable auto-merge
 
 Before enabling auto-merge, capture the live PR head and compare it to
@@ -74,7 +111,8 @@ gh pr view <pr> --json state,mergeStateStatus,mergeable,reviewDecision,statusChe
 ```
 
 Handle every blocker class; after any fix, re-poll and continue. Do not stop while
-the PR is still open and progress is possible.
+the PR is still open and progress is possible. On each iteration, refresh the
+babysitter lease if its last stamp is older than ~30 minutes (section 0).
 
 In **`on_blocker=report`** mode, only the mechanical step (a) and auto-merge enabling
 apply; for any of (b)–(e) do not act — classify the blocker and return per the input
@@ -150,6 +188,16 @@ Some org rulesets allow 0 approvals yet a bot `CHANGES_REQUESTED` still blocks
 auto-merge — dismissing the stale review after resolving all threads is what
 unblocks it.
 
+### f. Pending auto-fix PR into this branch
+If an open PR from `claude-auto-fix-<headRefName>` targets this PR's head
+branch (the CI auto-fix workflow engaged before this session took the lease),
+adjudicate it: merge it into the head branch if the fix is correct and still
+needed, otherwise close it and delete the side branch. Never leave it dangling
+— it represents a competing writer's pending work. Merging it mutates the
+driven branch, so treat it like any other push: disarm auto-merge first,
+re-read `headRefOid`, reset `verify_commit` to the merged head, wait for that
+head's checks to start, then re-enable auto-merge (section 1).
+
 ## 3. Merge and verify it actually shipped (ancestry check)
 
 Enabling auto-merge + green checks + resolved threads is **not** proof the merge
@@ -177,3 +225,8 @@ Loop until one of:
   needs design input, or genuine unresolved human objection (not a bot gate). Stop
   and report exactly what is blocking and what was already tried — never force the
   merge or weaken a gate to get past it.
+
+At every terminal state, release the babysitter lease
+(`gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"`) so the CI
+auto-fix workflow can take over as fixer of last resort if the branch goes
+red later with nobody driving it.

package/plugins/lisa-agy/plugin.json

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

package/plugins/lisa-agy/skills/lisa-drive-pr-to-merge/SKILL.md

@@ -36,6 +36,43 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
 Resolve `<owner>/<repo>` from `gh repo view --json nameWithOwner` (or the PR URL).
 Use plain `gh` + `git` so Claude and Codex execute identically.
 
+## 0. Take the babysitter lease
+
+This skill is the branch's owner while it runs. Declare that ownership so the
+CI auto-fix workflow (`reusable-claude-ci-auto-fix.yml`) stands down instead of
+pushing competing fixes to the same branch (the single-writer rule):
+
+```bash
+gh label create "lisa:babysitter-on-duty" \
+  --description "A drive-pr-to-merge session is actively driving this PR; CI auto-fix must stand down" \
+  --color FBCA04 || true  # tolerate only already-exists; check the next step
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+gh pr view <pr> --json labels \
+  --jq '[.labels[].name] | contains(["lisa:babysitter-on-duty"])'
+```
+
+Verify the final command prints `true` before driving. If the label could not
+be attached (for example, no label-write permission), retry once; if it still
+fails, surface a warning that the branch is unleased — the CI auto-fix
+workflow may engage in parallel — and watch for its `claude-auto-fix-*` PR
+per section 2f while driving.
+
+The auto-fix workflow reads freshness from the label's most recent `labeled`
+timeline event and treats stamps older than its TTL (default 90 minutes) as
+stale. **Refresh the lease** whenever more than ~30 minutes have passed since
+the last stamp while the watch loop is still running — a refresh is a
+remove + re-add (re-adding an existing label does not create a new timeline
+event):
+
+```bash
+gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+```
+
+**Release the lease** (remove the label) at every terminal state — merged,
+closed, or a hard block handed to a human. A crashed session that never
+releases is why the TTL exists; do not rely on it as the normal release path.
+
 ## 1. Enable auto-merge
 
 Before enabling auto-merge, capture the live PR head and compare it to
@@ -74,7 +111,8 @@ gh pr view <pr> --json state,mergeStateStatus,mergeable,reviewDecision,statusChe
 ```
 
 Handle every blocker class; after any fix, re-poll and continue. Do not stop while
-the PR is still open and progress is possible.
+the PR is still open and progress is possible. On each iteration, refresh the
+babysitter lease if its last stamp is older than ~30 minutes (section 0).
 
 In **`on_blocker=report`** mode, only the mechanical step (a) and auto-merge enabling
 apply; for any of (b)–(e) do not act — classify the blocker and return per the input
@@ -150,6 +188,16 @@ Some org rulesets allow 0 approvals yet a bot `CHANGES_REQUESTED` still blocks
 auto-merge — dismissing the stale review after resolving all threads is what
 unblocks it.
 
+### f. Pending auto-fix PR into this branch
+If an open PR from `claude-auto-fix-<headRefName>` targets this PR's head
+branch (the CI auto-fix workflow engaged before this session took the lease),
+adjudicate it: merge it into the head branch if the fix is correct and still
+needed, otherwise close it and delete the side branch. Never leave it dangling
+— it represents a competing writer's pending work. Merging it mutates the
+driven branch, so treat it like any other push: disarm auto-merge first,
+re-read `headRefOid`, reset `verify_commit` to the merged head, wait for that
+head's checks to start, then re-enable auto-merge (section 1).
+
 ## 3. Merge and verify it actually shipped (ancestry check)
 
 Enabling auto-merge + green checks + resolved threads is **not** proof the merge
@@ -177,3 +225,8 @@ Loop until one of:
   needs design input, or genuine unresolved human objection (not a bot gate). Stop
   and report exactly what is blocking and what was already tried — never force the
   merge or weaken a gate to get past it.
+
+At every terminal state, release the babysitter lease
+(`gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"`) so the CI
+auto-fix workflow can take over as fixer of last resort if the branch goes
+red later with nobody driving it.

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

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

package/plugins/lisa-copilot/skills/lisa-drive-pr-to-merge/SKILL.md

@@ -36,6 +36,43 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
 Resolve `<owner>/<repo>` from `gh repo view --json nameWithOwner` (or the PR URL).
 Use plain `gh` + `git` so Claude and Codex execute identically.
 
+## 0. Take the babysitter lease
+
+This skill is the branch's owner while it runs. Declare that ownership so the
+CI auto-fix workflow (`reusable-claude-ci-auto-fix.yml`) stands down instead of
+pushing competing fixes to the same branch (the single-writer rule):
+
+```bash
+gh label create "lisa:babysitter-on-duty" \
+  --description "A drive-pr-to-merge session is actively driving this PR; CI auto-fix must stand down" \
+  --color FBCA04 || true  # tolerate only already-exists; check the next step
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+gh pr view <pr> --json labels \
+  --jq '[.labels[].name] | contains(["lisa:babysitter-on-duty"])'
+```
+
+Verify the final command prints `true` before driving. If the label could not
+be attached (for example, no label-write permission), retry once; if it still
+fails, surface a warning that the branch is unleased — the CI auto-fix
+workflow may engage in parallel — and watch for its `claude-auto-fix-*` PR
+per section 2f while driving.
+
+The auto-fix workflow reads freshness from the label's most recent `labeled`
+timeline event and treats stamps older than its TTL (default 90 minutes) as
+stale. **Refresh the lease** whenever more than ~30 minutes have passed since
+the last stamp while the watch loop is still running — a refresh is a
+remove + re-add (re-adding an existing label does not create a new timeline
+event):
+
+```bash
+gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+```
+
+**Release the lease** (remove the label) at every terminal state — merged,
+closed, or a hard block handed to a human. A crashed session that never
+releases is why the TTL exists; do not rely on it as the normal release path.
+
 ## 1. Enable auto-merge
 
 Before enabling auto-merge, capture the live PR head and compare it to
@@ -74,7 +111,8 @@ gh pr view <pr> --json state,mergeStateStatus,mergeable,reviewDecision,statusChe
 ```
 
 Handle every blocker class; after any fix, re-poll and continue. Do not stop while
-the PR is still open and progress is possible.
+the PR is still open and progress is possible. On each iteration, refresh the
+babysitter lease if its last stamp is older than ~30 minutes (section 0).
 
 In **`on_blocker=report`** mode, only the mechanical step (a) and auto-merge enabling
 apply; for any of (b)–(e) do not act — classify the blocker and return per the input
@@ -150,6 +188,16 @@ Some org rulesets allow 0 approvals yet a bot `CHANGES_REQUESTED` still blocks
 auto-merge — dismissing the stale review after resolving all threads is what
 unblocks it.
 
+### f. Pending auto-fix PR into this branch
+If an open PR from `claude-auto-fix-<headRefName>` targets this PR's head
+branch (the CI auto-fix workflow engaged before this session took the lease),
+adjudicate it: merge it into the head branch if the fix is correct and still
+needed, otherwise close it and delete the side branch. Never leave it dangling
+— it represents a competing writer's pending work. Merging it mutates the
+driven branch, so treat it like any other push: disarm auto-merge first,
+re-read `headRefOid`, reset `verify_commit` to the merged head, wait for that
+head's checks to start, then re-enable auto-merge (section 1).
+
 ## 3. Merge and verify it actually shipped (ancestry check)
 
 Enabling auto-merge + green checks + resolved threads is **not** proof the merge
@@ -177,3 +225,8 @@ Loop until one of:
   needs design input, or genuine unresolved human objection (not a bot gate). Stop
   and report exactly what is blocking and what was already tried — never force the
   merge or weaken a gate to get past it.
+
+At every terminal state, release the babysitter lease
+(`gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"`) so the CI
+auto-fix workflow can take over as fixer of last resort if the branch goes
+red later with nobody driving it.

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

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

package/plugins/lisa-cursor/skills/lisa-drive-pr-to-merge/SKILL.md

@@ -36,6 +36,43 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
 Resolve `<owner>/<repo>` from `gh repo view --json nameWithOwner` (or the PR URL).
 Use plain `gh` + `git` so Claude and Codex execute identically.
 
+## 0. Take the babysitter lease
+
+This skill is the branch's owner while it runs. Declare that ownership so the
+CI auto-fix workflow (`reusable-claude-ci-auto-fix.yml`) stands down instead of
+pushing competing fixes to the same branch (the single-writer rule):
+
+```bash
+gh label create "lisa:babysitter-on-duty" \
+  --description "A drive-pr-to-merge session is actively driving this PR; CI auto-fix must stand down" \
+  --color FBCA04 || true  # tolerate only already-exists; check the next step
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+gh pr view <pr> --json labels \
+  --jq '[.labels[].name] | contains(["lisa:babysitter-on-duty"])'
+```
+
+Verify the final command prints `true` before driving. If the label could not
+be attached (for example, no label-write permission), retry once; if it still
+fails, surface a warning that the branch is unleased — the CI auto-fix
+workflow may engage in parallel — and watch for its `claude-auto-fix-*` PR
+per section 2f while driving.
+
+The auto-fix workflow reads freshness from the label's most recent `labeled`
+timeline event and treats stamps older than its TTL (default 90 minutes) as
+stale. **Refresh the lease** whenever more than ~30 minutes have passed since
+the last stamp while the watch loop is still running — a refresh is a
+remove + re-add (re-adding an existing label does not create a new timeline
+event):
+
+```bash
+gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+```
+
+**Release the lease** (remove the label) at every terminal state — merged,
+closed, or a hard block handed to a human. A crashed session that never
+releases is why the TTL exists; do not rely on it as the normal release path.
+
 ## 1. Enable auto-merge
 
 Before enabling auto-merge, capture the live PR head and compare it to
@@ -74,7 +111,8 @@ gh pr view <pr> --json state,mergeStateStatus,mergeable,reviewDecision,statusChe
 ```
 
 Handle every blocker class; after any fix, re-poll and continue. Do not stop while
-the PR is still open and progress is possible.
+the PR is still open and progress is possible. On each iteration, refresh the
+babysitter lease if its last stamp is older than ~30 minutes (section 0).
 
 In **`on_blocker=report`** mode, only the mechanical step (a) and auto-merge enabling
 apply; for any of (b)–(e) do not act — classify the blocker and return per the input
@@ -150,6 +188,16 @@ Some org rulesets allow 0 approvals yet a bot `CHANGES_REQUESTED` still blocks
 auto-merge — dismissing the stale review after resolving all threads is what
 unblocks it.
 
+### f. Pending auto-fix PR into this branch
+If an open PR from `claude-auto-fix-<headRefName>` targets this PR's head
+branch (the CI auto-fix workflow engaged before this session took the lease),
+adjudicate it: merge it into the head branch if the fix is correct and still
+needed, otherwise close it and delete the side branch. Never leave it dangling
+— it represents a competing writer's pending work. Merging it mutates the
+driven branch, so treat it like any other push: disarm auto-merge first,
+re-read `headRefOid`, reset `verify_commit` to the merged head, wait for that
+head's checks to start, then re-enable auto-merge (section 1).
+
 ## 3. Merge and verify it actually shipped (ancestry check)
 
 Enabling auto-merge + green checks + resolved threads is **not** proof the merge
@@ -177,3 +225,8 @@ Loop until one of:
   needs design input, or genuine unresolved human objection (not a bot gate). Stop
   and report exactly what is blocking and what was already tried — never force the
   merge or weaken a gate to get past it.
+
+At every terminal state, release the babysitter lease
+(`gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"`) so the CI
+auto-fix workflow can take over as fixer of last resort if the branch goes
+red later with nobody driving it.

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

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

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

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

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

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

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

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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.214.0",
+  "version": "2.216.0",
   "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-drive-pr-to-merge/SKILL.md

@@ -36,6 +36,43 @@ merges" loop. Other skills delegate here instead of re-implementing it. Runs
 Resolve `<owner>/<repo>` from `gh repo view --json nameWithOwner` (or the PR URL).
 Use plain `gh` + `git` so Claude and Codex execute identically.
 
+## 0. Take the babysitter lease
+
+This skill is the branch's owner while it runs. Declare that ownership so the
+CI auto-fix workflow (`reusable-claude-ci-auto-fix.yml`) stands down instead of
+pushing competing fixes to the same branch (the single-writer rule):
+
+```bash
+gh label create "lisa:babysitter-on-duty" \
+  --description "A drive-pr-to-merge session is actively driving this PR; CI auto-fix must stand down" \
+  --color FBCA04 || true  # tolerate only already-exists; check the next step
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+gh pr view <pr> --json labels \
+  --jq '[.labels[].name] | contains(["lisa:babysitter-on-duty"])'
+```
+
+Verify the final command prints `true` before driving. If the label could not
+be attached (for example, no label-write permission), retry once; if it still
+fails, surface a warning that the branch is unleased — the CI auto-fix
+workflow may engage in parallel — and watch for its `claude-auto-fix-*` PR
+per section 2f while driving.
+
+The auto-fix workflow reads freshness from the label's most recent `labeled`
+timeline event and treats stamps older than its TTL (default 90 minutes) as
+stale. **Refresh the lease** whenever more than ~30 minutes have passed since
+the last stamp while the watch loop is still running — a refresh is a
+remove + re-add (re-adding an existing label does not create a new timeline
+event):
+
+```bash
+gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"
+gh pr edit <pr> --add-label "lisa:babysitter-on-duty"
+```
+
+**Release the lease** (remove the label) at every terminal state — merged,
+closed, or a hard block handed to a human. A crashed session that never
+releases is why the TTL exists; do not rely on it as the normal release path.
+
 ## 1. Enable auto-merge
 
 Before enabling auto-merge, capture the live PR head and compare it to
@@ -74,7 +111,8 @@ gh pr view <pr> --json state,mergeStateStatus,mergeable,reviewDecision,statusChe
 ```
 
 Handle every blocker class; after any fix, re-poll and continue. Do not stop while
-the PR is still open and progress is possible.
+the PR is still open and progress is possible. On each iteration, refresh the
+babysitter lease if its last stamp is older than ~30 minutes (section 0).
 
 In **`on_blocker=report`** mode, only the mechanical step (a) and auto-merge enabling
 apply; for any of (b)–(e) do not act — classify the blocker and return per the input
@@ -150,6 +188,16 @@ Some org rulesets allow 0 approvals yet a bot `CHANGES_REQUESTED` still blocks
 auto-merge — dismissing the stale review after resolving all threads is what
 unblocks it.
 
+### f. Pending auto-fix PR into this branch
+If an open PR from `claude-auto-fix-<headRefName>` targets this PR's head
+branch (the CI auto-fix workflow engaged before this session took the lease),
+adjudicate it: merge it into the head branch if the fix is correct and still
+needed, otherwise close it and delete the side branch. Never leave it dangling
+— it represents a competing writer's pending work. Merging it mutates the
+driven branch, so treat it like any other push: disarm auto-merge first,
+re-read `headRefOid`, reset `verify_commit` to the merged head, wait for that
+head's checks to start, then re-enable auto-merge (section 1).
+
 ## 3. Merge and verify it actually shipped (ancestry check)
 
 Enabling auto-merge + green checks + resolved threads is **not** proof the merge
@@ -177,3 +225,8 @@ Loop until one of:
   needs design input, or genuine unresolved human objection (not a bot gate). Stop
   and report exactly what is blocking and what was already tried — never force the
   merge or weaken a gate to get past it.
+
+At every terminal state, release the babysitter lease
+(`gh pr edit <pr> --remove-label "lisa:babysitter-on-duty"`) so the CI
+auto-fix workflow can take over as fixer of last resort if the branch goes
+red later with nobody driving it.

package/typescript/copy-overwrite/.github/GITHUB_ACTIONS.md

@@ -174,12 +174,16 @@ AI-powered code assistance that can:
 
 **Triggers**: CI Quality Checks workflow failure (non-environment branches)
 
-Automatically fixes CI failures by having Claude analyze error logs and push fixes. Replaces the previous `create-issue-on-failure` workflow.
+Fixer of last resort for red CI on unattended branches: Claude analyzes error logs and prepares a fix as a pull request into the failing branch.
 
+- Stands down when the branch has an active owner: a fresh `lisa:babysitter-on-duty` lease label on the branch's open PR (stamped by drive-pr-to-merge sessions), or any push during a quiet-period wait (default 20 minutes)
 - Fetches failed job names and error logs from the CI run
 - Runs Claude with full context to diagnose and fix the root cause
-- Commits and pushes the fix to the failing branch
-- Skips environment branches (`main`, `staging`, `dev`) and auto-fix branches (prevents infinite loops)
+- Never pushes to the failing branch — commits land on a `claude-auto-fix-<branch>` side branch and a PR is opened into the failing branch
+- Falls back to a non-frozen dependency install when the lockfile itself is broken, so Claude can repair and commit the lockfile
+- When no fix can be produced, files a deduplicated ticket in the tracker declared in `.lisa.config.json` (`tracker`: jira | github | linear) with a title that says whether Claude ran at all
+- Skips environment branches (`main`, `staging`, `dev`) and auto-fix branches (prevents infinite loops); failing checks on an auto-fix PR escalate to a ticket instead of re-entering
+- Requires `secrets: inherit` in the caller so tracker credentials (`JIRA_API_TOKEN` / `LINEAR_API_KEY`) reach the issue dispatcher
 
 ### Claude Code Review Response (`claude-code-review-response.yml`)
 

package/typescript/create-only/.github/workflows/claude-ci-auto-fix.yml

@@ -25,5 +25,9 @@ jobs:
       head_branch: ${{ github.event.workflow_run.head_branch }}
       run_id: ${{ github.event.workflow_run.id }}
       package_manager: 'bun'
-    secrets:
-      CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+    # `secrets: inherit` (not an explicit mapping) is load-bearing: the
+    # reusable workflow forwards secrets to the issue dispatcher, which needs
+    # JIRA_API_TOKEN / LINEAR_API_KEY to file failure tickets in the tracker
+    # declared in .lisa.config.json. An explicit CLAUDE_CODE_OAUTH_TOKEN-only
+    # mapping silently strands those tickets in GitHub Issues.
+    secrets: inherit

package/typescript/create-only/.github/workflows/claude-deploy-auto-fix.yml

@@ -25,5 +25,7 @@ jobs:
       head_branch: ${{ github.event.workflow_run.head_branch }}
       run_id: ${{ github.event.workflow_run.id }}
       package_manager: 'bun'
-    secrets:
-      CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+    # `secrets: inherit` (not an explicit mapping) is load-bearing: the
+    # reusable workflow needs tracker credentials (JIRA_API_TOKEN /
+    # LINEAR_API_KEY) to reach the tracker declared in .lisa.config.json.
+    secrets: inherit