ext/hyperframes
2
0
Fork 0
mirror of https://github.com/heygen-com/hyperframes.git synced 2026-09-07 18:26:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(cli): stop calling the router trial an opt-in in risk prose

Browse Source 
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) <noreply@anthropic.com>
This commit is contained in:
Vance Ingalls
2026-08-07 17:38:28 -07:00
co-authored by Claude Opus 5
parent 4a2514232b
commit 1033d03271
1 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/cli/src/commands/render.ts
+9 -4
View File
@@ -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