Lisa Update Projects

Lisa Update Projects

Updates local Lisa projects in batches by running the package manager update command for @codyswann/lisa in each configured project, which triggers Lisa's postinstall script to apply template changes automatically.

Instructions

1. Read @.lisa.config.local.json to get the list of projects and their target branches.
2. For each project directory, checkout the target branch and pull the latest from the remote.
3. If you can't because of existing changes or a dirty worktree, don't do anything. Ask the human what should be done about it before moving on.
4. Once you have resolution, within each clean project, check out a new branch (e.g. chore/lisa-update-YYYY-MM-DD).
5. Check if @codyswann/lisa is in the project's trustedDependencies array in package.json. If missing, add it using jq. Bun only runs postinstall scripts for trusted packages, so without this entry Lisa's postinstall (template application and file deletions) is silently skipped.
6. Determine the project's package manager from package.json engines BEFORE choosing a command. The engines field is authoritative — lockfile presence is not.
   • Read engines with jq -r '.engines // {}' package.json.
   • If engines.bun === "please-use-npm" (or engines.yarn / engines.pnpm use the same sentinel), that package manager is forbidden. Use npm.
   • If a forbidden lockfile exists anyway (e.g., bun.lockb in a project where engines.bun === "please-use-npm"), it is rogue — bun ignores the engines string and writes the lockfile if invoked. Delete it (git rm bun.lockb) and include the deletion in the commit.
   • Pick the update command from the surviving package manager:
     • bun.lockb exists and bun is allowed → bun add -D @codyswann/lisa@latest (use bun add -D <pkg>@latest, not bun update <pkg>. bun update only walks within the existing semver range, so an exact-pinned 1.95.0 or a caret-pinned ^1.95.0 against a new major like 2.x is a no-op. bun add -D <pkg>@latest always resolves to the latest published version and rewrites the manifest.)
     • otherwise → npm install -D @codyswann/lisa@latest (use install -D not update; npm update only bumps within the existing semver range and won't move pinned versions or update the manifest)
   • Bun's postinstall and npm's both run only the reduced postinstall-safe apply, which skips every agent emit and the Sonar integration — they declare it with LISA_POSTINSTALL=1, the only thing that selects that mode (CodySwannGT/lisa#3066). Commit the install first, then apply in full: LISA_BOOTSTRAP=1 node node_modules/@codyswann/lisa/dist/index.js --yes .. Verify .lisa/apply-receipt.json records "apply_mode": "full".
   • Never run both bun add and npm install against the same project. That perpetuates the dual-lockfile bug. Pick one based on the engines field and stick to it.
7. After updating, check if @codyswann/lisa appears in the project's dependencies (not devDependencies). If so, move it: remove from dependencies and ensure it's in devDependencies. Use jq to check and the package manager to reinstall correctly.
8. Check for legacy inline Codex workflows that need migration. For each file in .github/workflows/ matching Codex*.yml, Codex*.yaml, ci.yml, ci.yaml, deploy.yml, and deploy.yaml:
   • If the workflow has inline steps: blocks instead of calling uses: CodySwannGT/lisa/.github/workflows/reusable-*.yml@main, it is legacy.
   • Detect project capabilities independently (Rails: has bin/rails or config/application.rb; TypeScript: has tsconfig.json or package.json with TypeScript signals). A repo may be both.
   • Apply per-file mapping rules — not a single repo-wide template selection — so dual-stack repos get the correct template for each workflow file:
     • ci.yml/ci.yaml in a Rails project → rails/create-only/.github/workflows/ci.yml (calls quality-rails.yml@main)
     • deploy.yml/deploy.yaml in a Rails project → rails/create-only/.github/workflows/deploy.yml (calls release-rails.yml@main)
     • ci.yml/ci.yaml in a TypeScript-only project → typescript/create-only/.github/workflows/ci.yml (calls quality.yml@main)
     • Codex*.yml/Codex*.yaml → typescript/create-only/.github/workflows/ (e.g., Codex.yml → reusable-Codex.yml@main, Codex-ci-auto-fix.yml → reusable-Codex-ci-auto-fix.yml@main)
     • auto-update-pr-branches.yml/auto-update-pr-branches-dispatch.yml → no template; do not migrate. The auto-update-PR-branches subsystem was removed (CodySwannGT/lisa#3590) and both paths are listed in typescript/deletions.json, so the apply deletes them. If one survives an apply, that is a bug — report it rather than re-creating the workflow by hand.
   • The create-only templates are the source of truth for the correct caller format.
   • A caller that already correctly uses uses: CodySwannGT/lisa/.github/workflows/reusable-*.yml@main is NOT automatically clean — its with: block can still carry an input the reusable workflow's current contract no longer declares (e.g. an early-generation claude.yml still passing package_manager, which reusable-claude.yml historically did not accept — issue #1423). GitHub hard-fails such a run at startup, and because create-only workflow files are not overwritten automatically the repo can never self-heal on its own. Run node scripts/detect-stale-workflow-inputs.mjs --project <project> --json (from the Lisa repo checkout) against the project to catch this: it diffs each caller's with: keys against the corresponding reusable-*.yml's declared workflow_call.inputs in this repo's .github/workflows/. For every row reported "status": "stale", remove just the listed staleInputs key(s) from the caller's with: block (this is a contract-breaking-input migration, not a customization edit, so it's in scope even though the file is otherwise create-only) — do not otherwise touch the file. A "status": "unknown-contract" row means the caller references a reusable workflow this repo doesn't have a file for; leave it and flag for human review rather than guessing.
9. Remove stale file: references to bundled ESLint plugins from the project's package.json. Previous Lisa versions copied plugin directories and added file:./ dependencies; current Lisa deletes the directories but the package.json references remain. Use jq to remove these keys from both dependencies and devDependencies if they exist:
   • eslint-plugin-code-organization
   • eslint-plugin-component-structure
   • eslint-plugin-ui-standards
10. Remove stale $CLAUDE_PROJECT_DIR/.Codex/hooks/ references from the project's .Codex/settings.json. Previous Lisa versions installed hook scripts into the project's .Codex/hooks/ directory and registered them in .Codex/settings.json. Current Lisa deletes these scripts via all/deletions.json and provides them through the plugin system (${CLAUDE_PLUGIN_ROOT}/hooks/ in plugin.json) instead. The settings.json references to the deleted scripts cause "No such file or directory" errors. Use jq to:

• Remove any hook entry objects where the command contains $CLAUDE_PROJECT_DIR/.Codex/hooks/
• Remove entire hook matcher blocks that become empty after removing those entries
• Remove entire hook category arrays that have no remaining matcher blocks
• Preserve all non-file-path hook entries (inline commands like echo ..., command -v entire ..., etc.)

11. Update create-only workflow schedules that have drifted from the current templates. For each create-only workflow in .github/workflows/ (e.g., Codex-nightly-jira-triage.yml), compare the cron schedule against the corresponding template in typescript/create-only/.github/workflows/ (or rails/create-only/ for Rails projects) in the Lisa repo. If the project's schedule differs from the template, update it to match. For example, if the template uses 0 */2 * * * but the project still has 0 6 * * 1-5, update the project file.
12. Check git diff to see if the project changed any Lisa-managed files. If so, examine them to see if any changes need to be upstreamed back to Lisa and do so if necessary.
13. Commit, push, and PR the branch to the project's target branch specified in @.lisa.config.local.json.
14. If you hit any pre-push blockers, fix them and upstream anything that needs to. Do not lower any thresholds to get around a pre-push block. Instead, fix the code.

For steps 4-13, use up to 4 parallel subagents to accomplish those steps.

Fixing Upstream Bugs

If the Lisa postinstall crashes, rolls back changes, or applies incorrect templates during a project update, do not just work around it in the downstream project. Instead:

1. Diagnose the root cause in the Lisa source code at the current working directory.
2. Fix the bug in Lisa (create a branch, commit, push, and open a PR).
3. Wait for the fix to merge and release before continuing project updates, OR apply the workaround in downstream projects only as a temporary measure while the upstream fix is in flight.

Common symptoms that indicate an upstream Lisa bug:

• Postinstall crashes with errors (e.g., missing function, module resolution failures)
• Templates from a parent stack (typescript) overwriting child stack templates (expo, nestjs, cdk) — this means the postinstall crashed after applying parent templates but before child templates could override them, triggering a rollback
• Rollback messages in the postinstall output ([WARN] Rolling back changes...) followed by an error
• Files that should be stack-specific (eslint.config.ts, tsconfig.json, knip.json) containing generic TypeScript config instead of the expected child stack config

The goal is to fix bugs at the source so they don't recur on every future update across all projects.