@integrity-labs/agt-cli 0.28.1059 → 0.28.1060

package/dist/bin/agt.js

@@ -40,12 +40,12 @@ import {
   success,
   table,
   warn
-} from "../chunk-EWJ6A7AO.js";
+} from "../chunk-GOTLGDZJ.js";
 import {
   getProjectDir,
   isSessionResumeDisabled,
   readDirectChatSessionState
-} from "../chunk-E3XTUL7S.js";
+} from "../chunk-ROZAO2DB.js";
 import {
   AnchorSessionClient,
   CHANNEL_REGISTRY,
@@ -79,7 +79,7 @@ import {
   serializeManifestForSlackCli,
   sessionFileExists,
   sessionTranscriptDir
-} from "../chunk-VQITKTZU.js";
+} from "../chunk-JFLRDMGU.js";
 import "../chunk-OCMJ5E6J.js";
 import "../chunk-XWVM4KPK.js";
 import "../chunk-EL5MWGGH.js";
@@ -5474,7 +5474,7 @@ import { execFileSync, execSync } from "child_process";
 import { existsSync as existsSync11, realpathSync as realpathSync2 } from "fs";
 import chalk18 from "chalk";
 import ora16 from "ora";
-var cliVersion = true ? "0.28.1059" : "dev";
+var cliVersion = true ? "0.28.1060" : "dev";
 async function fetchLatestVersion() {
   const host2 = getHost();
   if (!host2) return null;
@@ -6734,7 +6734,7 @@ function handleError(err) {
 }
 
 // src/bin/agt.ts
-var cliVersion2 = true ? "0.28.1059" : "dev";
+var cliVersion2 = true ? "0.28.1060" : "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-EWJ6A7AO.js → chunk-GOTLGDZJ.js}

@@ -16,7 +16,7 @@ import {
   parseEnvFileEntries,
   parseEnvIntegrations,
   shellQuote
-} from "./chunk-E3XTUL7S.js";
+} from "./chunk-ROZAO2DB.js";
 import {
   BIND_FAILURE_QUARANTINE_THRESHOLD,
   INTEGRATIONS_SECTION_END,
@@ -79,7 +79,7 @@ import {
   sessionTranscriptDir,
   worseConnectivityOutcome,
   wrapScheduledTaskPrompt
-} from "./chunk-VQITKTZU.js";
+} from "./chunk-JFLRDMGU.js";
 import {
   classifyUnanswerablePane,
   isConsumerTermsDialogVisible,
@@ -7122,7 +7122,7 @@ function exchangeFailureKind(err) {
 }
 
 // src/lib/api-client.ts
-var agtCliVersion = true ? "0.28.1059" : "dev";
+var agtCliVersion = true ? "0.28.1060" : "dev";
 var lastConfigHash = null;
 function setConfigHash(hash) {
   lastConfigHash = hash && hash.length > 0 ? hash : null;
@@ -12089,4 +12089,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-EWJ6A7AO.js.map
+//# sourceMappingURL=chunk-GOTLGDZJ.js.map

package/dist/{chunk-VQITKTZU.js → chunk-JFLRDMGU.js}

@@ -680,6 +680,7 @@ later tick:
   \u2014 missing access, credential failure, tool error.
 - **No longer needed** (there's no "cancelled" status): \`kanban_done\` with a \`result\`
   saying why. Do this generously \u2014 it tells the user you consciously stood it down.
+  Not for a denied, expired or cancelled approval: that is \`status="failed"\`.
 - **\`kanban_update\` with notes** if blocked but maybe unblockable later; leave it
   \`in_progress\` and pick up other work.
 
@@ -1494,42 +1495,43 @@ and channel rules live in \`CHARTER.md\`.
 
 ${guardrailsSection}${agentRulesSection}## Approval acknowledgements
 
-This applies to **any** deferred-approval tool \u2014 anything returning \`pending\` that
+This applies to **any** deferred-approval tool: anything returning \`pending\` that
 resolves later via a notification (AWS access grants, channel posts needing a human
 OK, deploy gates, budget overrides, any future broker of the same shape).
 
-**Acknowledge before acting \u2014 on both sides of the round-trip.**
-
-1. **On the initial \`pending\` response.** Post a brief, jargon-free one-liner in the
-   user's channel naming the task and what's being waited on ("Requesting access to
-   the prod-data account to pull that report \u2014 pinged an admin, will resume the
-   moment it lands"). Save the returned id, return control, **do not poll** \u2014 the
-   broker pushes the resolution to you.
+1. **On \`pending\`.** If the tool result says the card was posted in the conversation
+   you are replying in (e.g. a Direct Chat card with buttons), the card is the
+   acknowledgement: post nothing, and in Direct Chat end with \`direct_chat_consume\`.
+   Otherwise post a brief, jargon-free one-liner naming the task and what's being
+   waited on ("Requesting access to the prod-data account to pull that report,
+   pinged an admin, will resume the moment it lands"). Save the returned id, return
+   control, **do not poll**.
 
 2. **When the resolution notification arrives** (in direct-chat, with an
    \`Original conversation:\` line naming the thread the request started in):
    before you call any follow-up tool, post one short line **in that original
    conversation**:
-   - On approve: name the task and signal you're acting \u2014 "Approval came through \u2014
-     kicking off <the task> now."
-   - On deny: name the task, paraphrase the reason, ask how to proceed \u2014 "Couldn't
-     get approval for <the task>: <paraphrased reason> \u2014
-     let me know how you'd like to proceed."
+   - On approve: "Approval came through, kicking off <the task> now."
+   - On deny, expiry or cancel: one factual line, then stop. Use its \`Decided by:\`
+     line: "Not sent, you denied it." if the decider is the person you are talking
+     to, else "Not sent, <name> denied it." or "Not sent, it expired." Add a reason
+     only if one was typed. **Never guess why**, and never send the user to "the
+     approver" when they decided it.
+
+   No \`Original conversation:\` line \u2192 fall back to direct-chat.
 
-   Only then call the follow-up (approve) or stop (deny). No \`Original
-   conversation:\` line \u2192 fall back to direct-chat.
+3. **Kanban card for a denied, expired or cancelled action:** \`kanban_move\`
+   \`status="failed"\` with a note, **never \`kanban_done\`** (done means it worked).
 
 **Across all approval flows:**
 
-- No broker vocabulary in user messages \u2014 "grant_id", "secret_ref",
-  "approval_request_id", "STS", any underlying tool name stay out; talk about the
-  task and resource, not the plumbing. Never paste a request/grant UUID into
-  user-facing prose (it's operator metadata users can't act on).
-- If the broker reports a notification-delivery failure (\`notification_status:
-  failed\` \u2014 meaning no human was paged), surface that as its own problem, don't
-  silently assume approval will arrive.
-- Going silent between request and resolution, or between resolution and work,
-  defeats the human-in-the-loop signal \u2014 lead with the outcome before acting.
+- No broker vocabulary in user messages: "grant_id", "secret_ref",
+  "approval_request_id", "STS", any underlying tool name stay out. Never paste a
+  request/grant UUID into user-facing prose (it's operator metadata users can't act on).
+- \`notification_status: failed\` means no human was paged: surface that as its own
+  problem, don't assume approval will arrive.
+- Going silent when the card is somewhere the user cannot see defeats the
+  human-in-the-loop signal: lead with the outcome before acting.
 
 ## Integration trust calibration
 
@@ -16006,4 +16008,4 @@ export {
   peekCurrentSession,
   readDailySessionPin
 };
-//# sourceMappingURL=chunk-VQITKTZU.js.map
+//# sourceMappingURL=chunk-JFLRDMGU.js.map