[ptrcja]

Description

Wires the new QA mentee@wcc.dev account (role MENTEE) into the framework so mentee and
application tests can authenticate as a mentee.

• tests/.env.example: MENTEE_EMAIL / MENTEE_PASSWORD
• roles.data.ts: Role.MENTEE and its USERS entry
• common.fixtures.ts: menteeApi fixture (plus the fixture list in the doc comment)
• admin-nav.data.ts: NAV_LINKS[Role.MENTEE] = ["Dashboard"]. The portal shows MENTEE the
  same nav as a VIEWER (AdminLayout.tsx has no MENTEE-specific links). Confirmed by ADMIN-LOGIN-02.
• AUTH-09 (new): loops over every Role, calls GET /api/auth/me with that role's token, and
  checks member.email matches the role's account. This proves menteeApi (and the previously
  untested memberApi / mentorAdHocApi) log in, and covers future roles automatically.
• AUTH-04 still checks the role claim for MENTOR.
• TEST_PLAN.md: AUTH-09 row.
• CLAUDE.md: updated the seeded-accounts sentence (it still said member / ad-hoc mentor were
  "not yet wired to fixtures", and didn't mention the mentee).

Depends on Women-Coding-Community/wcc-backend#827, which adds the account to the seed.
Until it merges, nightly runs against backend main without the mentee, so the mentee cases of
AUTH-09 and ADMIN-LOGIN-02 will fail there. Please merge #827 first, or run Nightly manually.

Related Issue

Closes #55

Type

• New test coverage
• Test fix (flaky, broken, or incorrect test)
• Framework change (fixtures, clients, services, factories, schemas)
• Bug fix
• Documentation
• Tooling / CI
• Other

Test Evidence

Run locally against npm run env:up with wcc-backend on feat/seed-mentee-account:

Pull request checklist

• This PR is linked to an issue
• npm run lint and npm run typecheck pass locally
• Tests have been added or updated for this change
• tests/api/TEST_PLAN.md has a row for every new test ID (API flows only)
• No secrets committed — credentials stay in tests/.env, and no token, password, or API key is logged or hardcoded
• I have performed a self-review of my own code

[nora-weisser]

LGTM!