feat(API): document GET /projects/{project_id}/members list endpoint STRINGS-3471

[junior-ai-bot]

What changed

Adds the previously-undocumented GET /projects/{project_id}/members endpoint to the published spec:

• paths/members/index_project.yaml — new path definition (operationId: members/by_project), following the existing jobs/list / jobs/by_account naming convention for a project-scoped vs. account-scoped variant of the same resource.
• schemas/project_member.yaml — new response schema. It mirrors the existing member schema shape but adds the position field and explicitly has no project_role/project_roles field, per the ticket's evidence about the actual controller response.
• paths.yaml — wires the new path in under /projects/{project_id}/members, alongside the existing /projects/{project_id}/members/{id} (PATCH) sibling.
• doc/compiled.json — regenerated via make bundle (purely additive diff, matches the convention from prior PRs like feat(API): add name filter query parameter to spaces list #STRINGS-3036 #1267).

Why

The endpoint exists and works in strings-app (config/routes/api.rb:296, Api::V2::MembersController#index project branch), authorized via ProjectPolicy#list_members? and requiring only the read scope — unlike the account-level members endpoints which require team.manage. It was undiscoverable via the API reference and could only be reached by guessing the path from the documented PATCH sibling (update_settings). This surfaced during analysis of a production Atlas session where an agent needed the project-scoped fallback after being refused on account-level members endpoints.

Per the ticket's acceptance criteria:

• Documents the read scope requirement, called out explicitly in both the endpoint description and a 403-response override distinguishing it from the account-level endpoint's team.manage requirement (mirrors the existing jobs/by_account override pattern).
• Documents the q, job_id, page, per_page query parameters and the Link/Pagination response headers.
• Documents the response schema, noting the position field and the absence of a project_role field.

Test plan

• npx swagger-cli validate main.yaml — passes.
• make bundle (npx swagger-cli bundle -t json/yaml ...) — regenerates doc/compiled.json / tmp/compiled.yaml with a purely additive diff for the new path/schema.
• bash ./lint.sh (openapi-generator-cli validate) — "No validation errors".
• No client library regeneration performed, matching the precedent of similar param/path-only PRs (e.g. feat(API): add name filter query parameter to spaces list #STRINGS-3036 #1267) which did not regenerate clients/.

Related

• https://phrase.atlassian.net/browse/STRINGS-3040 and https://phrase.atlassian.net/browse/STRINGS-3195 (adjacent members docs work, neither covers this endpoint)

STRINGS-3471

Co-Authored-By: junior-dev

🤖 Generated with Claude Code

[github-actions]

API changelog (oasdiff)

Doc-only edits (descriptions, examples) do not appear here.

1 changes: 0 error, 0 warning, 1 info
info	[endpoint-added] at doc/compiled.json
	in API GET /projects/{project_id}/members
		endpoint added

[junior-ai-bot]

Junior hit its fix-attempt cap (5/5) and has stopped retrying this PR.

Still failing

CI checks:

• Validate PR title: failure
• Validate PR title: failure

Unresolved bot review threads:
None

Next steps

A human needs to take it from here — either:

• Fix the remaining issues manually and push a commit, or
• Run /reset-pr-fix (or use the dashboard) to clear the needs-human label and attempt counter so Junior resumes automatically.

[Sven Dunemann (forelabs)]

Actually this endpoint behaves differently based on params, which is not ideal. Before documenting this we will look into its current usage and decide.

[Sven Dunemann (forelabs)]

Reopening -> the /accounts/.../members path is already documented with correct serializer, the /projects/.../members path is what will be added here and has its own serializer, no mixing possible.

[junior-ai-bot]

Resumed via the dashboard — the needs-human label was cleared and both fix-attempt counters were reduced by 2. Junior will pick this PR back up on its next CI-fix poll cycle.

change implemented

[junior-ai-bot]

Thanks for the clarification. Since /projects/{project_id}/members has its own dedicated serializer (distinct from /accounts/.../members, no mixing possible), I've kept project_member as a separate, project-specific schema and corrected it to the actual attributes: id, username, name, position, created_at, updated_at (see the reply on the inline thread). Let me know if there's anything else re: the params-dependent behavior you'd like reflected in the docs before this is good to merge.