Update templates and authoring skill to the current pipeline contract
Bring the packaged starters and the pipelines skill up to the guidelines the project now works to. Templates: - task and three-stage now end in a committer stage that stages the union of the runner's captured input.server_changed_files and the producer's declared changed_files, runs the repository's checks, commits locally and never pushes; their producers no longer commit. - Every model/agent prompt states the line-oriented result contract (outcome on the first non-empty line, "# output" JSON map, other "# <heading>" sections kept verbatim as evidence) and an "# evidence" section for exact commands and results, with proportionate verification and no fabricated checks. - Stages that can write save their reports, logs and screenshots into the runtime artifacts directory. - Remove the summary starter: a tool-free single-prompt text transform with no repository interaction, artifact or commit is a format demonstration, not a reusable workflow. No starter invents a pretend approval stage; a decision point is a type=human stage. Skill: - references/format.md gains a Result format section (line form, legacy JSON precedence, result_parse, raw-output.md, artifacts) and a Committer stages section with the pre-commit checklist; the role-split and envelope notes mention the line form and the committer. - orchestration.md points at the checklist and records that a genuine gate is a human stage; operations.md and the SKILL.md index drop the removed starter and name the result format and committer. No new reference, so the managed inventory is unchanged. Docs/tests: examples/README, README, docs/cli, docs/first-version-testing, the CLI help example and the smoke script track the four starters; catalog, tool-role, server, tui and pipeline tests are updated, with a new test pinning the committer ending and server-captured change set. Commands run: go build ./...; go vet ./...; go test ./...; python3 -m unittest discover -s scripts -p 'test_*.py'; python3 scripts/smoke-first-install.py. All passed. Templates inspected through an isolated CLI server (pipelines templates; pipelines template KEY --source). No server, service or device was restarted, and nothing was pushed.
This commit is contained in:
@@ -76,10 +76,11 @@ override the saved endpoint; check that you are connected to the intended server
|
||||
1. Create a disposable repository, then launch `pipelines` **from that directory**.
|
||||
Docker must see the same absolute path; repositories on another computer are
|
||||
not uploaded automatically.
|
||||
2. Use `:templates` and create the **summary** starter. Review its name and publish
|
||||
explicitly. A fresh database is empty; templates are never auto-published.
|
||||
3. Open the pipeline and use `:run` with a small task, such as summarizing a short
|
||||
passage included in the task itself. Review the execution confirmation.
|
||||
2. Use `:templates` and create the **review** starter (read-only, no repository
|
||||
change). Review its name and publish explicitly. A fresh database is empty;
|
||||
templates are never auto-published.
|
||||
3. Open the pipeline and use `:run` with a small task, such as reviewing one short
|
||||
file in the disposable repository. Review the execution confirmation.
|
||||
4. Read the retained report and recorded visits. For an editing workflow, inspect
|
||||
File changes as well as actual file contents and any verification commands.
|
||||
Model-written claims alone are not verification.
|
||||
@@ -91,13 +92,13 @@ override the saved endpoint; check that you are connected to the intended server
|
||||
|
||||
Phone reception is a separate manual check. Install/subscribe in the ntfy app and
|
||||
confirm receipt before depending on it. The installer confirms publishing, not
|
||||
delivery to your phone. A summary starter does not send alerts automatically.
|
||||
delivery to your phone. A review starter does not send alerts automatically.
|
||||
|
||||
## Known boundaries
|
||||
|
||||
- Sequential stages within a run; no parallel branches or built-in
|
||||
human-approval stages. Independent runs in different workspaces do execute
|
||||
concurrently.
|
||||
- Sequential stages within a run; no parallel branches. `type=human` decision
|
||||
stages pause a run for an operator's choice. Independent runs in different
|
||||
workspaces do execute concurrently.
|
||||
- Cancellation/retry is **not rollback**. Retry starts from the entry stage with
|
||||
fresh sessions and the pinned definition; earlier side effects can repeat.
|
||||
- Diffs are bounded stage-start/stage-end observations, not full backups or proof
|
||||
@@ -144,7 +145,7 @@ python3 scripts/smoke-first-install.py
|
||||
|
||||
The developer-only smoke check builds source binaries and installs the skill into a disposable directory,
|
||||
starts an isolated loopback server/database, checks build identity, empty initial
|
||||
state, five starters, draft/validate/publish, identical ZIP import and restart
|
||||
state, four starters, draft/validate/publish, identical ZIP import and restart
|
||||
persistence, then shuts it down and removes only its temporary directory. It does
|
||||
not call models, send alerts, update your installed clients or deploy Docker services.
|
||||
It does not replace real-provider, terminal interaction or fresh Docker-install tests.
|
||||
|
||||
Reference in New Issue
Block a user