stageflow 0.9.0 → 0.12.0

package/dist/ui/index.html

@@ -13,8 +13,8 @@
     <link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Figtree:wght@400;500;600;700&display=swap" />
     <link rel="icon" type="image/svg+xml" href="/stageflow-icon.svg" />
     <title>Stageflow</title>
-    <script type="module" crossorigin src="/assets/index-CSoGDA3A.js"></script>
-    <link rel="stylesheet" crossorigin href="/assets/index-C3N7MXAC.css">
+    <script type="module" crossorigin src="/assets/index-CXGz4nL7.js"></script>
+    <link rel="stylesheet" crossorigin href="/assets/index-uVHiae8s.css">
   </head>
   <body>
     <div id="root"></div>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "stageflow",
-  "version": "0.9.0",
+  "version": "0.12.0",
   "description": "Stageflow — CLI pipeline runtime for configurable stages on Pi",
   "type": "module",
   "bin": {
@@ -60,6 +60,7 @@
     "vitest": "^4.1.10"
   },
   "dependencies": {
+    "@anthropic-ai/claude-agent-sdk": "^0.3.263",
     "@earendil-works/pi-ai": "^0.84.1",
     "@earendil-works/pi-coding-agent": "^0.84.1",
     "@modelcontextprotocol/node": "^2.0.0",

package/skills/stageflow-author/references/catalog-mapping.md

@@ -16,18 +16,19 @@ Collision handling lives in [`catalog-write-conventions.md`](catalog-write-conve
 
 ## Sequencing
 
-`needs` is a single parent stage id. Fan-in (one stage needing two parents) is out of catalog shape.
+`needs` is a single parent stage id, or an array of at least two parent ids when one step waits for several earlier steps. Strings default to `on: [succeeded]`. `{ id, on }` accepts a non-empty unique subset of `succeeded` | `failed` | `skipped`.
 
 | Human says | Pipeline shape |
 |---|---|
 | Steps in order | Each later stage `needs` the previous id. No `fork` field. |
 | Steps happen together | Sibling stages share one `needs` (the same parent). No `fork` field. |
+| A later step waits for two or more earlier steps | That stage `needs` an array of those parent ids (length ≥ 2). |
 | Exactly one branch runs | Deciding stage gets `fork: { select: one }`. Each branch `needs` the decider. |
 | Either, both, or a subset may run | Deciding stage gets `fork: { select: subset }`. Each branch `needs` the decider. |
 
 Default `select` is `one` unless the human says more than one branch can run.
 
-Map linear chains, sibling fan-out, and single-level `fork`. A runtime clone count is not knowable from a static description — stay on those three shapes. Leave `clonable` and `clone_forks` unset.
+Map linear chains, sibling fan-out, generic fan-in (`needs` array), and single-level `fork`. A runtime clone count is not knowable from a static description — leave `clonable` and `clone_forks` unset. Clone-list joins (one catalog parent, `priorEnvelopes`) are not this shape.
 
 A review, approval, or sign-off step is a gated stage: put `gate_kinds` on that stage file and follow [`stage-prompt-template.md`](stage-prompt-template.md).
 
@@ -110,6 +111,29 @@ stages:
 
 No `fork` field. Both siblings run.
 
+### Diamond join
+
+"After research and validation both finish, synthesize":
+
+```yaml
+stages:
+  - id: clarify
+    uses: ./clarify.yaml
+  - id: research
+    uses: ./research.yaml
+    needs: clarify
+  - id: validation
+    uses: ./validation.yaml
+    needs: clarify
+  - id: synthesize
+    uses: ./synthesize.yaml
+    needs:
+      - research
+      - validation
+```
+
+`needs` array length is ≥ 2. The join reads `priorEnvelopesByStage`, not clone-list `priorEnvelopes`.
+
 ### Fork, select subset
 
 "Email, post, or both could go out":

package/skills/stageflow-author/references/catalog-write-conventions.md

@@ -20,7 +20,7 @@ One directory (or the project root) holds:
 | `<pipeline-id>.pipeline.yaml` | `id` matching the filename stem; `stages:` object entries |
 | `<stage-id>.yaml` | `id`, `system_prompt`, `model`; `gate_kinds` when the step is gated |
 
-Each pipeline stage entry has `id` and `uses: ./<id>.yaml` (path relative to the pipeline file). Non-root stages add `needs: <parent-id>`. A deciding stage adds `fork:`. Filename stem matches `id` on every file.
+Each pipeline stage entry has `id` and `uses: ./<id>.yaml` (path relative to the pipeline file). Non-root stages add `needs: <parent-id>`, or `needs:` as an array of at least two parent ids (strings or `{ id, on }`) when the stage waits for several parents. A deciding stage adds `fork:`. Filename stem matches `id` on every file.
 
 ## Collisions