Each model_request/model_payload repeated the full context, so the trace
grew with the square of the request count: batch 6 Qwen runs hit 64 MiB
at ~75 requests and 14 attempts (13 graded PASS) were discarded.
Requests now record only items after the common prefix with the previous
one (schema embedded-rollout.pi/2), and pi_run.expand rebuilds full
payloads before the unchanged broker/feedback checks. Needs a new image
(trace6) and recalibration before use.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Output limits were baked into pi.mjs inside the runtime image, so every
change (GLM 32000 -> 131072, Qwen 8192 -> 65536) needed a new image and a
full 785-trial recalibration, and the Qwen baseline ran on an image the
repo could not rebuild.
- MODELS holds max_tokens and its wire field per model; pi_run passes
--model and --max-tokens to the adapter, which has no defaults left.
- Receipts record model_max_tokens and model_sampling=service-default;
evidence requires every payload to carry exactly that limit, which
would have caught the SDK's silent 32000 cap.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bos tasks with 131072-token reasoning produce ~110 bytes per streamed
token plus a full context per request; the trace3 batch hit 16 MiB
before finishing. Adapter and host share the new limit, and the size
tests now derive their data from MAX_TRACE_BYTES. Runtime trace4 carries
this adapter; all 21 tasks recalibrated.
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>
- Pi controller accepts a fixed Qwen qwen3.8-27b-nvfp4 Responses route next
to GLM-5.3; the broker requires exactly one response.completed per call
and evidence checks the native model identity.
- rollout.export writes the UltraData five-field JSONL from a frozen
dataset.json snapshot; every archive now carries dataset.jsonl.
- A Docker CLI that did not finish cannot confirm container or network
cleanup, and auto-calibration cleanup uncertainty reaches the controller.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>