Sentry auto-triage follow-up: status and watch items (no immediate action required)

Backfill triage completed: all 19 unresolved Sentry issues are now concluded (0 open) via merged PRs [#632](https://github.com/epicweb-dev/epicshop/pull/632)–[#638](https://github.com/epicweb-dev/epicshop/pull/638), plus Sentry-side ignores. Nothing requires action right now; two watch items were **ignored rather than filtered**, so they will re-alert and auto-triage if they recur:

- [ ] Watch [EPICSHOP-B1](https://kent-c-dodds-tech-llc.sentry.io/issues/7211203146/) — "workshop directory must be an absolute path" MCP error (407 events, stopped 2026-07-28). If it re-alerts, consider making workshop-mcp resolve relative paths (or reject them client-side) instead of erroring per event.
- [ ] Watch [EPICSHOP-H9](https://kent-c-dodds-tech-llc.sentry.io/issues/7635709014/) — client fetch failures against deployed workshop preview hosts; ignored as external/transient. If it recurs, soften preview fetch failures in the app.

New issues in the `epicshop` Sentry project now auto-triage (one Cursor agent per issue, outcome in #sentry-reports).

---
*Opened by the sentry-triage automation follow-up (Cursor agent via Kody).*

This is a completed triage follow-up, not an actionable change. Review merged PRs #632–#638 and the linked Sentry issues only if EPICSHOP-B1 or EPICSHOP-H9 recurs; otherwise there is no code or test target and nothing to mark done.

Written by the indexing model from the issue text.