translation.wording_missing: A supported locale has no wording for a message

A supported locale has no wording for a message.

Area 10, Configuration and time; not declinable; the next step is usually the agent's.

A message is worded in every supported locale that isn't in progress, so a call in French has words to show.

example

translations {    order_shipped: "La commande de {name} a été expédiée."}

text

error: `parcels` has no wording in `domains/shipping/translations/fr_fr.jadpo` --> domains/shipping/translations/fr_fr.jadpo:1:1  |1 | translations {  | ^^^^^^^^^^^^ no `parcels`  reason: A message is worded in every supported locale that isn't in progress, so a call with `locale: Locale.fr_fr` has words to show.  next: Add `parcels`, with a wording for each plural form (`one`, `many` and `other`) to `domains/shipping/translations/fr_fr.jadpo`, which may write `{count}` (agent)  rule: translation.wording_missing  help: https://jadpo.dev/docs/errors/translation.wording_missingcheck failed: 1 error, 5 files

A failure a route can answer with is worded the same way, keyed by its code, so a client app showing French has text for it.

example

translations {}

text

error: `slot_taken` has no wording in `domains/booking/translations/fr_fr.jadpo` --> domains/booking/translations/fr_fr.jadpo:1:1  |1 | translations {}  | ^^^^^^^^^^^^ no `slot_taken`  reason: A failure a route can answer with is worded in every supported locale that isn't in progress, so a client app showing `Locale.fr_fr` has text for its code.  next: Add `slot_taken: "..."` to `domains/booking/translations/fr_fr.jadpo` (agent)  rule: translation.wording_missing  help: https://jadpo.dev/docs/errors/translation.wording_missingcheck failed: 1 error, 11 files