substrate-ai 0.5.6 → 0.5.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -18,6 +18,8 @@ substrate run --events --stories 1-1,1-2,1-3
|
|
|
18
18
|
|
|
19
19
|
If substrate needs input it can't auto-detect (e.g., a project concept for analysis), it will exit with a clear error message telling you what to provide.
|
|
20
20
|
|
|
21
|
+
**Scope warning:** Without `--stories`, substrate auto-discovers ALL pending stories across ALL epics and may dispatch 30+ stories at once. For controlled runs, always specify story keys explicitly with `--stories`.
|
|
22
|
+
|
|
21
23
|
**CRITICAL execution rules:**
|
|
22
24
|
- Pipeline runs take **5–40 minutes**. You MUST use `run_in_background: true` or `timeout: 600000` (10 min) when invoking via Bash tool. Default 2-minute timeout WILL kill the pipeline.
|
|
23
25
|
- **NEVER pipe substrate output** to `head`, `tail`, `grep`, or any command that may close the pipe early — this causes EPIPE stalls that hang the process.
|
|
@@ -41,6 +43,8 @@ For long-running pipelines, attach the **supervisor** for automatic stall detect
|
|
|
41
43
|
substrate supervisor --output-format json
|
|
42
44
|
```
|
|
43
45
|
|
|
46
|
+
**CRITICAL: Only attach a supervisor to runs you started in the same session.** Attaching a supervisor to another session's run risks killing healthy dispatches and restarting with incorrect scope. The supervisor inherits story keys from the health snapshot on restart, but cross-session interference can cause unexpected behavior.
|
|
47
|
+
|
|
44
48
|
**Interpreting silence:** No output for 5 minutes = normal (agent is working). No output for 15+ minutes = likely stalled. Use `substrate health` to confirm, then consider killing and resuming.
|
|
45
49
|
|
|
46
50
|
### After Pipeline Completes
|