@codyswann/lisa 2.258.0 → 2.258.1

package/package.json

@@ -102,7 +102,7 @@
     "form-data": ">=4.0.6"
   },
   "name": "@codyswann/lisa",
-  "version": "2.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "description": "Universal governance: agents, skills, commands, hooks, and rules for all projects.",
   "author": {
     "name": "Cody Swann"

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

@@ -198,11 +198,16 @@ One line each; expand them into the operator's voice, keep the meaning.
 **Retirement condition is mandatory and non-empty.** Every seeded runbook states one, and a loop
 that is structurally permanent says exactly that instead of leaving the section blank — an operator
 reading it aloud must be able to say when this loop should stop existing, or that it never should.
-A valid condition is **stateless**: derived from the tracker, and **never an ad-hoc counter**, a new
-state file, or bounded run-history record. The mechanism itself — the two-part test, the single
-marker-deduped teardown proposal, and the
-three operator responses — is defined once in the `automation-runbook-contract` rule; these seeds
-only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
+A valid condition is **stateless**: derived from the tracker, or from the loop's own bounded run
+history at `.lisa/automations/runs/<loop-id>.jsonl` — written by the contract's own recorder, not
+private per-loop state — and **never an ad-hoc counter** or a new state file. Those two sources are
+the same discipline, not a loosening of the contract's "never from a counter or a state file": the
+run history is written and bounded by `automation-run-record.mjs`, is readable by any run on any
+machine, and is never invented per loop. What the contract forbids is a loop minting private state
+to remember itself by. Prefer the tracker; reach for the run history only when the tracker cannot
+answer the question. The mechanism itself — the two-part test, the single marker-deduped teardown
+proposal, and the three operator responses — is defined once in the `automation-runbook-contract`
+rule; these seeds only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
 two-part test — an extra AND that must also hold — because an additional conjunct is strictly
 tighter and never divergent. It may never drop or weaken either of the contract's two conditions.
 Silence alone means obsolescence only for the gardener; for a monitoring or exploratory loop a quiet

package/plugins/lisa/skills/lisa-setup-automations/SKILL.md

@@ -198,11 +198,16 @@ One line each; expand them into the operator's voice, keep the meaning.
 **Retirement condition is mandatory and non-empty.** Every seeded runbook states one, and a loop
 that is structurally permanent says exactly that instead of leaving the section blank — an operator
 reading it aloud must be able to say when this loop should stop existing, or that it never should.
-A valid condition is **stateless**: derived from the tracker, and **never an ad-hoc counter**, a new
-state file, or bounded run-history record. The mechanism itself — the two-part test, the single
-marker-deduped teardown proposal, and the
-three operator responses — is defined once in the `automation-runbook-contract` rule; these seeds
-only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
+A valid condition is **stateless**: derived from the tracker, or from the loop's own bounded run
+history at `.lisa/automations/runs/<loop-id>.jsonl` — written by the contract's own recorder, not
+private per-loop state — and **never an ad-hoc counter** or a new state file. Those two sources are
+the same discipline, not a loosening of the contract's "never from a counter or a state file": the
+run history is written and bounded by `automation-run-record.mjs`, is readable by any run on any
+machine, and is never invented per loop. What the contract forbids is a loop minting private state
+to remember itself by. Prefer the tracker; reach for the run history only when the tracker cannot
+answer the question. The mechanism itself — the two-part test, the single marker-deduped teardown
+proposal, and the three operator responses — is defined once in the `automation-runbook-contract`
+rule; these seeds only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
 two-part test — an extra AND that must also hold — because an additional conjunct is strictly
 tighter and never divergent. It may never drop or weaken either of the contract's two conditions.
 Silence alone means obsolescence only for the gardener; for a monitoring or exploratory loop a quiet

package/plugins/lisa-agy/plugin.json

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

package/plugins/lisa-agy/skills/lisa-setup-automations/SKILL.md

@@ -198,11 +198,16 @@ One line each; expand them into the operator's voice, keep the meaning.
 **Retirement condition is mandatory and non-empty.** Every seeded runbook states one, and a loop
 that is structurally permanent says exactly that instead of leaving the section blank — an operator
 reading it aloud must be able to say when this loop should stop existing, or that it never should.
-A valid condition is **stateless**: derived from the tracker, and **never an ad-hoc counter**, a new
-state file, or bounded run-history record. The mechanism itself — the two-part test, the single
-marker-deduped teardown proposal, and the
-three operator responses — is defined once in the `automation-runbook-contract` rule; these seeds
-only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
+A valid condition is **stateless**: derived from the tracker, or from the loop's own bounded run
+history at `.lisa/automations/runs/<loop-id>.jsonl` — written by the contract's own recorder, not
+private per-loop state — and **never an ad-hoc counter** or a new state file. Those two sources are
+the same discipline, not a loosening of the contract's "never from a counter or a state file": the
+run history is written and bounded by `automation-run-record.mjs`, is readable by any run on any
+machine, and is never invented per loop. What the contract forbids is a loop minting private state
+to remember itself by. Prefer the tracker; reach for the run history only when the tracker cannot
+answer the question. The mechanism itself — the two-part test, the single marker-deduped teardown
+proposal, and the three operator responses — is defined once in the `automation-runbook-contract`
+rule; these seeds only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
 two-part test — an extra AND that must also hold — because an additional conjunct is strictly
 tighter and never divergent. It may never drop or weaken either of the contract's two conditions.
 Silence alone means obsolescence only for the gardener; for a monitoring or exploratory loop a quiet

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

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

package/plugins/lisa-copilot/skills/lisa-setup-automations/SKILL.md

@@ -198,11 +198,16 @@ One line each; expand them into the operator's voice, keep the meaning.
 **Retirement condition is mandatory and non-empty.** Every seeded runbook states one, and a loop
 that is structurally permanent says exactly that instead of leaving the section blank — an operator
 reading it aloud must be able to say when this loop should stop existing, or that it never should.
-A valid condition is **stateless**: derived from the tracker, and **never an ad-hoc counter**, a new
-state file, or bounded run-history record. The mechanism itself — the two-part test, the single
-marker-deduped teardown proposal, and the
-three operator responses — is defined once in the `automation-runbook-contract` rule; these seeds
-only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
+A valid condition is **stateless**: derived from the tracker, or from the loop's own bounded run
+history at `.lisa/automations/runs/<loop-id>.jsonl` — written by the contract's own recorder, not
+private per-loop state — and **never an ad-hoc counter** or a new state file. Those two sources are
+the same discipline, not a loosening of the contract's "never from a counter or a state file": the
+run history is written and bounded by `automation-run-record.mjs`, is readable by any run on any
+machine, and is never invented per loop. What the contract forbids is a loop minting private state
+to remember itself by. Prefer the tracker; reach for the run history only when the tracker cannot
+answer the question. The mechanism itself — the two-part test, the single marker-deduped teardown
+proposal, and the three operator responses — is defined once in the `automation-runbook-contract`
+rule; these seeds only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
 two-part test — an extra AND that must also hold — because an additional conjunct is strictly
 tighter and never divergent. It may never drop or weaken either of the contract's two conditions.
 Silence alone means obsolescence only for the gardener; for a monitoring or exploratory loop a quiet

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

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

package/plugins/lisa-cursor/skills/lisa-setup-automations/SKILL.md

@@ -198,11 +198,16 @@ One line each; expand them into the operator's voice, keep the meaning.
 **Retirement condition is mandatory and non-empty.** Every seeded runbook states one, and a loop
 that is structurally permanent says exactly that instead of leaving the section blank — an operator
 reading it aloud must be able to say when this loop should stop existing, or that it never should.
-A valid condition is **stateless**: derived from the tracker, and **never an ad-hoc counter**, a new
-state file, or bounded run-history record. The mechanism itself — the two-part test, the single
-marker-deduped teardown proposal, and the
-three operator responses — is defined once in the `automation-runbook-contract` rule; these seeds
-only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
+A valid condition is **stateless**: derived from the tracker, or from the loop's own bounded run
+history at `.lisa/automations/runs/<loop-id>.jsonl` — written by the contract's own recorder, not
+private per-loop state — and **never an ad-hoc counter** or a new state file. Those two sources are
+the same discipline, not a loosening of the contract's "never from a counter or a state file": the
+run history is written and bounded by `automation-run-record.mjs`, is readable by any run on any
+machine, and is never invented per loop. What the contract forbids is a loop minting private state
+to remember itself by. Prefer the tracker; reach for the run history only when the tracker cannot
+answer the question. The mechanism itself — the two-part test, the single marker-deduped teardown
+proposal, and the three operator responses — is defined once in the `automation-runbook-contract`
+rule; these seeds only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
 two-part test — an extra AND that must also hold — because an additional conjunct is strictly
 tighter and never divergent. It may never drop or weaken either of the contract's two conditions.
 Silence alone means obsolescence only for the gardener; for a monitoring or exploratory loop a quiet

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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.258.0",
+  "version": "2.258.1",
   "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

@@ -198,11 +198,16 @@ One line each; expand them into the operator's voice, keep the meaning.
 **Retirement condition is mandatory and non-empty.** Every seeded runbook states one, and a loop
 that is structurally permanent says exactly that instead of leaving the section blank — an operator
 reading it aloud must be able to say when this loop should stop existing, or that it never should.
-A valid condition is **stateless**: derived from the tracker, and **never an ad-hoc counter**, a new
-state file, or bounded run-history record. The mechanism itself — the two-part test, the single
-marker-deduped teardown proposal, and the
-three operator responses — is defined once in the `automation-runbook-contract` rule; these seeds
-only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
+A valid condition is **stateless**: derived from the tracker, or from the loop's own bounded run
+history at `.lisa/automations/runs/<loop-id>.jsonl` — written by the contract's own recorder, not
+private per-loop state — and **never an ad-hoc counter** or a new state file. Those two sources are
+the same discipline, not a loosening of the contract's "never from a counter or a state file": the
+run history is written and bounded by `automation-run-record.mjs`, is readable by any run on any
+machine, and is never invented per loop. What the contract forbids is a loop minting private state
+to remember itself by. Prefer the tracker; reach for the run history only when the tracker cannot
+answer the question. The mechanism itself — the two-part test, the single marker-deduped teardown
+proposal, and the three operator responses — is defined once in the `automation-runbook-contract`
+rule; these seeds only fill in each loop's specifics. A seed may add a **domain conjunct** on top of the contract's
 two-part test — an extra AND that must also hold — because an additional conjunct is strictly
 tighter and never divergent. It may never drop or weaken either of the contract's two conditions.
 Silence alone means obsolescence only for the gardener; for a monitoring or exploratory loop a quiet