[P3] Add deployment recipes for generated artifacts

[KayleeWilliams]

Problem

Leadtype generates several artifacts, but users still need clear deployment guidance for where each file lives and how it composes with the host framework.

The release should make deployment predictable across frameworks and hosts.

Proposal

Add deployment-focused recipes for common framework/host combinations.

Targets:

• Next.js on Vercel
• Nuxt on Vercel/Netlify/Cloudflare
• SvelteKit with adapter-static, adapter-node, and adapter-vercel
• Astro static/server
• Cloudflare Workers/Pages
• Plain Vite static hosting

Each recipe should cover:

• When leadtype generate runs.
• Where llms.txt and llms-full.txt are served from.
• Where markdown mirrors live.
• How search JSON is loaded.
• How raw markdown routes work.
• How sitemap/robots output composes with an existing app.
• Differences between static and server deployments.

Acceptance Criteria

• Each recipe lists artifact output paths.
• Each recipe explains build-time vs runtime responsibilities.
• Each recipe verifies /llms.txt, /llms-full.txt, markdown mirrors, and search JSON.
• Recipes distinguish site mode from package bundle mode.
• Recipes distinguish static hosting from server/edge deployments.
• Users can deploy Leadtype artifacts without reading source code.

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}