@integrity-labs/agt-cli 0.22.1 → 0.22.3

package/dist/{chunk-7AOVUCPO.js → chunk-QGP4XD7R.js}

@@ -8,7 +8,7 @@ import {
   parseDeliveryTarget,
   registerFramework,
   wrapScheduledTaskPrompt
-} from "./chunk-ZNRQSPPM.js";
+} from "./chunk-E56L56ER.js";
 
 // ../../packages/core/dist/integrations/registry.js
 var INTEGRATION_REGISTRY = [
@@ -2548,6 +2548,81 @@ ${lines.join("\n")}
 
 Check \`.claude/skills/\` for detailed usage instructions for each integration.
 
+`;
+}
+function buildKanbanWorkPolicySection() {
+  return `## Kanban Work Policy
+
+Every 5 minutes you receive a \`/loop\` trigger that says "kanban_list \u2014
+follow Kanban Work Policy." When that trigger fires, this is what to do.
+
+### Throttle yourself first
+
+If you're mid-task, mid-conversation with a user, or otherwise busy on
+something more important, just briefly acknowledge the tick and continue
+what you were doing. The loop is automatic \u2014 missing one tick costs
+nothing; interrupting active work to satisfy it costs the user.
+
+### Walk the board
+
+1. **Resume in-progress work first.** If \`kanban_list\` shows an item
+   in \`in_progress\`, continue working on it. The most common reason
+   it exists is that *you* created it on a prior tick and got
+   interrupted by a restart \u2014 resume.
+2. **Then pull from todo/backlog.** If no \`in_progress\` items, pick
+   the highest-priority \`todo\` (or \`backlog\` if todo is empty),
+   call \`kanban_move\` to move it to \`in_progress\`, then work on it.
+3. **Self-initiated work needs a row too.** If neither path above
+   applies and you decide to do work on your own initiative (follow
+   up on something you noticed, check on a recurring concern), call
+   \`kanban_add\` with \`status="in_progress"\` BEFORE you start.
+   That's what makes your work crash-recoverable: if the session
+   restarts mid-work, the orphan row is what tells the next tick to
+   resume rather than start over.
+
+### DO NOT create a row when
+
+- You read the board and there's nothing to do \u2014 stand down silently.
+  **Empty ticks produce no rows.** The "work" of checking the board
+  is not itself a row.
+- You're acknowledging a tick that landed during active work.
+
+### Terminate every row you started
+
+Each row you started must reach a terminal state on the same or a
+later tick:
+
+- **\`kanban_done\` with the deliverable as the result** when the work
+  produced its expected output. The \`result\` field is what the user
+  will see in completion notifications (Telegram/Slack/email), so put
+  the **deliverable itself** there, not a description of it.
+  - BAD: \`result: "Email summary \u2014 last 48h"\` (a label).
+  - GOOD: \`result: "Inbox last 48h: 3 unread from <addr> re budget;
+    1 from <addr> re Q3 plan; \u2026"\` (the actual summary).
+  - For long-form output (>500 chars), lead with a one-line summary,
+    then a blank line, then the full content. Channel formatters
+    truncate gracefully but the lede always lands.
+- **\`kanban_fail\` with a reason** when something went wrong
+  (missing access, credential failure, tool error). The work was
+  attempted but failed.
+- **\`kanban_cancel\` with a reason** when you started, then realised
+  the work isn't actually needed (precondition no longer holds,
+  duplicate of another task, asker changed their mind, data was
+  already current). This is distinct from \`kanban_fail\`: nothing
+  went wrong; you wisely didn't bother. Use this generously \u2014 it's
+  cheaper than running unneeded work to a forced "done".
+- **\`kanban_update\` with notes** if you're blocked but might unblock
+  later; leave the row in \`in_progress\` and pick up other work.
+
+### When the board is empty
+
+- If \`todo\` and \`in_progress\` are both empty but \`backlog\` has
+  items, don't self-assign. Message your manager once asking which
+  backlog item to pick up; then stand down. Don't re-escalate on
+  every tick.
+- If \`backlog\` is also empty, say "All clear, no pending work" once
+  and stand down.
+
 `;
 }
 function buildSkillAuthoringSection() {
@@ -2855,6 +2930,7 @@ function generateClaudeMd(input) {
   const memorySection = buildMemorySection(hasQmd);
   const integrationsSection = buildIntegrationsSection(integrations);
   const knowledgeSection = buildKnowledgeSection2(knowledge);
+  const kanbanWorkPolicySection = buildKanbanWorkPolicySection();
   const skillAuthoringSection = buildSkillAuthoringSection();
   const personalitySection = buildPersonalitySection(personalitySeed);
   const reportsToSection = buildReportsToSection2(reportsTo);
@@ -3104,7 +3180,7 @@ first to load your recent board state. This gives you context about completed an
 in-progress items so you can answer accurately.
 
 ${memorySection}
-${reportsToSection}${teamSection}${peopleSection}${multiAgentSection}${integrationsSection}${knowledgeSection}${skillAuthoringSection}## Dashboards
+${reportsToSection}${teamSection}${peopleSection}${multiAgentSection}${integrationsSection}${knowledgeSection}${kanbanWorkPolicySection}${skillAuthoringSection}## Dashboards
 
 You can publish your own dashboards inside the Augmented console. They are
 **first-class platform artifacts** \u2014 KPI tiles, charts, refresh-on-demand \u2014
@@ -6536,4 +6612,4 @@ export {
   managerInstallSystemUnitCommand,
   managerUninstallSystemUnitCommand
 };
-//# sourceMappingURL=chunk-7AOVUCPO.js.map
+//# sourceMappingURL=chunk-QGP4XD7R.js.map