castle-web-cli 0.4.36 → 0.4.37

package/dist/agent-prompts.js

@@ -20,7 +20,6 @@ Hard rules:
 \`\`\`castle-task
 short imperative title on the first line
 after: comma-separated titles or ids this task must wait for (optional line)
-supersedes: comma-separated titles or ids this task replaces (optional line)
 Then a SHORT self-contained prompt -- one tight paragraph (aim under 100
 words): what to build or fix and what "done" looks like. Task agents read
 the deck's own docs for framework/API detail, so never restate recipes,
@@ -28,23 +27,22 @@ file layouts, or implementation steps.
 \`\`\`
 
 - Use \`after:\` only when a task truly builds on or would conflict with another (it may reference tasks spawned in this same reply, by title). Independent tasks must NOT wait on each other.
-- Use \`supersedes:\` whenever the new task fixes, redoes, or makes obsolete an earlier task -- the old row is checked off the user's board automatically. Keep the board meaning "what to look at right now".
-- When the user clearly confirms something works (or tells you to clear items), check those finished tasks off the board by including:
+
+Keeping the board clean. The background-tasks list below IS the board the user sees -- every row, with its id and status. Be diligent about removing rows that no longer belong, using these two fences:
 
 \`\`\`castle-done
-comma-separated titles or ids of the finished tasks
+comma-separated finished-task titles or ids, or \`all\`
 \`\`\`
-
-- NEVER check a task off on your own judgment -- only a clear user statement that it works (or an explicit ask to clear it) counts. When in doubt, leave the row on the board.
-- The background-tasks list below IS the board the user sees -- every row, with its id. To clear the WHOLE board at once (e.g. "clear all the tasks"), use \`all\` instead of listing ids: a \`castle-done\` with body \`all\` checks off every finished row, and a \`castle-stop\` with body \`all\` stops everything still running. Never claim the board is cleared without actually emitting the fence.
-- To STOP tasks (running or waiting) when the user asks or their work is clearly no longer wanted, include:
-
 \`\`\`castle-stop
-comma-separated titles or ids of the tasks to stop
+comma-separated active-task titles or ids, or \`all\`
 \`\`\`
 
-Stopped tasks show as interrupted on the board. If a new task replaces the stopped work, prefer \`supersedes:\` on the new task instead.
-- Tasks are one-and-done -- when the user gives feedback on a finished task, spawn a new fix task rather than reopening the old one.
+- \`castle-done\` removes FINISHED rows (done/failed). Use it when the user confirms a task works, or to clear a finished task that has become obsolete (replaced by newer work). \`all\` clears every finished row.
+- \`castle-stop\` stops AND removes ACTIVE rows (running/waiting) -- a running task's agent is killed. Use it when the user asks to stop something, or when you spawn a fix/replacement that makes an in-flight task obsolete. \`all\` stops everything active.
+- When you spawn a task that fixes, redoes, or replaces an earlier one, remove the earlier one in the SAME reply: \`castle-done\` if it already finished, \`castle-stop\` if it is still running or waiting. Keep the board meaning "what to look at right now".
+- Do not mark a task done to imply YOU verified its quality -- the user playtests and confirms that. But DO keep the board tidy: clear finished work the user blessed, and remove anything clearly obsolete. When genuinely unsure, leave the row.
+- Never claim the board is cleared without actually emitting the fence.
+- Tasks are one-and-done -- when the user gives feedback on a finished task, spawn a new fix task (and \`castle-done\` the old row) rather than reopening it.
 - Task agents are capable coding agents working in this same deck directory, but they know nothing about this conversation beyond your prompt.
 
 Conversation style:

package/dist/agent.js

@@ -113,8 +113,7 @@ function visibleLength(raw) {
     return raw.length;
 }
 // Pull ```castle-task fenced directives out of a finished router reply.
-// Block format: title line, then optional "after:" / "supersedes:" lines (in
-// either order), then the task prompt.
+// Block format: title line, then an optional "after:" line, then the prompt.
 function extractDirectives(full) {
     const directives = [];
     const checkoffs = [];
@@ -135,9 +134,9 @@ function extractDirectives(full) {
     const cleaned = withoutDone.replace(fenceRe, (_match, body) => {
         const lines = String(body).replace(/\r/g, '').split('\n');
         const title = (lines.shift() ?? '').trim();
-        const headers = { after: [], supersedes: [] };
+        const headers = { after: [] };
         while (lines.length > 0) {
-            const headerMatch = /^(after|supersedes):\s*(.*)$/i.exec((lines[0] ?? '').trim());
+            const headerMatch = /^(after):\s*(.*)$/i.exec((lines[0] ?? '').trim());
             if (!headerMatch)
                 break;
             lines.shift();
@@ -148,7 +147,7 @@ function extractDirectives(full) {
         }
         const prompt = lines.join('\n').trim();
         if (title) {
-            directives.push({ title, after: headers.after, supersedes: headers.supersedes, prompt });
+            directives.push({ title, after: headers.after, prompt });
         }
         return '';
     });
@@ -528,6 +527,9 @@ function createTaskStore(opts) {
             refreshTaskFiles(tasksDir, task);
             const wasStopped = stopRequested.delete(task.id);
             task.status = wasStopped ? 'interrupted' : result.ok ? 'done' : 'failed';
+            // A stopped task is cleared off the board (castle-stop = halt + remove).
+            if (wasStopped)
+                task.acknowledged = true;
             if (result.ok && !wasStopped)
                 task.progress = 100;
             task.finishedAt = nowIso();
@@ -543,19 +545,6 @@ function createTaskStore(opts) {
         });
     }
     function spawnFromDirective(directive, originMessageId) {
-        // A fix/redo task sweeps the rows it obsoletes off the user's board. Halt
-        // first -- a superseded task that is still running must have its process
-        // killed (not just hidden, which left an invisible zombie the rest of the
-        // board could depend on), and a waiting one must not start later.
-        for (const id of resolveDeps(tasks, directive.supersedes)) {
-            const old = tasks.get(id);
-            if (old && !old.acknowledged) {
-                haltTask(old);
-                old.acknowledged = true;
-                touch(old);
-                opts.onSuperseded(old);
-            }
-        }
         const task = {
             id: nanoid(8),
             title: directive.title,
@@ -621,12 +610,14 @@ function createTaskStore(opts) {
     // stop everything still active. Waiting tasks are cancelled outright;
     // running ones get their agent process killed and finalize as interrupted
     // via the stopRequested path.
-    // Halt an active task: a waiting one is cancelled (-> interrupted); a
-    // running one gets its agent process killed and finalizes as interrupted
-    // via the stopRequested path. No-op on terminal tasks.
+    // Halt + remove an active task (castle-stop): a waiting one is cancelled and
+    // cleared off the board immediately; a running one gets its agent process
+    // killed and is cleared when it finalizes (the stopRequested path acks it).
+    // No-op on terminal tasks.
     function haltTask(task) {
         if (task.status === 'waiting') {
             task.status = 'interrupted';
+            task.acknowledged = true;
             touch(task);
         }
         else if (task.status === 'running') {
@@ -992,7 +983,6 @@ export function createAgentServer(opts) {
         onStarted: () => undefined,
         onRetry: (task, attempt) => addLog(`agent died, retrying (${attempt}/${MAX_TASK_ATTEMPTS}): ${task.title}`),
         onFinished: (task) => taskFeeds.map.delete(task.id),
-        onSuperseded: () => undefined,
         onFeed: (task, entry) => taskFeeds.push(task, entry),
     });
     // A new user message interrupts the in-flight router reply: its partial

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "castle-web-cli",
-  "version": "0.4.36",
+  "version": "0.4.37",
   "type": "module",
   "bin": {
     "castle-web": "./dist/index.js"