From ee3d6418f7e8ba42e0a3985cb9ff8efc1d5ce3cf Mon Sep 17 00:00:00 2001 From: Vance Ingalls Date: Fri, 18 Sep 2026 10:43:40 -0700 Subject: [PATCH] docs(long-form): record the adversarial review outcome and the retry target per routing - HANDOFF section 4a: the single-worker fallback applies on default routing (non-DE router and the manual opt-in); a DE-router plan keeps its precomputed fallback. Adds the review's verdicts: three confirmed defects fixed, one latent hardened, one split accepted, one low left open (a worker wedged before its first capture is bounded only by player-ready and CDP timeouts and is not retry-eligible). - cli.mdx: the parallel-stream paragraph no longer promises a single-worker retry for every case. Co-Authored-By: Claude Fable 5.1 --- docs/packages/cli.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/packages/cli.mdx b/docs/packages/cli.mdx index fd71c7bd09..920e29ac71 100644 --- a/docs/packages/cli.mdx +++ b/docs/packages/cli.mdx @@ -940,8 +940,9 @@ on the bundled `chrome-headless-shell`, at DPR 1, with no forced screenshot. On macOS and Windows, multi-worker capture is screenshot-based and still writes frames to disk unless you opt in with `HF_CAPTURE_PARALLEL_STREAM=true`. That path now retries a stalled worker pool or a mid-stream encoder exit on a fresh -single-worker session instead of failing the render, but it stays opt-in until -its error rate matches the disk path's. +screenshot session, dropping an interleaved render to one worker, instead of +failing the render; it stays opt-in until its error rate matches the disk +path's. Renders still land on the disk path when the output is `png-sequence` or `gif`, when HDR or shader-transition layering is in play, and when streaming is