@codyswann/lisa 4.81.3 → 4.81.5

package/plugins/lisa-agy/skills/lisa-session-manager/scripts/setup-checks.mjs

@@ -0,0 +1,168 @@
+/**
+ * Read-only facts setup needs before it asks the operator for anything:
+ * which worker directories Claude Code already trusts, and whether a
+ * scheduled intake loop is still running alongside the manager.
+ *
+ * Both used to be manual (CodySwannGT/lisa#4465). Setup asked the operator to
+ * open `claude` in every worker directory to accept workspace trust, even
+ * where Claude Code had already recorded it; and it only warned that
+ * `intake-tickets` / `intake-repair` compete with the manager, leaving the
+ * agent to dig through run logs to find out whether either was alive.
+ *
+ * Neither check writes anything, and neither answers a trust prompt.
+ * @module session-manager/setup-checks
+ */
+import * as nodeFs from "node:fs";
+import path from "node:path";
+
+/** The scheduled loops that compete with the manager for the same items. */
+export const COMPETING_LOOPS = Object.freeze([
+  "intake-tickets",
+  "intake-repair",
+]);
+
+/** A loop counts as recent when it ran within at least this long. */
+const MIN_RECENT_MS = 24 * 60 * 60 * 1000;
+
+/**
+ * Where Claude Code keeps its global state, including per-directory trust:
+ * `$CLAUDE_CONFIG_DIR/.claude.json` when that is set, else `~/.claude.json`.
+ * @param {{ env?: Record<string, string | undefined>, homedir: string }} input
+ *   - Environment and home directory
+ * @returns {string} Absolute path
+ */
+export function claudeStateFile({ env = {}, homedir }) {
+  const configDir = env.CLAUDE_CONFIG_DIR;
+  return configDir
+    ? path.join(configDir, ".claude.json")
+    : path.join(homedir, ".claude.json");
+}
+
+/**
+ * Whether Claude Code has recorded workspace trust for each directory.
+ *
+ * `true` and `false` come from Claude Code's own record
+ * (`projects[<dir>].hasTrustDialogAccepted`). A directory and the key Claude
+ * Code recorded can name the same place through different symlinks (macOS
+ * `/var` is `/private/var`), so a key matches when the two realpaths agree;
+ * only keys with the same final segment are resolved, so a large state file
+ * costs a handful of realpath calls. `unknown` means the record could not be
+ * read, so the operator still has to check that directory by hand.
+ * @param {{ dirs: string[], env?: Record<string, string | undefined>,
+ *   homedir: string, fs?: Pick<typeof nodeFs, "readFileSync" | "realpathSync"> }}
+ *   input - Worker directories, environment, home directory and fs seam
+ * @returns {{ file: string, dirs: Array<{ dir: string,
+ *   trusted: true | false | "unknown" }> }} One row per directory
+ */
+export function trustStatus({ dirs, env, homedir, fs = nodeFs }) {
+  const file = claudeStateFile({ env, homedir });
+  let projects = null;
+  try {
+    const parsed = JSON.parse(fs.readFileSync(file, "utf8"));
+    projects =
+      parsed && typeof parsed.projects === "object" ? parsed.projects : {};
+  } catch {
+    projects = null;
+  }
+  const realpath = dir => {
+    try {
+      return fs.realpathSync(dir);
+    } catch {
+      return dir;
+    }
+  };
+  const entryFor = dir => {
+    if (Object.hasOwn(projects, dir)) return projects[dir];
+    const target = realpath(dir);
+    const key = Object.keys(projects).find(
+      candidate =>
+        path.basename(candidate) === path.basename(dir) &&
+        realpath(candidate) === target
+    );
+    return key === undefined ? undefined : projects[key];
+  };
+  return {
+    file,
+    dirs: dirs.map(dir => {
+      if (projects === null) return { dir, trusted: "unknown" };
+      return { dir, trusted: entryFor(dir)?.hasTrustDialogAccepted === true };
+    }),
+  };
+}
+
+/**
+ * The last parseable record of a loop's run log, or null.
+ * @param {string} file - `.lisa/automations/runs/<loop>.jsonl`
+ * @param {Pick<typeof nodeFs, "readFileSync">} fs - Filesystem seam
+ * @returns {{ ts: string, outcome: string | null } | null} Last record
+ */
+function lastRunRecord(file, fs) {
+  let text;
+  try {
+    text = fs.readFileSync(file, "utf8");
+  } catch {
+    return null;
+  }
+  const lines = text.split("\n").filter(line => line.trim());
+  for (const line of lines.reverse()) {
+    try {
+      const record = JSON.parse(line);
+      if (
+        typeof record?.ts === "string" &&
+        !Number.isNaN(Date.parse(record.ts))
+      ) {
+        return { ts: record.ts, outcome: record.outcome ?? null };
+      }
+    } catch {
+      // A torn or foreign line: keep looking further back.
+    }
+  }
+  return null;
+}
+
+/**
+ * How long a loop may go without a recorded run and still count as live:
+ * twice the time the manager gives a silent worker before giving up on it
+ * (`stall.noOutputMinutes × stall.maxAttempts`), and never under a day.
+ * @param {{ noOutputMinutes?: number, maxAttempts?: number } | undefined} stall
+ *   - The manager's stall settings
+ * @returns {number} Milliseconds
+ */
+export function recentWindowMs(stall) {
+  const minutes = (stall?.noOutputMinutes ?? 60) * (stall?.maxAttempts ?? 3);
+  return Math.max(MIN_RECENT_MS, 2 * minutes * 60 * 1000);
+}
+
+/**
+ * What this project's own run logs say about each competing intake loop.
+ *
+ * A loop with a recent recorded run is probably still scheduled and will
+ * compete with the manager. A stale or missing log is evidence, not proof,
+ * that it stopped: the runtime's scheduler (claude.ai routines, Codex
+ * automations, GitHub Actions) is the authority, and setup lists it too.
+ * @param {{ root: string, now: Date, stall?: object,
+ *   fs?: Pick<typeof nodeFs, "readFileSync"> }} input - Project root, the
+ *   current time, the manager's stall settings and fs seam
+ * @returns {{ windowHours: number, loops: Array<{ loop: string,
+ *   log: string, lastRun: { ts: string, outcome: string | null } | null,
+ *   recent: boolean }> }} One row per competing loop
+ */
+export function coexistence({ root, now, stall, fs = nodeFs }) {
+  const windowMs = recentWindowMs(stall);
+  return {
+    windowHours: windowMs / 3_600_000,
+    loops: COMPETING_LOOPS.map(loop => {
+      const log = path.join(
+        root,
+        ".lisa",
+        "automations",
+        "runs",
+        `${loop}.jsonl`
+      );
+      const lastRun = lastRunRecord(log, fs);
+      const recent =
+        lastRun !== null && now.getTime() - Date.parse(lastRun.ts) <= windowMs;
+      return { loop, log, lastRun, recent };
+    }),
+  };
+}

package/plugins/lisa-agy/skills/lisa-session-manager/scripts/token.mjs

@@ -1,7 +1,8 @@
 /**
  * The Telegram bot token the manager needs: validated, stored in
  * `<stateDir>/.env` (dir 0700, file 0600), read from the operator's terminal
- * with echo off, and never put in argv, a return value, an error message or a
+ * with echo off or from the clipboard (`--from-clipboard`, for when no TTY is
+ * reachable), and never put in argv, a return value, an error message or a
  * log line. An existing token is replaced only on request. Split out of
  * launch.mjs, which re-exports everything here.
  * @module token
@@ -10,6 +11,7 @@ import { randomUUID } from "node:crypto";
 import * as nodeFs from "node:fs";
 import path from "node:path";
 
+import { readClipboard } from "./clipboard.mjs";
 import { LaunchError, resolveStateDir } from "./state-dir.mjs";
 
 /** The shape of a BotFather token: `<bot id>:<secret>`. */
@@ -94,41 +96,110 @@ function shellQuote(word) {
  *   input - Script and project locations, and whether to carry `--replace`
  * @returns {string} One shell line
  */
-export function buildStoreTokenCommand({ scriptsDir, projectRoot, replace }) {
+export function buildStoreTokenCommand({
+  scriptsDir,
+  projectRoot,
+  replace,
+  fromClipboard = false,
+}) {
   const script = shellQuote(path.join(scriptsDir, "session-manager.mjs"));
-  const flag = replace ? " --replace" : "";
-  return `node ${script} store-token${flag} --project-root ${shellQuote(projectRoot)}`;
+  const flags =
+    (replace ? " --replace" : "") + (fromClipboard ? " --from-clipboard" : "");
+  return `node ${script} store-token${flags} --project-root ${shellQuote(projectRoot)}`;
+}
+
+/** Why `store-token` cannot prompt here, and the two ways forward. */
+const NO_TTY_HINT =
+  "No terminal to prompt on, and Claude Code's ! prefix has no TTY either. " +
+  "Run `command` in a separate terminal app, or copy the token from " +
+  "BotFather and run `clipboardCommand`.";
+
+/** The `invalid` outcome; names the expected shape, never the input. */
+const INVALID = Object.freeze({
+  stored: false,
+  reason: "invalid",
+  message:
+    "That does not look like a Telegram bot token " +
+    "(expected <digits>:<30 or more letters, digits, _ or ->).",
+});
+
+/**
+ * Refuse to overwrite an existing token unless `replace` was asked for: a
+ * second project that shares this state dir by mistake would otherwise
+ * silently take over the first project's bot.
+ * @param {string} stateDir - Resolved state dir
+ * @param {boolean} replace - `--replace`
+ * @param {{ fs?: { existsSync?: (p: string) => boolean } }} io - Seams
+ */
+function assertReplaceable(stateDir, replace, io) {
+  const existing = path.join(stateDir, TOKEN_FILE_NAME);
+  const exists = io.fs?.existsSync ?? nodeFs.existsSync;
+  if (!replace && exists(existing)) {
+    throw new LaunchError(
+      `A bot token already exists at ${existing}. Nothing was changed. ` +
+        `Re-run store-token with --replace to overwrite it.`
+    );
+  }
+}
+
+/**
+ * Store the bot token from the system clipboard, with no TTY needed.
+ *
+ * Same validation and the same existing-token rule as the prompt. The
+ * clipboard is cleared only after a successful store, so a failed attempt
+ * leaves the operator's copy in place to retry with. The token is never
+ * returned, and an invalid value is reported by shape, never echoed.
+ * @param {{ stateDir: string, replace?: boolean,
+ *   env?: Record<string, string | undefined>, homedir?: string,
+ *   io?: { readClipboard?: typeof readClipboard, fs?: object } }} input -
+ *   Configured state dir, the `--replace` flag and seams
+ * @returns {{ stored: true, path: string, clipboardCleared: boolean } |
+ *   { stored: false, reason: "empty" | "invalid" | "unsupported" |
+ *     "unavailable" | "failed", message: string }} Outcome
+ */
+export function storeTokenFromClipboard(input) {
+  const { replace = false, io = {} } = input;
+  const stateDir = resolveStateDir(input.stateDir, input);
+  assertReplaceable(stateDir, replace, io);
+  const clip = (io.readClipboard ?? readClipboard)();
+  if (!clip.ok) {
+    return { stored: false, reason: clip.reason, message: clip.message };
+  }
+  const token = clip.text.trim();
+  if (!token) {
+    return {
+      stored: false,
+      reason: "empty",
+      message: "The clipboard is empty.",
+    };
+  }
+  if (!validateBotToken(token)) return { ...INVALID };
+  const written = writeTokenFile(stateDir, token, io);
+  return { stored: true, ...written, clipboardCleared: clip.clear() };
 }
 
 /**
  * Prompt for the bot token on the operator's terminal and store it.
  *
- * An existing token is never overwritten without `replace`: a second project
- * that shares this state dir by mistake would otherwise silently take over the
- * first project's bot. With no TTY this does not prompt and does not fail: it
- * returns the exact command for the operator to run themselves, because an
- * agent's Bash can never answer a prompt and a hung setup looks like a slow
- * one.
+ * An existing token is never overwritten without `replace`. With no TTY this
+ * does not prompt and does not fail: it returns the exact command for the
+ * operator to run in a separate terminal app, and the `--from-clipboard` form
+ * of it, because an agent's Bash (and Claude Code's `!` prefix) can never
+ * answer a prompt and a hung setup looks like a slow one.
  * @param {{ stateDir: string, scriptsDir: string, projectRoot: string,
  *   replace?: boolean, env?: Record<string, string | undefined>,
  *   homedir?: string, io?: { canPrompt?: () => boolean,
  *   promptSecret?: (message: string) => string, fs?: object } }} input -
  *   Configured state dir, locations, the `--replace` flag and seams
  * @returns {Promise<{ stored: true, path: string } |
- *   { stored: false, reason: "no-tty", command: string } |
+ *   { stored: false, reason: "no-tty", message: string, command: string,
+ *     clipboardCommand: string } |
  *   { stored: false, reason: "empty" | "invalid", message: string }>} Outcome
  */
 export async function storeToken(input) {
   const { scriptsDir, projectRoot, replace = false, io = {} } = input;
   const stateDir = resolveStateDir(input.stateDir, input);
-  const existing = path.join(stateDir, TOKEN_FILE_NAME);
-  const exists = io.fs?.existsSync ?? nodeFs.existsSync;
-  if (!replace && exists(existing)) {
-    throw new LaunchError(
-      `A bot token already exists at ${existing}. Nothing was changed. ` +
-        `Re-run store-token with --replace to overwrite it.`
-    );
-  }
+  assertReplaceable(stateDir, replace, io);
   const loaded =
     io.canPrompt && io.promptSecret ? null : await loadPromptSecret();
   const canPrompt = io.canPrompt ?? (() => loaded.canPrompt());
@@ -138,7 +209,14 @@ export async function storeToken(input) {
     return {
       stored: false,
       reason: "no-tty",
+      message: NO_TTY_HINT,
       command: buildStoreTokenCommand({ scriptsDir, projectRoot, replace }),
+      clipboardCommand: buildStoreTokenCommand({
+        scriptsDir,
+        projectRoot,
+        replace,
+        fromClipboard: true,
+      }),
     };
   }
   const typed = promptSecret(
@@ -147,15 +225,7 @@ export async function storeToken(input) {
   if (!typed) {
     return { stored: false, reason: "empty", message: "Nothing entered." };
   }
-  if (!validateBotToken(typed)) {
-    return {
-      stored: false,
-      reason: "invalid",
-      message:
-        "That does not look like a Telegram bot token " +
-        "(expected <digits>:<30 or more letters, digits, _ or ->).",
-    };
-  }
+  if (!validateBotToken(typed)) return { ...INVALID };
   return { stored: true, ...writeTokenFile(stateDir, typed, io) };
 }
 

package/plugins/lisa-agy/skills/lisa-setup-session-manager/SKILL.md

@@ -42,16 +42,31 @@ writes `$SM`, and pass `--project-root "$ROOT"` (the absolute project root) on e
 
 1. Preview: `node "$SM/session-manager.mjs" init-config --project-root "$ROOT"`. It detects
    `projects/*/.lisa.config.json` and proposes `name`, `interval`, `repos`, `capacity`, `stall` and a
-   per-project `notify.stateDir`. Show the block to the operator.
+   per-project `notify.stateDir`. Repo detection leaves out linked worktrees and keeps one checkout
+   per remote, so ticket worktrees and second clones under `projects/` are not proposed. Show the
+   block to the operator and ask whether any repo is missing or should not be routed.
 2. Write it: the same command with `--write`. It adds only non-secret fields and never overwrites an
    existing block (`reason: "exists"` means keep it).
-3. Ask the operator to replace each repo's starter `hints` with the technologies and areas that
-   identify it (e.g. `api`: `["NestJS","migrations"]`, `web`: `["Expo","screens"]`), and whether to
+3. Each repo's `hints` are a draft: its name plus one per well-known dependency (`NestJS`, `Expo`,
+   `AWS CDK`, ...). Ask the operator to correct them and add the areas that identify the repo
+   (e.g. `api`: `["NestJS","migrations"]`, `web`: `["Expo","screens"]`), and whether to
    set `sessionManager.trustedAuthorIds`. Without it, any author's Ready item reaches a
    bypass-permissions worker; say so plainly. The list holds stable tracker user ids as strings,
    never logins: the GitHub numeric user id (`gh api users/<login> --jq .id`), the Jira
    `accountId`, or the Linear user id. A login matches no one and silently excludes every item.
-4. `node "$SM/session-manager.mjs" validate --project-root "$ROOT"` must print `valid: true`.
+4. Set `sessionManager.operatorIds` to a non-empty **array** holding the operator's own tracker
+   user id, e.g. `"operatorIds": ["<operator-id>"]` (a bare string fails `validate`). Look up the
+   OPERATOR, not the credential: `gh api user` / `viewer.id` return whoever the tracker credential
+   belongs to, which is the agent account in exactly the case this key exists for. The manager dispatches
+   the operator's assigned items first, then items assigned to the tracker credential's identity
+   ("me"), then unassigned ones, and skips items assigned to anyone else. When the tracker
+   credential is not the operator's (an agent or bot account), leaving this unset means the
+   operator's own Ready items are never dispatched; say so plainly. Unlike `trustedAuthorIds`, this
+   is matched against the assignee, exactly and case-sensitively, so use the same kind of id as
+   "me", spelled as the tracker API returns it: the GitHub **login** (`gh api users/<login> --jq
+   .login`), the Jira `accountId`, or the Linear user id (the operator's entry in the team's member
+   list, or `viewer.id` only when the operator runs the lookup with their own credential).
+5. `node "$SM/session-manager.mjs" validate --project-root "$ROOT"` must print `valid: true`.
 
 ## Step 3: Store the bot token
 
@@ -61,8 +76,14 @@ The operator creates a bot with @BotFather, one per project. Then run
 - `stored: true`: done.
 - Exit 2 because a token already exists: keep it (re-running setup is safe). Only when the operator
   says the stored token is wrong or belongs to another project, re-run with `store-token --replace`.
-- `reason: "no-tty"` (an agent's Bash has no terminal): print `command` from the output and ask the
-  operator to run it in their own terminal, where it prompts with echo off. Wait for them to confirm.
+- `reason: "no-tty"` (an agent's Bash has no terminal): offer the operator both routes, and say
+  plainly that Claude Code's `!` prefix has no terminal either, so it fails the same way:
+  - **Clipboard (simplest):** they copy the token from the BotFather chat and tell you; then run
+    `clipboardCommand` from the output (`store-token --from-clipboard`). It validates the token,
+    stores it, never prints it, and clears the clipboard. On `stored: false`, say what `message`
+    reports and ask them to copy it again.
+  - **Separate terminal app:** print `command` and ask them to run it in Terminal, iTerm or similar,
+    outside the agent, where it prompts with echo off. Wait for them to confirm.
 - `empty` / `invalid`: say what was wrong and ask again.
 
 Never ask for the token in chat, never echo, log or commit it, and never put it in
@@ -97,14 +118,24 @@ If `.lisa/automations/session-manager.runbook.md` does not exist, copy
 `$SM/../references/runbook-template.md` there. Never overwrite an existing runbook: it is the
 project's. It is checked in, like every automation runbook (`automation-runbook-contract`).
 
-## Step 7: Coexistence warning
-
-Tell the operator, before starting: if this project also runs the scheduled `intake-repair` loop, it
-can re-dispatch an item a local worker is still building (it treats a claimed item with no tracker
-activity for `intake.repair.staleAfterHours` as stalled). `intake-tickets` competes for the same
-Ready items. Recommend tearing down `intake-tickets` (`/lisa:tear-down-automations intake-tickets`)
-and either raising `intake.repair.staleAfterHours` above `stall.noOutputMinutes × stall.maxAttempts`
-or tearing down `intake-repair`.
+## Step 7: Check for competing intake loops
+
+The scheduled `intake-repair` loop can re-dispatch an item a local worker is still building (it treats
+a claimed item with no tracker activity for `intake.repair.staleAfterHours` as stalled), and
+`intake-tickets` competes for the same Ready items. Find out whether either is running before you
+start the manager; do not leave the operator to check.
+
+1. Run `node "$SM/session-manager.mjs" coexistence --project-root "$ROOT"`. For each loop it reports
+   the last run recorded in this project's run log and whether that is `recent`. `live` lists the
+   loops that ran recently.
+2. A run log is evidence, not proof: also list your runtime's scheduler for those loop names (Claude
+   Code: the `/schedule` listing of claude.ai routines; Codex: automations; a `lisa-<loop>.yml`
+   workflow with a `schedule:` trigger on GitHub Actions).
+3. Report what you found, per loop, in one line each. Only for a loop that is live (a recent run, or a
+   scheduler entry): recommend tearing down `intake-tickets` (`/lisa:tear-down-automations
+   intake-tickets`) and either raising `intake.repair.staleAfterHours` above
+   `stall.noOutputMinutes × stall.maxAttempts` or tearing down `intake-repair`. When neither is live,
+   say so and move on.
 
 ## Step 8: Accept workspace trust in each worker repo
 
@@ -113,12 +144,15 @@ folder?" prompt: until someone has accepted it in a directory, `claude --bg` ref
 and `spawn` exits 2 saying so. Do this once per routed repo (or once for the root on a single-repo
 project), on every machine that runs the manager:
 
-1. List the directories workers start in. Single-repo: the project root. Multi-repo: for each key in
-   `sessionManager.repos.entries`,
-   `node "$SM/session-manager.mjs" repo-dir --repo <key> --raw --project-root "$ROOT"`.
-2. Ask the operator, in their own terminal, to run `claude` once in that directory,
-   accept the trust prompt, then exit. An agent's Bash cannot answer that prompt, so never try to
-   accept it for them.
+1. Run `node "$SM/session-manager.mjs" trust-status --project-root "$ROOT"`. It lists every
+   directory workers start in (each routed repo, or the root on a single-repo project) with whether
+   Claude Code has already recorded trust for it. `needsTrust` lists the ones that are not
+   `trusted: true`. When it is empty, this step is done: say so.
+2. For each directory in `needsTrust`, ask the operator, in a separate terminal app (not the agent's
+   Bash or Claude Code's `!` prefix), to run `claude` once in that directory, accept the trust prompt,
+   then exit. An agent's Bash cannot answer that prompt, so never try to accept it for them. Then
+   re-run `trust-status` to confirm. (`trusted: "unknown"` means Claude Code's state file could not be
+   read; treat it as needing trust.)
 3. Re-run this step whenever a repo is added to `sessionManager.repos`.
 
 ## Step 9: Start and pair
@@ -152,5 +186,6 @@ confirm the "Session manager Telegram isolation?" check is green. Fix every warn
 `node "$SM/session-manager.mjs" status --project-root "$ROOT"` should show the manager running.
 
 Report: the config block written (or kept), where the token lives (the path, never the value), the
-plugin scope result, the runbook path, which repo dirs had workspace trust accepted, the manager's
-tmux session name, and the doctor result.
+plugin scope result, the runbook path, which repo dirs were already trusted and which the operator
+accepted trust in, what the competing-loop check found, the manager's tmux session name, and the
+doctor result.

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "4.81.3",
+  "version": "4.81.5",
   "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.81.3",
+  "version": "4.81.5",
   "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.81.3",
+  "version": "4.81.5",
   "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.81.3",
+  "version": "4.81.5",
   "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.81.3",
+  "version": "4.81.5",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "4.81.3",
+  "version": "4.81.5",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

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

package/plugins/lisa-copilot/rules/reference/config-resolution.md

@@ -733,6 +733,7 @@ bypassed). `/lisa:setup:session-manager` writes it, detecting a multi-repo layou
 | `sessionManager.notify.provider` | no | `telegram` | Only `telegram` is implemented. |
 | `sessionManager.notify.stateDir` | **yes** | — | This project's own Telegram state dir. Never the shared default `~/.claude/channels/telegram`, because one bot per state dir is how projects stay isolated. Setup writes `~/.claude/channels/telegram-<project>`. |
 | `sessionManager.trustedAuthorIds` | no | — | Optional list of **stable tracker user ids**, as strings: the GitHub numeric user id (`gh api users/<login> --jq .id`), the Jira `accountId`, or the Linear user id. Not logins or display names: matching compares ids, so a login silently matches no one and excludes every item. When set, the manager takes only items authored by these people. |
+| `sessionManager.operatorIds` | no | — | Optional, non-empty list of the people the manager works for, as tracker user ids matched against the **assignee** the same way "me" is: the GitHub **login**, the Jira `accountId`, or the Linear user id, spelled exactly as the tracker API returns it (matching is case-sensitive, so look the OPERATOR up rather than typing from memory: `gh api users/<operator-login> --jq .login` returns the canonical GitHub spelling. Do not use `gh api user`, which returns whoever the credential belongs to — the agent account, when that is the case this key exists for). Dispatch order is assigned to an operator, then to "me" (the tracker credential's identity), then unassigned; items assigned to anyone else are skipped. Set it whenever the tracker credential is not the operator's own (an agent account), or the operator's Ready items are never dispatched. |
 
 - **Non-secret only.** The bot token lives in `<stateDir>/.env` (directory 0700, file 0600),
   written by setup. A credential-named field or a token-shaped value anywhere in this block is a

package/plugins/lisa-copilot/scripts/ready-queue-order.mjs

@@ -1,15 +1,20 @@
 #!/usr/bin/env node
 /**
- * Vendor-neutral Ready-queue normalization and mine-first dispatch order.
+ * Vendor-neutral Ready-queue normalization and operator-first dispatch order.
  *
  * ## Why this exists
  *
  * Intake has always taken Ready work in whatever order the tracker returned
  * it, and `intake.assignee` only NARROWS a selection — it never ranks one. A
  * dispatcher that runs several workers at once needs a stable answer to "what
- * next?": the work already assigned to me first (somebody chose me for it),
- * then unassigned work, most urgent and oldest first. Work assigned to someone
- * else is theirs, so it is excluded, never re-ordered.
+ * next?": work assigned to the operator first (the person the dispatcher works
+ * for), then work assigned to me (the identity the tracker credential belongs
+ * to, often an agent account rather than the operator), then unassigned work,
+ * most urgent and oldest first. Work assigned to anyone else is theirs, so it
+ * is excluded, never re-ordered. When the credential IS the operator's, the
+ * first two groups coincide. With "me" as the only identity, an operator whose
+ * credential is an agent account had every one of their own items excluded as
+ * someone else's (CodySwannGT/lisa#4467).
  *
  * The three trackers disagree on every field this needs — GitHub has priority
  * LABELS, Linear a native 0..4 number where 0 means "none", Jira a priority
@@ -252,12 +257,18 @@ function shape(input) {
  * Order matters only for the reason reported: an item can fail several rules,
  * and "someone else owns it" is the most useful thing to say about it.
  * @param {Record<string, any>} item
- * @param {{ me: string | null, trusted: ReadonlySet<string>, humanNeededLabel: string }} context
+ * @param {{ me: string | null, operators: ReadonlySet<string>, trusted: ReadonlySet<string>, humanNeededLabel: string }} context
  * @returns {string | null}
  */
 function exclusionReason(item, context) {
   const assignee = idOrNull(item.assigneeId);
-  if (assignee !== null && assignee !== context.me) return "assigned-to-other";
+  if (
+    assignee !== null &&
+    assignee !== context.me &&
+    !context.operators.has(assignee)
+  ) {
+    return "assigned-to-other";
+  }
   if (item.isContainer === true) return "container";
   if (
     isHumanGated({
@@ -293,20 +304,25 @@ function compareWithinGroup(left, right) {
 }
 
 /**
- * Order normalized Ready items for dispatch, mine first.
+ * Order normalized Ready items for dispatch: the operator's, then mine, then
+ * unassigned.
  *
- * Group 0 is assigned to `me`, group 1 unassigned; within a group, priority
- * rank ascending, then creation time ascending, then ref as a stable
- * tiebreak. Excluded items keep their input order. With no `me`, every
- * assigned item is someone else's — the safe direction, since claiming
- * assigned work steals it.
+ * Group 0 is assigned to an operator, group 1 to `me`, group 2 unassigned;
+ * within a group, priority rank ascending, then creation time ascending, then
+ * ref as a stable tiebreak. Excluded items keep their input order. With no
+ * `me` and no operators, every assigned item is someone else's — the safe
+ * direction, since claiming assigned work steals it.
+ *
+ * `operators` match the way `me` does, against the normalized assignee id:
+ * GitHub login, Jira accountId, Linear user id.
  * @param {readonly Record<string, any>[]} items - Normalized items
- * @param {{ me?: string | null, trustedAuthorIds?: readonly unknown[], humanNeededLabel?: string }} [options]
+ * @param {{ me?: string | null, operators?: readonly unknown[], trustedAuthorIds?: readonly unknown[], humanNeededLabel?: string }} [options]
  * @returns {{ ordered: Record<string, any>[], excluded: { ref: string, reason: string }[] }}
  */
 export function orderReadyQueue(items, options = {}) {
   const context = {
     me: idOrNull(options.me),
+    operators: new Set((options.operators ?? []).map(idOrNull).filter(Boolean)),
     trusted: new Set(
       (options.trustedAuthorIds ?? []).map(idOrNull).filter(Boolean)
     ),
@@ -319,7 +335,11 @@ export function orderReadyQueue(items, options = {}) {
   const eligible = judged
     .filter(one => one.reason === null)
     .map(one => one.item);
-  const group = item => (idOrNull(item.assigneeId) === null ? 1 : 0);
+  const group = item => {
+    const assignee = idOrNull(item.assigneeId);
+    if (assignee === null) return 2;
+    return context.operators.has(assignee) ? 0 : 1;
+  };
 
   return {
     ordered: [...eligible].sort(