feat: add Sentry error capture to page title and image plugin (#82)

[zacharias-ona]

Closes #82

What

Adds Sentry error capture to the remaining editor-adjacent components that were silently dropping errors.

Changes

src/components/page-title.tsx

• Added captureSupabaseError(error, "page.title.save") in the else branch when the Supabase title update fails. Previously, save failures were silently ignored.

src/components/editor/image-plugin.tsx

• Added Sentry.captureException in a .catch() handler on the drop-to-upload promise chain, which previously had no error handling for unhandled rejections.
• Wrapped openImagePicker's upload call in a try/catch with Sentry.captureException for the same reason.

Already handled (no changes needed)

• page-menu.tsx: Already has Sentry.captureException and captureSupabaseError from PR feat: add Sentry error capture to API routes and sidebar components (#81) #86 (issue Add Sentry error capture to API routes and sidebar components #81).
• Static analysis allowlists in sentry.test.ts: Already empty — no entries to remove.

Acceptance Criteria Verification

• ✅ page-title.tsx: title save failure captured via captureSupabaseError
• ✅ page-menu.tsx: export and import catch blocks already use Sentry.captureException (from feat: add Sentry error capture to API routes and sidebar components (#81) #86)
• ✅ image-plugin.tsx: upload failure captured via Sentry.captureException + captureSupabaseError
• ✅ No files to remove from static analysis allowlist (already empty)
• ✅ No console.error without an accompanying Sentry call in changed files
• ✅ pnpm lint && pnpm typecheck && pnpm test pass (51/51 tests)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
memo	Ready	Preview, Comment	Apr 16, 2026 1:26pm

[zacharias-ona]

✅ UI verification passed — design spec compliance confirmed.

Summary: This PR adds Sentry error capture to image-plugin.tsx and page-title.tsx. Changes are purely logic-level (try/catch, .catch(), Sentry.captureException, captureSupabaseError) with zero visual impact.

Static analysis: No color tokens, typography, spacing, component usage, button variants, loading states, transitions, accessibility, or border changes detected.

Visual verification: Playwright screenshots of the editor page (/{workspaceSlug}/{pageId}) in desktop dark mode (1280×800) and mobile (375×812) show no regressions — layout, spacing, typography, and dark mode tokens all match .agents/design.md.

[zacharias-ona]

✅ Post-merge verification passed.

Ad-hoc smoke tests — all passed:

• / — landing page loads, has title
• /sign-in — renders email input
• /api/health — returns healthy status
• Authenticated login flow — redirects to workspace
• Workspace page loads fully
• Editor page navigates and renders contenteditable element
• No console errors (unauthenticated or authenticated)

E2E test suite — 16 passed, 7 failed, 4 skipped. The 7 failures are pre-existing and tracked by #85 (editor link tests, drag reorder, Cmd+B shortcut, page-crud duplicate selector). None are related to the Sentry error capture changes in this PR.