Add warning to README about cleaning Nuxt build output before dev

[Yndira-E]

Description

Running npm run build:nuxt locally populates nuxt/public/ and nuxt/.output/ with the full static build output. Starting npm run dev afterwards causes a spawn EBADF error on macOS because Nitro serves those stale files as static assets, opening thousands of file descriptors simultaneously.

This PR documents the fix: run npm run clean:nuxt before npm run dev after a production build.

Related Issue(s)

Checklist

• I have read the contribution guidelines
• I have considered the performance impact of these changes
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
• For blog PRs, an Art Request has been created (instructions)

[netlify]

✅ Deploy Preview for flowforge-website ready!

Name	Link
🔨 Latest commit	b44160b
🔍 Latest deploy log	https://app.netlify.com/projects/flowforge-website/deploys/6a0db6619a4da70008ba3d9a
😎 Deploy Preview	https://deploy-preview-5042--flowforge-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 89 (🔴 down 3 from production) Accessibility: 89 (no change from production) Best Practices: 100 (no change from production) SEO: 91 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.