rollout.salty_run keeps the gateway, grading and evidence on 36 and moves only the
agent step into a Salty job. The gateway listens on 127.0.0.1 with a per-attempt
bearer token; the job reaches it over port 22 with a restricted one-time key that is
removed after each attempt. rollout.batch gains --backend salty and repeatable
--credential-file, and writes pass/fail SFT exports through rollout.sft at the end.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
trace6 is trace5 plus the prefix-delta pi.mjs; image ID equals the manifest
digest under 36's containerd store. The CCR push is pending a fresh login.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first Bos pilot batch exposed two adapter faults on long responses:
- fs.writeSync(1, ...) ignored partial writes to a nonblocking stdout pipe,
so host stdout lost the tail of 100 KB lines and could no longer match
the native trace. writeAll now loops until every byte is written and
waits briefly on EAGAIN.
- Pi SDK caps max_tokens at 32000 unless told otherwise; GLM-5.3 spent
all of it reasoning and stopped with "length" before any edit. The
adapter now passes the registered 131072 (accepted upstream).
Runtime trace3 is the trace2 digest plus this pi.mjs; 12/12 SDK checks
pass inside it and all 21 tasks were recalibrated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add the current and target deployment diagrams, the task author standard
and copyable spec template, the five-field data contract, and record the
Qwen Responses trial and pending-create cleanup fix in progress and
acceptance.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>