Everything now renders inside a phone illustration on the entry screen,
with a five-tab bar. The frame lives in the root layout rather than one
page, so sign-in, onboarding and the job form are inside it too.
- Entry screen is the product running, not a marketing page: a live
swipeable deck of real verified pros with a trade-filter strip above
the card. deck.showcase is the only public procedure in that router
and writes nothing, so an anonymous right swipe reaches no one.
- Settings: notification preferences (new table, defaults returned when
no row exists), signed-in devices, GDPR export, deletion request.
Closes the setEmail finding: an unverified address is no longer
written to users.email, which is UNIQUE -- claiming a stranger's
address used to block them from ever signing up with Google, and the
uniqueness error leaked whether an address was registered. Now parked
in email_change_requests until a token proves ownership.
- Profile: for a pro it leads with their REAL deck card, rendered by the
same exported <Card> clients swipe, so the two cannot drift. Adds
pro.previewCard (works at draft/pending, where publicProfile 404s) and
pro.reorderMedia (photo position 0 is the deck card). Warns before an
edit that would send a verified pro back for review, rather than after
it silently drops them off the deck. Clients get a thin profile plus a
route into pro onboarding -- supply is the launch blocker.
- Dev login: +34600000000 / 000000, behind THREE guards (NODE_ENV,
an explicit ALLOW_DEV_LOGIN flag, and an exact number match). It
overwrites the stored code rather than skipping verification, so the
real expiry, attempt cap and single-use consumption still apply.
- Seed uses portrait photos. The cards previously showed picsum stock
scenery -- a locksmith standing on a railway track.
Fixes found along the way: the card's name rendered ink-950 navy on a
dark photo because globals.css sets h1..h6 colour in @layer base, which
beat the inherited text-white; and the card referenced --color-go-500,
--border and --card, none of which exist, so the SEND JOB stamp had no
colour.
Also adds public/sw.js as a kill-switch: a service worker left
registered on localhost:3000 by a different project was intercepting
this app's chunks.
typecheck, lint clean; 186 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>
Greenfield scaffold for Linkder, a swipe-to-hire marketplace for local
professional services.
- pnpm/turbo monorepo: apps/web, packages/{shared,db}
- Postgres 16 + PostGIS via docker compose (ports 5442/6389 to avoid
clashing with other local stacks)
- Drizzle schema, 23 tables, geography(Point,4326) with GiST indexes
- Domain core in packages/shared: integer-cent money, status transition
graphs, deck ranking weights, cancellation policy — 46 unit tests
- Deck query: filtering in Postgres on the GiST index, ranking in JS so
the weights stay tunable — 18 integration tests against a seeded DB
- Deterministic seed placing pros at known distances, including three
that must NOT appear on a deck (out of radius, unverified, away)
- Next.js 15 app shell with a working swipe deck
- CI: typecheck, lint, test, build against live postgres+redis
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
