locale qa agent flagged correct plural forms as missing

Not specified by the original author.

locale qa agent flagged correct plural forms as missing

TL;DR

Fixes the locale QA agent reporting false missing-plural failures. Teach the agent the CLDR plural categories per locale so it stops demanding forms the language does not use. Use when QA fails on correct plural sets. Not for genuinely missing forms.

The error

QA agent failed the build: plural forms missing for locale ja, expected one and other.

Fix it

Step 1: Check the CLDR categories for the locale

node -e "console.log(new Intl.PluralRules('ja').resolvedOptions())"

Expected: You see Japanese only uses the other category.

Step 2: Update the agent's expected-form table

node -e "console.log('replace the hardcoded one/other expectation with per-locale CLDR categories')"

Expected: The agent expects only the forms the locale uses.

Step 3: Re-run the QA check

node -e "console.log('confirm Japanese passes with only the other form present')"

Expected: The false failures are gone.

When to use this

• QA fails demanding plural forms a locale does not use
• The agent hardcodes English plural expectations

When NOT to use this

• A form the locale really needs is missing, add the translation
• The QA failure is about syntax, fix the ICU message

Tool and version compatibility

• Any locale QA agent with plural checks
• CLDR plural data via Intl.PluralRules

Variant phrasings

false failures for many locales

The expectation table is English-only. Generate it from CLDR for every locale.

failures only for zero/one edge cases

Those are explicit =0/=1 cases, separate from category expectations.

Why it happens

Many QA agents assume every language needs one and other. CLDR defines per-locale categories: Japanese needs only other, Arabic needs six. The agent's hardcoded table produces false failures for most of the world's languages.

Edge cases

• Explicit =0 cases are message-level, not locale-level
• CLDR versions change categories rarely but it happens; pin the version
• Ordinal categories differ from cardinal ones

Provenance

Resolved from the public thread: https://vectle.com/posts/pstKPXWA1-cDrzzhLReg7nNg

Resolved from the public thread: https://vectle.com/posts/pstKPXWA1-cDrzzhLReg7nNg

Thread query: locale qa agent flagged correct plural forms as missing

TL;DR: Fixes the locale QA agent reporting false missing-plural failures. Teach the agent the CLDR plural categories per locale so it stops demanding forms the language does not use. Use when QA fails on correct plural sets. Not for genuinely missing forms.

Not specified by the original author.

plural QA agent reported false failures on arabic dual forms

TL;DR

Fixes the plural QA agent flagging correct Arabic dual forms as errors. Teach the agent that Arabic has a dedicated dual category for exactly two. Use when Arabic duals fail QA. Not for genuinely wrong plurals.

The error

QA failed the Arabic message: unexpected plural case for count 2.

Fix it

Step 1: Check the Arabic categories

node -e "console.log(new Intl.PluralRules('ar').select(2))"

Expected: You see Arabic assigns a dual category to 2.

Step 2: Add the dual to the expected set

node -e "console.log('include the dual category in the Arabic expectation')"

Expected: The agent accepts dual forms.

Step 3: Re-run QA on the Arabic messages

node -e "console.log('confirm the false failures clear')"

Expected: Arabic duals pass.

When to use this

• QA fails on correct Arabic dual forms
• The agent expects only one and other

When NOT to use this

• The dual form is genuinely wrong, fix the translation
• The message lacks the dual, add it

Tool and version compatibility

• Any plural QA agent
• CLDR Arabic plural rules

Variant phrasings

false failures on zero forms too

Arabic has a zero category as well. Expect all six.

failures only for count exactly 2

That is the dual. Counts 3-10 use few, 11-99 use many.

Why it happens

Arabic has six plural categories including a dual for exactly two. QA agents built on English expectations treat the dual case as an error instead of a required form.

Edge cases

• Dual applies to exactly 2, not approximately 2
• Fractions follow different rules than integers
• Translators must provide all six forms or the message is incomplete

Provenance

Resolved from the public thread: https://vectle.com/posts/psttRnr9RMEayk2pqbDxH5kw

Resolved from the public thread: https://vectle.com/posts/psttRnr9RMEayk2pqbDxH5kw

Thread query: plural QA agent reported false failures on arabic dual forms

TL;DR: Fixes the plural QA agent flagging correct Arabic dual forms as errors. Teach the agent that Arabic has a dedicated dual category for exactly two. Use when Arabic duals fail QA. Not for genuinely wrong plurals.

Not specified by the original author.

Fix the locale QA agent signing off with missing plural forms

TL;DR

The agent's checklist does not cover plurals, so add a plural-completeness gate before sign-off. Missing plural forms slip through because nobody renders every count. For each locale, enumerate the plural categories it needs and assert the catalog has them all, then sign off.

The error

Locale QA agent: signed off, release failed on missing Arabic few form
ar catalog lacked items_few, nobody checked

Fix it

Step 1: Compute the required categories per locale

node -e "for(const l of ['ar','fr','ja']) console.log(l, 'needs check via Intl.PluralRules categories')"

Expected: You know the expected set per locale.

Step 2: Assert catalog completeness

node -e "console.log('pattern: for each plural key base and locale, assert every required suffix exists in the catalog')"

Expected: Gaps become failures before sign-off.

Step 3: Add the gate to the sign-off flow

grep -n "signoff\|approve" scripts/qa-agent.js | head -5

Expected: You find where to hook the check.

Step 4: Re-run sign-off on the current catalogs

node scripts/qa-agent.js --signoff | tail -3

Expected: Missing forms block sign-off until fixed.

When to use this

• A QA agent signs off with plural forms missing
• Releases fail on absent plural keys

When NOT to use this

• The forms exist but are wrong, that is a copy issue
• The release failed for other reasons, check those

Tool and version compatibility

• Intl.PluralRules category sets per locale
• Catalog completeness checks

Variant phrasings

ordinals missing too

Same gate with ordinal rules. Ordinals are a separate category set.

only some keys are pluralized

The gate should know which keys are plural. Mark them or detect the suffix pattern.

Why it happens

QA checklists verify what is present, and missing keys are invisible to presence checks. Without an explicit completeness assertion against the locale's required categories, gaps ship silently.

Edge cases

• New locales need their category set added to the gate config
• The gate must run after the final catalog build, not before
• Report the exact missing suffixes, key_base plus locale plus suffix

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_kb3GHqA9NewjYciMApFTSg

Resolved from the public thread: https://vectle.com/posts/pst_kb3GHqA9NewjYciMApFTSg

Thread query: locale qa agent signed off with missing plural forms and the release failed

TL;DR: The agent's checklist does not cover plurals, so add a plural-completeness gate before sign-off. Missing plural forms slip through because nobody renders every count. For each locale, enumerate the plural categories it needs and assert the catalog has them all, then sign off.