@codyswann/lisa 4.64.9 → 4.65.1

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.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": "4.64.9",
+  "version": "4.65.1",
   "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:

package/plugins/src/base/skills/lisa-secrets-access/scripts/providers.mjs

@@ -429,6 +429,24 @@ export function fetchRaw(cfg) {
   );
 }
 
+/**
+ * The argument vector a provider CLI is actually spawned with.
+ *
+ * `bws` 2.1.0 colours its output even into a pipe and ignores `NO_COLOR`,
+ * `TERM=dumb` and `CLICOLOR=0` alike, so `bws secret list --output json`
+ * arrives as ANSI-wrapped JSON and `JSON.parse` fails on the first escape
+ * byte — for EVERY secret, including a known-good control. Its own `--color`
+ * flag is the one switch it honours, and it is a global option that must
+ * precede the subcommand. It is applied here rather than at each call site
+ * because a call site that forgets it reproduces the outage in silence.
+ * @param {string} bin Executable name.
+ * @param {readonly string[]} args Arguments the caller composed.
+ * @returns {string[]} Arguments with the CLI's colour switched off.
+ */
+export function providerArgs(bin, args) {
+  return bin === "bws" ? ["--color", "no", ...args] : [...args];
+}
+
 /**
  * Run a provider CLI, keeping its output off any shared stream.
  * @param {string} bin Executable name.
@@ -438,7 +456,7 @@ export function fetchRaw(cfg) {
  */
 function run(bin, args, env, operation = "talking to the secrets provider") {
   try {
-    return boundedChildOutput(bin, args, {
+    return boundedChildOutput(bin, providerArgs(bin, args), {
       encoding: "utf8",
       env,
       stdio: ["ignore", "pipe", "pipe"],