@codyswann/lisa 4.64.9 → 4.65.0

package/dist/core/nightly-e2e-guard-behavior-certificate.js

@@ -48,9 +48,9 @@ export const NIGHTLY_E2E_GUARD_BEHAVIOR_CERTIFICATES = Object.freeze({
     }),
     f87e6eee47ddb6416f2c639b79b96a68173c9c562999fbad98abe012ac913d28: Object.freeze({
         contractVersion: "1.9.0",
-        packageVersions: Object.freeze(["4.64.9"]),
+        packageVersions: Object.freeze(["4.65.0"]),
         provenances: Object.freeze([
-            "workspace package @codyswann/lisa@4.64.9 (typescript/copy-overwrite/scripts/check-nightly-e2e-health.mjs)",
+            "workspace package @codyswann/lisa@4.65.0 (typescript/copy-overwrite/scripts/check-nightly-e2e-health.mjs)",
         ]),
     }),
 });

package/dist/core/upstream-evidence-manifest.js

@@ -446,7 +446,7 @@ export const UPSTREAM_EVIDENCE_MANIFEST = Object.freeze({
     "plugins/src/base/rules/eager/operational-hazards.md": "9acb3b13a6b3f7d993c7fc37cf70fa94947119c4d59e6295217cafe9f13c6c58",
     "plugins/src/base/rules/eager/report-actionability.md": "b817c042d834fb046ead75db19cf827322b1abfbb0886fd4545213dd68a80554",
     "plugins/src/base/rules/eager/security-audit-handling.md": "1f6effe92be66736a0c9fab634c5fdd6ad1e789865faa67bb783c67ddb4ad490",
-    "plugins/src/base/rules/eager/session-status-updates.md": "bbb42e86b8eb68334b8b9c0bc70beb4895a54015e097bf745fc92156b3e24766",
+    "plugins/src/base/rules/eager/session-status-updates.md": "d2d657eda85ce00c3c0699e1c32bc0080df1140b940f9271800f233953f91b4c",
     "plugins/src/base/rules/eager/settled-decisions.md": "ae1e8d1292db266038af41d9313708a3fba437c036de043ec6b0311418b56017",
     "plugins/src/base/rules/eager/stale-state-claims.md": "faf5057f5910237b8d5048dbcccb73e0cd03762a8eefbeae43b5d0153104a85a",
     "plugins/src/base/rules/eager/tool-access-gate.md": "854eb5b16a8e0f51fe7caa0517c10d1ec5ded5ca7324c8304beddc7b81befcf2",
@@ -502,7 +502,7 @@ export const UPSTREAM_EVIDENCE_MANIFEST = Object.freeze({
     "plugins/src/base/rules/reference/report-actionability.md": "42fa86bb189467c7bc7ee64f6ebccd3926bb2aaf512ee5a498c232025b8a364b",
     "plugins/src/base/rules/reference/reset-seed-coverage.md": "cfbb50fc9fdb6f0a354255802392adc717ea18af65aca92cc866416bf9256d91",
     "plugins/src/base/rules/reference/security-audit-handling.md": "9633e11ac89af26444a272449f36fe03f26e61fab40ca16a0ab50464725f7d8c",
-    "plugins/src/base/rules/reference/session-status-updates.md": "8c34dc9399d6b20103edb3ed8d214aaa05a97065e4c78d8010f394cd041b3320",
+    "plugins/src/base/rules/reference/session-status-updates.md": "8878eceb7d81ee4d1ebd51f2f179e659ce36fac3ee7d04bc8631f44923d5e9ae",
     "plugins/src/base/rules/reference/settled-decisions.md": "a26eb4e879ab33468d2c55c1cf8128fbbfbec9c2cb634d9dd9f008304ad9aa05",
     "plugins/src/base/rules/reference/stale-state-claims.md": "6329e1a7629f9a12f10454c767842aecee4964df8b7bb4aebda9dde3c0959c2a",
     "plugins/src/base/rules/reference/tool-access-gate.md": "29579f403648d3b550b8b7e5fba01986fba8d3f0f285b5b5bf6bb0a839f7f10e",

package/package.json

@@ -187,7 +187,7 @@
     "zod-validation-error": "^4.0.0"
   },
   "name": "@codyswann/lisa",
-  "version": "4.64.9",
+  "version": "4.65.0",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {
@@ -336,7 +336,7 @@
     "test": "tests"
   },
   "types": "./dist/index.d.ts",
-  "lisaReleaseCommit": "b965dfb22ce7fd5d76d4c6ed22d07ce6ea3e545c",
-  "gitHead": "b965dfb22ce7fd5d76d4c6ed22d07ce6ea3e545c",
-  "lisaReleaseTag": "v4.64.9"
+  "lisaReleaseCommit": "2b4ff537ed99a9d705e74d521996c98807508208",
+  "gitHead": "2b4ff537ed99a9d705e74d521996c98807508208",
+  "lisaReleaseTag": "v4.65.0"
 }

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

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

package/plugins/lisa/rules/eager/session-status-updates.md

@@ -7,6 +7,7 @@ Assume the reader is **non-technical** — the same obligation Lisa already plac
 ## Mandatory
 
 - **Plain, conversational language.** No jargon, no Lisa vocabulary, no tool or file names the reader has no use for. Say "the login page broke", not "the auth guard regressed at the controller boundary".
+- **Write every response in ASD-STE100 Simplified Technical English.** All responses, not only status updates. One idea per sentence, active voice, present tense, sentences under 20 words, approved vocabulary — "start" not "initiate", "use" not "utilize". The proper name of a real thing (a command, a file, an error) is always permitted.
 - **A decision is presented as a decision** — never buried in a status paragraph the reader has to mine. State the choice, give **your recommendation**, and name the **ramifications** of each option in one line apiece.
 - **End every update with a close line**, exactly this shape:
 

package/plugins/lisa/rules/reference/session-status-updates.md

@@ -27,6 +27,57 @@ Write the way you would speak to a competent colleague who does not work on this
 
 Two lines the user themselves offered as the target: *"just tell me what's going on and what my options are"* and *"give me the summary, I'll ask for detail if I want it."*
 
+## ASD-STE100 Simplified Technical English
+
+Every response you write to a human is written in ASD-STE100 Simplified Technical
+English — the controlled-language standard maintained by the AeroSpace and Defence
+Industries Association of Europe. It is not a separate style from the plain language
+this rule already asks for; it is the written specification of it. "Plain" is a
+preference and gets argued about. ASD-STE100 is a rulebook, so it does not.
+
+The scope is every response, not only a status update. A one-line answer, a
+question back to the operator, a review summary and a final report are all bound by
+it.
+
+### The writing rules that bind you
+
+- **One idea per sentence.** Split a compound thought into separate sentences.
+- **Sentences stay short.** 20 words at most for a descriptive sentence, 20 for a
+  procedural step. Break a longer one in two.
+- **Active voice.** "The test failed", not "a failure was observed".
+- **Present tense** unless you are describing something that already happened.
+- **One word, one meaning.** Use a word in a single sense throughout a response.
+  Do not use "check" to mean both an inspection and a CI job in the same message.
+- **Approved vocabulary.** Prefer the simple verb: *start* over initiate, *use*
+  over utilize, *do* over perform, *about* over approximately, *before* over prior
+  to, *help* over facilitate, *end* over terminate.
+- **No noun clusters longer than three words.** "the deploy approval gate", not
+  "the protected environment deploy approval gate policy".
+- **Say the subject.** Do not drop articles or the actor: "The gate blocks the
+  push", not "Gate blocks push".
+- **No idiom, no metaphor, no humour that depends on a shared culture.** The reader
+  may not speak English as a first language.
+- **Paragraphs stay short.** Six sentences at most.
+
+### What the standard does not forbid
+
+The proper name of a real thing is always permitted, even when it is technical: a
+command, a file path, a branch, an error string, a ticket id. ASD-STE100 keeps
+technical names — it constrains the words around them. The plain-language rule
+above still decides *whether* the reader needs that name at all.
+
+Numbers, units, measurements and quoted output are reproduced exactly. Never
+simplify the content of an error message, a test result or a security warning to
+obey a word rule; quote it and explain it in simplified prose around the quote.
+
+### Why it is worth the constraint
+
+Lisa's premise is that a non-technical person directs the work. The people standing
+at the gates read intake rejections, ticket descriptions and verification reports,
+and many of them do not read English first. A controlled language is the cheapest
+thing that makes those artifacts uniformly readable, and it removes the argument
+about whether a given sentence was "plain enough".
+
 ## Decisions
 
 A decision presented as a paragraph of context is a decision the human has to excavate. State it as a decision:

package/plugins/lisa-agy/plugin.json

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

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

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

package/plugins/lisa-copilot/rules/eager/session-status-updates.md

@@ -7,6 +7,7 @@ Assume the reader is **non-technical** — the same obligation Lisa already plac
 ## Mandatory
 
 - **Plain, conversational language.** No jargon, no Lisa vocabulary, no tool or file names the reader has no use for. Say "the login page broke", not "the auth guard regressed at the controller boundary".
+- **Write every response in ASD-STE100 Simplified Technical English.** All responses, not only status updates. One idea per sentence, active voice, present tense, sentences under 20 words, approved vocabulary — "start" not "initiate", "use" not "utilize". The proper name of a real thing (a command, a file, an error) is always permitted.
 - **A decision is presented as a decision** — never buried in a status paragraph the reader has to mine. State the choice, give **your recommendation**, and name the **ramifications** of each option in one line apiece.
 - **End every update with a close line**, exactly this shape:
 

package/plugins/lisa-copilot/rules/reference/session-status-updates.md

@@ -27,6 +27,57 @@ Write the way you would speak to a competent colleague who does not work on this
 
 Two lines the user themselves offered as the target: *"just tell me what's going on and what my options are"* and *"give me the summary, I'll ask for detail if I want it."*
 
+## ASD-STE100 Simplified Technical English
+
+Every response you write to a human is written in ASD-STE100 Simplified Technical
+English — the controlled-language standard maintained by the AeroSpace and Defence
+Industries Association of Europe. It is not a separate style from the plain language
+this rule already asks for; it is the written specification of it. "Plain" is a
+preference and gets argued about. ASD-STE100 is a rulebook, so it does not.
+
+The scope is every response, not only a status update. A one-line answer, a
+question back to the operator, a review summary and a final report are all bound by
+it.
+
+### The writing rules that bind you
+
+- **One idea per sentence.** Split a compound thought into separate sentences.
+- **Sentences stay short.** 20 words at most for a descriptive sentence, 20 for a
+  procedural step. Break a longer one in two.
+- **Active voice.** "The test failed", not "a failure was observed".
+- **Present tense** unless you are describing something that already happened.
+- **One word, one meaning.** Use a word in a single sense throughout a response.
+  Do not use "check" to mean both an inspection and a CI job in the same message.
+- **Approved vocabulary.** Prefer the simple verb: *start* over initiate, *use*
+  over utilize, *do* over perform, *about* over approximately, *before* over prior
+  to, *help* over facilitate, *end* over terminate.
+- **No noun clusters longer than three words.** "the deploy approval gate", not
+  "the protected environment deploy approval gate policy".
+- **Say the subject.** Do not drop articles or the actor: "The gate blocks the
+  push", not "Gate blocks push".
+- **No idiom, no metaphor, no humour that depends on a shared culture.** The reader
+  may not speak English as a first language.
+- **Paragraphs stay short.** Six sentences at most.
+
+### What the standard does not forbid
+
+The proper name of a real thing is always permitted, even when it is technical: a
+command, a file path, a branch, an error string, a ticket id. ASD-STE100 keeps
+technical names — it constrains the words around them. The plain-language rule
+above still decides *whether* the reader needs that name at all.
+
+Numbers, units, measurements and quoted output are reproduced exactly. Never
+simplify the content of an error message, a test result or a security warning to
+obey a word rule; quote it and explain it in simplified prose around the quote.
+
+### Why it is worth the constraint
+
+Lisa's premise is that a non-technical person directs the work. The people standing
+at the gates read intake rejections, ticket descriptions and verification reports,
+and many of them do not read English first. A controlled language is the cheapest
+thing that makes those artifacts uniformly readable, and it removes the argument
+about whether a given sentence was "plain enough".
+
 ## Decisions
 
 A decision presented as a paragraph of context is a decision the human has to excavate. State it as a decision:

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

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

package/plugins/lisa-cursor/rules/session-status-updates-reference.mdc

@@ -32,6 +32,57 @@ Write the way you would speak to a competent colleague who does not work on this
 
 Two lines the user themselves offered as the target: *"just tell me what's going on and what my options are"* and *"give me the summary, I'll ask for detail if I want it."*
 
+## ASD-STE100 Simplified Technical English
+
+Every response you write to a human is written in ASD-STE100 Simplified Technical
+English — the controlled-language standard maintained by the AeroSpace and Defence
+Industries Association of Europe. It is not a separate style from the plain language
+this rule already asks for; it is the written specification of it. "Plain" is a
+preference and gets argued about. ASD-STE100 is a rulebook, so it does not.
+
+The scope is every response, not only a status update. A one-line answer, a
+question back to the operator, a review summary and a final report are all bound by
+it.
+
+### The writing rules that bind you
+
+- **One idea per sentence.** Split a compound thought into separate sentences.
+- **Sentences stay short.** 20 words at most for a descriptive sentence, 20 for a
+  procedural step. Break a longer one in two.
+- **Active voice.** "The test failed", not "a failure was observed".
+- **Present tense** unless you are describing something that already happened.
+- **One word, one meaning.** Use a word in a single sense throughout a response.
+  Do not use "check" to mean both an inspection and a CI job in the same message.
+- **Approved vocabulary.** Prefer the simple verb: *start* over initiate, *use*
+  over utilize, *do* over perform, *about* over approximately, *before* over prior
+  to, *help* over facilitate, *end* over terminate.
+- **No noun clusters longer than three words.** "the deploy approval gate", not
+  "the protected environment deploy approval gate policy".
+- **Say the subject.** Do not drop articles or the actor: "The gate blocks the
+  push", not "Gate blocks push".
+- **No idiom, no metaphor, no humour that depends on a shared culture.** The reader
+  may not speak English as a first language.
+- **Paragraphs stay short.** Six sentences at most.
+
+### What the standard does not forbid
+
+The proper name of a real thing is always permitted, even when it is technical: a
+command, a file path, a branch, an error string, a ticket id. ASD-STE100 keeps
+technical names — it constrains the words around them. The plain-language rule
+above still decides *whether* the reader needs that name at all.
+
+Numbers, units, measurements and quoted output are reproduced exactly. Never
+simplify the content of an error message, a test result or a security warning to
+obey a word rule; quote it and explain it in simplified prose around the quote.
+
+### Why it is worth the constraint
+
+Lisa's premise is that a non-technical person directs the work. The people standing
+at the gates read intake rejections, ticket descriptions and verification reports,
+and many of them do not read English first. A controlled language is the cheapest
+thing that makes those artifacts uniformly readable, and it removes the argument
+about whether a given sentence was "plain enough".
+
 ## Decisions
 
 A decision presented as a paragraph of context is a decision the human has to excavate. State it as a decision:

package/plugins/lisa-cursor/rules/session-status-updates.mdc

@@ -12,6 +12,7 @@ Assume the reader is **non-technical** — the same obligation Lisa already plac
 ## Mandatory
 
 - **Plain, conversational language.** No jargon, no Lisa vocabulary, no tool or file names the reader has no use for. Say "the login page broke", not "the auth guard regressed at the controller boundary".
+- **Write every response in ASD-STE100 Simplified Technical English.** All responses, not only status updates. One idea per sentence, active voice, present tense, sentences under 20 words, approved vocabulary — "start" not "initiate", "use" not "utilize". The proper name of a real thing (a command, a file, an error) is always permitted.
 - **A decision is presented as a decision** — never buried in a status paragraph the reader has to mine. State the choice, give **your recommendation**, and name the **ramifications** of each option in one line apiece.
 - **End every update with a close line**, exactly this shape:
 

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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/session-status-updates.md

@@ -7,6 +7,7 @@ Assume the reader is **non-technical** — the same obligation Lisa already plac
 ## Mandatory
 
 - **Plain, conversational language.** No jargon, no Lisa vocabulary, no tool or file names the reader has no use for. Say "the login page broke", not "the auth guard regressed at the controller boundary".
+- **Write every response in ASD-STE100 Simplified Technical English.** All responses, not only status updates. One idea per sentence, active voice, present tense, sentences under 20 words, approved vocabulary — "start" not "initiate", "use" not "utilize". The proper name of a real thing (a command, a file, an error) is always permitted.
 - **A decision is presented as a decision** — never buried in a status paragraph the reader has to mine. State the choice, give **your recommendation**, and name the **ramifications** of each option in one line apiece.
 - **End every update with a close line**, exactly this shape:
 

package/plugins/src/base/rules/reference/session-status-updates.md

@@ -27,6 +27,57 @@ Write the way you would speak to a competent colleague who does not work on this
 
 Two lines the user themselves offered as the target: *"just tell me what's going on and what my options are"* and *"give me the summary, I'll ask for detail if I want it."*
 
+## ASD-STE100 Simplified Technical English
+
+Every response you write to a human is written in ASD-STE100 Simplified Technical
+English — the controlled-language standard maintained by the AeroSpace and Defence
+Industries Association of Europe. It is not a separate style from the plain language
+this rule already asks for; it is the written specification of it. "Plain" is a
+preference and gets argued about. ASD-STE100 is a rulebook, so it does not.
+
+The scope is every response, not only a status update. A one-line answer, a
+question back to the operator, a review summary and a final report are all bound by
+it.
+
+### The writing rules that bind you
+
+- **One idea per sentence.** Split a compound thought into separate sentences.
+- **Sentences stay short.** 20 words at most for a descriptive sentence, 20 for a
+  procedural step. Break a longer one in two.
+- **Active voice.** "The test failed", not "a failure was observed".
+- **Present tense** unless you are describing something that already happened.
+- **One word, one meaning.** Use a word in a single sense throughout a response.
+  Do not use "check" to mean both an inspection and a CI job in the same message.
+- **Approved vocabulary.** Prefer the simple verb: *start* over initiate, *use*
+  over utilize, *do* over perform, *about* over approximately, *before* over prior
+  to, *help* over facilitate, *end* over terminate.
+- **No noun clusters longer than three words.** "the deploy approval gate", not
+  "the protected environment deploy approval gate policy".
+- **Say the subject.** Do not drop articles or the actor: "The gate blocks the
+  push", not "Gate blocks push".
+- **No idiom, no metaphor, no humour that depends on a shared culture.** The reader
+  may not speak English as a first language.
+- **Paragraphs stay short.** Six sentences at most.
+
+### What the standard does not forbid
+
+The proper name of a real thing is always permitted, even when it is technical: a
+command, a file path, a branch, an error string, a ticket id. ASD-STE100 keeps
+technical names — it constrains the words around them. The plain-language rule
+above still decides *whether* the reader needs that name at all.
+
+Numbers, units, measurements and quoted output are reproduced exactly. Never
+simplify the content of an error message, a test result or a security warning to
+obey a word rule; quote it and explain it in simplified prose around the quote.
+
+### Why it is worth the constraint
+
+Lisa's premise is that a non-technical person directs the work. The people standing
+at the gates read intake rejections, ticket descriptions and verification reports,
+and many of them do not read English first. A controlled language is the cheapest
+thing that makes those artifacts uniformly readable, and it removes the argument
+about whether a given sentence was "plain enough".
+
 ## Decisions
 
 A decision presented as a paragraph of context is a decision the human has to excavate. State it as a decision: