Deck: five actions — rewind, watch and ask, either side of pass and send

The deck had two answers, which is a lot to hang on a swipe: send this pro a job
right now, or lose them. Three more, in one fixed row (DESIGN.md §6.8):

  rewind · ✗ · watch · ✓ · ask

Size is the hierarchy — the two that end the card stay 64px, the three that do
not are 44px, never below the §8 floor. Rewind is disabled rather than hidden
when there is nothing to undo, so the row never changes length and the big pair
never moves out from under a thumb.

Rewind is local. The entry deck writes no swipes — a `swipes` row is job-scoped
and there is no job there — so the card leaving was only ever an index move.

Watch: "tell me when this one is free"
- `pro_watches` snapshots the pro's availability AT WATCH TIME, because the
  trigger is a change, not a state. Without it a sweep would notify every
  watcher on every run, since "available" stays true for as long as they stay
  available.
- Deliberately the narrow version: a pro with is_accepting_jobs = false is
  invisible everywhere (eligibleProAtAnyDistance requires it), so a watch can
  only be placed on somebody already free and fires on the away-and-back cycle.
  "Free at a time that suits me" needs pro_availability — seeded since M1, read
  by nothing — to become a real calendar. Flagged rather than faked.

Ask: a question, before there is a job
- This is the first way to reach a pro who has not agreed to anything. Chat was
  gated behind message → match → accepted request → job, and that gate is what
  made a pro's inbox worth opening, so the cap is not decoration:
  MAX_OPEN_ENQUIRIES unanswered at a time, one thread per pair so it cannot be
  walked around, answered threads stop counting, stale ones fall out, and the
  pro can close one.
- `enquiries` is its own table, not a match with a null job: a match means a pro
  said yes to specific work, and collapsing the two would put rows in `matches`
  that no quote, booking or review could hang off.
- `messages` now belongs to a match OR an enquiry, with a CHECK making the
  illegal state unrepresentable. One message table, so one chat screen.

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

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

DESIGN.md

@@ -296,8 +296,29 @@ The tab bar is the app's only persistent navigation. There is no footer.
 
 The one place that breaks the flat rule. `radius-deck` (28px), `shadow-lg`, full-bleed photo,
 bottom scrim `linear-gradient(to top, rgb(0 6 36 / .92), rgb(0 6 36 / .35) 45%, transparent)`.
-Overlay stamps: `SEND JOB` in `go-600`, `PASS` in `stop-500`, 4px border, ±12° rotation. Action
-buttons are 64px circles, 2px border, `ink-0` fill.
+Overlay stamps: `SEND JOB` in `go-600`, `PASS` in `stop-500`, 4px border, ±12° rotation.
+
+**The action row** is five circles, in one fixed order:
+
+| | Action | Size | Ink |
+|---|---|---|---|
+| 1 | Rewind — bring the last card back | 44px | `ink-600` |
+| 2 | Pass | **64px** | `stop-500` |
+| 3 | Watch — tell me when they are free | 44px | `brand-500` |
+| 4 | Send this job | **64px** | `go-600` |
+| 5 | Ask a question | 44px | `ink-950` |
+
+Two sizes, and the size *is* the hierarchy: the two decisions that end the card
+are 64px and reach the thumb first; the three that do not are 44px — still the
+minimum target from §8, never smaller. Gaps are 16px between a small and a large,
+24px between the two larges, so the pair still reads as the pair.
+
+All five are 2px bordered circles on `ink-0`. A control whose state persists —
+watch — fills with its own colour when active, and its label changes with it;
+selection is never carried by fill alone (§8).
+
+Rewind is `disabled` with nothing to undo rather than hidden. A row that changes
+length as you swipe moves the two buttons underneath your thumb.
 
 ---