fix(curated-corpus): add Polish to the language picker

[mmiermans]

Problem

#1274 added Poland (NEW_TAB_PL_PL) as a scheduled surface, but Polish is missing from the language picker, so curators cannot set or see PL on corpus items and sections.

Change

• Add Polish to the languages dropdown options (definitions.ts).
• Add Pl = 'PL' to the generated CorpusLanguage enum (generatedTypes.ts).

The enum value comes from the backing schema change in Pocket/content-monorepo#391, which is now deployed. generatedTypes.ts was updated by running api:generate-types.

[claude]

Claude finished @mmiermans's task in 51s —— View job

---

PR Review — add Polish to the language picker

• Read PR diff
• Review definitions.ts change
• Review generatedTypes.ts change
• Post review feedback

---

Verdict: LGTM ✅ — small, correct, and consistent with the existing pattern. One observation worth a look before merge.

definitions.ts ✅

• { code: CorpusLanguage.Pl, name: 'Polish' } matches the shape and style of the surrounding entries exactly.
• The comment update (// Language codes for the curation tool's language picker.) is a nice fix — the old "Currently only English and German are needed" was already stale.
• I checked the other consumers of CorpusLanguage and nothing else needs touching: the only language-specific branching is applyTitleFormattingByLanguage in helperFunctions.ts:246/266, which is gated on CorpusLanguage.De (German-only capitalization) — Polish correctly falls through to the default path, same as ES/FR/IT.

generatedTypes.ts — ⚠️ unrelated codegen changes bundled in

The Pl = 'PL' enum entry is correct: alphabetical order (De, En, Es, Fr, It, Pl), /** Polish */ doc comment, and trailing-comma style all match codegen output exactly.

However, the diff also pulls in schema changes unrelated to this PR's stated purpose — the PR body says only the Pl entry was added, but the file also gains:

• updateSectionItem on Mutation
• MutationUpdateSectionItemArgs
• UpdateSectionItemInput

These are legitimate codegen drift (the dev schema picked up the SectionItem mutation since the file was last generated), so they're not wrong — but bundling them into a "add Polish" PR makes the diff harder to reason about and couples this change to a backend feature that may not be in use by this frontend yet.

Suggestion: This is fine to merge as-is if you're comfortable that the SectionItem mutation is deployed on every environment this UI targets (not just dev). If you'd prefer a minimal, focused diff, you could hand-edit generatedTypes.ts to add only the Pl enum entry and drop the three SectionItem-related blocks. Just flagging it so it's a conscious decision rather than an accidental inclusion. Fix this →

Notes

• No test changes are needed for this — the language list isn't snapshot-tested, and the prospects.test.ts language table only covers de/en/es/fr/it. Optionally you could add a pl row there for completeness, but it's not required.
  · fix/add-pl-language

[mmiermans]

Generated from dev schema.