@codyswann/lisa 2.290.0 → 2.291.0

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

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

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

@@ -86,4 +86,12 @@ A non-integration environment bug is fixed, merged, and verified on that
 environment branch first, then
 forward cherry-picked down to the integration branch via a linked follow-up.
 
+## Deploy status sync
+
+`deployStatusSync` is an optional machine-written config block (`tier`, `provisioned` ids,
+`linearBinding: labels|states`, `verifiedAt`). The deploy ladder is `deploy.order` (else canonical
+`dev < staging < production`) over `deploy.branches` joined with the tracker's env-keyed done map;
+a configured done status whose env has no branch is a config error, and the sole
+`prod` ↔ `production` alias applies to the join.
+
 Full reference: [reference/config-resolution.md](../reference/config-resolution.md).

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

@@ -596,6 +596,53 @@ This is the same `deploy.branches` map already used by env-keyed `done` (reverse
 env from PR base branch) and the build flow (forward: base branch from env);
 `deploy.order` only adds the ranking those two directions never needed.
 
+### Deploy status sync (deployStatusSync)
+
+`deployStatusSync` is an **optional, machine-written** section recorded by the
+deploy-status-sync setup flow. Humans never need to author it; unknown fields
+inside it are preserved on round-trip.
+
+| Field | Type | Default | Meaning |
+| --- | --- | --- | --- |
+| `tier` | string | — | Provisioning tier chosen at setup time |
+| `provisioned` | object (string → string) | — | Provisioned tracker artifact ids, keyed by artifact name |
+| `linearBinding` | `"labels"` \| `"states"` | — | Whether Linear deploy statuses are represented as labels or workflow states |
+| `verifiedAt` | string | — | Strict ISO-8601 UTC timestamp (`Z` suffix, e.g. `2026-01-01T00:00:00Z`) of the last successful verification |
+
+**Ladder resolution.** The environment universe is the keys of
+`deploy.branches`. Each env's done status comes from the tracker's env-keyed
+done map — `github.labels.build.done`, `linear.labels.build.done`, or
+`jira.workflow.done` — with configured entries winning over the built-in
+defaults (`status:on-dev` / `status:on-stg` / `status:done` for label trackers;
+`On Dev` / `On Stg` / `Done` for JIRA). Environments are ordered by
+`deploy.order` when present (its env-name set must exactly match the keys of
+`deploy.branches`); otherwise by the canonical `dev < staging < production`
+rank, and an unrankable custom env name with more than one env configured is a
+config error rather than a guess. A string-valued `done` binds only the
+terminal (highest) rung; lower rungs fall back to the default table. An env
+with a branch but no done status anywhere (possible only for custom names
+outside the default tables) is **skipped**, not an error; an explicitly
+configured done status whose env has no branch **is** a config error. A ladder
+is flagged terminal-only when it resolves to exactly one rung **and** that
+rung's env is the highest-ranked environment of the configured universe
+(post-alias) — a sole surviving lower rung after skips is NOT terminal-only,
+so downstream native closure never fires on an intermediate environment.
+Absent or empty `deploy` yields an empty ladder, never an error.
+
+**Alias.** Iff exactly one of `prod` / `production` appears across the
+configured surfaces (`deploy.branches`, the configured done map,
+`deploy.order`), the two spellings join as one environment — so
+`branches.prod` meets the default `done.production` — and rungs report the
+configured spelling. When both spellings appear they are distinct environments
+and no aliasing occurs. No other alias exists.
+
+**Error catalog** (verbatim):
+
+- `Invalid deploy configuration in <source>: a done status ("<status>") is configured for environment "<env>", but deploy.branches has no "<env>" entry. Add deploy.branches.<env> (the git branch that deploys to <env>) or remove "<env>" from the done map.`
+- `Invalid deploy.order in <source>: its environment names must exactly match the keys of deploy.branches. deploy.order has [<order-envs>]; deploy.branches has [<branch-envs>].` (also raised for duplicate `deploy.order` entries)
+- `Invalid deploy.order in <source>: every entry must be an environment name string; found <entry>.`
+- `Invalid deploy configuration in <source>: cannot order environment "<env>". Set deploy.order (environments listed lowest first, e.g. ["dev","staging","production"]) so Lisa knows the promotion order.`
+
 ### What's configurable, what's not
 
 - **Status / label NAMES** are configurable per project — that's the point of the vocabulary maps.