[WaterrrForever]

What

Raises @hyperframes/core's unpacked budget in scripts/package-size-budgets.json from 3930000 to 3935667, its measured size on main. Nothing else changes.

Why

main's Build has failed since 4371981b7 (22:07 UTC, Oct 21) with:

@hyperframes/core unpacked size 3935667 bytes is over its budget of 3930000.

#5969 raised this budget for capture motion blur. #5971 and #5990–#5992 then added packages/core/src/htmlInCanvasDefects.ts (338 lines) and a new package export for it without raising it again, putting core 5,667 bytes over. The growth is shipped feature code, not stray source maps, tests or assets, so this follows #5969 and raises the budget.

Because main is red, every merge-queue entry fails Build and is dequeued (#5656 was removed twice for this).

@vanceingalls this is your stack's growth. If you'd rather trim core than raise the budget, close this and I'll wait for your fix.

Test plan

• Build passes here (it runs verify:packed-manifests, which measures core against this budget)

🤖 Generated with Claude Code

[jerrai-bot-heygen]

At this head, the sole change raises @hyperframes/core’s unpacked budget by 5,667 bytes to the 3,935,667 bytes measured in main’s failing Build. The verifier fails only when measured size is greater than the budget, so equality is accepted; packed and other budgets remain unchanged. The PR states the motion-blur addition as the reason. Exact-head Build is still running, and I did not run a local pack/build. Miao expressly authorized this PR’s merge and armed auto-merge; this review is an approval only, not a direct merge or enqueue. — Jerrai