chore: release v0.7.103

[vanceingalls]

Release v0.7.103.

Behavioural change for users

The parallel drawElement router is on for everyone again. Long renders go
back to the faster parallel capture path.

v0.7.101 shipped that router behind a 5% canary. Measured the next day, the
gate had cut fleet router exposure from 3.13-4.25% of non-CI renders to
0.13% — roughly 25x — because out-of-cohort installs are explicitly
disarmed and #2840 deleted the everyone-armed trial in the same change. 2,537
installs lost a feature they already had. #3120 removed the canary entry and
its guard together, restoring the shipped default.

Impact is speed only, never output: a router revert forfeits the speedup, not
the render. The per-install circuit breaker and per-render self-verify are
untouched, and HF_DE_PARALLEL_ROUTER=false remains the kill switch.

Monitoring note

$feature/canary-de-parallel-router and canary_reason_de_parallel_router
are emitted from the canary registry, so they stop with this release. The
Ramp — tiles and the exposure-floor alert on PostHog dashboard 1918875 go
blank once this is adopted. Watch drawElement engagement on 1807532 instead.

Reverting is now a code revert rather than a registry edit — that was the
trade accepted for shipping in one step instead of two.

Also in this release

• Core: retry bpm-detective import after transient failure (fix(core): retry bpm-detective import after transient failure #2736)
• Docs: fix preview port in DOCS_GUIDELINES example (docs: fix preview port in DOCS_GUIDELINES example #2903)

Full changelog: v0.7.102...v0.7.103

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
hyperframes	🟢 Ready	View Preview	Aug 9, 2026, 10:00 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.