@integrity-labs/agt-cli 0.28.480 → 0.28.481

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.
package/dist/bin/agt.js CHANGED
@@ -40,7 +40,7 @@ import {
40
40
  success,
41
41
  table,
42
42
  warn
43
- } from "../chunk-JBDLGPQU.js";
43
+ } from "../chunk-YYNUZWK7.js";
44
44
  import {
45
45
  AnchorSessionClient,
46
46
  CHANNEL_REGISTRY,
@@ -71,7 +71,7 @@ import {
71
71
  requiredMcpWildcard,
72
72
  resolveChannels,
73
73
  serializeManifestForSlackCli
74
- } from "../chunk-EOH75U22.js";
74
+ } from "../chunk-4XLEJP7G.js";
75
75
  import "../chunk-XWVM4KPK.js";
76
76
 
77
77
  // src/bin/agt.ts
@@ -4830,7 +4830,7 @@ import { execFileSync, execSync } from "child_process";
4830
4830
  import { existsSync as existsSync10, realpathSync as realpathSync2 } from "fs";
4831
4831
  import chalk18 from "chalk";
4832
4832
  import ora16 from "ora";
4833
- var cliVersion = true ? "0.28.480" : "dev";
4833
+ var cliVersion = true ? "0.28.481" : "dev";
4834
4834
  async function fetchLatestVersion() {
4835
4835
  const host2 = getHost();
4836
4836
  if (!host2) return null;
@@ -6002,7 +6002,7 @@ function handleError(err) {
6002
6002
  }
6003
6003
 
6004
6004
  // src/bin/agt.ts
6005
- var cliVersion2 = true ? "0.28.480" : "dev";
6005
+ var cliVersion2 = true ? "0.28.481" : "dev";
6006
6006
  var program = new Command();
6007
6007
  program.name("agt").description("Augmented CLI \u2014 agent provisioning and management").version(cliVersion2).option("--json", "Emit machine-readable JSON output (suppress spinners and colors)").option("--skip-update-check", "Skip the automatic update check on startup");
6008
6008
  program.hook("preAction", async (thisCommand, actionCommand) => {
@@ -6,7 +6,7 @@ import {
6
6
  import { spawn as spawn2, execSync as execSync2, execFileSync as execFileSync3 } from "child_process";
7
7
  import { join as join5, dirname as dirname3 } from "path";
8
8
  import { homedir as homedir5, platform, userInfo as userInfo2 } from "os";
9
- import { existsSync as existsSync6, readFileSync as readFileSync7, readdirSync as readdirSync3, writeFileSync as writeFileSync5, appendFileSync as appendFileSync2, mkdirSync as mkdirSync5, chmodSync as chmodSync3, copyFileSync, rmSync as rmSync3 } from "fs";
9
+ import { existsSync as existsSync6, readFileSync as readFileSync7, readdirSync as readdirSync3, writeFileSync as writeFileSync5, appendFileSync as appendFileSync2, mkdirSync as mkdirSync5, chmodSync as chmodSync3, copyFileSync, rmSync as rmSync3, lstatSync, realpathSync } from "fs";
10
10
 
11
11
  // src/lib/mcp-sanitize.ts
12
12
  import { readFileSync, writeFileSync } from "fs";
@@ -9601,17 +9601,25 @@ var FLAG_REGISTRY = [
9601
9601
  },
9602
9602
  {
9603
9603
  key: "synthetic-probe-enabled",
9604
- description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. Ships dark (OFF) because the probe cron was generating false positives (probe_timeout on angie for 7+ days while healthy, ENG-8048) and had open cron_invocation_errors alarms (since 2026-07-23). Flip ON per-environment via the admin Feature Flags page once the reliability issues are resolved. The existing AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it to "true"/"1" to force-enable (env takes precedence over the DB stage value), or "false"/"0" to force-disable without a DB lookup. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
9604
+ description: 'Global gate for the agent synthetic-liveness cron (ENG-8074). When OFF, the cron exits after reading the flag \u2014 no probes sent, no metrics emitted, no CloudWatch alarms fired, near-zero DB footprint. This is the fleet-wide kill switch for synthetic probing, flippable per-environment from the admin Feature Flags page. The AUGMENTED_SYNTHETIC_PROBE_ENABLED env var is the declared envVar for this flag (ADR-0022): set it in the deploy environment to "true"/"1" to force-enable or "false"/"0" to force-disable without a DB lookup. Leave it UNSET (the default on every stage since ENG-8303) so this flag governs. Evaluated as a global stage value by the central cron (no per-org targeting). Boolean gate.',
9605
9605
  flagType: "boolean",
9606
- // Safe/dark default: false = probe off. This encodes the ENG-8074 intent (disable
9607
- // in prod until reliability issues are resolved) and is the fail-safe direction for
9608
- // a flag-DB read error — a hiccup degrades to keeping the cron dormant rather than
9609
- // silently re-arming a broken probe fleet-wide.
9610
- // The env var AUGMENTED_SYNTHETIC_PROBE_ENABLED was the pre-flag emergency kill switch
9611
- // (read as `!== 'false'`, so unset = probe ON). The flag inverts this: unset env var
9612
- // now resolves to the flag default (OFF). Set AUGMENTED_SYNTHETIC_PROBE_ENABLED=true to
9613
- // explicitly re-arm the probe via env, or flip the flag ON from the admin UI.
9614
- defaultValue: false,
9606
+ // ON by default this deliberately matches the fleet's live behaviour rather than the
9607
+ // dark default ENG-8074 declared, and the history is worth keeping straight:
9608
+ //
9609
+ // ENG-8074 set `false` to hold the probe dark until its reliability issues were fixed
9610
+ // (probe_timeout false positives, ENG-8048; open cron_invocation_errors alarms). That
9611
+ // default was never reachable: sst.config.ts pinned the declared envVar to the literal
9612
+ // 'true' on every deployed stage, and a declared envVar outranks the DB value, so the
9613
+ // probe ran throughout (ENG-8303). ENG-8303 un-pinned the env var, which hands this flag
9614
+ // real authority for the first time — so its value must now be chosen for the fleet it
9615
+ // actually controls, not inherited from an intent that never took effect.
9616
+ //
9617
+ // `true` keeps prod exactly as it has been running. Flipping to `false` here instead
9618
+ // would have silently switched agent liveness probing off at the next deploy — including
9619
+ // the prod verification of ENG-8302's PutMetricAlarm quota fix, which needs the cron
9620
+ // alive to observe. The reliability concern behind ENG-8074 is addressed by ENG-8302;
9621
+ // if it recurs, the kill switch is now a genuine admin-UI flip rather than a redeploy.
9622
+ defaultValue: true,
9615
9623
  envVar: "AUGMENTED_SYNTHETIC_PROBE_ENABLED"
9616
9624
  },
9617
9625
  {
@@ -14284,8 +14292,17 @@ async function stopAllSessionsAndWait(log2, opts) {
14284
14292
  }
14285
14293
  await new Promise((resolve) => setTimeout(resolve, Math.min(opts.timeoutMs, 2e3)));
14286
14294
  }
14295
+ function resolveRealAgentPath(codeNamePath) {
14296
+ try {
14297
+ if (lstatSync(codeNamePath).isSymbolicLink()) {
14298
+ return realpathSync(codeNamePath);
14299
+ }
14300
+ } catch {
14301
+ }
14302
+ return codeNamePath;
14303
+ }
14287
14304
  function getProjectDir(codeName) {
14288
- return join5(homedir5(), ".augmented", codeName, "project");
14305
+ return join5(resolveRealAgentPath(join5(homedir5(), ".augmented", codeName)), "project");
14289
14306
  }
14290
14307
 
14291
14308
  export {
@@ -14460,4 +14477,4 @@ export {
14460
14477
  stopAllSessionsAndWait,
14461
14478
  getProjectDir
14462
14479
  };
14463
- //# sourceMappingURL=chunk-EOH75U22.js.map
14480
+ //# sourceMappingURL=chunk-4XLEJP7G.js.map