@integrity-labs/agt-cli 0.28.749 → 0.28.750

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.
@@ -57,7 +57,7 @@ import {
57
57
  safeWriteJsonAtomic,
58
58
  setConfigHash,
59
59
  tripClass
60
- } from "../chunk-WTBSFYTA.js";
60
+ } from "../chunk-5GJ2JEFA.js";
61
61
  import {
62
62
  getProjectDir as getProjectDir2,
63
63
  getReadyTasks,
@@ -1695,7 +1695,28 @@ async function runConnectivityProbes(integrations, options = {}) {
1695
1695
  // assumed. Defaults to 'none' rather than being omitted — an absent field
1696
1696
  // from an older manager and a probe that contacted nothing must land in
1697
1697
  // the same, conservative place.
1698
- evidence: outcome.evidence ?? "none"
1698
+ evidence: outcome.evidence ?? "none",
1699
+ // ENG-9173's other half. That ticket added `last_connectivity_cause` and
1700
+ // the API-side write for it, and the probes compute a cause today
1701
+ // (`causeForHttp` in connectivity-http-probes.ts, and the did-not-run
1702
+ // branches in cli-probe.ts). This line is what puts it ON THE WIRE.
1703
+ //
1704
+ // Without it `ConnectivityReport` had no `cause` field at all, so the
1705
+ // host lane never sent one and the API's
1706
+ // `last_connectivity_cause: item.cause ?? 'unknown'` resolved to
1707
+ // `'unknown'` for EVERY host-probed row on the fleet, forever. The column
1708
+ // added to stop an escalation boundary matching prose was itself never
1709
+ // populated by the lane that does almost all the probing — the identical
1710
+ // parse-then-drop the ENG-9173 header describes, one layer further up.
1711
+ //
1712
+ // Omitted rather than defaulted when absent: unlike `evidence`, where a
1713
+ // missing value and "contacted nothing" must both land conservatively on
1714
+ // `'none'`, the API already coerces an absent or unrecognised cause to
1715
+ // `'unknown'` (`isConnectivityCause`, integration-connectivity-report.ts).
1716
+ // Sending an explicit `'unknown'` would be indistinguishable from an older
1717
+ // manager that cannot classify at all, and that distinction is worth
1718
+ // keeping while this rolls out across hosts.
1719
+ ...outcome.cause ? { cause: outcome.cause } : {}
1699
1720
  });
1700
1721
  }
1701
1722
  return { reports, due: due.length, probed: batch.length, skipped };
@@ -13370,7 +13391,7 @@ var agentRestartTimezoneInputs = /* @__PURE__ */ new Map();
13370
13391
  var lastVersionCheckAt = 0;
13371
13392
  var VERSION_CHECK_INTERVAL_MS = 5 * 60 * 1e3;
13372
13393
  var lastResponsivenessProbeAt = 0;
13373
- var agtCliVersion = true ? "0.28.749" : "dev";
13394
+ var agtCliVersion = true ? "0.28.750" : "dev";
13374
13395
  function resolveBrewPath(execFileSync3) {
13375
13396
  try {
13376
13397
  const out = execFileSync3("which", ["brew"], { timeout: 5e3 }).toString().trim();