@volter/supercode-orchestrator 0.4.40 → 0.4.42

package/board/dispatch.mjs

@@ -595,10 +595,10 @@ function launchPane(board, task, runId, lane, fleet, { input = null, slot = 'wor
   tx(board, (db) => {
     setRunSession(db, runId, session);
     event(db, task.id, kind, { session_id: session.session_id, machine, pane: session.pane, address: session.address, mode: session.mode, ...(replaced ? { replaced } : {}) }, runId);
-    // the working session hears updates to its card; a session no longer working it does not
-    for (const s of subscriptions(db, task.id)) {
-      if (s.delivery_metadata?.role === 'worker' && s.chat_id !== session.address) db.prepare("DELETE FROM kanban_notify_subs WHERE task_id = ? AND platform = 'supercode' AND chat_id = ?").run(task.id, s.chat_id);
-    }
+    // the working session hears updates to its card; the slot's previous session no longer does (a reviewer starting
+    // leaves the implementer's, and a subtask's arc session's, subscription alone)
+    const before = prev ? prev.address ?? `sc:${prev.machine}:claude-code:${prev.session_id}` : null;
+    if (before && before !== session.address) db.prepare("DELETE FROM kanban_notify_subs WHERE task_id = ? AND platform = 'supercode' AND chat_id = ?").run(task.id, before);
     subscribeIn(db, task.id, session.address, 'worker');
     // it sees the cards its own depends on change, and works its subtasks
     for (const p of db.prepare('SELECT parent_id FROM task_links WHERE child_id = ?').all(task.id)) subscribeIn(db, p.parent_id, session.address, 'dependency');
@@ -783,11 +783,10 @@ async function notify(board, fleet, report, entry) {
   // each subscription's notices go in order; different subscribers are told side by side
   await pool(subscriptions(board.db).filter((sub) => sub.platform === 'supercode'), SEND_CONCURRENCY, async (sub) => {
     const role = ['worker', 'dependency'].includes(sub.delivery_metadata?.role) ? sub.delivery_metadata.role : 'creator';
-    // a session that worked or watched a card and is gone hears nothing more; a creator is retried until it is back
-    if (role !== 'creator' && fleet.ok && !fleet.alive.has(sub.chat_id)) {
-      tx(board, (db) => db.prepare("DELETE FROM kanban_notify_subs WHERE task_id = ? AND platform = 'supercode' AND chat_id = ?").run(sub.task_id, sub.chat_id));
-      return;
-    }
+    // a session the fleet does not list this tick is told next tick: one reading is not a loss (a loaded box drops
+    // sessions from a read, and a dropped subscription never came back), and a session that is replaced on its card
+    // has its subscription moved when the new one starts
+    if (role !== 'creator' && fleet.ok && !fleet.alive.has(sub.chat_id)) return;
     const kinds = heardBy(entry, role);
     if (!kinds.length) return;
     const events = board.db.prepare(`SELECT id, kind, payload, created_at FROM task_events WHERE task_id = ? AND id > ? AND kind IN (${kinds.map(() => '?').join(', ')}) ORDER BY id`)

package/board/workflow.mjs

@@ -94,7 +94,7 @@ export function scopeOf(db, board, task, { params, event = {}, extra = {} } = {}
     goal_mode: Boolean(task.goal_mode),
     implementer: asked.implementer ?? task.assignee,
     last_reviewer: changes.reviewer ?? null,
-    arc: task.subtask_of ? one(db, 'SELECT id, status, title, assignee FROM tasks WHERE id = ?', task.subtask_of) ?? null : null,
+    arc: task.subtask_of ? one(db, 'SELECT id, status, title, body, assignee FROM tasks WHERE id = ?', task.subtask_of) ?? null : null,
     // the cards filed as its subtasks (`create --subtask-of`), in the order they were filed
     subtasks: all(db, 'SELECT t.id, t.status, t.title, t.assignee FROM tasks t JOIN supercode_cards c ON c.task_id = t.id WHERE c.subtask_of = ? ORDER BY t.created_at', task.id),
     queue_reason: json(one(db, "SELECT payload FROM task_events WHERE task_id = ? AND kind = 'respawn_guarded' AND created_at >= ? ORDER BY id DESC LIMIT 1",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@volter/supercode-orchestrator",
-  "version": "0.4.40",
+  "version": "0.4.42",
   "type": "module",
   "description": "The orchestrator runtime over the Volter Harness ontology: one typed operational model whose folder is its serialization, read and written through the harness orchestration doors (docs/ORCHESTRATOR-IR.md)",
   "exports": {