The homepage was a marketing brochure -- a hero paragraph, a "three
steps" explainer and a tag list. It described the gesture in prose
while the actual Tinder deck sat behind /deck/[jobId], reachable only
after signing in AND posting a job. Nobody opening the app ever saw
the product.
Now / renders a phone illustration with the real app running inside
it: the same <Deck>, the same drag physics, real verified pros. On a
phone the bezel collapses and the deck simply fills the viewport --
drawing a picture of a phone on a phone is absurd, and it would eat
the width the cards need.
- Removed the fixed app bar and bottom tab bar. AppShell now renders
the screen title as an in-flow h1; the bar owned the only h1 on
every screen, so dropping it silently would have left every page
headingless. The /jobs "post" action moved from bar chrome into the
content, since the tab bar was its only other route there.
- getShowcaseDeck(): a deck with no job behind it. getDeck is
job-scoped (joins jobs for category and location, anti-joins
swipes), which an anonymous visitor has none of, so this centres on
the launch city. Eligibility rules are copied verbatim -- nobody may
appear in the shop window who could not appear on a real deck.
- deck.showcase: the only public procedure in the router. list and
swipe stay behind clientProcedure. It reads nothing about the caller
and writes nothing, so a right swipe on the entry screen is purely
local. No real tradesperson is contacted until a job is posted.
- <Deck> filled a hardcoded 560px desktop box; it now fills its
container. The card counter moved out from between the two action
buttons so the thumb zone holds nothing but the two controls.
Verified against the seeded database: 22 eligible pros returned, and
all three seeded traps excluded for the right reason -- Pau Ribas
(22km out, 5km radius), Unverified Ulla (pending), Away Arnau (not
accepting). 7 new integration tests cover exactly that.
Also corrects a label I had written as "Plumbers near you" -- the
showcase deck is not category-filtered and shows every trade.
Includes concurrent edits to the mobile shell, ui/ primitives and
DESIGN.md made outside this session.
typecheck, lint, build clean; 141 tests pass.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Switches from the planned Auth.js v5 to better-auth 1.7.1. The plan
assumed the blocker would be schema fit; it is not. @auth/drizzle-adapter
accepts our tables verbatim. What rules Auth.js out is that credentials
providers hardcode JWT and never call adapter.createSession, and the
config assertion that would catch it only fires when EVERY provider is
credentials — so adding Google suppresses the warning and the app ships
silently broken. Phone OTP with database sessions is not reachable there
without hand-building the whole OTP security layer.
Also corrects a premise: better-auth's drizzle-orm peer is declared
OPTIONAL, so no 0.38 -> 0.45 upgrade is forced. Verified on 0.38.4.
- auth schema rewritten to better-auth 1.7.1's own getSchema() output:
sessions/accounts/verifications reshaped, emailVerified and
phoneVerified are BOOLEAN (a timestamptz there fails 100% of signups),
accounts.issuer added, phone_otps dropped. Ban state now comes from the
admin plugin rather than a second bannedAt column.
- Session resolution is one file. Everything downstream is written
against our own Session type, so the provider stays swappable.
- Ban enforcement lives in the resolver because Session carries no ban
field and protectedProcedure promises a non-banned user.
- Phone OTP sign-in, Google, role selection, tRPC user router.
- Synthetic emails for phone-first users, with isSyntheticEmail() gating
every future send. Pros must supply a real address; clients need not.
- Duplicate-account detection, since both signup routes stay open and
nothing correlates a phone to a Google identity. Detects only — merging
accounts that carry reviews and payments needs its own tooling.
- SMS sender refuses to fall back to console logging in production.
- declaration:false for the app, which is the actual fix for the TS2742
wall from better-auth's transitive zod under pnpm.
Verified against a live server: OTP sent, code verified, uuid PK honoured,
database session written, and an authenticated tRPC call resolved. A
signed-in stranger gets NOT_FOUND on another client's deck; anonymous
gets UNAUTHORIZED.
124 tests passing.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
