fix: stop spamming Sentry when draft publish/discard hits expected 4xx

[cursor]

Summary

Fixes the Sentry alert: publish failed: 400 {"code":9,"message":"only draft versions can be published","details":[]} (#7516282874).

Root cause

The agent sidebar's DraftActionsWidget exposes Publish / Discard buttons for the latest draft. callApi unconditionally called console.error whenever the request returned a non-OK response:

if (response.ok) {
  onDismiss?.();
} else {
  const text = await response.text();
  console.error(`${action} failed:`, response.status, text);
}

The frontend Sentry SDK is initialized with captureConsoleIntegration({ levels: ["warn", "error"] }) (see web_src/src/sentry.ts), so this log is shipped as a Sentry event. But the case being hit here is a normal business-logic outcome — the draft was already published from another tab, the CLI, or by another collaborator — so the server correctly responds with 400 FailedPrecondition: only draft versions can be published. Treating that as an unhandled error pollutes Sentry and obscures real bugs.

Fix

In DraftActionsWidget:

• Parse the API error body and surface message inline in the widget (role="alert").
• For 4xx responses, treat them as expected outcomes — no console.error, no Sentry event.
• When the 4xx message indicates the widget is stale (only draft versions can be published, version not found, version owner mismatch), call onDismiss so the bar disappears instead of leaving a dead Publish button.
• Reserve console.error for genuine failures (5xx, network errors).

Tests

Added DraftActionsWidget.spec.tsx covering:

• Silently dismisses (and does not call console.error) when the API returns the stale-draft 400.
• Shows an inline error on other 4xx responses and stays mounted, without logging.
• Still logs console.error (and surfaces inline) for 5xx responses so real failures keep flowing to Sentry.
• Calls onDismiss after a successful publish.

All 4 new tests pass.

  

[superplanehq-integration]

👋 Commands for maintainers:

• /sp start - Start an ephemeral machine (takes ~30s)
• /sp stop - Stop a running machine (auto-executed on pr close)