CLI init: app scripts hardcode bun --bun regardless of selected package manager

Description

When running npx next-forge@latest init and selecting pnpm as the package manager, the CLI correctly sets packageManager in root package.json and creates pnpm-workspace.yaml, but the generated app-level scripts still hardcode bun --bun.

Steps to reproduce

1. Run npx next-forge@latest init
2. Select pnpm when prompted for package manager
3. Check scripts in apps/app/package.json, apps/web/package.json, apps/api/package.json

Expected

Scripts should use next dev, next build, etc. (or the equivalent for the selected package manager).

Actual

Scripts contain bun --bun next dev, bun --bun next build, etc. Root package.json also has bunx and bun install in scripts.

Affected files

• apps/app/package.json
• apps/web/package.json
• apps/api/package.json
• root package.json (bunx → should be npx, bun install → should be pnpm install)

Workaround

Manually replace bun --bun next with next in all app scripts, and bunx → npx, bun install → pnpm install in root scripts.

Version

next-forge v6.0.0 and v6.0.1