@integrity-labs/agt-cli 0.22.1 → 0.22.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  import {
2
2
  KANBAN_LOOP_COMMAND
3
- } from "./chunk-ZNRQSPPM.js";
3
+ } from "./chunk-E56L56ER.js";
4
4
 
5
5
  // src/lib/persistent-session.ts
6
6
  import { spawn, execSync, execFileSync as execFileSync2 } from "child_process";
@@ -1113,4 +1113,4 @@ export {
1113
1113
  stopAllSessionsAndWait,
1114
1114
  getProjectDir
1115
1115
  };
1116
- //# sourceMappingURL=chunk-KTPMEVEO.js.map
1116
+ //# sourceMappingURL=chunk-DJH6JFF7.js.map
@@ -1000,7 +1000,7 @@ function looksLikeNotesOnly(remainder) {
1000
1000
  }
1001
1001
 
1002
1002
  // ../../packages/core/dist/loops/kanban-loop.js
1003
- var KANBAN_LOOP_COMMAND = '/loop 5m Check the kanban board with kanban_list. Use your judgement \u2014 if mid-task or mid-conversation, briefly acknowledge and continue. POLICY: every unit of work you start is a kanban row, transitioned to a terminal state when done. No rows for no-ops. Walk the board: (1) If you have an item in "in_progress", continue working on it \u2014 usually you created it on a prior tick and got interrupted by a restart, so resume. (2) If no in_progress items, pick the highest-priority "todo" or "backlog" item, call kanban_move to in_progress, then work on it. (3) If neither path applies AND you decide to do self-initiated work, call kanban_add with status="in_progress" BEFORE starting \u2014 that is what makes your work crash-recoverable. DO NOT create a row when you read the board and there is nothing to do \u2014 stand down silently. Empty ticks produce no rows. The "work" of checking the board is not itself a row. Transition every row you started to a terminal state: kanban_done with a clear result for successful work; kanban_fail with a reason when something went wrong (missing access, tool error); kanban_cancel with a reason when you started then realised the work is not needed (duplicate, precondition no longer holds, data already current) \u2014 distinct from kanban_fail because nothing went wrong, you wisely did not bother; kanban_update with notes if blocked but might unblock later, then move on. If todo and in_progress are both empty: if backlog has items, do not self-assign \u2014 message your manager once asking which to pick up, then stand down; if backlog is also empty, say "All clear, no pending work" and stand down.';
1003
+ var KANBAN_LOOP_COMMAND = "/loop 5m kanban_list \u2014 follow Kanban Work Policy.";
1004
1004
 
1005
1005
  // ../../packages/core/dist/types/models.js
1006
1006
  var DEFAULT_MODELS = {
@@ -3148,4 +3148,4 @@ export {
3148
3148
  parseUsageBanner,
3149
3149
  KANBAN_LOOP_COMMAND
3150
3150
  };
3151
- //# sourceMappingURL=chunk-ZNRQSPPM.js.map
3151
+ //# sourceMappingURL=chunk-E56L56ER.js.map