support Expo init adoption

[zbeyens]

• Auto release

🐛 Fixes Discord Expo init/adoption report
🟢 95-100% confidence

Phase	🧪 Tests	🌐 Browser
Reproduced	🔴 bun test packages/kitcn/src/cli/commands/init.test.ts covered the previous Expo adoption rejection and Bun-only scaffold launch path	➖ N/A
Verified	🟢 bun check	➖ N/A

✅ Outcome

• Existing Expo apps can run kitcn init --yes instead of getting the unsupported-adoption error.
• Fresh Expo init launched through pnpm/npm can avoid the Bun-only bunx create-expo-app path that triggers Windows EPERM cache extraction failures.

⚠️ Caveat

• This does not fix Bun's Windows cache bug. It fixes kitcn's fallback so pnpm/npm-launched init does not invoke Bun for Expo scaffolding.

🏗️ Design

• Detect the launcher package manager from npm_config_user_agent when no project package manager exists yet.
• Keep Bun as the default for direct Bun-launched flows.
• Remove the temporary Expo adoption blocker and rely on the existing adoption/overwrite protections.

🧪 Verified

• bun lint:fix
• bun test packages/kitcn/src/cli/commands/init.test.ts
• bun --cwd packages/kitcn typecheck
• bun --cwd packages/kitcn build
• bun typecheck
• bun check

[changeset-bot]

🦋 Changeset detected

Latest commit: 0fd1411

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
kitcn	Patch
@kitcn/resend	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
better-convex	Ready	Preview, Comment	May 6, 2026 2:43pm