feat(API): document translation_keys_sort_collation on /projects endpoints

[junior-ai-bot]

What changed

• Added translation_keys_sort_collation to the project_details schema (schemas/project_details.yaml), so it now shows up as a documented, readable field on the responses for GET /projects/{project_id}, POST /projects, and PATCH /projects/{project_id} (all three already reference this schema for their response body).
• Documented the field's two valid enum values (general_ci, unicode_ci) on the request bodies for POST /projects (paths/projects/create.yaml) and PATCH /projects/{project_id} (paths/projects/update.yaml), matching app/models/project.rb's enum :translation_keys_sort_collation, { general_ci: 0, unicode_ci: 1 } in strings-app.

Why

STRINGS-3248 added translation_keys_sort_collation to Project::API_EXPOSED_ATTRIBUTES in strings-app, so the field is now returned by GET /api/v2/projects/{project_id} (and, per that ticket, the list endpoint) in addition to the existing POST/PATCH write support. Since it's an enum-backed column rather than a settings-store attribute, the automated openapi-sync bot flow may not produce a correct spec update for it, so this PR manually verifies/adds the documentation as a tracking follow-up.

The lightweight project schema used for GET /projects (list) intentionally omits settings-style attributes like cldr_version and the various boolean flags already present on project_details — following that existing precedent, translation_keys_sort_collation was not added there either, only to project_details, consistent with how cldr_version and similar fields are handled.

Per the ticket, GET /projects/{project_id}/settings remains intentionally undocumented — no changes were made for that endpoint.

phrase-engineering/strings-git-sync will be updated with the same schema change in a separate PR against that repo.

Test plan

• npx swagger-cli validate main.yaml — passes
• npx swagger-cli bundle -t yaml -w 300 main.yaml — bundles successfully
• bash ./lint.sh (openapi-generator-cli validate) — no validation errors
• Verified the compiled bundle (tmp/compiled.yaml) contains the new field/enum in all three expected locations (project_details schema, create request body, update request body)

STRINGS-3445

Co-Authored-By: junior-dev

🤖 Generated with Claude Code

[github-actions]

API changelog (oasdiff)

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

9 changes: 2 error, 0 warning, 7 info
error	[request-property-became-enum] at doc/compiled.json
	in API POST /projects
		request property `translation_keys_sort_collation` was restricted to a list of enum values

error	[request-property-became-enum] at doc/compiled.json
	in API PATCH /projects/{id}
		request property `translation_keys_sort_collation` was restricted to a list of enum values

info	[request-property-enum-value-added] at doc/compiled.json
	in API POST /projects
		added the new `general_ci` enum value to the request property `translation_keys_sort_collation`

info	[request-property-enum-value-added] at doc/compiled.json
	in API POST /projects
		added the new `unicode_ci` enum value to the request property `translation_keys_sort_collation`

info	[response-optional-property-added] at doc/compiled.json
	in API POST /projects
		added the optional property `allOf[subschema #2: project_details]/translation_keys_sort_collation` to the response with the `201` status

info	[response-optional-property-added] at doc/compiled.json
	in API GET /projects/{id}
		added the optional property `allOf[subschema #2: project_details]/translation_keys_sort_collation` to the response with the `200` status

info	[request-property-enum-value-added] at doc/compiled.json
	in API PATCH /projects/{id}
		added the new `general_ci` enum value to the request property `translation_keys_sort_collation`

info	[request-property-enum-value-added] at doc/compiled.json
	in API PATCH /projects/{id}
		added the new `unicode_ci` enum value to the request property `translation_keys_sort_collation`

info	[response-optional-property-added] at doc/compiled.json
	in API PATCH /projects/{id}
		added the optional property `allOf[subschema #2: project_details]/translation_keys_sort_collation` to the response with the `200` status

[junior-ai-bot]

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

Still failing

CI checks:

• Breaking changes: 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.