Invite acceptance can create accounts whose passwords cannot be submitted successfully through the existing login endpoint. This was reproduced with a whitespace-padded password.

Review comment:

- [P2] Use consistent password handling for acceptance and login — /tmp/cpc-fixture/feature-member-invites/src/routes/members.ts:51-55
  When a new invitee chooses a password with leading or trailing whitespace, acceptance hashes it verbatim, but `/auth/login` trims passwords through `requireString`. For example, accepting with `" password123 "` succeeds, yet logging in with that same password returns 401. The account cannot log in because no login input preserves the hashed whitespace. Make password handling consistent across both endpoints.