Enforce runtime report contracts and recoverable session exports
This commit is contained in:
+20
@@ -878,3 +878,23 @@ run test uses a controlled executor, not a model). The isolated installed CLI
|
||||
also exercised the actual OpenCode API's session creation and skill activation,
|
||||
while capturing interactive launch arguments to avoid a model turn. Full
|
||||
model-driven authoring and Linux execution are **not tested**.
|
||||
|
||||
## Per-run report contract
|
||||
|
||||
`pipelines run NAME PROMPT --output-format html` requires a server-written
|
||||
`public/report.html` before run success; `--output-format markdown` requires
|
||||
`public/report.md`. Omit the option for historical behavior. The `run_pipeline`
|
||||
wire request and returned run record carry `output_format` (`html` or `markdown`),
|
||||
and retries inherit it. Request-key replays must retain the same format.
|
||||
Reports use nonempty terminal text output and are bounded to 2 MiB; missing,
|
||||
empty, unsafe or unverifiable files fail the run. This checks structure, not
|
||||
factual correctness. See [audit notes](notes/audit-deliverables.md).
|
||||
|
||||
`pipelines repair-session-export RUN_ID SEQUENCE [--json]` asks the runtime to
|
||||
read back that settled visit's exact recorded native session/backend. It never
|
||||
executes a stage or changes a definition. It writes a versioned repair artifact
|
||||
and appends evidence without replacing original files or outcomes. The protocol
|
||||
command is `repair_session_export` with `run_id` and `export_sequence`; the reply
|
||||
is a run detail containing each visit's `session_export_repairs`. CLI JSON emits
|
||||
the repair record with explicit completeness `status`, and incomplete repair
|
||||
exits nonzero. Recovery still depends on upstream session availability.
|
||||
|
||||
Reference in New Issue
Block a user