@integrity-labs/agt-cli 0.22.0 → 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.
- package/dist/bin/agt.js +4 -4
- package/dist/{chunk-27FZ5QEI.js → chunk-6GNZJZCU.js} +71 -3
- package/dist/{chunk-27FZ5QEI.js.map → chunk-6GNZJZCU.js.map} +1 -1
- package/dist/{chunk-DBGGT2MC.js → chunk-DJH6JFF7.js} +20 -9
- package/dist/chunk-DJH6JFF7.js.map +1 -0
- package/dist/{chunk-BZV2KNHY.js → chunk-E56L56ER.js} +2 -24
- package/dist/chunk-E56L56ER.js.map +1 -0
- package/dist/{claude-pair-runtime-LZAGWNME.js → claude-pair-runtime-SN3CBW26.js} +2 -2
- package/dist/lib/manager-worker.js +7 -7
- package/dist/{persistent-session-EI7576OO.js → persistent-session-PZTMNCH3.js} +3 -3
- package/dist/{responsiveness-probe-SIMNGYC4.js → responsiveness-probe-VMKE3ARC.js} +3 -3
- package/package.json +1 -1
- package/dist/chunk-BZV2KNHY.js.map +0 -1
- package/dist/chunk-DBGGT2MC.js.map +0 -1
- /package/dist/{claude-pair-runtime-LZAGWNME.js.map → claude-pair-runtime-SN3CBW26.js.map} +0 -0
- /package/dist/{persistent-session-EI7576OO.js.map → persistent-session-PZTMNCH3.js.map} +0 -0
- /package/dist/{responsiveness-probe-SIMNGYC4.js.map → responsiveness-probe-VMKE3ARC.js.map} +0 -0
package/dist/bin/agt.js
CHANGED
|
@@ -26,7 +26,7 @@ import {
|
|
|
26
26
|
success,
|
|
27
27
|
table,
|
|
28
28
|
warn
|
|
29
|
-
} from "../chunk-
|
|
29
|
+
} from "../chunk-6GNZJZCU.js";
|
|
30
30
|
import {
|
|
31
31
|
CHANNEL_REGISTRY,
|
|
32
32
|
DEPLOYMENT_TEMPLATES,
|
|
@@ -52,7 +52,7 @@ import {
|
|
|
52
52
|
renderTemplate,
|
|
53
53
|
resolveChannels,
|
|
54
54
|
serializeManifestForSlackCli
|
|
55
|
-
} from "../chunk-
|
|
55
|
+
} from "../chunk-E56L56ER.js";
|
|
56
56
|
|
|
57
57
|
// src/bin/agt.ts
|
|
58
58
|
import { join as join10 } from "path";
|
|
@@ -3736,7 +3736,7 @@ import { execFileSync, execSync } from "child_process";
|
|
|
3736
3736
|
import { existsSync as existsSync5, realpathSync } from "fs";
|
|
3737
3737
|
import chalk17 from "chalk";
|
|
3738
3738
|
import ora15 from "ora";
|
|
3739
|
-
var cliVersion = true ? "0.22.
|
|
3739
|
+
var cliVersion = true ? "0.22.2" : "dev";
|
|
3740
3740
|
async function fetchLatestVersion() {
|
|
3741
3741
|
const host2 = getHost();
|
|
3742
3742
|
if (!host2) return null;
|
|
@@ -4268,7 +4268,7 @@ function handleError(err) {
|
|
|
4268
4268
|
}
|
|
4269
4269
|
|
|
4270
4270
|
// src/bin/agt.ts
|
|
4271
|
-
var cliVersion2 = true ? "0.22.
|
|
4271
|
+
var cliVersion2 = true ? "0.22.2" : "dev";
|
|
4272
4272
|
var program = new Command();
|
|
4273
4273
|
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");
|
|
4274
4274
|
program.hook("preAction", (thisCommand) => {
|
|
@@ -8,7 +8,7 @@ import {
|
|
|
8
8
|
parseDeliveryTarget,
|
|
9
9
|
registerFramework,
|
|
10
10
|
wrapScheduledTaskPrompt
|
|
11
|
-
} from "./chunk-
|
|
11
|
+
} from "./chunk-E56L56ER.js";
|
|
12
12
|
|
|
13
13
|
// ../../packages/core/dist/integrations/registry.js
|
|
14
14
|
var INTEGRATION_REGISTRY = [
|
|
@@ -2548,6 +2548,73 @@ ${lines.join("\n")}
|
|
|
2548
2548
|
|
|
2549
2549
|
Check \`.claude/skills/\` for detailed usage instructions for each integration.
|
|
2550
2550
|
|
|
2551
|
+
`;
|
|
2552
|
+
}
|
|
2553
|
+
function buildKanbanWorkPolicySection() {
|
|
2554
|
+
return `## Kanban Work Policy
|
|
2555
|
+
|
|
2556
|
+
Every 5 minutes you receive a \`/loop\` trigger that says "kanban_list \u2014
|
|
2557
|
+
follow Kanban Work Policy." When that trigger fires, this is what to do.
|
|
2558
|
+
|
|
2559
|
+
### Throttle yourself first
|
|
2560
|
+
|
|
2561
|
+
If you're mid-task, mid-conversation with a user, or otherwise busy on
|
|
2562
|
+
something more important, just briefly acknowledge the tick and continue
|
|
2563
|
+
what you were doing. The loop is automatic \u2014 missing one tick costs
|
|
2564
|
+
nothing; interrupting active work to satisfy it costs the user.
|
|
2565
|
+
|
|
2566
|
+
### Walk the board
|
|
2567
|
+
|
|
2568
|
+
1. **Resume in-progress work first.** If \`kanban_list\` shows an item
|
|
2569
|
+
in \`in_progress\`, continue working on it. The most common reason
|
|
2570
|
+
it exists is that *you* created it on a prior tick and got
|
|
2571
|
+
interrupted by a restart \u2014 resume.
|
|
2572
|
+
2. **Then pull from todo/backlog.** If no \`in_progress\` items, pick
|
|
2573
|
+
the highest-priority \`todo\` (or \`backlog\` if todo is empty),
|
|
2574
|
+
call \`kanban_move\` to move it to \`in_progress\`, then work on it.
|
|
2575
|
+
3. **Self-initiated work needs a row too.** If neither path above
|
|
2576
|
+
applies and you decide to do work on your own initiative (follow
|
|
2577
|
+
up on something you noticed, check on a recurring concern), call
|
|
2578
|
+
\`kanban_add\` with \`status="in_progress"\` BEFORE you start.
|
|
2579
|
+
That's what makes your work crash-recoverable: if the session
|
|
2580
|
+
restarts mid-work, the orphan row is what tells the next tick to
|
|
2581
|
+
resume rather than start over.
|
|
2582
|
+
|
|
2583
|
+
### DO NOT create a row when
|
|
2584
|
+
|
|
2585
|
+
- You read the board and there's nothing to do \u2014 stand down silently.
|
|
2586
|
+
**Empty ticks produce no rows.** The "work" of checking the board
|
|
2587
|
+
is not itself a row.
|
|
2588
|
+
- You're acknowledging a tick that landed during active work.
|
|
2589
|
+
|
|
2590
|
+
### Terminate every row you started
|
|
2591
|
+
|
|
2592
|
+
Each row you started must reach a terminal state on the same or a
|
|
2593
|
+
later tick:
|
|
2594
|
+
|
|
2595
|
+
- **\`kanban_done\` with a clear result** when the work produced its
|
|
2596
|
+
expected output.
|
|
2597
|
+
- **\`kanban_fail\` with a reason** when something went wrong
|
|
2598
|
+
(missing access, credential failure, tool error). The work was
|
|
2599
|
+
attempted but failed.
|
|
2600
|
+
- **\`kanban_cancel\` with a reason** when you started, then realised
|
|
2601
|
+
the work isn't actually needed (precondition no longer holds,
|
|
2602
|
+
duplicate of another task, asker changed their mind, data was
|
|
2603
|
+
already current). This is distinct from \`kanban_fail\`: nothing
|
|
2604
|
+
went wrong; you wisely didn't bother. Use this generously \u2014 it's
|
|
2605
|
+
cheaper than running unneeded work to a forced "done".
|
|
2606
|
+
- **\`kanban_update\` with notes** if you're blocked but might unblock
|
|
2607
|
+
later; leave the row in \`in_progress\` and pick up other work.
|
|
2608
|
+
|
|
2609
|
+
### When the board is empty
|
|
2610
|
+
|
|
2611
|
+
- If \`todo\` and \`in_progress\` are both empty but \`backlog\` has
|
|
2612
|
+
items, don't self-assign. Message your manager once asking which
|
|
2613
|
+
backlog item to pick up; then stand down. Don't re-escalate on
|
|
2614
|
+
every tick.
|
|
2615
|
+
- If \`backlog\` is also empty, say "All clear, no pending work" once
|
|
2616
|
+
and stand down.
|
|
2617
|
+
|
|
2551
2618
|
`;
|
|
2552
2619
|
}
|
|
2553
2620
|
function buildSkillAuthoringSection() {
|
|
@@ -2855,6 +2922,7 @@ function generateClaudeMd(input) {
|
|
|
2855
2922
|
const memorySection = buildMemorySection(hasQmd);
|
|
2856
2923
|
const integrationsSection = buildIntegrationsSection(integrations);
|
|
2857
2924
|
const knowledgeSection = buildKnowledgeSection2(knowledge);
|
|
2925
|
+
const kanbanWorkPolicySection = buildKanbanWorkPolicySection();
|
|
2858
2926
|
const skillAuthoringSection = buildSkillAuthoringSection();
|
|
2859
2927
|
const personalitySection = buildPersonalitySection(personalitySeed);
|
|
2860
2928
|
const reportsToSection = buildReportsToSection2(reportsTo);
|
|
@@ -3104,7 +3172,7 @@ first to load your recent board state. This gives you context about completed an
|
|
|
3104
3172
|
in-progress items so you can answer accurately.
|
|
3105
3173
|
|
|
3106
3174
|
${memorySection}
|
|
3107
|
-
${reportsToSection}${teamSection}${peopleSection}${multiAgentSection}${integrationsSection}${knowledgeSection}${skillAuthoringSection}## Dashboards
|
|
3175
|
+
${reportsToSection}${teamSection}${peopleSection}${multiAgentSection}${integrationsSection}${knowledgeSection}${kanbanWorkPolicySection}${skillAuthoringSection}## Dashboards
|
|
3108
3176
|
|
|
3109
3177
|
You can publish your own dashboards inside the Augmented console. They are
|
|
3110
3178
|
**first-class platform artifacts** \u2014 KPI tiles, charts, refresh-on-demand \u2014
|
|
@@ -6536,4 +6604,4 @@ export {
|
|
|
6536
6604
|
managerInstallSystemUnitCommand,
|
|
6537
6605
|
managerUninstallSystemUnitCommand
|
|
6538
6606
|
};
|
|
6539
|
-
//# sourceMappingURL=chunk-
|
|
6607
|
+
//# sourceMappingURL=chunk-6GNZJZCU.js.map
|