@codyswann/lisa 4.84.6 → 4.84.8

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.84.6",
+  "version": "4.84.8",
   "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-devin/.devin-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "4.84.6",
+  "version": "4.84.8",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-devin/.devin-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "4.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "4.84.6",
+  "version": "4.84.8",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "4.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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.84.6",
+  "version": "4.84.8",
   "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-devin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "4.84.6",
+  "version": "4.84.8",
   "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-devin/.devin-plugin/plugin.json

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.84.6",
+  "version": "4.84.8",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-devin/.devin-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "4.84.6",
+  "version": "4.84.8",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/src/base/hooks/block-host-name-leak.mjs

@@ -287,8 +287,16 @@ export function publishableText(tokens, cwd, noun) {
       const value = valueAt(tokens, index);
       // On `gh api`, `-F` is `--field`: `key=@path` or `key=value`. Read as a
       // bare path, `body=@file` named no file and published unchecked (#4462).
-      if (noun === "api" && /^[\w.[\]-]+=/u.test(value))
-        return [fieldSource(value, cwd)];
+      if (
+        (noun === "api" || (noun === undefined && bare === "-F")) &&
+        /^[\w.[\]-]+=/u.test(value)
+      ) {
+        const field = fieldSource(value, cwd);
+        if (noun === "api") return [field];
+        // An unresolved noun may become api or issue/pr. Inspect both possible
+        // meanings of -F without evaluating the expansion or certifying routing.
+        return [field, { origin: value, text: readIfPresent(value, cwd) }];
+      }
       const file = value.replace(/^@/u, "");
       return [{ origin: file, text: readIfPresent(file, cwd) }];
     }
@@ -414,20 +422,24 @@ export async function evaluate(command, projectDir) {
     // protection, and name the unread input instead of claiming the text clean.
     if (
       context.cwd === undefined &&
-      [...context.flags].some(([flag, item]) => {
+      [
+        ...context.flags,
+        ...(context.noun === "api" || context.noun === undefined
+          ? context.fieldOccurrences
+          : []),
+      ].some(([flag, item]) => {
         const field =
-          context.noun === "api" && FIELD_FLAGS.has(flag)
+          (context.noun === "api" || context.noun === undefined) &&
+          FIELD_FLAGS.has(flag)
             ? /^([^=]+)=@(.+)$/u.exec(item.value)
             : null;
-        const file =
-          field !== null
-            ? PROSE_FIELDS.has(field[1])
-              ? field[2]
-              : undefined
-            : FILE_FLAGS.has(flag)
-              ? item.value.replace(/^@/, "")
-              : undefined;
-        return file !== undefined && !path.isAbsolute(file);
+        const files = [
+          field !== null && PROSE_FIELDS.has(field[1]) ? field[2] : undefined,
+          FILE_FLAGS.has(flag) && (context.noun !== "api" || field === null)
+            ? item.value.replace(/^@/, "")
+            : undefined,
+        ];
+        return files.some(file => file !== undefined && !path.isAbsolute(file));
       })
     ) {
       return {

package/plugins/src/base/hooks/host-name-command-context.mjs

@@ -103,6 +103,7 @@ function words(command) {
  */
 function argumentsOf(input) {
   const flags = new Map(),
+    fieldOccurrences = [],
     positional = [],
     tokens = [];
   // Any expansion can add/replace routing arguments after shell word splitting.
@@ -139,23 +140,34 @@ function argumentsOf(input) {
         flag === "-R" ? "--repo" : flag === "-X" ? "--method" : flag,
         value
       );
+      // API fields are additive even though routing options use last values.
+      if (FIELD_FLAGS.has(flag)) fieldOccurrences.push([flag, value]);
       tokens.push(value.value);
     } else if (!word.value.startsWith("-")) positional.push(word);
     else if (!word.literal) certain = false;
   }
-  const noun = positional[0]?.value,
-    verb = positional[1]?.value;
+  const nounWord = positional[0],
+    verbWord = positional[1];
+  const noun = nounWord?.literal ? nounWord.value : undefined,
+    verb = verbWord?.value;
+  // Command-name expansions can supply several argv words. A following
+  // read-looking literal does not prove that the expanded command is a read.
+  const uncertainName =
+    nounWord?.literal === false ||
+    (["issue", "pr"].includes(noun) && verbWord?.literal === false);
   const method = flags.get("--method");
   const writes =
-    noun === "api"
+    uncertainName ||
+    (noun === "api"
       ? method
         ? !method.literal || METHODS.has(method.value.toUpperCase())
         : [...FIELD_FLAGS].some(flag => flags.has(flag)) ||
           Boolean(flags.get("--input")?.value)
       : ["issue", "pr"].includes(noun) &&
-        ["create", "comment", "edit"].includes(verb);
+        ["create", "comment", "edit"].includes(verb));
   return {
     flags,
+    fieldOccurrences,
     positional,
     tokens: ["gh", ...tokens],
     noun,

package/plugins/src/base/hooks/parity-safety-net.sh

@@ -3472,8 +3472,10 @@ if [ -f "$rules_file" ]; then
     # here — before the remaining rules ran, and with an exit status that is
     # not a refusal. The `||` puts the pipeline in a condition context, where
     # a non-zero status is expected rather than fatal.
+    # Consume the whole input: grep -q can close an early match while printf
+    # is still writing, making pipefail report SIGPIPE instead of the match.
     rule_status=0
-    printf '%s' "$custom_command_str" | grep -Eiq -- "$rule" || rule_status=$?
+    printf '%s' "$custom_command_str" | grep -Ei -- "$rule" >/dev/null || rule_status=$?
     case "$rule_status" in
       0) block "matched a project custom safety rule (${rules_file##*/}): $rule" ;;
       1) ;; # no match

package/plugins/src/base/rules/eager/00-rule-index.md

@@ -46,6 +46,7 @@ Paths are relative to this file.
 | `bdd-e2e-coverage` | the work item adds or changes a user-observable surface | [../reference/bdd-e2e-coverage.md](../reference/bdd-e2e-coverage.md) |
 | `reset-seed-coverage` | the work item adds or changes persistent state | [../reference/reset-seed-coverage.md](../reference/reset-seed-coverage.md) |
 | `claim-evidence-mapping` | citing evidence for a claim, or reviewing evidence someone cited | [../reference/claim-evidence-mapping.md](../reference/claim-evidence-mapping.md) |
+| `completion-authorization` | publishing proof or completing work items | [../reference/completion-authorization.md](../reference/completion-authorization.md) |
 | `observability-audit` | running the `lisa-monitor` audit-and-file arm | [../reference/observability-audit.md](../reference/observability-audit.md) |
 | `readiness-rubric` | judging whether an unattended fleet may run in a repository | [../reference/readiness-rubric.md](../reference/readiness-rubric.md) |
 

package/plugins/src/base/rules/reference/completion-authorization.md

@@ -0,0 +1,10 @@
+# Accepted completion proof
+
+Read the single maintained contract at
+`skills/lisa-tracker-evidence/references/completion-authorization.md`, relative
+to the Lisa plugin root. The tracker-evidence skill resolves it as its own
+`references/completion-authorization.md` companion.
+
+The contract travels with skill resources on every supported agent, including
+Antigravity, whose native plugin intentionally omits the rules tree. The shared
+Node producer and completion guard enforce the same contract for every agent.

package/plugins/src/base/skills/lisa-drive-pr-to-merge/SKILL.md

@@ -1353,7 +1353,8 @@ Four properties make the command safe to run unconditionally:
    above does, and for the same reason. A merged pull request is not evidence
    on its own: the writer resolves `<baseRefName>` through `.lisa.config.json`
    `deploy.branches` and applies only the role that base earned. A merge into
-   the production deploy branch is terminal and closes the item; a merge into a
+   the production deploy branch becomes eligible for terminal completion only
+   after canonical accepted-for-completion proof passes; a merge into a
    branch mapping to a lower env records that env's role and leaves the item
    open; a merge into a branch the project does not deploy at all — an
    integration/stack branch — records nothing, closes nothing, and reports the
@@ -1375,6 +1376,19 @@ If the command refuses, do not close by hand. A refusal means the evidence is
 not there, and a lifecycle step performed by hand is one nothing can verify
 happened.
 
+`work-item pending-proof` is a normal nonterminal outcome: the merge does not
+prove the configured whole delivery run, runtime behavior, typed attachments,
+CONFORMS, canonical Verify usage, exact linkage and acceptance. Keep the item
+owned/open, finish canonical Verify and `lisa-tracker-evidence`, and use its
+shipped `publish-completion-proof` producer after actual uploads/readbacks.
+Then retry canonical completion. Read the sibling skill companion
+`../lisa-tracker-evidence/references/completion-authorization.md` relative to this
+skill directory; it is the portable `completion-authorization` reference.
+Publish an immutable required pending-state journey artifact first; append the
+real native terminal readback/acceptedAt afterward. Never require the future
+close event as its own authorization. A configured bot publisher's still-running
+pinned attempt keeps completion pending until that exact attempt succeeds.
+
 **The backstop, for the ones that still slip:** `lisa-work-item.mjs sweep`
 reports every open item — in the **ready** lane as well as the **claimed** one —
 that a commit on a deploy branch DECLARES via its `Work-Item:` trailer, and

package/plugins/src/base/skills/lisa-tracker-evidence/SKILL.md

@@ -14,6 +14,11 @@ Apply `lisa-tracker-sync` — **Agent attribution** when composing evidence comm
 
 ## Workflow
 
+The portable accepted-completion contract is this skill's own
+`references/completion-authorization.md` companion. Read that file when preparing
+or publishing completion proof. It ships with the skill even on runtimes that
+omit the plugin rules tree; do not assume a runtime-specific rules directory.
+
 1. Resolve tracker config (same logic as `lisa-tracker-write`).
 2. Missing / empty → stop and report `"No tracker configured in .lisa.config.json. Run /lisa:setup:jira, /lisa:setup:github, or /lisa:setup:linear first."`
 3. Before dispatching, update the generated evidence artifact through `lisa-usage-accounting` so the comment body / PR evidence section carries a direct `lisa-verify` usage entry in the canonical `## Lisa Usage` section. If the originating work item's parentage or child refs are already known, prefer `record_and_rollup` so ancestor totals refresh in the same write; otherwise still write the direct entry, and if trustworthy runtime usage is unavailable, write `source: unavailable` with nullable token/cost fields instead of skipping the row.
@@ -22,7 +27,8 @@ Apply `lisa-tracker-sync` — **Agent attribution** when composing evidence comm
    - `github` → invoke `lisa-github-evidence` with `$ARGUMENTS` verbatim. Arg shape: `<ISSUE_REF> <EVIDENCE_DIR> <PR_NUMBER>` where `ISSUE_REF` is `org/repo#<number>` or a GitHub issue URL.
    - `linear` → invoke `lisa-linear-evidence` with `$ARGUMENTS` verbatim. Arg shape: `<IDENTIFIER> <EVIDENCE_DIR>` where `IDENTIFIER` is a Linear Issue identifier (e.g., `ENG-123`).
    - Anything else → stop and report `"Unknown tracker '<value>' in .lisa.config.json. Expected 'jira', 'github', or 'linear'."`
-5. Pass through the vendor skill's output.
+5. For supported GitHub/Linear production completion, after actual uploads and exact native readbacks, prepare the accepted-for-completion input from the observed source/delivery, schema2 verdicts, actual typed attachment pointers, complete requirement conjunction map, structured CONFORMS report, canonical Verify usage, linkage and explicit acceptance. Apply the shipped `completion-authorization` reference; the executable validates the contract in every installed host. Run `node scripts/lisa-work-item.mjs publish-completion-proof --ref <exact-work-item> --record <evidence-dir>/completion-record.json`. It uploads immutable hash-named acceptance bytes to the implementation repository's `pr-assets`, reads them back and publishes the exact-item native locator. Never construct a locator manually or treat a narrative evidence comment as acceptance. Jira completion remains unsupported.
+6. Pass through both the vendor output and actual producer category. `published/pending-producer` means the pinned configured automation attempt must finish successfully before completion; do not rewrite the asset after the job or invent a successful future outcome. A User publisher does not require a producer workflow run. Only after accepted publication may the canonical lifecycle owner retry `complete`; pending proof preserves ownership and state and names the Verify/evidence action. Capture actual terminal readback/usage acceptedAt afterward, not as a circular publication prerequisite. A required pending-state journey artifact is immutable Phase-A proof captured before completion; the later actual terminal readback is a separate Phase-B supplement.
 
 ## Rules