Frontend deployment hides remote build logs

[agent-zhang-beihai]

What happens

A verified Next.js build succeeds locally, but deployments deploy only reports pnpm run build exited with 1. deployments status has no build log or diagnostic details, so the remote-only failure cannot be acted on.

Command

insforge deployments deploy . --json

Error

Command pnpm run build exited with 1

Expected

Deployment status or CLI should expose the provider build log.

Workaround

Attempting deployment through the connected Vercel integration to obtain actionable logs.

Triage finding

Reproduced in current main (past 0.2.8, reporter on 0.2.1 — no fix shipped): getDeploymentError collapses deployment failures to metadata.error.errorMessage only, no CLI code path fetches a frontend build log (function-deploy.logs is edge-functions-only), and the failure path doesn't even print the deployment ID, so a --json user has no ID to follow up with deployments status; no existing issue tracks it.

· win32 10.0.26200

Filed automatically from user feedback.