@integrity-labs/agt-cli 0.27.15 → 0.27.16

package/dist/bin/agt.js

@@ -27,7 +27,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-LJEV2QHN.js";
+} from "../chunk-6D55CCVZ.js";
 import {
   CHANNEL_REGISTRY,
   DEPLOYMENT_TEMPLATES,
@@ -4643,7 +4643,7 @@ import { execFileSync, execSync } from "child_process";
 import { existsSync as existsSync10, realpathSync as realpathSync2 } from "fs";
 import chalk18 from "chalk";
 import ora16 from "ora";
-var cliVersion = true ? "0.27.15" : "dev";
+var cliVersion = true ? "0.27.16" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -5175,7 +5175,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.27.15" : "dev";
+var cliVersion2 = true ? "0.27.16" : "dev";
 var program = new Command();
 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");
 program.hook("preAction", (thisCommand) => {

package/dist/{chunk-LJEV2QHN.js → chunk-6D55CCVZ.js}

@@ -2681,42 +2681,6 @@ If your charter doesn't authorise team-scope skill writes
 refused server-side \u2014 surface that error to the user rather than
 falling back to a local-disk write.
 
-`;
-}
-function buildProgressHeartbeatSection(resolvedChannels) {
-  const hasSlack = !!resolvedChannels?.includes("slack");
-  const hasDirectChat = !!resolvedChannels?.includes("direct-chat");
-  if (!hasSlack && !hasDirectChat)
-    return "";
-  const bullets = [];
-  if (hasSlack) {
-    bullets.push("- **Slack threads:** `slack_progress_start` (channel + thread_ts from the inbound `<channel>` tag, label = short task name) \u2192 `slack_progress_update` between steps (pass `step_label`, optional `step_current`/`step_total`) \u2192 `slack_progress_complete` (summary) or `slack_progress_fail` (one-sentence reason).");
-  }
-  if (hasDirectChat) {
-    bullets.push("- **Direct Chat sessions:** `direct_chat_progress_start` (session_id from the inbound tag, label) \u2192 `direct_chat_progress_update` \u2192 `direct_chat_progress_complete` / `_fail`.");
-  }
-  return `
-## Progress heartbeats during multi-step work
-
-When a task involves **\u22653 tool calls or is likely to take >5 seconds**
-of tool work, open an in-place progress anchor instead of streaming
-"working on\u2026" / "still working\u2026" / "done" messages. The operator sees
-one message that ticks forward as you advance, not a thread flooded
-with status pings.
-
-${bullets.join("\n")}
-
-The state machine debounces updates to roughly one API call per second
-per channel, so it's safe to call \`_update\` after every step rather
-than batching. Always end with \`_complete\` or \`_fail\` \u2014 leaving an
-anchor in the "working" state means a future stale-state sweep flips it
-to \u26A0\uFE0F "agent unresponsive" once the heartbeat goes cold.
-
-**Skip the heartbeat for one-shot replies.** A single \`slack.reply\` /
-\`direct_chat.reply\` is still the right pattern when there's no
-multi-step work to surface. Heartbeats are for the case where you'd
-otherwise emit several intermediate messages.
-
 `;
 }
 function buildPersonalitySection(seed) {
@@ -3077,7 +3041,7 @@ inline replies \u2014 they do NOT replace this dispatch decision.
 If the work turns out to be unexpectedly slow after you started inline,
 finish the current sub-step, then dispatch the rest. Don't apologise for
 mid-task switching \u2014 operators care about responsiveness, not consistency.
-${buildProgressHeartbeatSection(resolvedChannels)}
+
 ${activeTasksSection}${personalitySection}## Identity
 
 - Code Name: ${frontmatter.code_name}
@@ -6920,4 +6884,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-LJEV2QHN.js.map
+//# sourceMappingURL=chunk-6D55CCVZ.js.map