Replace shipped pipeline examples with research and task starters

This commit is contained in:
2026-11-12 02:17:09 +00:00
parent 2330f50268
commit 340c07e5a3
28 changed files with 306 additions and 402 deletions
+5 -5
View File
@@ -159,7 +159,7 @@ pipelines edit # fuzzy pipeline selection
pipelines edit "bug fix" # ask the harness what to change
pipelines edit "bug fix" "Add a review step"
pipelines new "release notes" "Summarize changes and notify my phone"
pipelines new "Add a feature" --template feedback-loop
pipelines new "Add a feature" --template task
```
`new` opens the configured harness (Pi or OpenCode; host by default, or
@@ -222,10 +222,10 @@ is not ownership (the kernel lock is). This is a local-filesystem lock, not a
distributed lease; hard-link database aliases and filesystems without reliable
advisory locking are unsupported.
Use `:templates` for the four manual-only examples, read in order: one stage,
two stages, a feedback loop and a human decision (`examples/README.md`). A
brand-new database already holds them as ordinary pipelines; the server seeds
them once and never again, so removing them or upgrading never brings them back.
Use `:templates` for the two general-purpose starters, research and task
(`examples/README.md`). A brand-new database already holds them as ordinary
pipelines; the server seeds them once and never again, so removing them or
upgrading never brings them back.
**Submit template** (`s` or Enter) asks for a
name without opening an editor. Enter saves a retained draft, then a separate
confirmation publishes it as a new pipeline. Esc before naming creates nothing;