fix: Vercel production-readiness for Krosebrook/interact

[Copilot]

• Explore repository structure and identify issues
• Fix vercel.json: correct env var names (VITE_BASE44_APP_ID, VITE_BASE44_BACKEND_URL), add SPA fallback rewrite, remove invalid redirect, remove no-op env.NODE_VERSION
• Add .nvmrc pinned to Node 20
• Update README: correct Node prerequisite, add Vercel deploy button and env var table
• Create docs/operations/VERCEL_AUDIT.md with multi-repo assessment report
• Build validated: npm run build produces dist/index.html successfully
• Code review: no issues found
• CodeQL: no security issues detected

Original prompt

Search across all repositories for GitHub user Krosebrook and assess which are production-ready for deployment on Vercel. For each repository, determine whether it is deployable on Vercel (e.g., Next.js/React/Vite, supported frameworks) and identify blockers (missing build scripts, missing vercel.json when needed, unsupported framework, missing environment variables, build failing, monorepo misconfiguration, missing output directory, node version mismatch, missing package-lock/pnpm-lock, missing public directory, etc.).

Scope/steps:

1. Enumerate Krosebrook repositories (public and any accessible private).
2. For each repo, detect whether it is a web app suitable for Vercel:
   • Presence of package.json and framework indicators (next.config.js, vite.config.*, nuxt, sveltekit, remix, etc.).
   • Determine package manager (npm/yarn/pnpm/bun) from lockfiles.
3. For Vercel-ready repos, validate:
   • package.json has build and start scripts.
   • For Next.js: next build works, output is correct, app router/pages router okay.
   • For Vite/SPA: build output dir and rewrites if needed.
   • Ensure Node engine compatibility with Vercel.
   • Presence of environment variable requirements documented; add .env.example if missing.
   • Add/adjust vercel.json only when necessary (monorepo, custom build/output, rewrites).
   • Add README deployment instructions.
4. For repos not ready, list blockers clearly and optionally suggest minimal fixes.
5. Output a report summarizing:
   • Production-ready on Vercel (yes/no)
   • Framework
   • Build command / output dir
   • Required env vars
   • Blockers
   • Recommended changes

If feasible, implement fixes in Krosebrook/interact (ref main) to make it Vercel-ready: ensure scripts, configuration, and documentation, and add any needed vercel.json, .nvmrc, and .env.example. Keep changes minimal and safe.

This pull request was created from Copilot chat.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

---

Summary by cubic

Audits all Krosebrook repositories for Vercel deployment readiness and adds docs/operations/VERCEL_AUDIT.md with a per-repo report. Makes Krosebrook/interact deployable on Vercel by adding an SPA fallback rewrite, fixing env var names in vercel.json, pinning Node 20 via .nvmrc, and updating the README with a deploy button and env var table.

^{Written for commit bc155d3. Summary will update on new commits.}

[Copilot]

Pull request overview

This PR aims to make Krosebrook/interact more deployable on Vercel by aligning environment variable naming, pinning Node to the repo’s standard version, and documenting the deployment process.

Changes:

• Updated vercel.json to use the app’s Base44 env var names and added an SPA fallback rewrite.
• Added .nvmrc to pin Node.js to 20 and updated README deployment/prerequisites documentation.
• Added an operations audit doc covering Vercel readiness and deployment steps.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File	Description
vercel.json	Adjusts Vercel build env var names and adds SPA rewrite behavior.
docs/operations/VERCEL_AUDIT.md	Adds Vercel readiness/deployment audit and guidance.
README.md	Updates Node prerequisite and documents Vercel deploy + required env vars.
.nvmrc	Pins Node.js version for local/Vercel consistency.

[Copilot]

The audit lists VITE_BASE44_API_URL as an optional frontend variable that “falls back to backend URL”, but this repo’s runtime code doesn’t read import.meta.env.VITE_BASE44_API_URL (it uses VITE_BASE44_BACKEND_URL via src/lib/app-params.js). This is likely misleading—either document that it’s currently unused in this codebase, or remove the fallback claim / variable from the required list to avoid confusion during deployments.

Suggested change

	| `VITE_BASE44_API_URL` | Optional | Base44 API URL (falls back to backend URL) |
	| `VITE_BASE44_API_URL` | Optional | Currently unused by this frontend; API base URL is derived from `VITE_BASE44_BACKEND_URL` via `src/lib/app-params.js` |

[Copilot]

The catch-all SPA rewrite will also rewrite /api/* requests (including the app’s client-side error logging POST to /api/logError) to /index.html. That prevents any /api endpoints (current or future) from working and can cause unexpected behavior for callers expecting non-HTML responses. Add a higher-priority rewrite for /api/:path* (to /api/:path*), or otherwise exclude /api/* from the SPA fallback rule.

Suggested change

	{
	{
	"source": "/api/(.*)",
	"destination": "/api/$1"
	},
	{

[Copilot]

build.env is mapping frontend env vars from Vercel “secret” references (e.g. @vite_base44_app_id), but the README instructs users to set VITE_BASE44_APP_ID / VITE_BASE44_BACKEND_URL as standard Vercel Environment Variables. Unless those @... secrets are created, builds can run with missing values or fail unexpectedly. Consider removing the build.env block and relying on Vercel project env vars, or update documentation to explicitly require creating the referenced secrets.