Pipelines skill: outcome-first output, aligned review and loop guidance, operator material moved to docs
Rewrite format.md around turn files, the output.md order (# outcome, edge word, # handoff, detail), checks, configs, human stages and the land stage delivery gate (sh -c in a fresh detached worktree, clean checkouts incl. untracked, 64 KB output cap, opencode only). Align review guidance across practices, verification, orchestration and the feedback-loop example. Fix loop-limit semantics in control.md against runner.go, budget_tokens sizing, read for large inputs, blocked-else-error and one stage naming set. Move dated verification logs to docs/verification-history.md and brokered chat, TUI keys and harness internals to docs/operator-reference.md; label operator-only references in SKILL.md.
This commit is contained in:
@@ -15,7 +15,7 @@ select a recorded stage/visit, bounded input correction and explicit compatible
|
||||
version of the same pipeline. Verify actual retained stage input, not merely
|
||||
successful admission. Do not silently restart from entry.
|
||||
|
||||
A clean preparation stage succeeds without an empty commit. A committer with a
|
||||
A clean preparation stage succeeds without an empty commit. A `land` stage with a
|
||||
delivery gate succeeds with a clean checked candidate; the server lands afterward.
|
||||
Read-only, nonvisual work does not require device screenshots. Visual acceptance
|
||||
requires a ready fixture, verified connection and actual captured interactions.
|
||||
|
||||
Reference in New Issue
Block a user