@botbuddy/cli 1.44.1 → 1.45.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@botbuddy/cli",
-  "version": "1.44.1",
+  "version": "1.45.1",
   "description": "BotBuddy — Swarm coordination CLI for multi-agent workflows",
   "type": "module",
   "bin": {

package/src/wait-core.mjs

@@ -190,7 +190,8 @@ const VALIDATORS = {
     const id = hex ? `${hex.slice(0, 8)}-${hex.slice(8, 12)}-${hex.slice(12, 16)}-${hex.slice(16, 20)}-${hex.slice(20)}` : raw;
     return { id };
   },
-  // BOT-1064 — linear: wake on a logical state change of a named BOT-* issue.
+  // BOT-1064 / BOT-2112 — linear: wake on a logical state change of a named
+  // issue in any Linear team bound to the authenticated tenant.
   // The spine subject_key is the issue identifier as stored on the tickets
   // projection (upper-cased at write), so normalize to upper-case here too.
   linear(p) {
@@ -435,10 +436,13 @@ function prSubjectMatches(subjectKey, params) {
   return subjectKey.startsWith(`${params.repo}#`);
 }
 
-// Does a commit field on a signal payload start with the condition's sha prefix?
-// A missing / non-string field never matches a sha-scoped condition.
+// Does a commit field on a signal payload identify the same commit as the
+// condition's SHA? GitHub may send either side as a 7–40-character prefix, so
+// accept either prefix direction while refusing malformed payload values.
 function shaPrefixMatches(value, sha) {
-  return typeof value === "string" && value.trim().toLowerCase().startsWith(sha);
+  if (typeof value !== "string") return false;
+  const candidate = value.trim().toLowerCase();
+  return /^[0-9a-f]{7,40}$/.test(candidate) && (candidate.startsWith(sha) || sha.startsWith(candidate));
 }
 
 // BOT-1975: optional head scoping for pr-state. pr_state signals carry the PR

package/src/wait.mjs

@@ -78,8 +78,8 @@ CONDITIONS  (TYPE:key=val,key=val — repeat for several; --any wakes on the fir
                                       by the PR read model. Omit pr= to wake on ANY of your PRs
                                       in the repo; or pass pr=<owner/repo#n> in one value. A
                                       conflict/clean flip sets payload.mergeable_changed. The
-                                      payload carries head_ref_oid; sha=<head> (7-40 hex, a
-                                      prefix is fine) wakes only on signals for that head, so a
+                                      payload carries head_ref_oid; sha=<head> (7-40 hex; either
+                                      side may be an abbreviated prefix) wakes only on signals for that head, so a
                                       previous head's check result can't wake you. A push alone
                                       emits nothing — the head rides on the next transition.
   pr-review:repo=<owner/repo>[,pr=<n>][,reviewer=<login>][,sha=<commit>]
@@ -96,7 +96,7 @@ CONDITIONS  (TYPE:key=val,key=val — repeat for several; --any wakes on the fir
                                       existing review will not re-wake it.
                                       reviewer=<login> wakes only on that reviewer (case-
                                       insensitive; a trailing [bot] is ignored). sha=<commit>
-                                      wakes only on verdicts for that commit (submitted reviews
+                                      wakes only on verdicts for that commit (either side may be an abbreviated prefix; submitted reviews
                                       and clean passes carry commit_sha; thread comments do not,
                                       so they never match sha=); the usage-limit decline always
                                       passes sha=. Any other key is refused (exit 4).
@@ -108,8 +108,9 @@ CONDITIONS  (TYPE:key=val,key=val — repeat for several; --any wakes on the fir
   guidance:request=<post_id>          a command-post guidance request being answered
                                       (scoped to the asking agent; fetch the body with
                                       get_guidance_response)
-  linear:issue=<KEY>                  a BOT-* issue changing state, a new comment, or an
-                                      assignee change (e.g. issue=BOT-123; tenant-scoped).
+  linear:issue=<KEY>                  an issue in any Linear team bound to your tenant;
+                                      wakes on a state change, new comment, or assignee change (e.g.
+                                      issue=BOT-123; tenant-scoped).
                                       Flags linear_feed_lagging if the ingest feed has stalled.
   unblocked:<KEY>                     a ticket's LAST open blocker clearing (open-blocker
                                       count >0 → 0): a blocker moving to Done/Canceled/Duplicate
@@ -378,6 +379,10 @@ async function registerWait(opts, conditions, deadlineIso) {
       // wake-capable run for. The wait could only ever expire, and no amount of
       // waiting repairs a typo — a hard stop, with the server's candidates.
       "unknown_workflow",
+      // BOT-2112: these are arm-time authorization/target errors. Retrying as
+      // an untracked live-only wait would silently park on a signal it cannot
+      // receive, so preserve the relay's typed error and exit 4.
+      "linear_team_not_bound",
       // BOT-1612: a `chat:channel=<id>` wait whose bound agent is not one of the
       // channel's participants could only ever park to timeout (the emitter never
       // scopes a message to a non-participant). The relay refuses it at arm time;
@@ -395,6 +400,29 @@ async function registerWait(opts, conditions, deadlineIso) {
       throw err;
     }
   }
+  if (res.status === 404) {
+    const body = await res.json().catch(() => ({}));
+    if (body.error === "linear_issue_not_found") {
+      const err = new Error(body.detail || body.error);
+      err.invalidCondition = true;
+      err.errorCode = body.error;
+      if (Array.isArray(body.candidates)) err.candidates = body.candidates;
+      throw err;
+    }
+    // BOT-1523 retains its existing not-found contract. Keep every 404's body
+    // handling in one branch: parsing it above and falling through would consume
+    // the body before this typed unblocked refusal could see it.
+    if (body.error === "unblocked_ticket_not_found") {
+      const err = new Error(body.detail || body.error);
+      err.hydrationRegister = true;
+      err.errorCode = body.error;
+      err.ticket = body.ticket ?? null;
+      err.retryable = body.retryable ?? null;
+      err.hydration = body.hydration ?? null;
+      err.notFound = true;
+      throw err;
+    }
+  }
   if (res.status === 403) {
     const body = await res.json().catch(() => ({}));
     if (new Set(["wait_tenant_unresolved", "wait_cross_tenant", "wait_tenant_mismatch", "wait_resume_identity_mismatch"]).has(body.error)) {
@@ -427,7 +455,7 @@ async function registerWait(opts, conditions, deadlineIso) {
     err.minimumProtocol = body.minimum_wait_protocol ?? null;
     throw err;
   }
-  if (res.status === 409 || res.status === 404) {
+  if (res.status === 409) {
     // BOT-1523: `unblocked:<KEY>` hydration at registration could not arm the wait
     // truthfully. These are NOT the untracked-live-only fallback: arming a live-only
     // unblocked wait would skip the server's initial evaluation and could resume a