stage turns: replace JSON results with file-based markdown turns
Each model visit now gets <run>/stages/<seq>-<stage>/ with input.md, memory.md, output.md, private/ and a shared run-level public/. The model reads the two input files, follows the stage's instructions verbatim and returns complete markdown; only the # outcome section is parsed. - add internal/turn layout, render and output parsing - write input.md/memory.md before a visit and output.md from the final message; inventory all turn files as stage artifacts - accumulate completed turns and system-written public file additions in memory, including across retries and resume - remove the JSON envelope, strict field validation, line format and the repair ladder for model stages - republish pipeline authoring prompts and docs in the new style Checks: go build ./..., go vet ./..., go test -count=1 ./..., gofmt -l .
This commit is contained in:
+25
@@ -564,6 +564,31 @@ appear when persisted (currently after generation). This does not attach a live
|
||||
harness client or stream its messages. Supporting live attachment consistently
|
||||
across the shared and privately owned harness backends is deliberately deferred.
|
||||
|
||||
## Stage turn files
|
||||
|
||||
Each model-stage visit receives a file-based turn under the run's artifact
|
||||
directory. `pipelines inspect <run-id> --json` and the run inspector list these
|
||||
files as that step's artifacts:
|
||||
|
||||
```
|
||||
<artifacts>/<run>/stages/01-implementer/input.md
|
||||
<artifacts>/<run>/stages/01-implementer/memory.md
|
||||
<artifacts>/<run>/stages/01-implementer/output.md
|
||||
<artifacts>/<run>/stages/01-implementer/private/
|
||||
<artifacts>/<run>/public/
|
||||
```
|
||||
|
||||
`input.md` is the run prompt on the first visit and the previous visit's output
|
||||
body (without its outcome section) afterwards. `memory.md` is the accumulated markdown of completed turns plus the
|
||||
files each turn added to the shared `public/` directory. A text-only stage (an
|
||||
explicit empty `tools` block) receives both files' contents in its prompt
|
||||
instead, because it has no file-reading tool. The model returns the complete
|
||||
`output.md` markdown; only its `# outcome` section is interpreted by the server.
|
||||
Everything else is free-form and preserved under the step's `markdown` output.
|
||||
`private/` belongs to its own visit, while `public/` is shared by every stage in
|
||||
the run. Artifacts are served from `/artifacts/<run>/<step>/<name>`; shared files
|
||||
appear with a `public/` prefix.
|
||||
|
||||
## Investigating runs with a configured harness
|
||||
|
||||
On the runs list or inspector, press `D` or use `:debug`; CLI equivalent:
|
||||
|
||||
Reference in New Issue
Block a user