Replace niche templates with simple starters and direct template submission

This commit is contained in:
2026-10-10 02:37:31 +01:00
parent 4cae37f950
commit 7b10e3889e
38 changed files with 389 additions and 1195 deletions
+10 -2
View File
@@ -50,7 +50,7 @@ pipelines edit # fuzzy pipeline selection
pipelines edit "bug fix" # ask OpenCode what to change
pipelines edit "bug fix" "Add a review step"
pipelines new "release notes" "Summarize changes and notify my phone"
pipelines new "weekly digest" --template scheduled-summary
pipelines new "Text summary" --template summary
```
`new` opens OpenCode immediately when its name/request is omitted. The skill asks
@@ -70,7 +70,15 @@ Every submission, including agent-issued `submit`/`rpc`, still uses server valid
## Drafts in the TUI
Home's `n` / `:new` and Enter on a template first ask how to author the new
Use `:templates` for five simple, manual-only starters: task, summary, review,
research, and plan/implement/review. **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;
Esc at publication keeps the draft. **Customize** (`e`) opens the editor picker
instead. Both paths inherit the configured default model and preserve existing
pipelines/history. The research starter requires configured web search support.
Home's `n` / `:new` and **Customize** (`e`) on a template first ask how to author the new
pipeline: **nvim** opens a retained Markdown draft file, or **OpenCode** opens
the collaborative harness with `@pipelines`. Tab/Shift+Tab or arrows select;
typing fuzzy-searches the choices; Enter launches and Esc cancels without
+2 -2
View File
@@ -127,8 +127,8 @@ go run ./cmd/pipelines-tui -url ws://127.0.0.1:8081/connect
If the TUI is on another machine, use an SSH/VPN tunnel instead of exposing the
unauthenticated pipeline port publicly. The bundled examples are not automatically
submitted. Copy `examples/anime-digest.md` into an editor draft to create that
pipeline; submitting activates its daily 19:00 schedule.
submitted. Open `:templates` and use **Submit template** to name/review/publish a
simple starter, or **Customize** to edit it first. All bundled starters are manual-only.
## 4. Android
+4 -4
View File
@@ -165,10 +165,10 @@ File-attachment bytes are stored by ntfy, not permanently archived in SQLite;
run metadata stores the delivered filename/URL, and workspace files may later
change. Download attachments before your ntfy retention expires.
`examples/anime-digest.md` provides discover → compose with per-stage notification hooks and daily 19:00
scheduling. It uses direct `webfetch` of Jikan's current-season API, avoiding the
unconfigured OpenCode search-provider selection. The example is a file only;
submitting it activates its schedule. Its anime/model/phone path is **not tested**.
Bundled starters do not require notification or schedule setup. Add a `notify`
block to the stages of your own workflow using the example above; configure the
system phone connection first. Adding a schedule activates it on publication,
so review it explicitly rather than copying a scheduled niche example.
References: [publishing](https://docs.ntfy.sh/publish/),
[server configuration](https://docs.ntfy.sh/config/),
+3 -1
View File
@@ -34,9 +34,11 @@ TestUIUXReviewSnapshots -count=1` regenerates rendered snapshots without server
mutations. Temporary snapshot/reviewer artifacts are under the session's
approved temporary directory, not committed runtime data.
The real anime pipeline is `examples/anime-today.md`: dated web evidence →
The historical anime pipeline (no longer bundled as a template) used dated web evidence →
verify/enrich → Markdown report → native ntfy attachment, using the system
connection. It is submitted as **anime episodes today v1**, pipeline **8**, with
no schedule. Its full model/web/phone execution has **not been tested**. The
LiveChart schedule was fetched during source investigation; the final delivery
stage uses the existing native publisher, not credentials handled by a model.
Current snapshot fixtures use the generic `examples/three-stage.md` starter;
removing a bundled definition does not remove published history.