@integrity-labs/agt-cli 0.28.922 → 0.28.924

package/dist/mcp/direct-chat-channel.js

@@ -35092,13 +35092,16 @@ function parseResetDateTime(humanDate, now) {
 
 // ../core/dist/claude-code-usage/banner-parser.js
 var SESSION_QUALIFIER = /^(?:session|\d{1,2}\s*-?\s*hours?|\d{1,2}h)$/i;
-var SPEND_QUALIFIER = /^(?:individual\s+)?spend$/i;
+var SPEND_QUALIFIER = /^(?:individual\s+)?(?:(?:daily|weekly|monthly)\s+)?spend$/i;
+var ORG_SPEND_QUALIFIER = /^(?:your\s+)?(?:org|organi[sz]ation|team|workspace)['’]s\s+(?:(?:daily|weekly|monthly)\s+)?spend$/i;
 function classifyLimitScope(qualifier) {
   const q = (qualifier ?? "").trim();
   if (!q)
     return "weekly";
   if (SESSION_QUALIFIER.test(q))
     return "session";
+  if (ORG_SPEND_QUALIFIER.test(q))
+    return "org_spend";
   if (SPEND_QUALIFIER.test(q))
     return "spend";
   if (/^weekly$/i.test(q))
@@ -35135,7 +35138,13 @@ var BANNER_PATTERNS = [
     // "limit". This parser runs over agent-produced pane.log tails, so that is
     // reachable input. Requiring at least one separator per extra token, and
     // bounding the count, keeps it linear.
-    `${SUBJECT}hit\\s+your\\s+(?<qualifier>[a-z0-9]+(?:[\\s-]+[a-z0-9]+){0,3}\\s+)?limit${SEP}resets\\s+(?<reset>${RESET_DATE})`,
+    //
+    // ENG-10474: the token class admits an apostrophe (both ' and ’). It was
+    // `[a-z0-9]`, so ANY possessive qualifier ("org's monthly", "team's") made
+    // the whole banner unmatchable, not merely unclassified: null, no
+    // observation, no alert. The apostrophe cannot match empty, so the
+    // at-least-one-separator shape above still keeps this linear.
+    `${SUBJECT}hit\\s+your\\s+(?<qualifier>[a-z0-9'\u2019]+(?:[\\s-]+[a-z0-9'\u2019]+){0,3}\\s+)?limit${SEP}resets\\s+(?<reset>${RESET_DATE})`,
     "i"
   ),
   // ENG-10365 — the Claude Team seat's INDIVIDUAL SPEND LIMIT.
@@ -35188,7 +35197,23 @@ var BANNER_PATTERNS = [
   // monitor's auto-close, and synthesising an instant we never read is the exact
   // confident-and-false reporting ENG-8901 exists to stop. Every spend banner
   // observed so far carries one.
-  new RegExp(`${SUBJECT}hit\\s+your\\s+(?<qualifier>(?:individual\\s+)?spend)\\s+limit[\\s\\S]{0,160}?resets\\s+(?<reset>${RESET_DATE})`, "i")
+  //
+  // ENG-10474 — THE CAPTURE NO LONGER GATES THE CLASSIFIER. It admitted exactly
+  // `spend` or `individual spend`, so "You've hit your org's monthly spend
+  // limit" failed here as well as in both patterns above and alyve's agents went
+  // dark with every platform signal green. The capture now takes up to three
+  // qualifier tokens (apostrophes allowed) in front of `spend`, and
+  // `classifyLimitScope` decides what they mean, which is how pattern 2 already
+  // worked.
+  //
+  // `spend` STAYS THE ANCHOR, and that is the design decision. Making this
+  // capture as open as pattern 2's would turn it into "any saturated banner with
+  // up to 160 characters before `resets`", so "You've hit your weekly limit"
+  // followed by pane prose and an unrelated "resets Nov 28" would start
+  // producing observations — the false-pairing surface the 160-character bound
+  // exists to fence. Pattern 2 keeps its adjacency rule for every non-spend
+  // qualifier; this pattern only widens WHICH spend. Pinned by a test either way.
+  new RegExp(`${SUBJECT}hit\\s+your\\s+(?<qualifier>(?:[a-z0-9'\u2019]+[\\s-]+){0,3}spend)\\s+limit[\\s\\S]{0,160}?resets\\s+(?<reset>${RESET_DATE})`, "i")
 ];
 function parseUsageBanner(text, now = /* @__PURE__ */ new Date()) {
   let bestIndex = -1;

package/dist/mcp/index.js

@@ -27761,7 +27761,13 @@ var BANNER_PATTERNS = [
     // "limit". This parser runs over agent-produced pane.log tails, so that is
     // reachable input. Requiring at least one separator per extra token, and
     // bounding the count, keeps it linear.
-    `${SUBJECT}hit\\s+your\\s+(?<qualifier>[a-z0-9]+(?:[\\s-]+[a-z0-9]+){0,3}\\s+)?limit${SEP}resets\\s+(?<reset>${RESET_DATE})`,
+    //
+    // ENG-10474: the token class admits an apostrophe (both ' and ’). It was
+    // `[a-z0-9]`, so ANY possessive qualifier ("org's monthly", "team's") made
+    // the whole banner unmatchable, not merely unclassified: null, no
+    // observation, no alert. The apostrophe cannot match empty, so the
+    // at-least-one-separator shape above still keeps this linear.
+    `${SUBJECT}hit\\s+your\\s+(?<qualifier>[a-z0-9'\u2019]+(?:[\\s-]+[a-z0-9'\u2019]+){0,3}\\s+)?limit${SEP}resets\\s+(?<reset>${RESET_DATE})`,
     "i"
   ),
   // ENG-10365 — the Claude Team seat's INDIVIDUAL SPEND LIMIT.
@@ -27814,7 +27820,23 @@ var BANNER_PATTERNS = [
   // monitor's auto-close, and synthesising an instant we never read is the exact
   // confident-and-false reporting ENG-8901 exists to stop. Every spend banner
   // observed so far carries one.
-  new RegExp(`${SUBJECT}hit\\s+your\\s+(?<qualifier>(?:individual\\s+)?spend)\\s+limit[\\s\\S]{0,160}?resets\\s+(?<reset>${RESET_DATE})`, "i")
+  //
+  // ENG-10474 — THE CAPTURE NO LONGER GATES THE CLASSIFIER. It admitted exactly
+  // `spend` or `individual spend`, so "You've hit your org's monthly spend
+  // limit" failed here as well as in both patterns above and alyve's agents went
+  // dark with every platform signal green. The capture now takes up to three
+  // qualifier tokens (apostrophes allowed) in front of `spend`, and
+  // `classifyLimitScope` decides what they mean, which is how pattern 2 already
+  // worked.
+  //
+  // `spend` STAYS THE ANCHOR, and that is the design decision. Making this
+  // capture as open as pattern 2's would turn it into "any saturated banner with
+  // up to 160 characters before `resets`", so "You've hit your weekly limit"
+  // followed by pane prose and an unrelated "resets Nov 28" would start
+  // producing observations — the false-pairing surface the 160-character bound
+  // exists to fence. Pattern 2 keeps its adjacency rule for every non-spend
+  // qualifier; this pattern only widens WHICH spend. Pinned by a test either way.
+  new RegExp(`${SUBJECT}hit\\s+your\\s+(?<qualifier>(?:[a-z0-9'\u2019]+[\\s-]+){0,3}spend)\\s+limit[\\s\\S]{0,160}?resets\\s+(?<reset>${RESET_DATE})`, "i")
 ];
 
 // ../core/dist/claude-code-usage/run-marker.js

package/dist/mcp/origami.js

@@ -41683,7 +41683,13 @@ var BANNER_PATTERNS = [
     // "limit". This parser runs over agent-produced pane.log tails, so that is
     // reachable input. Requiring at least one separator per extra token, and
     // bounding the count, keeps it linear.
-    `${SUBJECT}hit\\s+your\\s+(?<qualifier>[a-z0-9]+(?:[\\s-]+[a-z0-9]+){0,3}\\s+)?limit${SEP}resets\\s+(?<reset>${RESET_DATE})`,
+    //
+    // ENG-10474: the token class admits an apostrophe (both ' and ’). It was
+    // `[a-z0-9]`, so ANY possessive qualifier ("org's monthly", "team's") made
+    // the whole banner unmatchable, not merely unclassified: null, no
+    // observation, no alert. The apostrophe cannot match empty, so the
+    // at-least-one-separator shape above still keeps this linear.
+    `${SUBJECT}hit\\s+your\\s+(?<qualifier>[a-z0-9'\u2019]+(?:[\\s-]+[a-z0-9'\u2019]+){0,3}\\s+)?limit${SEP}resets\\s+(?<reset>${RESET_DATE})`,
     "i"
   ),
   // ENG-10365 — the Claude Team seat's INDIVIDUAL SPEND LIMIT.
@@ -41736,7 +41742,23 @@ var BANNER_PATTERNS = [
   // monitor's auto-close, and synthesising an instant we never read is the exact
   // confident-and-false reporting ENG-8901 exists to stop. Every spend banner
   // observed so far carries one.
-  new RegExp(`${SUBJECT}hit\\s+your\\s+(?<qualifier>(?:individual\\s+)?spend)\\s+limit[\\s\\S]{0,160}?resets\\s+(?<reset>${RESET_DATE})`, "i")
+  //
+  // ENG-10474 — THE CAPTURE NO LONGER GATES THE CLASSIFIER. It admitted exactly
+  // `spend` or `individual spend`, so "You've hit your org's monthly spend
+  // limit" failed here as well as in both patterns above and alyve's agents went
+  // dark with every platform signal green. The capture now takes up to three
+  // qualifier tokens (apostrophes allowed) in front of `spend`, and
+  // `classifyLimitScope` decides what they mean, which is how pattern 2 already
+  // worked.
+  //
+  // `spend` STAYS THE ANCHOR, and that is the design decision. Making this
+  // capture as open as pattern 2's would turn it into "any saturated banner with
+  // up to 160 characters before `resets`", so "You've hit your weekly limit"
+  // followed by pane prose and an unrelated "resets Nov 28" would start
+  // producing observations — the false-pairing surface the 160-character bound
+  // exists to fence. Pattern 2 keeps its adjacency rule for every non-spend
+  // qualifier; this pattern only widens WHICH spend. Pinned by a test either way.
+  new RegExp(`${SUBJECT}hit\\s+your\\s+(?<qualifier>(?:[a-z0-9'\u2019]+[\\s-]+){0,3}spend)\\s+limit[\\s\\S]{0,160}?resets\\s+(?<reset>${RESET_DATE})`, "i")
 ];
 
 // ../core/dist/claude-code-usage/run-marker.js

package/dist/mcp/slack-channel.js

@@ -35965,13 +35965,16 @@ function parseResetDateTime(humanDate, now) {
 
 // ../core/dist/claude-code-usage/banner-parser.js
 var SESSION_QUALIFIER = /^(?:session|\d{1,2}\s*-?\s*hours?|\d{1,2}h)$/i;
-var SPEND_QUALIFIER = /^(?:individual\s+)?spend$/i;
+var SPEND_QUALIFIER = /^(?:individual\s+)?(?:(?:daily|weekly|monthly)\s+)?spend$/i;
+var ORG_SPEND_QUALIFIER = /^(?:your\s+)?(?:org|organi[sz]ation|team|workspace)['’]s\s+(?:(?:daily|weekly|monthly)\s+)?spend$/i;
 function classifyLimitScope(qualifier) {
   const q = (qualifier ?? "").trim();
   if (!q)
     return "weekly";
   if (SESSION_QUALIFIER.test(q))
     return "session";
+  if (ORG_SPEND_QUALIFIER.test(q))
+    return "org_spend";
   if (SPEND_QUALIFIER.test(q))
     return "spend";
   if (/^weekly$/i.test(q))
@@ -36008,7 +36011,13 @@ var BANNER_PATTERNS = [
     // "limit". This parser runs over agent-produced pane.log tails, so that is
     // reachable input. Requiring at least one separator per extra token, and
     // bounding the count, keeps it linear.
-    `${SUBJECT}hit\\s+your\\s+(?<qualifier>[a-z0-9]+(?:[\\s-]+[a-z0-9]+){0,3}\\s+)?limit${SEP}resets\\s+(?<reset>${RESET_DATE})`,
+    //
+    // ENG-10474: the token class admits an apostrophe (both ' and ’). It was
+    // `[a-z0-9]`, so ANY possessive qualifier ("org's monthly", "team's") made
+    // the whole banner unmatchable, not merely unclassified: null, no
+    // observation, no alert. The apostrophe cannot match empty, so the
+    // at-least-one-separator shape above still keeps this linear.
+    `${SUBJECT}hit\\s+your\\s+(?<qualifier>[a-z0-9'\u2019]+(?:[\\s-]+[a-z0-9'\u2019]+){0,3}\\s+)?limit${SEP}resets\\s+(?<reset>${RESET_DATE})`,
     "i"
   ),
   // ENG-10365 — the Claude Team seat's INDIVIDUAL SPEND LIMIT.
@@ -36061,7 +36070,23 @@ var BANNER_PATTERNS = [
   // monitor's auto-close, and synthesising an instant we never read is the exact
   // confident-and-false reporting ENG-8901 exists to stop. Every spend banner
   // observed so far carries one.
-  new RegExp(`${SUBJECT}hit\\s+your\\s+(?<qualifier>(?:individual\\s+)?spend)\\s+limit[\\s\\S]{0,160}?resets\\s+(?<reset>${RESET_DATE})`, "i")
+  //
+  // ENG-10474 — THE CAPTURE NO LONGER GATES THE CLASSIFIER. It admitted exactly
+  // `spend` or `individual spend`, so "You've hit your org's monthly spend
+  // limit" failed here as well as in both patterns above and alyve's agents went
+  // dark with every platform signal green. The capture now takes up to three
+  // qualifier tokens (apostrophes allowed) in front of `spend`, and
+  // `classifyLimitScope` decides what they mean, which is how pattern 2 already
+  // worked.
+  //
+  // `spend` STAYS THE ANCHOR, and that is the design decision. Making this
+  // capture as open as pattern 2's would turn it into "any saturated banner with
+  // up to 160 characters before `resets`", so "You've hit your weekly limit"
+  // followed by pane prose and an unrelated "resets Nov 28" would start
+  // producing observations — the false-pairing surface the 160-character bound
+  // exists to fence. Pattern 2 keeps its adjacency rule for every non-spend
+  // qualifier; this pattern only widens WHICH spend. Pinned by a test either way.
+  new RegExp(`${SUBJECT}hit\\s+your\\s+(?<qualifier>(?:[a-z0-9'\u2019]+[\\s-]+){0,3}spend)\\s+limit[\\s\\S]{0,160}?resets\\s+(?<reset>${RESET_DATE})`, "i")
 ];
 function parseUsageBanner(text, now = /* @__PURE__ */ new Date()) {
   let bestIndex = -1;

package/dist/mcp/telegram-channel.js

@@ -36001,13 +36001,16 @@ function parseResetDateTime(humanDate, now) {
 
 // ../core/dist/claude-code-usage/banner-parser.js
 var SESSION_QUALIFIER = /^(?:session|\d{1,2}\s*-?\s*hours?|\d{1,2}h)$/i;
-var SPEND_QUALIFIER = /^(?:individual\s+)?spend$/i;
+var SPEND_QUALIFIER = /^(?:individual\s+)?(?:(?:daily|weekly|monthly)\s+)?spend$/i;
+var ORG_SPEND_QUALIFIER = /^(?:your\s+)?(?:org|organi[sz]ation|team|workspace)['’]s\s+(?:(?:daily|weekly|monthly)\s+)?spend$/i;
 function classifyLimitScope(qualifier) {
   const q = (qualifier ?? "").trim();
   if (!q)
     return "weekly";
   if (SESSION_QUALIFIER.test(q))
     return "session";
+  if (ORG_SPEND_QUALIFIER.test(q))
+    return "org_spend";
   if (SPEND_QUALIFIER.test(q))
     return "spend";
   if (/^weekly$/i.test(q))
@@ -36044,7 +36047,13 @@ var BANNER_PATTERNS = [
     // "limit". This parser runs over agent-produced pane.log tails, so that is
     // reachable input. Requiring at least one separator per extra token, and
     // bounding the count, keeps it linear.
-    `${SUBJECT}hit\\s+your\\s+(?<qualifier>[a-z0-9]+(?:[\\s-]+[a-z0-9]+){0,3}\\s+)?limit${SEP}resets\\s+(?<reset>${RESET_DATE})`,
+    //
+    // ENG-10474: the token class admits an apostrophe (both ' and ’). It was
+    // `[a-z0-9]`, so ANY possessive qualifier ("org's monthly", "team's") made
+    // the whole banner unmatchable, not merely unclassified: null, no
+    // observation, no alert. The apostrophe cannot match empty, so the
+    // at-least-one-separator shape above still keeps this linear.
+    `${SUBJECT}hit\\s+your\\s+(?<qualifier>[a-z0-9'\u2019]+(?:[\\s-]+[a-z0-9'\u2019]+){0,3}\\s+)?limit${SEP}resets\\s+(?<reset>${RESET_DATE})`,
     "i"
   ),
   // ENG-10365 — the Claude Team seat's INDIVIDUAL SPEND LIMIT.
@@ -36097,7 +36106,23 @@ var BANNER_PATTERNS = [
   // monitor's auto-close, and synthesising an instant we never read is the exact
   // confident-and-false reporting ENG-8901 exists to stop. Every spend banner
   // observed so far carries one.
-  new RegExp(`${SUBJECT}hit\\s+your\\s+(?<qualifier>(?:individual\\s+)?spend)\\s+limit[\\s\\S]{0,160}?resets\\s+(?<reset>${RESET_DATE})`, "i")
+  //
+  // ENG-10474 — THE CAPTURE NO LONGER GATES THE CLASSIFIER. It admitted exactly
+  // `spend` or `individual spend`, so "You've hit your org's monthly spend
+  // limit" failed here as well as in both patterns above and alyve's agents went
+  // dark with every platform signal green. The capture now takes up to three
+  // qualifier tokens (apostrophes allowed) in front of `spend`, and
+  // `classifyLimitScope` decides what they mean, which is how pattern 2 already
+  // worked.
+  //
+  // `spend` STAYS THE ANCHOR, and that is the design decision. Making this
+  // capture as open as pattern 2's would turn it into "any saturated banner with
+  // up to 160 characters before `resets`", so "You've hit your weekly limit"
+  // followed by pane prose and an unrelated "resets Nov 28" would start
+  // producing observations — the false-pairing surface the 160-character bound
+  // exists to fence. Pattern 2 keeps its adjacency rule for every non-spend
+  // qualifier; this pattern only widens WHICH spend. Pinned by a test either way.
+  new RegExp(`${SUBJECT}hit\\s+your\\s+(?<qualifier>(?:[a-z0-9'\u2019]+[\\s-]+){0,3}spend)\\s+limit[\\s\\S]{0,160}?resets\\s+(?<reset>${RESET_DATE})`, "i")
 ];
 function parseUsageBanner(text, now = /* @__PURE__ */ new Date()) {
   let bestIndex = -1;

package/dist/{persistent-session-OQRYZ3YP.js → persistent-session-UEAJJ72P.js}

@@ -62,8 +62,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-NGJFE75J.js";
-import "./chunk-ZOPP3ZC7.js";
+} from "./chunk-BLEV5PAO.js";
+import "./chunk-VHO7KAB7.js";
 import "./chunk-XWVM4KPK.js";
 export {
   CLAUDE_HOST_WIDE,
@@ -130,4 +130,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-OQRYZ3YP.js.map
+//# sourceMappingURL=persistent-session-UEAJJ72P.js.map

package/dist/{responsiveness-probe-RBWP6HJE.js → responsiveness-probe-VXJKA6RF.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-NGJFE75J.js";
-import "./chunk-ZOPP3ZC7.js";
+} from "./chunk-BLEV5PAO.js";
+import "./chunk-VHO7KAB7.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -799,4 +799,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-RBWP6HJE.js.map
+//# sourceMappingURL=responsiveness-probe-VXJKA6RF.js.map

package/dist/{session-auth-dead-4KUPTD7M.js → session-auth-dead-XOP4XYBD.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-ZOPP3ZC7.js";
+} from "./chunk-VHO7KAB7.js";
 
 // src/lib/session-auth-dead.ts
 import { closeSync, openSync, readSync, readdirSync, statSync } from "fs";
@@ -203,4 +203,4 @@ export {
   decideSessionAuthState,
   probeSessionAuth
 };
-//# sourceMappingURL=session-auth-dead-4KUPTD7M.js.map
+//# sourceMappingURL=session-auth-dead-XOP4XYBD.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integrity-labs/agt-cli",
-  "version": "0.28.922",
+  "version": "0.28.924",
   "description": "Augmented Team CLI — agent provisioning and management",
   "type": "module",
   "engines": {