feat: Invite a contributor as a member (pitch #3806, scope D)

[Anty0]

Part of pitch #3806 (Community translation v1.1 — Contributors), scope D. Targets the integration branch (PR #3819), not main.

What

Adds an "Invite as member" button to a Community-tab row on the project Members page. Clicking it invites that contributor to the project by user id — the server resolves their address, sends the invitation mail, and never returns it to the org.

• New endpoint PUT /v2/projects/{projectId}/invite-contributor (MEMBERS_EDIT); the body carries userId + permission fields, no email.
• Email-free by construction. The address is stored server-side (needed to send the mail and bind acceptance) but is masked at read time by Invitation.visibleEmail — the single home of the rule — which every assembler that serializes an invitee address reads (Team-tab pending list and the unauthenticated invitation_info endpoint). Pitch hard-constraint 1: no contributor email reaches the org before acceptance.
• Anti-oracle guard. Only visible contributors of the project may be invited (reusing the Community tab's member / deleted / disabled exclusions, via a single shared VISIBLE_CONTRIBUTOR query). Every other id — nonexistent, deleted, disabled, member, org member, or a contributor of another project — returns one byte-identical 404, so the endpoint leaks neither account existence nor state.
• No permission-less membership. type = NONE is rejected server-side (CANNOT_INVITE_CONTRIBUTOR_WITH_NO_PERMISSION), not merely hidden in the picker.
• Scoped/advanced invites route through the EE service exactly like the email invite; agencyId stays null (a non-null agency would short-circuit acceptance binding).
• Acceptance is bound to the invitee (email = user.username); a different user gets INVITATION_EMAIL_MISMATCH.

Frontend

• members.edit-gated "Invite as member" button on the contributor row, opening the existing PermissionsModal picker with hideNone (matching the email dialog). The permission→body mapping is factored into a shared helper used by both invite hooks.

Tests

• Backend (InviteContributorControllerTest, InviteContributorEeTest): email stored + hidden, model + public-endpoint email null, MEMBERS_EDIT gate, uniform-404 for every non-visible-contributor id, re-invite dedup, NONE rejection, EE scoped routing + granted languages, nameless-contributor path, acceptance binding + granted membership.
• Frontend: vitest over the shared permission-body helper (all role/scope/language branches, incl. scope-based filtering); an E2E case that invites a contributor from the Community tab (typed data-cy selectors), asserts the request succeeds, that a pending invitation appears, and that the NONE role is absent from the picker.

Notes

• Accepted, documented limitations (see the plan's Risks): an already-invited contributor stays listed with a live button until they accept (a second click fails safely with a no-email error), and acceptance is email-bound rather than user-FK-bound (a full user-FK model is deferred to a follow-up across all invitation kinds).

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e7e9cbac-8ec4-4f7a-8b1a-0997e54d5b56

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jirikuchynka/invite-contributor

---

_{Comment @coderabbitai help to get the list of available commands.}