@volter/supercode-orchestrator 0.4.143 → 0.4.144

package/board/ci.mjs

@@ -98,14 +98,21 @@ export function observeCompletionEvidence(board, id, entry, payload = {}) {
     // need a successful native deployment containing this task's native changes.
     // Retain each artifact's actual SHA, rather than calling the SDK run a native release.
     state.coverage = [];
-    let successful;
+    const deployments = new Map();
     for (const rule of matchedRules) {
       if (rule.workflows.includes(receipt.workflowName)) continue;
-      successful ??= JSON.parse(run('gh', ['run', 'list', '--repo', repo, '--status', 'success', '--limit', '100', '--json', 'databaseId,workflowName,headSha,status,conclusion,url'], path));
+      for (const workflow of rule.workflows) {
+        if (!deployments.has(workflow)) deployments.set(workflow, JSON.parse(run('gh', ['run', 'list', '--repo', repo, '--workflow', workflow, '--limit', '100', '--json', 'databaseId,workflowName,headSha,status,conclusion,url'], path)));
+      }
+      const successful = rule.workflows.flatMap(workflow => deployments.get(workflow)).filter(row => row.status === 'completed' && row.conclusion === 'success');
       const covering = successful.find(row => {
         if (!rule.workflows.includes(row.workflowName) || !configured.includes(row.workflowName)) return false;
         try {
           run('git', ['merge-base', '--is-ancestor', rule.changed_at, row.headSha], path);
+          try {
+            run('git', ['merge-base', '--is-ancestor', commit, row.headSha], path);
+            return true;
+          } catch {}
           run('git', ['merge-base', '--is-ancestor', row.headSha, commit], path);
           // Any later change in these paths requires another native deployment,
           // even when a different task authored that change.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@volter/supercode-orchestrator",
-  "version": "0.4.143",
+  "version": "0.4.144",
   "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": {