@codyswann/lisa 4.45.3 → 4.45.4

package/dist/opencode/plugin-templates/lisa-block-direct-issue-create.ts

@@ -159,6 +159,41 @@ const LisaBlockDirectIssueCreate = async () => {
    */
   const LIFECYCLE_ROLE_READY =
     /(?:^|[^\w.-])(?:lifecycle_role|LIFECYCLE_ROLE)["']?\s*[:=]\s*["']?ready\b|(?:^|[^\w.-])--role[=\s]+["']?ready\b/;
+  /**
+   * The third declaration: this item is a CONTAINER.
+   *
+   * A container is neither build-ready nor human-gated. `leaf-only-lifecycle`
+   * FORBIDS the build-ready role on an Epic, and a human gate it does not have
+   * is a durable false hold — so a guard with only the two arms above could be
+   * satisfied for a container only by writing something untrue, and both
+   * untruths corrupt data another control reads.
+   *
+   * It keys on the canonical container line that `derived-branch-plan` defines
+   * and `lisa-github-write-issue` already stamps, NOT on a declared
+   * `type:Epic`. A declared type is a claim that costs a leaf nothing and
+   * leaves it looking buildable; the container line costs the item its Target
+   * Backend Environment and Branch Plan, so it is only useful to something
+   * that actually is a container.
+   *
+   * Matched as the WHOLE canonical value, `None` included: the tail alone
+   * would match ordinary prose about how a container's state behaves, and a
+   * declaration that ordinary prose satisfies is not a declaration.
+   * Whitespace-tolerant because a body file may wrap the line; dash-tolerant
+   * because an author retyping it by hand will not always reach for the em
+   * dash.
+   */
+  const CONTAINER_DECLARATION =
+    /None\s*[\u2014\u2013-]\s*container:\s*state\s+rolls\s+up\s+from\s+children/i;
+  /**
+   * The checkable half of "is it really a container": an item cannot be a
+   * container and a by-design leaf at once. The types are quoted from
+   * `leaf-only-lifecycle`. Story and Spike are deliberately absent — that
+   * rule's childless-parent exception makes them leaf-or-container depending
+   * on child work, and a decomposition legitimately files a parent Story
+   * before the children that make it one.
+   */
+  const LEAF_TYPE_FLAG =
+    /--(?:label|labels|add-label|type|issue-type|issuetype)(?:=|\s+)(['"]?)(?:type:)?(bug|task|sub-?task|improvement)\1(?=[\s,]|$)/i;
   /** A creation verb, and a tracker endpoint to send it to. */
   const GRAPHQL_CREATE = /createIssue|issueCreate/;
   const TRACKER_ENDPOINT =
@@ -487,7 +522,11 @@ const LisaBlockDirectIssueCreate = async () => {
             .some(candidate => against.includes(candidate))
         ) ||
         text.includes(HUMAN_GATE_MARKER) ||
-        (roleOk && LIFECYCLE_ROLE_READY.test(text));
+        (roleOk && LIFECYCLE_ROLE_READY.test(text)) ||
+        // The container arm. The contradiction check comes first, so a filing
+        // declaring itself both a container and a by-design leaf is refused
+        // rather than allowed on the strength of the half that suits it.
+        (!LEAF_TYPE_FLAG.test(text) && CONTAINER_DECLARATION.test(text));
       const declares = (text: string): boolean =>
         declaresFor(text, roles, stateRoleOk);
       // A creation the command does not spell out itself, because it lives in

package/package.json

@@ -175,7 +175,7 @@
     "zod-validation-error": "^4.0.0"
   },
   "name": "@codyswann/lisa",
-  "version": "4.45.3",
+  "version": "4.45.4",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {
@@ -323,7 +323,7 @@
     "test": "tests"
   },
   "types": "./dist/index.d.ts",
-  "lisaReleaseCommit": "f771fcab3c0cc18480a639ae82b6d49e63e6716e",
-  "gitHead": "f771fcab3c0cc18480a639ae82b6d49e63e6716e",
-  "lisaReleaseTag": "v4.45.3"
+  "lisaReleaseCommit": "db444af7af5afc0672c5521038b9743b85adab29",
+  "gitHead": "db444af7af5afc0672c5521038b9743b85adab29",
+  "lisaReleaseTag": "v4.45.4"
 }

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

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

package/plugins/lisa/.codex-plugin/skills/lisa-github-write-issue/SKILL.md

@@ -289,6 +289,22 @@ proceed — the marker still holds. Never file the label *instead of* the marker
 
 If a leaf arrives with `build_ready` omitted or `false` **and** no `human_gate`, do not create it: report the incomplete handoff and name both ways to resolve it (`build_ready: true`, or a `human_gate` reason). Containers are exempt — their state rolls up from children, so they need neither.
 
+**The container exemption is executable, not prose.** It used to live only in the sentence above,
+which meant the `block-direct-issue-create.sh` guard — the control that actually runs on the CLI
+path — had no arm for it, and a container could satisfy that guard only by declaring a build-ready
+role `leaf-only-lifecycle` forbids on it or a human gate it does not have. A container now declares
+a **third** thing, and this skill already writes it: the canonical Target Backend Environment value
+`None — container: state rolls up from children`, defined once by `derived-branch-plan`. The guard
+reads that one string, so there is nothing for the skill and the guard to disagree about.
+
+Two consequences for a container written from here. Render the Target Backend Environment section
+with that exact value — an absent section reads as *underivable*, not exempt, and leaves the guard
+nothing to read. And do not put a **by-design leaf type** (`type:Bug` / `type:Task` /
+`type:Sub-task` / `type:Improvement`) on a filing carrying that declaration: an item cannot be a
+container and a leaf at once, and the guard refuses the combination. `type:Story` and `type:Spike`
+are not in that set, because `leaf-only-lifecycle`'s childless-parent exception makes them
+leaf-or-container depending on child work.
+
 ## Phase 5.5 — Validate (Pre-write Gate)
 
 Before any write, invoke `lisa-github-validate-issue` with the full proposed spec assembled from Phases 2 / 3 / 4 / 5. Pass it as a YAML block per the `lisa-github-validate-issue` schema, including `runtime_behavior_change`, `authenticated_surface`, and `artifacts_attached` flags so the right gates run.

package/plugins/lisa/hooks/block-blind-automerge.agy.sh

@@ -7,9 +7,10 @@
 # adapter only translates protocols; all classification — which commands arm
 # auto-merge, and what GitHub says about the PR's review gate — stays in the
 # canonical block-blind-automerge.sh beside it (same delegation pattern as
-# block-shell-json-parsing.agy.sh). Fail-open on missing runtimes, matching the
-# canonical guard's own degrade-loudly path: a guard that cannot read the PR
-# cannot tell an honest arming from a blind one.
+# block-shell-json-parsing.agy.sh) — including which commands re-target a pull
+# request onto a base ref no ruleset covers. Fail-open on missing runtimes,
+# matching the canonical guard's own degrade-loudly path: a guard that cannot
+# read the PR cannot tell an honest arming from a blind one.
 set -uo pipefail
 
 allow() {
@@ -50,5 +51,5 @@ else
 fi
 
 [ "$canonical_status" -eq 0 ] && allow
-[ -n "$canonical_output" ] || canonical_output="Blocked: arming auto-merge on a PR whose reviewDecision is CHANGES_REQUESTED."
+[ -n "$canonical_output" ] || canonical_output="Blocked: this command would arm auto-merge on a PR that cannot merge, or move a failing PR onto a base with no required checks."
 deny "$canonical_output"