@softspark/jira-mcp 1.12.0 → 1.14.0

package/README.md

@@ -4,17 +4,16 @@
 
 [![CI](https://github.com/softspark/jira-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/softspark/jira-mcp/actions/workflows/ci.yml)
 [![npm](https://img.shields.io/npm/v/@softspark/jira-mcp)](https://www.npmjs.com/package/@softspark/jira-mcp)
-[![version](https://img.shields.io/badge/version-1.12.0-blue)](CHANGELOG.md)
+[![version](https://img.shields.io/badge/version-1.14.0-blue)](CHANGELOG.md)
 [![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
 
 ---
 
-## What's New in v1.12.0
+## What's New in v1.14.0
 
-- Nothing changes for this package: same name, same `jira-mcp` binary, same `~/.softspark/jira-mcp/` config path, same 19 tools.
-- The repository is now a workspace. Confluence ships separately as [`@softspark/confluence-mcp`](../confluence-mcp), released together with this package under one version.
-- Jira and Confluence share one HTTP layer for auth, retry and backoff; each keeps its own error vocabulary.
-- Fixed: `jira-mcp config add-project` and `remove-project` rebuilt `config.json` from a fixed field list, discarding `default_language` and, once Confluence spaces existed, the whole `spaces` section.
+- Polish versions of all eight built-in comment templates ship with the package. Until now a templated comment was English on every project, including one configured for another language.
+- `jira-mcp template list-locales` shows which languages are available, and `jira-mcp template install-locale pl` installs them. Add `--keep-english` to keep the originals reachable as `<id>-en`.
+- Released together with `@softspark/confluence-mcp` under one version. See the [changelog](../../CHANGELOG.md).
 
 ## Table of Contents
 
@@ -75,6 +74,8 @@ All configuration lives in `~/.softspark/jira-mcp/` (created by `jira-mcp config
 | `jira-mcp template list [type]` | List active comment/task templates |
 | `jira-mcp template show <type> <id>` | Show the active template file content |
 | `jira-mcp template remove <type> <id>` | Remove a user-installed template override |
+| `jira-mcp template list-locales` | List languages with shipped template translations |
+| `jira-mcp template install-locale <lang> [--keep-english]` | Install the translated comment templates for a language |
 | `jira-mcp config init` | Initialize global config at `~/.softspark/jira-mcp/` |
 | `jira-mcp config add-project <key> <url>` | Add a Jira project to config |
 | `jira-mcp config remove-project <key>` | Remove a project from config |
@@ -151,6 +152,24 @@ jira-mcp template add task ./my-bug-task.md
 jira-mcp template list
 ```
 
+### Translated templates
+
+The shipped templates are English, and a template cannot pick a language at render time: its headings are fixed text in the body. On a project configured for another language, `add_templated_comment` would post an English comment and break the language-first rule.
+
+The package ships translations under `templates-system/locales/<lang>/comments/`, installed as overrides:
+
+```bash
+jira-mcp template list-locales
+jira-mcp template install-locale pl
+jira-mcp template install-locale pl --keep-english   # installs with several project languages
+```
+
+Each translation keeps the English `id` and the English variable names of the template it replaces, so it overrides cleanly and no existing `add_templated_comment` call breaks. Only the prose changes.
+
+Installing a language makes it the default for **every** project, because the choice cannot be made per call. `--keep-english` additionally installs the originals as `<id>-en`, which is what you want when some projects are English and some are not.
+
+**Restart your MCP client afterwards.** The template catalog is read once at server startup, so a running server keeps serving the templates it loaded and the next templated comment silently renders the old version.
+
 ## Usage with Claude Code
 
 Add to your Claude Code MCP configuration (`~/.claude/claude_desktop_config.json` or project-level):
@@ -181,7 +200,7 @@ Or copy `rules/jira-mcp.md` to your ai-toolkit rules directory manually. The rul
 - **Sync before read** -- cache may be stale
 - **Status transitions** -- check valid transitions before changing status
 - **Time format** -- `"2h 30m"`, never days
-- **All 19 MCP tools** and **21 CLI commands** reference
+- **All 19 MCP tools** and **23 CLI commands** reference
 
 ### AI Toolkit Hooks
 
@@ -254,7 +273,7 @@ src/
 
 **Typed error hierarchy** -- 26 error classes with machine-readable codes. Every tool returns structured `{ success, error, code }` responses. No stack traces leak to MCP clients.
 
-**Strict TypeScript** -- `strict: true`, no `any`, `readonly` interfaces, Zod validation at all boundaries, 910 tests across 77 test files.
+**Strict TypeScript** -- `strict: true`, no `any`, `readonly` interfaces, Zod validation at all boundaries, 970 tests across 79 test files.
 
 ## Documentation