M2: the full job lifecycle — chat, hiring, geocoding, quotes, bookings, reviews

Closes the funnel. Before this the product could match two people and then
stopped: `quotes`, `bookings` and `reviews` had tables and state machines and
nothing that wrote a row, the entry deck's right swipe was wired to an empty
handler, and every address resolved to the city centre.

Jobs tab and chat
- message router: thread, send, markRead, unreadTotal. A thread is a MATCH, not
  a job — one job with three interested pros is three private conversations.
- Current/Past segments derived from ACTIVE_JOB_STATUSES, job detail listing the
  pros who accepted, and the conversation itself with attachments.

Hiring from the deck
- A right swipe on the entry deck opened nothing. It now resolves "which job?"
  through a sheet — sign in, pick an open job, or post one — and calls the same
  deck.swipe the per-job deck does, so the open-request cap and row lock apply
  exactly once. Swipes are vetoable so closing the sheet returns the card.

Geocoding
- ST_Distance and ST_DWithin rank and filter every deck, and both operands were
  placeholders. Addresses now resolve through Mapbox (permanent=true, which is
  what licenses storing the coordinates), the server resolves points rather than
  trusting client-supplied lat/lng, and every stored point records how it was
  obtained. A `city`-precision base cannot reach the verification queue.

Quote -> booking -> review
- The commercial chain, minus payments. Accepting a quote is the only place a
  booking is created; confirming completion is what unlocks reviews and moves
  the pro's completed_jobs.
- Reviews publish double-blind with no sweeper: each is written with
  published_at already set to its embargo deadline and every read filters
  published_at <= now(), so it publishes itself. The second review pulls both
  forward. A silent counterparty cannot bury a bad review by never replying.

State machine changes, both deliberate
- booked -> matched: a cancelled booking is not a cancelled job.
- scheduled -> awaiting_confirmation: in_progress is optional, so a pro who
  never tapped Start can still say the work is done.

Test suite
- api tests ran files in parallel against one database and failed roughly one
  run in three on whichever file lost the race. Serialised, and three fixtures
  that grabbed "the first client" pinned to the seeded accounts.

Also includes work from a parallel session: admin verification queue, pro
public profile and reviews read path, notification sending, denormalised stats
recompute, search, and observability.

318 tests passing; typecheck and lint clean across 7 packages.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

apps/web/next.config.ts

@@ -1,4 +1,5 @@
 import { config as loadEnv } from 'dotenv';
+import { withSentryConfig } from '@sentry/nextjs';
 import type { NextConfig } from 'next';
 
 // The monorepo keeps one .env at the root; Next only looks in the app directory.
@@ -21,4 +22,26 @@ const config: NextConfig = {
   serverExternalPackages: ['postgres'],
 };
 
-export default config;
+/**
+ * Bugsink speaks the Sentry protocol, so the Sentry build plugin applies — but
+ * only the parts that make sense for a self-hosted error tracker.
+ *
+ * Source maps are uploaded so a minified production stack is readable, and then
+ * deleted from the build output so they are not served publicly. Everything
+ * tracing-related stays off: Bugsink does not ingest it.
+ */
+export default withSentryConfig(config, {
+  // Bugsink has no organisation/project slugs in the Sentry sense; the DSN
+  // carries the project. These are only used by the upload step, which is
+  // skipped entirely without an auth token.
+  silent: true,
+  disableLogger: true,
+  sourcemaps: {
+    deleteSourcemapsAfterUpload: true,
+  },
+  // Do NOT route events through a Next rewrite: the tunnel exists to dodge ad
+  // blockers against sentry.io, and this DSN is our own host already.
+  tunnelRoute: undefined,
+  // The SDK's automatic Vercel Cron instrumentation has nothing to talk to here.
+  automaticVercelMonitors: false,
+});