svamp-cli 0.2.128 → 0.2.130

package/bin/skills/crew/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: crew
 version: 0.1.0
-description: Coordinate work as a lead delegating features to managed worktree children — spawn a child per feature on its own branch, supervise it, and pull finished work back to the base branch with merge-and-close. Use when one session should run a project and farm out features instead of piling many sessions on one working tree.
+description: Coordinate work as a lead delegating features to managed worktree children — spawn a child per feature on its own branch, run it as a loop until done, and pull finished work back to the base branch with merge-and-close. Use when one session should run a project and farm out features instead of piling many sessions on one working tree.
 ---
 
 # Crew — a lead session that delegates features to managed worktree children
@@ -13,16 +13,16 @@ the same working tree.
 
 A **crew** is emergent, not a heavy object: it is just plain sessions linked by
 `parentSessionId` + a `crew.role`. A **feature child** always (a) has the lead as its
-parent, (b) lives in its own `.dev/worktree/<n>` on its own branch, and (c) is supervised
-with `judge: parent` — i.e. **the lead is the judge** that decides when the child is done
-(this is the `judge:parent` case of the Supervisor Gate; see the loop/supervisor skill).
+parent, (b) lives in its own `.dev/worktree/<n>` on its own branch, and (c) runs as a loop
+with `parent: <lead>` — i.e. **the lead is the judge** that decides when the child is done
+(this is the `parent`-routed case of the loop … until gate; see the `loop` skill).
 
 ## The verbs (these are your tools)
 
 ```
 svamp feature start "<brief>" [--oracle "<test cmd>"] [--base <branch>] [--action nudge|block]
-        # (lead) create a worktree child on a new branch, attach a supervisor
-        # (oracle → parent), and brief it. Prints the child id.
+        # (lead) create a worktree child on a new branch, run it as a loop until done
+        # (oracle → parent verdict), and brief it. Prints the child id.
 svamp feature list [--json]
         # (lead) your children: branch, ahead/behind base, dirty, idle/active.
 svamp feature report "<text>" [--blocker]
@@ -43,8 +43,9 @@ You coordinate the project. Keep your own working tree (the base branch, e.g. `m
   `--oracle "<cmd>"` so it's auto-checked.
 - **Stay aware:** run `svamp feature list` when you start working and whenever you manage the
   crew. Your children also **push** to you: progress notes, blockers, merge-requests, and
-  supervision verdicts all arrive in your inbox as `<feature-progress>`, `<feature-blocker>`,
-  `<merge-request>`, and `<supervision-verdict>` messages.
+  loop verdicts all arrive in your inbox as `<feature-progress>`, `<feature-blocker>`,
+  `<merge-request>`, and `<supervision-verdict>` messages (the verdict's wire tag name is
+  unchanged for back-compat).
 - **Review & merge — this is the gradient that closes the loop.** When a child sends a
   `<merge-request>` or you receive a `<supervision-verdict … verdict="approved">` from a
   child, **run `svamp feature merge <child-id>`**. With an oracle that passed, this is the
@@ -59,7 +60,7 @@ You coordinate the project. Keep your own working tree (the base branch, e.g. `m
 ## If you are a FEATURE CHILD
 
 You own one feature in an isolated worktree on your own branch, reporting to your lead. Your
-brief (and your supervisor's criteria) is injected each turn.
+brief (and your loop's "until" criteria) is injected each turn.
 
 - **Work in your worktree.** Implement the feature. Commit as you go. Keep the oracle/tests green.
 - **Report.** Use `svamp feature report "<note>"` for milestones and `--blocker` when stuck —
@@ -75,7 +76,7 @@ brief (and your supervisor's criteria) is injected each turn.
 
 - **One conversation, many features.** The lead is your single point of control; children run in
   parallel isolation and report up.
-- **Merge-and-close is the default, not a chore.** The supervisor routes a verdict to the lead,
+- **Merge-and-close is the default, not a chore.** The loop gate routes a verdict to the lead,
   the lead merges, the child closes — the "gradient" that keeps finished work from rotting on a
   stale branch.
 - **Isolation by worktree.** Each feature has its own branch + tree, so children never collide on

package/bin/skills/loop/bin/checklist.mjs

@@ -16,8 +16,9 @@ import { join, dirname } from 'node:path';
 import { execSync } from 'node:child_process';
 
 // CANONICAL: the session checklist lives INSIDE the loop dir at
-// <project>/.svamp/<sid>/loop/checklist.json — beside the other supervisor state
-// (loop-state.json, supervisor-verdict.json). Matches the daemon writer
+// <project>/.svamp/<sid>/loop/checklist.json — beside the other loop-gate state
+// (loop-state.json, supervisor-verdict.json — the latter is the daemon's legacy
+// verdict file name). Matches the daemon writer
 // (checklist/core.ts checklistPath) + the frontend (sync/ops.ts sessionChecklistRel).
 export function sessionChecklistPath(loopDir) { return join(loopDir, 'checklist.json'); }
 export function projectChecklistPath(projectDir) { return join(projectDir, '.svamp', 'checklist.json'); }

package/bin/skills/loop/bin/loop-init.mjs

@@ -71,8 +71,8 @@ const config = {
   // and resolve their own dir relatively) read this to run the oracle + fingerprint the
   // work product, since their depth no longer encodes the project root.
   project_dir: dir,
-  // The success contract — the durable thing the gate judges against. Read by the daemon
-  // to populate the supervision:verdict event (docs/supervisor-gate-design.md).
+  // The success contract — the "until" the loop gate runs against. Read by the daemon
+  // to populate the loop verdict event (legacy wire type: supervision:verdict).
   ...(criteria ? { criteria: criteria.trim() } : {}),
   oracle: oracle ? { command: oracle, timeout_sec: 600 } : null,
   evaluator: { enabled: evaluatorOn, model },

package/dist/{agentCommands-jGCEdEYn.mjs → agentCommands-DOUG625_.mjs}

@@ -2,7 +2,7 @@ import { existsSync, readFileSync, mkdirSync, writeFileSync, renameSync } from '
 import { join, dirname } from 'node:path';
 import os from 'node:os';
 import { requireNotSandboxed } from './sandboxDetect-DNTcbgWD.mjs';
-import { m as shortId } from './run-C23-A9KM.mjs';
+import { m as shortId } from './run-DMahGhJP.mjs';
 import 'os';
 import 'fs/promises';
 import 'fs';
@@ -96,7 +96,7 @@ async function sessionSetTitle(title) {
 }
 async function sessionSetProjectDescription(description) {
   const dir = process.cwd();
-  const { projectName, writeProjectInfo, sanitizeDescription, projectInfoPath } = await import('./run-C23-A9KM.mjs').then(function (n) { return n.Z; });
+  const { projectName, writeProjectInfo, sanitizeDescription, projectInfoPath } = await import('./run-DMahGhJP.mjs').then(function (n) { return n.Z; });
   const desc = sanitizeDescription(description, 240);
   if (!desc) {
     console.error("Project description is empty.");
@@ -180,7 +180,7 @@ async function sessionBroadcast(action, args) {
   console.log(`Broadcast sent: ${action}`);
 }
 async function connectToMachineService() {
-  const { connectAndGetMachine } = await import('./commands-BVx72l2K.mjs');
+  const { connectAndGetMachine } = await import('./commands-QGaI-ukW.mjs');
   return connectAndGetMachine();
 }
 async function inboxSend(targetSessionId, opts) {
@@ -197,7 +197,7 @@ async function inboxSend(targetSessionId, opts) {
   }
   const { server, machine } = await connectToMachineService();
   try {
-    const { resolveSessionId } = await import('./commands-BVx72l2K.mjs');
+    const { resolveSessionId } = await import('./commands-QGaI-ukW.mjs');
     const sessions = await machine.listSessions();
     const match = resolveSessionId(sessions, targetSessionId);
     const fullTargetId = match.sessionId;

package/dist/{auth-DVa-sVa9.mjs → auth-UNUDBJKU.mjs}

@@ -1,4 +1,4 @@
-import { D as resolveModel } from './run-C23-A9KM.mjs';
+import { D as resolveModel } from './run-DMahGhJP.mjs';
 import 'os';
 import 'fs/promises';
 import 'fs';