Investigate why `vp create` feels slow

[crusty-voidzero]

Context

A follow-up from Discord: vp create feels slow, and it's unclear whether the time is mostly spent on network activity or on local/heavy logic during scaffolding.

Goal

Figure out where the latency comes from when running vp create:

• network requests (package metadata, template downloads, etc.)
• package manager / install steps
• local compute / filesystem-heavy logic
• other startup overhead

Suggested follow-up

• add basic timing/instrumentation around the main vp create phases
• identify the slowest step(s) in a representative run
• confirm whether the bottleneck is network-bound or CPU/IO-bound
• decide whether we should optimize the path, cache something, or improve UX/progress visibility

Origin

Discord thread context:

vp create is kind of slow. Is it network issue or actually running some heavy logic?

[fengmk2]

embed the tsdown template directly into vite-plus