[olaservo]

Summary

1. Adds a members role for the contributor ladder's Member tier. The ladder promises "GitHub organization membership with triage rights", but no role here provided it.
2. Documents the ladder mapping in a new README section. It shows how each ladder role corresponds to the teams and org roles configured here, and where they diverge.

The members role

• GitHub team members, with no parent team, so it does not inherit steering-committee's push grants.

• triage on modelcontextprotocol, docs, .github, inspector, quickstart-resources and servers, granted per repository. I deliberately didn't use the all_repo_triage org role, because it would also cover private repos (community-moderators, maintainer-docs, GHSA forks).

• Discord role members (synced), with no permissions, which serves as the ladder's "community membership roster".

• Initial members come from the charters. SEP-2149 requires WG Leads and IG Facilitators to hold at least Member status. This adds the charter-listed leads/facilitators who already have users.ts entries and are not already Maintainer or above:

  GitHub	Charter role
  degiorgio	Interceptors WG Lead
  jeongukjae	Interceptors WG Lead
  rreichel3	Tool Annotations IG Facilitator

  Every other charter lead or facilitator with a users.ts entry already holds a Maintainer-level role. Facilitators who would need new org invites will follow in a separate PR. After that, people are added the normal way, by putting ROLE_IDS.MEMBERS in memberOf once the ladder's sponsorship requirements are met.

• Not included: charter "WG Members" and "Participants". SEP-2149 says WG Member is a group-level tier distinct from ladder Member, so they need nomination and sponsorship like anyone else.

Expected pulumi preview: 1 GitHub team, 6 team repository grants, 1 Discord role, 3 team memberships, and Discord role assignments for those 3 users. No existing access changes, and no new org invites.

What the mapping shows

• Contributor, Core Maintainer and Lead Maintainer match the ladder directly.
• Maintainer: an "owned area" is a team (SDK, docs, inspector, registry, and so on).
• Parent-team inheritance: WG, IG and SDK teams nest under steering-committee. Their members inherit push on docs, inspector, quickstart-resources and servers, whatever their ladder rank.
• WG leads: only some WGs have a *-wg-leads team (with admin on the extension repo). wg-ig-facilitators is one flat, hand-maintained Discord role for calendar access, and many charter leads are not in it.
• Roles with no ladder counterpart, and per-user grants.
• security-ig has admin on six repos. This was carried over from Fix WG/IG modeling gaps #170 and is flagged there as a separate workstream.

Testing

• npm run validate: all references valid
• npm test: 79 passed, 0 failed
• Prettier: clean

Open questions for maintainers

1. Is the set of six repos right for Member triage? Can sponsors confirm the three initial members?
2. Is the inherited push for all WG/IG members intended?
3. Should every WG have a leads team, and should wg-ig-facilitators be derived from the leads teams instead of maintained by hand?

🤖 Generated with Claude Code

[dsp-ant]

Thank you Ola