Show Candidate Email in Profile.

REQUEST

Hi. In the candidate detail drawer, display the candidate’s email address beneath their title and company. Make it a clickable mailto: link and add an automated test for it. Do not change the database schema or migrate any data.

APPROVED PLAN

1. User-visible behavior  
   In the candidate detail drawer, show the existing email address directly beneath the title/company line. Render it as a clickable link with `href="mailto:<email>"`.

2. Frontend changes  
   Update the drawer markup in [components/recruiting-app.tsx](/vercel/sandbox/target/components/recruiting-app.tsx:146). Add minimal styling if needed so the email reads as an interactive link. No data-fetching changes are required.

3. Backend and Convex changes  
   None. Email already exists in the shared type, API validation, fallback store, Convex schema, seed data, and dashboard response:

   - [lib/types.ts](/vercel/sandbox/target/lib/types.ts:6)
   - [app/api/candidates/route.ts](/vercel/sandbox/target/app/api/candidates/route.ts:7)
   - [convex/schema.ts](/vercel/sandbox/target/convex/schema.ts:22)
   - [convex/dashboard.ts](/vercel/sandbox/target/convex/dashboard.ts:11)

4. Migration assessment  
   No versioned migration is needed because no stored data, schema, or API shape changes.

   - No transient widened schema.
   - No backup/stash changes.
   - No forward transform.
   - No rollback or reapply logic.
   - No row-count or data-invariant migration validation required.

   Leave `convex/migrations.config.ts`, `convex/migrations.ts`, and the app version unchanged.

5. Tests and browser verification  
   Extend [e2e/factory-preview.spec.ts](/vercel/sandbox/target/e2e/factory-preview.spec.ts:51) to open a seeded candidate drawer and assert:

   - The email text is visible beneath the title/company information.
   - A link with the candidate’s email exists.
   - Its `href` equals the expected `mailto:` URL.

   Run the factory-configured typecheck, unit tests, build, and Playwright smoke test in an isolated preview. The existing preview login and recruiting workflow should remain covered.

6. Risks or questions  
   No blocking risks identified. The feature can be implemented safely in an isolated preview without credentials, database changes, or production operations. The test should assert the link target without activating the mail client.