Activity

Why

Companion to #156. That PR handles users already stuck in the wrong-role situation (cleaner trying to book → clear message + CTA to register a client account). This PR is the prevention side — make the constraint visible at decision-time so fewer new users end up there.

Tony's situation in particular: he owns a cleaning company, registered as one, then discovered he couldn't book another cleaner for his own needs. The role-picker modal currently doesn't tell anyone that the account is single-role.

Changes (resources/js/pages/auth/register.tsx)

• Modal subtitle now says "Each account does one thing — pick the one you'll use most" so the trade-off is visible before they click a card.
• New amber notice under the role cards: "One account = one role. If you need to be both a cleaner and a client (for example, a cleaning company that occasionally hires other cleaners), register a separate account for each — same person, different email."

That's it. No backend changes, no logic changes — pure copy.

Test plan

• Pint clean, Prettier clean, ESLint clean
• Existing RegisterTest assertions still match (the literal strings "How would you like to use TidyLinker" and "Joining as a Cleaner/Client" are unchanged)
• Visual check after deploy: amber notice renders correctly under the three cards