@integrity-labs/agt-cli 0.28.1138 → 0.28.1139

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (23) hide show
  1. package/dist/bin/agt.js +5 -5
  2. package/dist/{chunk-J6ORWGUB.js → chunk-7U4VSBOE.js} +2 -2
  3. package/dist/{chunk-EIXOI2ZB.js → chunk-DYFE224A.js} +14 -1
  4. package/dist/{chunk-EIXOI2ZB.js.map → chunk-DYFE224A.js.map} +1 -1
  5. package/dist/{chunk-3INFJV37.js → chunk-PI2WUKWD.js} +4 -4
  6. package/dist/{claude-pair-runtime-VQGEM5AY.js → claude-pair-runtime-BOTE3DRW.js} +2 -2
  7. package/dist/lib/manager-worker.js +261 -16
  8. package/dist/lib/manager-worker.js.map +1 -1
  9. package/dist/mcp/direct-chat-channel.js +13 -0
  10. package/dist/mcp/index.js +13 -0
  11. package/dist/mcp/origami.js +13 -0
  12. package/dist/mcp/slack-channel.js +13 -0
  13. package/dist/mcp/telegram-channel.js +13 -0
  14. package/dist/{persistent-session-ZBKLEYUQ.js → persistent-session-6O66QEI4.js} +3 -3
  15. package/dist/{responsiveness-probe-FXDO35IT.js → responsiveness-probe-WGD3NDWG.js} +3 -3
  16. package/dist/{session-auth-dead-OGNOSJIB.js → session-auth-dead-6N2AEFKX.js} +2 -2
  17. package/package.json +1 -1
  18. /package/dist/{chunk-J6ORWGUB.js.map → chunk-7U4VSBOE.js.map} +0 -0
  19. /package/dist/{chunk-3INFJV37.js.map → chunk-PI2WUKWD.js.map} +0 -0
  20. /package/dist/{claude-pair-runtime-VQGEM5AY.js.map → claude-pair-runtime-BOTE3DRW.js.map} +0 -0
  21. /package/dist/{persistent-session-ZBKLEYUQ.js.map → persistent-session-6O66QEI4.js.map} +0 -0
  22. /package/dist/{responsiveness-probe-FXDO35IT.js.map → responsiveness-probe-WGD3NDWG.js.map} +0 -0
  23. /package/dist/{session-auth-dead-OGNOSJIB.js.map → session-auth-dead-6N2AEFKX.js.map} +0 -0
@@ -45521,6 +45521,19 @@ var FLAG_REGISTRY = [
45521
45521
  // refuses aal1 there too.
45522
45522
  platformAdminOnly: true
45523
45523
  },
45524
+ {
45525
+ key: "two-factor-reminder-banner",
45526
+ description: "Show a banner across the console asking every user without an authenticator app to set one up before two-factor becomes required (ENG-11619). Also makes Settings > Two-factor authentication reachable, as `two-factor-settings` does, because the banner links there. Closing it hides it for a day in that browser.",
45527
+ flagType: "boolean",
45528
+ // PUBLIC: the nav reads it client-side; the layout and the settings page read
45529
+ // it server-side. Ships dark (default false): turn it on for one org first.
45530
+ public: true,
45531
+ defaultValue: false,
45532
+ // Staff only, for the same reason as `two-factor-settings` above: it opens
45533
+ // the settings page, and phase 1 still accepts an aal1 session outside page
45534
+ // loads, so an org admin must not be the one deciding they are covered.
45535
+ platformAdminOnly: true
45536
+ },
45524
45537
  {
45525
45538
  key: "platform-maintenance-mode",
45526
45539
  description: 'Platform-wide maintenance mode (ENG-6506; widened to modes by ENG-11436). off = normal operation (ships dark; channels behave exactly as today). tools-offline = every agent KEEPS conversing but every Augmented tool that WRITES to the control plane refuses with a reason, so nothing is created during a window whose database restore would discard it; reads are untouched. fleet-offline = the previous boolean-true behaviour AND the write gate: admitted human inbound gets a "we are offline for maintenance" notice instead of being dispatched, for whole-platform downtime such as DB upgrades. The modes are CUMULATIVE \u2014 fleet-offline gates writes too, because silencing channel inbound does not stop a /loop or a scheduled task filing work. Read host-side per inbound and per tool call from the flags cache (no MCP restart). (Proactive "back online" follow-up is the ENG-6508 fast-follow, not this flag.)',
package/dist/mcp/index.js CHANGED
@@ -31100,6 +31100,19 @@ var FLAG_REGISTRY = [
31100
31100
  // refuses aal1 there too.
31101
31101
  platformAdminOnly: true
31102
31102
  },
31103
+ {
31104
+ key: "two-factor-reminder-banner",
31105
+ description: "Show a banner across the console asking every user without an authenticator app to set one up before two-factor becomes required (ENG-11619). Also makes Settings > Two-factor authentication reachable, as `two-factor-settings` does, because the banner links there. Closing it hides it for a day in that browser.",
31106
+ flagType: "boolean",
31107
+ // PUBLIC: the nav reads it client-side; the layout and the settings page read
31108
+ // it server-side. Ships dark (default false): turn it on for one org first.
31109
+ public: true,
31110
+ defaultValue: false,
31111
+ // Staff only, for the same reason as `two-factor-settings` above: it opens
31112
+ // the settings page, and phase 1 still accepts an aal1 session outside page
31113
+ // loads, so an org admin must not be the one deciding they are covered.
31114
+ platformAdminOnly: true
31115
+ },
31103
31116
  {
31104
31117
  key: "platform-maintenance-mode",
31105
31118
  description: 'Platform-wide maintenance mode (ENG-6506; widened to modes by ENG-11436). off = normal operation (ships dark; channels behave exactly as today). tools-offline = every agent KEEPS conversing but every Augmented tool that WRITES to the control plane refuses with a reason, so nothing is created during a window whose database restore would discard it; reads are untouched. fleet-offline = the previous boolean-true behaviour AND the write gate: admitted human inbound gets a "we are offline for maintenance" notice instead of being dispatched, for whole-platform downtime such as DB upgrades. The modes are CUMULATIVE \u2014 fleet-offline gates writes too, because silencing channel inbound does not stop a /loop or a scheduled task filing work. Read host-side per inbound and per tool call from the flags cache (no MCP restart). (Proactive "back online" follow-up is the ENG-6508 fast-follow, not this flag.)',
@@ -45027,6 +45027,19 @@ var FLAG_REGISTRY = [
45027
45027
  // refuses aal1 there too.
45028
45028
  platformAdminOnly: true
45029
45029
  },
45030
+ {
45031
+ key: "two-factor-reminder-banner",
45032
+ description: "Show a banner across the console asking every user without an authenticator app to set one up before two-factor becomes required (ENG-11619). Also makes Settings > Two-factor authentication reachable, as `two-factor-settings` does, because the banner links there. Closing it hides it for a day in that browser.",
45033
+ flagType: "boolean",
45034
+ // PUBLIC: the nav reads it client-side; the layout and the settings page read
45035
+ // it server-side. Ships dark (default false): turn it on for one org first.
45036
+ public: true,
45037
+ defaultValue: false,
45038
+ // Staff only, for the same reason as `two-factor-settings` above: it opens
45039
+ // the settings page, and phase 1 still accepts an aal1 session outside page
45040
+ // loads, so an org admin must not be the one deciding they are covered.
45041
+ platformAdminOnly: true
45042
+ },
45030
45043
  {
45031
45044
  key: "platform-maintenance-mode",
45032
45045
  description: 'Platform-wide maintenance mode (ENG-6506; widened to modes by ENG-11436). off = normal operation (ships dark; channels behave exactly as today). tools-offline = every agent KEEPS conversing but every Augmented tool that WRITES to the control plane refuses with a reason, so nothing is created during a window whose database restore would discard it; reads are untouched. fleet-offline = the previous boolean-true behaviour AND the write gate: admitted human inbound gets a "we are offline for maintenance" notice instead of being dispatched, for whole-platform downtime such as DB upgrades. The modes are CUMULATIVE \u2014 fleet-offline gates writes too, because silencing channel inbound does not stop a /loop or a scheduled task filing work. Read host-side per inbound and per tool call from the flags cache (no MCP restart). (Proactive "back online" follow-up is the ENG-6508 fast-follow, not this flag.)',
@@ -39853,6 +39853,19 @@ var FLAG_REGISTRY = [
39853
39853
  // refuses aal1 there too.
39854
39854
  platformAdminOnly: true
39855
39855
  },
39856
+ {
39857
+ key: "two-factor-reminder-banner",
39858
+ description: "Show a banner across the console asking every user without an authenticator app to set one up before two-factor becomes required (ENG-11619). Also makes Settings > Two-factor authentication reachable, as `two-factor-settings` does, because the banner links there. Closing it hides it for a day in that browser.",
39859
+ flagType: "boolean",
39860
+ // PUBLIC: the nav reads it client-side; the layout and the settings page read
39861
+ // it server-side. Ships dark (default false): turn it on for one org first.
39862
+ public: true,
39863
+ defaultValue: false,
39864
+ // Staff only, for the same reason as `two-factor-settings` above: it opens
39865
+ // the settings page, and phase 1 still accepts an aal1 session outside page
39866
+ // loads, so an org admin must not be the one deciding they are covered.
39867
+ platformAdminOnly: true
39868
+ },
39856
39869
  {
39857
39870
  key: "platform-maintenance-mode",
39858
39871
  description: 'Platform-wide maintenance mode (ENG-6506; widened to modes by ENG-11436). off = normal operation (ships dark; channels behave exactly as today). tools-offline = every agent KEEPS conversing but every Augmented tool that WRITES to the control plane refuses with a reason, so nothing is created during a window whose database restore would discard it; reads are untouched. fleet-offline = the previous boolean-true behaviour AND the write gate: admitted human inbound gets a "we are offline for maintenance" notice instead of being dispatched, for whole-platform downtime such as DB upgrades. The modes are CUMULATIVE \u2014 fleet-offline gates writes too, because silencing channel inbound does not stop a /loop or a scheduled task filing work. Read host-side per inbound and per tool call from the flags cache (no MCP restart). (Proactive "back online" follow-up is the ENG-6508 fast-follow, not this flag.)',
@@ -40064,6 +40064,19 @@ var FLAG_REGISTRY = [
40064
40064
  // refuses aal1 there too.
40065
40065
  platformAdminOnly: true
40066
40066
  },
40067
+ {
40068
+ key: "two-factor-reminder-banner",
40069
+ description: "Show a banner across the console asking every user without an authenticator app to set one up before two-factor becomes required (ENG-11619). Also makes Settings > Two-factor authentication reachable, as `two-factor-settings` does, because the banner links there. Closing it hides it for a day in that browser.",
40070
+ flagType: "boolean",
40071
+ // PUBLIC: the nav reads it client-side; the layout and the settings page read
40072
+ // it server-side. Ships dark (default false): turn it on for one org first.
40073
+ public: true,
40074
+ defaultValue: false,
40075
+ // Staff only, for the same reason as `two-factor-settings` above: it opens
40076
+ // the settings page, and phase 1 still accepts an aal1 session outside page
40077
+ // loads, so an org admin must not be the one deciding they are covered.
40078
+ platformAdminOnly: true
40079
+ },
40067
40080
  {
40068
40081
  key: "platform-maintenance-mode",
40069
40082
  description: 'Platform-wide maintenance mode (ENG-6506; widened to modes by ENG-11436). off = normal operation (ships dark; channels behave exactly as today). tools-offline = every agent KEEPS conversing but every Augmented tool that WRITES to the control plane refuses with a reason, so nothing is created during a window whose database restore would discard it; reads are untouched. fleet-offline = the previous boolean-true behaviour AND the write gate: admitted human inbound gets a "we are offline for maintenance" notice instead of being dispatched, for whole-platform downtime such as DB upgrades. The modes are CUMULATIVE \u2014 fleet-offline gates writes too, because silencing channel inbound does not stop a /loop or a scheduled task filing work. Read host-side per inbound and per tool call from the flags cache (no MCP restart). (Proactive "back online" follow-up is the ENG-6508 fast-follow, not this flag.)',
@@ -68,8 +68,8 @@ import {
68
68
  writeDirectChatSessionState,
69
69
  writeEgressAllowlist,
70
70
  writePersistentClaudeWrapper
71
- } from "./chunk-J6ORWGUB.js";
72
- import "./chunk-EIXOI2ZB.js";
71
+ } from "./chunk-7U4VSBOE.js";
72
+ import "./chunk-DYFE224A.js";
73
73
  import "./chunk-B6UYVEMD.js";
74
74
  import "./chunk-XWVM4KPK.js";
75
75
  import "./chunk-EL5MWGGH.js";
@@ -145,4 +145,4 @@ export {
145
145
  writeEgressAllowlist,
146
146
  writePersistentClaudeWrapper
147
147
  };
148
- //# sourceMappingURL=persistent-session-ZBKLEYUQ.js.map
148
+ //# sourceMappingURL=persistent-session-6O66QEI4.js.map
@@ -1,7 +1,7 @@
1
1
  import {
2
2
  paneLogPath
3
- } from "./chunk-J6ORWGUB.js";
4
- import "./chunk-EIXOI2ZB.js";
3
+ } from "./chunk-7U4VSBOE.js";
4
+ import "./chunk-DYFE224A.js";
5
5
  import "./chunk-B6UYVEMD.js";
6
6
  import "./chunk-XWVM4KPK.js";
7
7
  import "./chunk-EL5MWGGH.js";
@@ -802,4 +802,4 @@ export {
802
802
  readAndResetSlackReplyBindingClassifications,
803
803
  readAndResetSlackReplyTargetClassifications
804
804
  };
805
- //# sourceMappingURL=responsiveness-probe-FXDO35IT.js.map
805
+ //# sourceMappingURL=responsiveness-probe-WGD3NDWG.js.map
@@ -1,6 +1,6 @@
1
1
  import {
2
2
  sessionTranscriptDir
3
- } from "./chunk-EIXOI2ZB.js";
3
+ } from "./chunk-DYFE224A.js";
4
4
  import "./chunk-DGUM43GV.js";
5
5
 
6
6
  // src/lib/session-auth-dead.ts
@@ -204,4 +204,4 @@ export {
204
204
  decideSessionAuthState,
205
205
  probeSessionAuth
206
206
  };
207
- //# sourceMappingURL=session-auth-dead-OGNOSJIB.js.map
207
+ //# sourceMappingURL=session-auth-dead-6N2AEFKX.js.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@integrity-labs/agt-cli",
3
- "version": "0.28.1138",
3
+ "version": "0.28.1139",
4
4
  "description": "Augmented Team CLI — agent provisioning and management",
5
5
  "type": "module",
6
6
  "engines": {