qubership-apihub

Authors and updates APIHUB deployment assets in qubership-apihub: Helm values/templates, Docker Compose env wiring, docs/configuration-reference.md parity, local-k8s-quickstart, and optional extensions (linter, agents-backend). Use when changing helm-templates/, docker-compose/, or deployment docs under docs/.

Decide whether a backend change requires follow-up in the qubership-apihub deployment repo (Helm, Compose, configuration reference) and remind the developer with concrete actions. Use when editing backend config, env defaults, or deployment-facing behaviour — not when authoring chart changes inside qubership-apihub itself.

British-English-first style guidance for developer-facing text of any length — README and docs, code comments and docstrings inside source files (.go, .js, .ts, .py, .java, .rs, .kt, .cs, .cpp, .rb, .swift, ...), Javadoc / KDoc / TSDoc / JSDoc, commit messages, PR descriptions and review replies, design docs, changelog entries, UI strings (buttons, labels, placeholders, tooltips), error and log messages, and English-side localisation files (.po, .properties, JSON i18n). Use whenever the task involves English developer text — writing, editing, rewriting, translating, localising, reviewing, proofreading, verifying, auditing, double-checking, sanity-checking, cross-checking, or "checking the wording". Length does not matter: a one-line `msgstr`, a `// FIXME: …` comment, or a three-word button label is in scope. Also covers choice of English identifier names (methods, variables, classes, files, tests) that will be read by humans. Covers em-dash usage, hyphen stacking, sentence structure, that/which, gerunds after