BUG-Fixed: Resolve SQL schema bindings and persistence constraints

[DrDead0]

Description:

This PR resolves critical blocking issues in the backend data layer affecting form data persistence and asynchronous job queuing, alongside necessary client-side state synchronization fixes for usage telemetry.

🔧 Backend & Data Layer (services/)

• Contact Service (internal/adapters/postgres/store.go):
  • Fixed an incorrect SQL relation binding during form processing.
  • Resolved a bug where target_email was erroneously being queried against a non-existent users schema instead of the correct forms schema. Website form fields are now correctly processed and routed.
• Outbox Service (internal/outbox/outbox.go):
  • Resolved a fatal parameter cardinality mismatch during transaction inserts (execution previously attempted to inject 6 variables into 5 declared columns).
  • This unblocks the WAL queue, restoring the background worker's ability to successfully dispatch Google Calendar sync events and deliver host/guest emails.

🖥️ Client State & Telemetry (apps/web/)

• Usage Quota Synchronization:
  • Fixed a state staleness bug on the dashboard where usage limits/quotas failed to update after interacting with the booking or forms lists.
  • Injected a refreshTrigger prop into the <FeatureAccess /> component and bound it directly to the list-level refresh mutations to force dynamic, accurate re-renders of the user's consumption data.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[vercel]

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

Project	Deployment	Actions	Updated
halomail-web	Ready	Preview	Sep 20, 2026 3:25am UTC

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.