@integrity-labs/agt-cli 0.12.4 → 0.12.5

package/dist/bin/agt.js

@@ -32,7 +32,7 @@ import {
   resolveChannels,
   serializeManifestForSlackCli,
   setActiveTeam
-} from "../chunk-UMDIT5CP.js";
+} from "../chunk-35KA6J3P.js";
 
 // src/bin/agt.ts
 import { join as join11 } from "path";
@@ -3717,7 +3717,7 @@ import { execFileSync, execSync } from "child_process";
 import { existsSync as existsSync5, realpathSync } from "fs";
 import chalk20 from "chalk";
 import ora15 from "ora";
-var cliVersion = true ? "0.12.4" : "dev";
+var cliVersion = true ? "0.12.5" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -4166,7 +4166,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.12.4" : "dev";
+var cliVersion2 = true ? "0.12.5" : "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-UMDIT5CP.js → chunk-35KA6J3P.js}

@@ -2650,6 +2650,15 @@ Worktrees allow parallel work without disrupting running services, other agents,
 
 **Never switch branches on the main repo checkout.** Use worktrees for all feature work.
 
+## Delivering Work
+
+When you reply to a user via any channel (Slack, Telegram, direct chat, scheduled task result):
+
+- **Match the scope of the request.** A yes/no question gets a one-line answer. A "quick summary" request gets a summary, not a dissertation. Cut any section, caveat, or restatement that does not directly answer what was asked. Long rambling messages are not useful.
+- **Never reference internal state.** Memory files, \`/tmp/\` paths, kanban task IDs, filesystem locations, "saved to \u2026" / "logged to \u2026" notes \u2014 these are invisible to the recipient and waste their attention. Only the deliverable content belongs in your reply.
+- **Put the full deliverable in the reply itself.** Don't tease ("I've prepared a detailed brief"), don't point "above" or "attached" as a shortcut, and don't assume the recipient can see intermediate tool output. If they asked for a brief, the brief goes verbatim into your reply.
+- **If the deliverable is a file** (PDF, CSV, screenshot, export, report), upload it to the channel using the channel's file-upload tool (e.g. \`slack.upload_file\`) rather than describing its path. The recipient cannot access your filesystem.
+
 ## Standards
 
 The marginal cost of completeness is near zero. Do the whole thing.
@@ -6325,4 +6334,4 @@ export {
   detectDrift,
   provision
 };
-//# sourceMappingURL=chunk-UMDIT5CP.js.map
+//# sourceMappingURL=chunk-35KA6J3P.js.map