[dikshantgoyal011]

What this does

FW-602: a profile name. Accounts kept only an email address. Now an account can go by a name, and the header shows it.

This PR builds on #44 (FW-601, the header sign-in), which should merge first. Until then, this PR's diff also shows that PR's commit, 780c547. This PR's own commits are 90b0e98 and a0b37ad.

Service (api/)

• Migration 0003_profile_name.sql adds users.name. The user the service describes carries name, which is null until it's given.
• POST /auth/verify takes an optional name. It names a new account, or one with no name yet, and never replaces an existing name.
• New POST /auth/profile { name } sets the signed-in account's name; an empty name clears it.
• What a name can be:
  • It's trimmed, and runs of spaces become one.
  • Up to 80 characters, counted as characters, not bytes.
  • Control characters and bidirectional overrides (which could make a name display as something else) are refused. They're refused before the code is checked, so a bad name doesn't use up one of the code's tries.
  • Zero-width joiners are kept, because some scripts and emoji need them.
• Admin listing: includes each account's name.
• README: documents all of the above.

Site

• /signup: an optional Your name field above the address.
• /account: a Name field to change or clear the name.
• Header: shows the name, with the initials of its first and last words ("AL" for Ada Lovelace). The menu shows the name above the address. Without a name, both show the address, as before.
• Console footer and admin page: show the name too.
• Demo mode: the in-browser demo keeps the name with its session.

Also fixed (a0b37ad): the outlined buttons (Sign out on /account, Resend code and Use another address while signing in) turned near-black on hover, which left their dark text unreadable. pillOutline never overrode shadcn's default hover:bg-primary/80. Now only the border darkens on hover, as intended.

When it merges, in this order

1. npm --prefix api run migrate:remote, to add the column to the live database.
2. npm --prefix api run deploy.

The Worker's new code reads users.name, so deploying it before the migration would break sign-in. The site copes with the Worker not being updated yet: it shows the address, and saving a name on /account says "Not found." until the deploy.

Testing

• npm --prefix api run check: 72 tests pass, 15 of them new, in api/test/profile.test.mjs. They cover:
  • giving a name at sign-up
  • tidying it
  • never replacing it
  • changing and clearing it
  • every refused kind of name, without using up the code's try
  • 80 multi-byte characters fitting
  • joiners being kept
  • needing a session
  • only changing your own account
  • other sites being refused
  • the admin listing
• Mutation check: with the never-replace rule or the character check undone, the tests fail.
• npm --prefix site run check passes at both commits, and docs/ matches a rebuild.
• The production build in Edge, against a local service: 29 checks.
  • The sign-up field, and the header after sign-up ("AL", the name, the button's accessible name, the menu).
  • /account with no name: saving one, keeping it after a reload, a refused name, clearing it, and a double-click saving only once.
  • The console footer, the hover fix, and the admin page.
  • The demo, with no service.
  • No console errors.
• The FW-601 header suite (62 checks) passes on this branch too.

Merging with the other two PRs

#44 (FW-601), this PR and #43 (FW-603, open sign-up) each rebuild docs/. Whichever merges second needs a rebuild, plus one test constant in api/test/auth.test.mjs: it takes name: null from this PR and waiting: false from FW-603. I merged all three locally and ran every check on the result: everything passes.

🤖 Generated with Claude Code

[ashutosh091]

Landed on preview through #47, which merged this branch together with the other two FW-60x PRs on top of the Paygate billing work. Your commits are unchanged. Changes made during the merge: the profile-name migration is renumbered to 0004_profile_name.sql (preview already had 0003_billing.sql); the /pricing copy now says to start on Free and upgrade, since billing is live; and the billing test suite pins SIGNUP_MODE: "waitlist". Thanks!