From 1033d03271fb381be51fbc1103063cd8147a626b Mon Sep 17 00:00:00 2001 From: Vance Ingalls Date: Fri, 7 Aug 2026 17:38:28 -0700 Subject: [PATCH] docs(cli): stop calling the router trial an opt-in in risk prose MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It is not a user opt-in — execute.ts arms it automatically on the CLI render path, so ~11% of installs already route without anyone choosing it. The opt-in is at the CALL SITE: the flag defaults off and only the two CLI sites set it, excluding programmatic renderLocal consumers because the mechanism mutates process.env. That polarity guards embedding contexts, not users. Calling it opt-in understates today's exposure, which changes how a reviewer judges the ramp: it is not protecting users from a feature they chose, it is governing exposure already happening without their choice. Leaves the accurate uses alone — 'explicit user opt-in' means someone setting HF_DE_PARALLEL_ROUTER themselves, and the call-site flag is genuinely opt-in. Co-Authored-By: Claude Opus 5 (1M context) --- packages/cli/src/commands/render.ts | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/packages/cli/src/commands/render.ts b/packages/cli/src/commands/render.ts index 25b6d9e57..76dbb8cde 100644 --- a/packages/cli/src/commands/render.ts +++ b/packages/cli/src/commands/render.ts @@ -1227,10 +1227,15 @@ function applyDeParallelRouterCircuitBreaker(quiet: boolean): boolean { } // The rollout slice. Default-ON means every eligible render routes the - // moment this ships — a ~17x jump in exposure, onto profiles the opt-in - // trial never covered (<=4 CPUs, Docker: ~12% of eligible renders between - // them). 0.7.60-0.7.64 is why that matters: every unclamped render - // reverted for five consecutive releases and nobody saw it. + // moment this ships — a ~17x jump in exposure, onto profiles today's trial + // population never covered (<=4 CPUs, Docker: ~12% of eligible renders + // between them). Note "trial" is not a user opt-in: it arms automatically on + // the CLI render path, so ~11% of installs already route without anyone + // choosing it. The opt-in is at the CALL SITE — the flag excludes + // programmatic renderLocal consumers, not users. + // + // 0.7.60-0.7.64 is why that matters: every unclamped render reverted for + // five consecutive releases and nobody saw it. // // Ramping through the registry makes the exposed fraction a number someone // chose. Today's ~11% is emergent — the product of eligibility rules and a