The Sentry wiring shipped today catches errors in the platform
itself. The bigger product opportunity is wiring Sentry into every
project Vibn ships, then feeding those errors back into the user's
AI chat — turning the AI from "codes for you" into "owns the
product."
Proposal lays out 4 staged shippable chunks (~8 hr total):
1. Auto-provision per-project Sentry on first deploy
2. Bake Sentry into every scaffold template
3. Expose project_recent_errors / _detail / _resolve as MCP tools
4. Auto-surface unresolved errors at chat-turn start
Folded into BETA_LAUNCH_PLAN.md as Phase 2.9.
Co-authored-by: Cursor <cursoragent@cursor.com>
- 2.6 (Dockerfile HEALTHCHECK 127.0.0.1) already in place; marked done.
- 2.7 audit: vibn-dev and vibn-agent-runner have no HEALTHCHECK so
cannot hit the localhost/IPv6 trap. Marked done.
- 2.8 (NEW): tool-error recovery middleware shipped — bumps the
vibn-frontend submodule to c105b42.
Co-authored-by: Cursor <cursoragent@cursor.com>
All 8 Phase 1 tasks done. HMR through Traefik proven end-to-end via
spike on 2026-05-01: WebSocket upgrade returns 101, Vite handshake
completes with vite-hmr subprotocol, js-update messages fire within
~1s of file edit.
Co-authored-by: Cursor <cursoragent@cursor.com>
