@integrity-labs/agt-cli 0.28.896 → 0.28.898

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

@@ -35085,12 +35085,15 @@ 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;
 function classifyLimitScope(qualifier) {
   const q = (qualifier ?? "").trim();
   if (!q)
     return "weekly";
   if (SESSION_QUALIFIER.test(q))
     return "session";
+  if (SPEND_QUALIFIER.test(q))
+    return "spend";
   if (/^weekly$/i.test(q))
     return "weekly";
   return "unknown";
@@ -35127,7 +35130,58 @@ var BANNER_PATTERNS = [
     // 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})`,
     "i"
-  )
+  ),
+  // ENG-10365 — the Claude Team seat's INDIVIDUAL SPEND LIMIT.
+  //
+  // WHY THE TWO PATTERNS ABOVE CANNOT MATCH IT. Both require `limit` to be
+  // followed immediately by a separator and then `resets`. The spend banner puts
+  // its remedy between the two:
+  //
+  //   You've hit your individual spend limit · run /usage-credits to ask your
+  //   admin for a higher limit · your weekly limit resets Sep 12, 5pm (UTC)
+  //   Continuing automatically at Sep 12, 5pm · esc to cancel
+  //
+  // so the adjacency fails and `parseUsageBanner` returned null — verified
+  // against origin/main on the verbatim pane capture in ENG-10365 before this
+  // pattern was written. Null means NO observation is POSTed, which means the
+  // `claude_code_usage_observations` row never exists, which means
+  // `usage-limit-monitor` never hears of the agent at all. cindy ran zero-second
+  // turns for ~32 hours with `heartbeat_verdict fresh` and no usage alert of any
+  // kind, because the whole chain starts here.
+  //
+  // THE GAP IS BOUNDED AND LAZY, deliberately. The real banner's gap is ~78
+  // characters; 160 leaves 2x headroom for phrasing drift and for the pane's own
+  // line wrap (which lands mid-sentence, as above, so `[\s\S]` and not `.`).
+  // Lazy + bounded keeps it linear on the pane.log tails this parser runs over —
+  // the same reason the saturated pattern refuses the naive `(a+)+` shape.
+  //
+  // WHAT IT INHERITS BY MATCHING AT ALL. Everything downstream keys on the
+  // `usage_limit_reached` ALERT KIND rather than on the scope, so one matching
+  // banner reaches the roster's `usage_limit_alert_open` flag (ENG-9634),
+  // `resolveCappedAgents`, and both monitors that suppress on a capped agent.
+  // That is why this fix is a regex and not a subsystem.
+  //
+  // AND A SECOND CONSUMER, which is worth stating precisely because it is easy
+  // to overclaim. `rate-limit-classifier.ts:160` calls this parser to read the
+  // RESET TIME out of a `rate_limit` / 429 transcript refusal, and
+  // `readUsageCapUntil` (agent-serving-probe.ts:296) returns null — i.e. does NOT
+  // defer — when that reset comes back null. So a parse failure here has always
+  // disarmed the ENG-8197 host-side dispatch deferral for this banner, which
+  // would explain cindy being dispatched into hourly while visibly blocked.
+  //
+  // NOT VERIFIED, and deliberately not claimed: whether a spend refusal is
+  // written to the transcript as `error: 'rate_limit'` / `apiErrorStatus: 429`
+  // at all. The classifier's verdict keys on those fields, not on this text. If
+  // it is, the deferral starts working as a side effect of this fix; if it is
+  // not, ENG-8197 is still blind to the spend ceiling and that is a separate
+  // ticket. Nothing here depends on which.
+  //
+  // KNOWN LIMIT, stated rather than papered over: a spend banner that carries no
+  // `resets` clause at all still yields null. `week_resets_at` drives the
+  // 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")
 ];
 function parseUsageBanner(text, now = /* @__PURE__ */ new Date()) {
   let bestIndex = -1;

package/dist/mcp/index.js

@@ -27729,7 +27729,58 @@ var BANNER_PATTERNS = [
     // 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})`,
     "i"
-  )
+  ),
+  // ENG-10365 — the Claude Team seat's INDIVIDUAL SPEND LIMIT.
+  //
+  // WHY THE TWO PATTERNS ABOVE CANNOT MATCH IT. Both require `limit` to be
+  // followed immediately by a separator and then `resets`. The spend banner puts
+  // its remedy between the two:
+  //
+  //   You've hit your individual spend limit · run /usage-credits to ask your
+  //   admin for a higher limit · your weekly limit resets Sep 12, 5pm (UTC)
+  //   Continuing automatically at Sep 12, 5pm · esc to cancel
+  //
+  // so the adjacency fails and `parseUsageBanner` returned null — verified
+  // against origin/main on the verbatim pane capture in ENG-10365 before this
+  // pattern was written. Null means NO observation is POSTed, which means the
+  // `claude_code_usage_observations` row never exists, which means
+  // `usage-limit-monitor` never hears of the agent at all. cindy ran zero-second
+  // turns for ~32 hours with `heartbeat_verdict fresh` and no usage alert of any
+  // kind, because the whole chain starts here.
+  //
+  // THE GAP IS BOUNDED AND LAZY, deliberately. The real banner's gap is ~78
+  // characters; 160 leaves 2x headroom for phrasing drift and for the pane's own
+  // line wrap (which lands mid-sentence, as above, so `[\s\S]` and not `.`).
+  // Lazy + bounded keeps it linear on the pane.log tails this parser runs over —
+  // the same reason the saturated pattern refuses the naive `(a+)+` shape.
+  //
+  // WHAT IT INHERITS BY MATCHING AT ALL. Everything downstream keys on the
+  // `usage_limit_reached` ALERT KIND rather than on the scope, so one matching
+  // banner reaches the roster's `usage_limit_alert_open` flag (ENG-9634),
+  // `resolveCappedAgents`, and both monitors that suppress on a capped agent.
+  // That is why this fix is a regex and not a subsystem.
+  //
+  // AND A SECOND CONSUMER, which is worth stating precisely because it is easy
+  // to overclaim. `rate-limit-classifier.ts:160` calls this parser to read the
+  // RESET TIME out of a `rate_limit` / 429 transcript refusal, and
+  // `readUsageCapUntil` (agent-serving-probe.ts:296) returns null — i.e. does NOT
+  // defer — when that reset comes back null. So a parse failure here has always
+  // disarmed the ENG-8197 host-side dispatch deferral for this banner, which
+  // would explain cindy being dispatched into hourly while visibly blocked.
+  //
+  // NOT VERIFIED, and deliberately not claimed: whether a spend refusal is
+  // written to the transcript as `error: 'rate_limit'` / `apiErrorStatus: 429`
+  // at all. The classifier's verdict keys on those fields, not on this text. If
+  // it is, the deferral starts working as a side effect of this fix; if it is
+  // not, ENG-8197 is still blind to the spend ceiling and that is a separate
+  // ticket. Nothing here depends on which.
+  //
+  // KNOWN LIMIT, stated rather than papered over: a spend banner that carries no
+  // `resets` clause at all still yields null. `week_resets_at` drives the
+  // 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")
 ];
 
 // ../core/dist/claude-code-usage/run-marker.js

package/dist/mcp/origami.js

@@ -41678,7 +41678,58 @@ var BANNER_PATTERNS = [
     // 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})`,
     "i"
-  )
+  ),
+  // ENG-10365 — the Claude Team seat's INDIVIDUAL SPEND LIMIT.
+  //
+  // WHY THE TWO PATTERNS ABOVE CANNOT MATCH IT. Both require `limit` to be
+  // followed immediately by a separator and then `resets`. The spend banner puts
+  // its remedy between the two:
+  //
+  //   You've hit your individual spend limit · run /usage-credits to ask your
+  //   admin for a higher limit · your weekly limit resets Sep 12, 5pm (UTC)
+  //   Continuing automatically at Sep 12, 5pm · esc to cancel
+  //
+  // so the adjacency fails and `parseUsageBanner` returned null — verified
+  // against origin/main on the verbatim pane capture in ENG-10365 before this
+  // pattern was written. Null means NO observation is POSTed, which means the
+  // `claude_code_usage_observations` row never exists, which means
+  // `usage-limit-monitor` never hears of the agent at all. cindy ran zero-second
+  // turns for ~32 hours with `heartbeat_verdict fresh` and no usage alert of any
+  // kind, because the whole chain starts here.
+  //
+  // THE GAP IS BOUNDED AND LAZY, deliberately. The real banner's gap is ~78
+  // characters; 160 leaves 2x headroom for phrasing drift and for the pane's own
+  // line wrap (which lands mid-sentence, as above, so `[\s\S]` and not `.`).
+  // Lazy + bounded keeps it linear on the pane.log tails this parser runs over —
+  // the same reason the saturated pattern refuses the naive `(a+)+` shape.
+  //
+  // WHAT IT INHERITS BY MATCHING AT ALL. Everything downstream keys on the
+  // `usage_limit_reached` ALERT KIND rather than on the scope, so one matching
+  // banner reaches the roster's `usage_limit_alert_open` flag (ENG-9634),
+  // `resolveCappedAgents`, and both monitors that suppress on a capped agent.
+  // That is why this fix is a regex and not a subsystem.
+  //
+  // AND A SECOND CONSUMER, which is worth stating precisely because it is easy
+  // to overclaim. `rate-limit-classifier.ts:160` calls this parser to read the
+  // RESET TIME out of a `rate_limit` / 429 transcript refusal, and
+  // `readUsageCapUntil` (agent-serving-probe.ts:296) returns null — i.e. does NOT
+  // defer — when that reset comes back null. So a parse failure here has always
+  // disarmed the ENG-8197 host-side dispatch deferral for this banner, which
+  // would explain cindy being dispatched into hourly while visibly blocked.
+  //
+  // NOT VERIFIED, and deliberately not claimed: whether a spend refusal is
+  // written to the transcript as `error: 'rate_limit'` / `apiErrorStatus: 429`
+  // at all. The classifier's verdict keys on those fields, not on this text. If
+  // it is, the deferral starts working as a side effect of this fix; if it is
+  // not, ENG-8197 is still blind to the spend ceiling and that is a separate
+  // ticket. Nothing here depends on which.
+  //
+  // KNOWN LIMIT, stated rather than papered over: a spend banner that carries no
+  // `resets` clause at all still yields null. `week_resets_at` drives the
+  // 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")
 ];
 
 // ../core/dist/claude-code-usage/run-marker.js

package/dist/mcp/slack-channel.js

@@ -35942,12 +35942,15 @@ 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;
 function classifyLimitScope(qualifier) {
   const q = (qualifier ?? "").trim();
   if (!q)
     return "weekly";
   if (SESSION_QUALIFIER.test(q))
     return "session";
+  if (SPEND_QUALIFIER.test(q))
+    return "spend";
   if (/^weekly$/i.test(q))
     return "weekly";
   return "unknown";
@@ -35984,7 +35987,58 @@ var BANNER_PATTERNS = [
     // 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})`,
     "i"
-  )
+  ),
+  // ENG-10365 — the Claude Team seat's INDIVIDUAL SPEND LIMIT.
+  //
+  // WHY THE TWO PATTERNS ABOVE CANNOT MATCH IT. Both require `limit` to be
+  // followed immediately by a separator and then `resets`. The spend banner puts
+  // its remedy between the two:
+  //
+  //   You've hit your individual spend limit · run /usage-credits to ask your
+  //   admin for a higher limit · your weekly limit resets Sep 12, 5pm (UTC)
+  //   Continuing automatically at Sep 12, 5pm · esc to cancel
+  //
+  // so the adjacency fails and `parseUsageBanner` returned null — verified
+  // against origin/main on the verbatim pane capture in ENG-10365 before this
+  // pattern was written. Null means NO observation is POSTed, which means the
+  // `claude_code_usage_observations` row never exists, which means
+  // `usage-limit-monitor` never hears of the agent at all. cindy ran zero-second
+  // turns for ~32 hours with `heartbeat_verdict fresh` and no usage alert of any
+  // kind, because the whole chain starts here.
+  //
+  // THE GAP IS BOUNDED AND LAZY, deliberately. The real banner's gap is ~78
+  // characters; 160 leaves 2x headroom for phrasing drift and for the pane's own
+  // line wrap (which lands mid-sentence, as above, so `[\s\S]` and not `.`).
+  // Lazy + bounded keeps it linear on the pane.log tails this parser runs over —
+  // the same reason the saturated pattern refuses the naive `(a+)+` shape.
+  //
+  // WHAT IT INHERITS BY MATCHING AT ALL. Everything downstream keys on the
+  // `usage_limit_reached` ALERT KIND rather than on the scope, so one matching
+  // banner reaches the roster's `usage_limit_alert_open` flag (ENG-9634),
+  // `resolveCappedAgents`, and both monitors that suppress on a capped agent.
+  // That is why this fix is a regex and not a subsystem.
+  //
+  // AND A SECOND CONSUMER, which is worth stating precisely because it is easy
+  // to overclaim. `rate-limit-classifier.ts:160` calls this parser to read the
+  // RESET TIME out of a `rate_limit` / 429 transcript refusal, and
+  // `readUsageCapUntil` (agent-serving-probe.ts:296) returns null — i.e. does NOT
+  // defer — when that reset comes back null. So a parse failure here has always
+  // disarmed the ENG-8197 host-side dispatch deferral for this banner, which
+  // would explain cindy being dispatched into hourly while visibly blocked.
+  //
+  // NOT VERIFIED, and deliberately not claimed: whether a spend refusal is
+  // written to the transcript as `error: 'rate_limit'` / `apiErrorStatus: 429`
+  // at all. The classifier's verdict keys on those fields, not on this text. If
+  // it is, the deferral starts working as a side effect of this fix; if it is
+  // not, ENG-8197 is still blind to the spend ceiling and that is a separate
+  // ticket. Nothing here depends on which.
+  //
+  // KNOWN LIMIT, stated rather than papered over: a spend banner that carries no
+  // `resets` clause at all still yields null. `week_resets_at` drives the
+  // 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")
 ];
 function parseUsageBanner(text, now = /* @__PURE__ */ new Date()) {
   let bestIndex = -1;

package/dist/mcp/telegram-channel.js

@@ -35992,12 +35992,15 @@ 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;
 function classifyLimitScope(qualifier) {
   const q = (qualifier ?? "").trim();
   if (!q)
     return "weekly";
   if (SESSION_QUALIFIER.test(q))
     return "session";
+  if (SPEND_QUALIFIER.test(q))
+    return "spend";
   if (/^weekly$/i.test(q))
     return "weekly";
   return "unknown";
@@ -36034,7 +36037,58 @@ var BANNER_PATTERNS = [
     // 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})`,
     "i"
-  )
+  ),
+  // ENG-10365 — the Claude Team seat's INDIVIDUAL SPEND LIMIT.
+  //
+  // WHY THE TWO PATTERNS ABOVE CANNOT MATCH IT. Both require `limit` to be
+  // followed immediately by a separator and then `resets`. The spend banner puts
+  // its remedy between the two:
+  //
+  //   You've hit your individual spend limit · run /usage-credits to ask your
+  //   admin for a higher limit · your weekly limit resets Sep 12, 5pm (UTC)
+  //   Continuing automatically at Sep 12, 5pm · esc to cancel
+  //
+  // so the adjacency fails and `parseUsageBanner` returned null — verified
+  // against origin/main on the verbatim pane capture in ENG-10365 before this
+  // pattern was written. Null means NO observation is POSTed, which means the
+  // `claude_code_usage_observations` row never exists, which means
+  // `usage-limit-monitor` never hears of the agent at all. cindy ran zero-second
+  // turns for ~32 hours with `heartbeat_verdict fresh` and no usage alert of any
+  // kind, because the whole chain starts here.
+  //
+  // THE GAP IS BOUNDED AND LAZY, deliberately. The real banner's gap is ~78
+  // characters; 160 leaves 2x headroom for phrasing drift and for the pane's own
+  // line wrap (which lands mid-sentence, as above, so `[\s\S]` and not `.`).
+  // Lazy + bounded keeps it linear on the pane.log tails this parser runs over —
+  // the same reason the saturated pattern refuses the naive `(a+)+` shape.
+  //
+  // WHAT IT INHERITS BY MATCHING AT ALL. Everything downstream keys on the
+  // `usage_limit_reached` ALERT KIND rather than on the scope, so one matching
+  // banner reaches the roster's `usage_limit_alert_open` flag (ENG-9634),
+  // `resolveCappedAgents`, and both monitors that suppress on a capped agent.
+  // That is why this fix is a regex and not a subsystem.
+  //
+  // AND A SECOND CONSUMER, which is worth stating precisely because it is easy
+  // to overclaim. `rate-limit-classifier.ts:160` calls this parser to read the
+  // RESET TIME out of a `rate_limit` / 429 transcript refusal, and
+  // `readUsageCapUntil` (agent-serving-probe.ts:296) returns null — i.e. does NOT
+  // defer — when that reset comes back null. So a parse failure here has always
+  // disarmed the ENG-8197 host-side dispatch deferral for this banner, which
+  // would explain cindy being dispatched into hourly while visibly blocked.
+  //
+  // NOT VERIFIED, and deliberately not claimed: whether a spend refusal is
+  // written to the transcript as `error: 'rate_limit'` / `apiErrorStatus: 429`
+  // at all. The classifier's verdict keys on those fields, not on this text. If
+  // it is, the deferral starts working as a side effect of this fix; if it is
+  // not, ENG-8197 is still blind to the spend ceiling and that is a separate
+  // ticket. Nothing here depends on which.
+  //
+  // KNOWN LIMIT, stated rather than papered over: a spend banner that carries no
+  // `resets` clause at all still yields null. `week_resets_at` drives the
+  // 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")
 ];
 function parseUsageBanner(text, now = /* @__PURE__ */ new Date()) {
   let bestIndex = -1;

package/dist/{persistent-session-5HSYQBF7.js → persistent-session-6QB3XNY2.js}

@@ -62,8 +62,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-RAEBKUW2.js";
-import "./chunk-5464FJVN.js";
+} from "./chunk-IVJVMR3S.js";
+import "./chunk-HQKGVPIV.js";
 import "./chunk-XWVM4KPK.js";
 export {
   CLAUDE_HOST_WIDE,
@@ -130,4 +130,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-5HSYQBF7.js.map
+//# sourceMappingURL=persistent-session-6QB3XNY2.js.map

package/dist/{responsiveness-probe-ZSB3DLLI.js → responsiveness-probe-ULU4DHEO.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-RAEBKUW2.js";
-import "./chunk-5464FJVN.js";
+} from "./chunk-IVJVMR3S.js";
+import "./chunk-HQKGVPIV.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -764,4 +764,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-ZSB3DLLI.js.map
+//# sourceMappingURL=responsiveness-probe-ULU4DHEO.js.map

package/dist/{session-auth-dead-J7SQAYRR.js → session-auth-dead-UXZ5DDKQ.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-5464FJVN.js";
+} from "./chunk-HQKGVPIV.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-J7SQAYRR.js.map
+//# sourceMappingURL=session-auth-dead-UXZ5DDKQ.js.map

package/package.json

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