plural audit agent missed missing _few form for russian

Not specified by the original author.

plural audit agent missed missing _few form for russian

TL;DR

Fixes the plural audit agent passing Russian messages that lack the few form. Check messages against the full CLDR category set per locale. Use when Russian renders the wrong plural and the audit passed. Not for syntax errors.

The error

Audit passed, but Russian users see the wrong plural form for counts like 2, 3, 4.

Fix it

Step 1: Check the Russian categories

node -e "console.log(new Intl.PluralRules('ru').select(2), new Intl.PluralRules('ru').select(5))"

Expected: You see Russian needs one, few, many, and other.

Step 2: Audit the message against all four

node -e "console.log('list the plural cases in the message and compare')"

Expected: You find the few case missing.

Step 3: Add the missing form and re-audit

node -e "console.log('confirm the audit now requires all Russian categories')"

Expected: The audit catches the gap.

When to use this

• A locale renders wrong plurals but the audit passed
• The audit only checks one and other

When NOT to use this

• The message has a syntax error, fix the ICU first
• The plural is wrong in every language, check the count value

Tool and version compatibility

• Any plural audit agent
• CLDR plural data

Variant phrasings

audit misses Arabic dual

Same fix: audit against the full six Arabic categories.

audit passes but translators skipped a form

The audit must check the message structure, not just key presence.

Why it happens

Audit agents written against English assume one and other suffice. Russian needs few for 2-4, and a message without it silently falls back to other, which the audit never flagged.

Edge cases

• Fractions use different categories than integers in some locales
• Explicit =2 cases override categories; audit those separately
• CLDR updates can add categories; re-audit on upgrade

Provenance

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

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

Thread query: plural audit agent missed missing _few form for russian

TL;DR: Fixes the plural audit agent passing Russian messages that lack the few form. Check messages against the full CLDR category set per locale. Use when Russian renders the wrong plural and the audit passed. Not for syntax errors.

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.

Not specified by the original author.

TL;DR

Fix this in Help center audit agent by acting on the exact symptom first: keep a visited list of synonyms already tried, stop when a synonym repeats, expand synonyms only from the search log terms readers actually used, and cap synonym expansion per article so the audit always moves to the next article. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Agent loop repeating the same search synonym during stale article audit

Use this when

• Work in Help center audit agent shows this exact symptom: Agent loop repeating the same search synonym during stale article audit.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Help center audit agent, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: keep a visited list of synonyms already tried, stop when a synonym repeats, expand synonyms only from the search log terms readers actually used, and cap synonym expansion per article so the audit always moves to the next article. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Help center audit agent that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Agent loop repeating the same search synonym during stale article audit

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - agent stuck loop detected repeating the same search synonym while trying to audit stale help center articles error failure

The how to phrasing for the same problem in Help center audit agent. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Help center audit agent troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Without a visited set the agent regenerates the same plausible synonym from the article title each pass, and the loop looks like progress while covering no new ground.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Help center audit agent at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

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

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

Thread query: agent stuck loop detected repeating the same search synonym while trying to audit stale help center articles error failure

TL;DR: Fix this in Help center audit agent by acting on the exact symptom first: keep a visited list of synonyms already tried, stop when a synonym repeats, expand synonyms only from the search log terms readers actually used, and cap synonym expansion per article so the audit always moves to the next article. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.