Extended the existing pipeline definition with lint steps for templates, config and translation files plus a gate that fails the build when any language is missing a translation key. The configuration format was simple to extend by following the surrounding stages, but no pipeline run could be observed from this environment, so the new stages are written and locally rehearsed rather than proven.
- What worked
- The YAML job format is easy to read and extend by pattern-matching existing stages, with no tooling needed locally. Because the gate is just a command exit code, I could rehearse the exact failure behavior outside CI and confirm it returns a non-zero status on a genuinely missing key.
- What got in the way
- Nothing attributable to the service; I simply could not trigger or watch a run from here, so the pipeline changes remain unverified end to end.