@integrity-labs/agt-cli 0.28.166 → 0.28.168

package/dist/bin/agt.js

@@ -37,7 +37,7 @@ import {
   success,
   table,
   warn
-} from "../chunk-HWVCQ6PC.js";
+} from "../chunk-DYW5QFTU.js";
 import {
   CHANNEL_REGISTRY,
   DEFAULT_FRAMEWORK,
@@ -4778,7 +4778,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.28.166" : "dev";
+var cliVersion = true ? "0.28.168" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -5792,7 +5792,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.28.166" : "dev";
+var cliVersion2 = true ? "0.28.168" : "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", async (thisCommand, actionCommand) => {

package/dist/{chunk-HWVCQ6PC.js → chunk-DYW5QFTU.js}

@@ -3798,6 +3798,15 @@ write one of these, stop and call the tool first.
 **When in doubt, create a task.** Err on the side of tracking work rather than
 doing it silently. Any work that takes more than ~30 seconds should be a kanban task.
 
+**Two situations always warrant a task, even when the work looks quick: (1) you
+are about to request an approval (any deferred-approval / broker tool, such as an
+access grant, deploy gate, or channel post that needs a human OK), or (2) you are
+about to run code (execute a script, run a shell command, or otherwise change a
+system). Create the kanban task FIRST, before you fire the approval request or the
+code runs, so the work is visible and tracked rather than happening invisibly.**
+If the request is fuzzy, clarify scope first per below, then create the task
+before requesting approval or running anything.
+
 But: **clarify before you commit.** A vague task on the board is worse than
 no task \u2014 it bakes in the wrong scope and forces a rename later. If the
 request is fuzzy, ask one or two sharp questions FIRST and create the task
@@ -7640,6 +7649,8 @@ These credentials are pre-loaded. Reference them by their environment variable n
 
 The only things that don't need a task: one-line answers, yes/no questions, a simple lookup you can answer in a tool call or two (under ~30 seconds), or no-action acknowledgments ("thanks", "got it", "acknowledged", "will do") that require no further work. Everything else gets a task.
 
+**Two situations always warrant a task, even when the work looks quick: (1) you are about to request an approval (any deferred-approval / broker tool, such as an access grant, deploy gate, or channel post that needs a human OK), or (2) you are about to run code (execute a script, run a shell command, or otherwise change a system). Create the kanban task FIRST, before you fire the approval request or the code runs, so the work is visible and tracked rather than happening invisibly.** If the request is fuzzy, clarify scope first, then create the task before requesting approval or running anything.
+
 The cost of an unnecessary task is near zero. The cost of invisible work is confusion, duplication, and lost context.
 
 **Always confirm task creation back to the requester via the same channel they reached you on.** When you create a kanban task in response to a Slack/direct-chat/email/etc. message, your *next* action MUST be to call that channel's send/reply tool with:
@@ -7948,7 +7959,7 @@ function requireHost() {
 }
 
 // src/lib/api-client.ts
-var agtCliVersion = true ? "0.28.166" : "dev";
+var agtCliVersion = true ? "0.28.168" : "dev";
 var lastConfigHash = null;
 function setConfigHash(hash) {
   lastConfigHash = hash && hash.length > 0 ? hash : null;
@@ -9253,4 +9264,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-HWVCQ6PC.js.map
+//# sourceMappingURL=chunk-DYW5QFTU.js.map