fix: bake site UUID into generated guards

[ejntaylor]

What changed

• centralize site UUID baking for generated runtime guards
• propagate the UUID from .patchstackrc.json into generic, Express, Fastify, NestJS, Next.js, SvelteKit, and Astro guards
• preserve the environment-variable fallback when the project has not been scanned
• keep protect --demo on its bundled local rule set

Why

Only the TanStack + Supabase adapter previously embedded the site UUID created by patchstack-connect scan. Other generated guards silently fell back to starter rules unless PATCHSTACK_SITE_UUID was configured separately, so Host-provisioned Bolt projects did not automatically load their live Pulse rules.

Impact

Running patchstack-connect protect after Bolt Host setup now connects managed guards to the same Patchstack site without additional deployment configuration.

Validation

• npm run typecheck
• npm test — 41 files, 470 tests passed
• added UUID propagation coverage across every managed adapter and demo-mode coverage

[coderbuds]

Adds bakeSiteUuid helper to embed site UUID into all generated guards.

🎯 Quality: 100% Elite · 📦 Size: Medium

📈 This month: Your 232nd PR — above team average · Averaging Excellent

_{See how your team is trending →}

[ejntaylor]

/review