# 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

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

## Fix it

### Step 1: Check the Arabic categories

```bash
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

```bash
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

```bash
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/pst_tRnr9RMEayk2pqbDx_H5kw