@codyswann/lisa 4.27.4 → 4.27.6

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

@@ -127,8 +127,15 @@ source-only work downward.
 If residue remains after applying the appropriate pattern, abort that hop and
 report the unresolved files and the evidence gathered. Do not silently choose
 source-wins when the target may already contain the change or has moved the code.
-5. **Push** the sync branch: `git push -u origin sync/<source>-to-<target> --force-with-lease`.
+5. **Push** the sync branch with a fully qualified destination refspec:
+   `git push origin sync/<source>-to-<target>:refs/heads/sync/<source>-to-<target> --force-with-lease`.
    Only ever force-push the sync branch — never the target environment branch.
+   The refspec is not decoration. `push -u origin <branch>` names only a
+   source, so git resolves the destination from the branch's upstream; where
+   `push.default` is `upstream` and the sync branch was created from the
+   target, that resolves to the TARGET ENVIRONMENT BRANCH and a force-push
+   lands there (CodySwannGT/lisa#3495). Naming the destination in full is
+   what makes the sentence above enforceable rather than advisory.
 6. **Open or update the PR.** Check for an existing open PR
    (`gh pr list --head sync/<source>-to-<target> --base <target> --state open`).
    Update its body if it exists, otherwise create it

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "4.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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.27.4",
+  "version": "4.27.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-automations/SKILL.md

@@ -207,6 +207,29 @@ project: the per-check marker dedupe converges under a single scheduled runner,
 and two concurrent runs can both observe an empty open-ticket set and both
 file. Tear-down removes it with the rest of the `lisa-auto-<project>-*` set.
 
+**Optional automation — the fleet enforcement census.** Register
+`lisa-auto-<project>-enforcement-census` running `/lisa:enforcement-census`
+once a **day** only when BOTH are true of the repository being set up: it
+maintains a fleet roster (`.lisa.workspaces.json`, the machine-local list of
+host checkouts), and it provides the `/lisa:enforcement-census` command. Both
+hold in the Lisa monorepo and in no ordinary host project, which is the point —
+the census measures OTHER checkouts on the same machine, so only the workstation
+holding the roster has a fleet to measure. Where either is absent, register
+nothing — a host project has no fleet, and scheduling a command it does not
+have would be a loop that fails every night — and report the census as SKIPPED
+naming which prerequisite was missing, per the report contract. Registering
+nothing is correct; omitting it from the report is not, because a silently
+absent loop is indistinguishable from one that was never asked for.
+
+It **reports and never gates**: no finding about the fleet changes an exit
+status, and no run files a ticket. Enforcement resolves from the checkout an
+agent is working in, so a checkout resolving no guard is protected by nothing
+while looking identical, from inside a session, to one protected by an old
+policy — and nothing was re-measuring that (CodySwannGT/lisa#3490). The
+per-checkout half of the same finding is carried by `lisa doctor`, which every
+host does get. Tear-down removes it with the rest of the `lisa-auto-<project>-*`
+set.
+
 **Exploratory PRD pressure gate.** `auto-start-prds=true` means "create PRDs in the ready PRD
 lifecycle when the PRD queue has capacity," not "always create a new ready PRD." The
 `exploratory-prds` automation uses the same PRD source queue and pressure roles reported by

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

@@ -127,8 +127,15 @@ source-only work downward.
 If residue remains after applying the appropriate pattern, abort that hop and
 report the unresolved files and the evidence gathered. Do not silently choose
 source-wins when the target may already contain the change or has moved the code.
-5. **Push** the sync branch: `git push -u origin sync/<source>-to-<target> --force-with-lease`.
+5. **Push** the sync branch with a fully qualified destination refspec:
+   `git push origin sync/<source>-to-<target>:refs/heads/sync/<source>-to-<target> --force-with-lease`.
    Only ever force-push the sync branch — never the target environment branch.
+   The refspec is not decoration. `push -u origin <branch>` names only a
+   source, so git resolves the destination from the branch's upstream; where
+   `push.default` is `upstream` and the sync branch was created from the
+   target, that resolves to the TARGET ENVIRONMENT BRANCH and a force-push
+   lands there (CodySwannGT/lisa#3495). Naming the destination in full is
+   what makes the sentence above enforceable rather than advisory.
 6. **Open or update the PR.** Check for an existing open PR
    (`gh pr list --head sync/<source>-to-<target> --base <target> --state open`).
    Update its body if it exists, otherwise create it

package/scripts/lisa-commit-and-pr-local.sh

@@ -148,9 +148,18 @@ while IFS=$'\t' read -r project_path target_branch; do
     continue
   fi
 
-  # Create branch
+  # Create branch.
+  #
+  # `--no-track` is load-bearing, not tidiness. Without it the new branch
+  # inherits "$target_branch" as its upstream, and in any repository where
+  # push.default is "upstream" or "tracking" git resolves a push's destination
+  # from that upstream rather than from the branch name — so the push below
+  # would land on the environment branch itself, bypassing branch protection
+  # and every required check, while reporting success (CodySwannGT/lisa#3495).
+  # This script runs across a whole fleet of repositories at once, so it cannot
+  # assume any one of them has a safe push.default.
   log_info "Creating branch: $branch_name"
-  if ! git -C "$expanded_path" checkout -b "$branch_name" "$target_branch" 2>&1; then
+  if ! git -C "$expanded_path" switch -c "$branch_name" --no-track "$target_branch" 2>&1; then
     log_error "Failed to create branch $branch_name in $expanded_path"
     ((fail_count++)) || true
     continue
@@ -169,17 +178,24 @@ while IFS=$'\t' read -r project_path target_branch; do
     continue
   fi
 
-  # Push
+  # Push with a FULLY QUALIFIED destination refspec. `push -u origin <branch>`
+  # names only a source, which leaves the destination for push.default to
+  # resolve; `<branch>:refs/heads/<branch>` states it, so no config can move it.
+  # Belt and braces with --no-track above: either alone closes the hole, and
+  # this script has no way to verify which of them a given host repository
+  # needed.
   log_info "Pushing to origin/$branch_name..."
-  if ! GIT_SSH_COMMAND="ssh -o ServerAliveInterval=30 -o ServerAliveCountMax=5" git -C "$expanded_path" push -u origin "$branch_name" 2>&1; then
+  if ! GIT_SSH_COMMAND="ssh -o ServerAliveInterval=30 -o ServerAliveCountMax=5" git -C "$expanded_path" push origin "$branch_name:refs/heads/$branch_name" 2>&1; then
     log_error "Failed to push $branch_name in $expanded_path"
     ((fail_count++)) || true
     continue
   fi
 
-  # Create PR
+  # Create PR. `--head` is explicit because the push above deliberately does not
+  # set an upstream, and without one `gh` would fall back to guessing (or
+  # prompting for) the head branch.
   log_info "Creating pull request..."
-  if ! (cd "$expanded_path" && gh pr create --title "chore: update Lisa configuration" --base "$target_branch" --body "Automated Lisa configuration update applied on $DATE_STAMP."); then
+  if ! (cd "$expanded_path" && gh pr create --title "chore: update Lisa configuration" --base "$target_branch" --head "$branch_name" --body "Automated Lisa configuration update applied on $DATE_STAMP."); then
     log_error "Failed to create PR for $expanded_path"
     ((fail_count++)) || true
     continue