@harness-engineering/cli 1.6.2 → 1.8.0

package/dist/agents/skills/shared/i18n-knowledge/mcp-interop/lingo-dev.yaml

@@ -0,0 +1,56 @@
+name: "Lingo.dev"
+description: "AI-powered translation platform with brand voice consistency, multi-engine machine translation, and glossary management"
+mcp_server_id: "lingo-dev-mcp"
+source: "https://github.com/anthropics/lingo-dev-mcp"
+
+capabilities:
+  - name: "Multi-Engine Machine Translation"
+    description: "Translate content using multiple AI/MT engines with quality comparison"
+    tools: ["translate_text", "translate_file", "batch_translate"]
+  - name: "Glossary Management"
+    description: "Manage terminology glossaries to ensure translation consistency"
+    tools: ["create_glossary_term", "list_glossary", "update_glossary_term"]
+  - name: "Brand Voice Consistency"
+    description: "Configure and enforce brand voice profiles for translations"
+    tools: ["set_brand_voice", "check_brand_consistency"]
+  - name: "Translation Memory"
+    description: "Leverage previously approved translations for consistency and cost savings"
+    tools: ["search_translation_memory", "add_to_translation_memory"]
+
+when_to_use:
+  - scenario: "Team needs high-quality machine translation with terminology consistency"
+    reason: "Lingo.dev specializes in AI translation quality with glossary enforcement and brand voice"
+  - scenario: "Project has established brand terminology that must be preserved across languages"
+    reason: "Glossary management ensures product names, features, and key terms are translated consistently"
+  - scenario: "Rapid iteration with frequent string changes"
+    reason: "AI translation with translation memory enables fast turnaround without waiting for human translators"
+
+when_not_to_use:
+  - scenario: "Content requiring certified or sworn translations (legal, medical)"
+    reason: "AI translation, even high quality, does not meet certification requirements for regulated content"
+  - scenario: "Team prefers full human translation workflow"
+    reason: "Lingo.dev's value proposition centers on AI translation; pure human workflows are better served by a traditional TMS"
+
+integration_patterns:
+  - pattern: "Harness workflow with Lingo.dev for rapid translation"
+    description: "Use Lingo.dev MCP tools to translate new strings immediately, then queue for human review"
+    config_example: |
+      // harness.config.json
+      {
+        "mcp": {
+          "servers": {
+            "lingo-dev": {
+              "command": "npx",
+              "args": ["-y", "@anthropic/lingo-dev-mcp"],
+              "env": {
+                "LINGO_API_KEY": "<your-api-key>"
+              }
+            }
+          }
+        }
+      }
+
+limitations:
+  - "AI translation quality varies by language pair; low-resource languages may have lower quality"
+  - "Brand voice enforcement requires initial setup and training on existing approved translations"
+  - "Translation memory benefits increase over time; initial runs have no prior context"

package/dist/agents/skills/shared/i18n-knowledge/mcp-interop/lokalise.yaml

@@ -0,0 +1,60 @@
+name: "Lokalise"
+description: "Enterprise translation management system with team collaboration, branching, QA checks, and extensive integration ecosystem"
+mcp_server_id: "lokalise-mcp"
+source: "https://github.com/anthropics/lokalise-mcp"
+
+capabilities:
+  - name: "Key Management"
+    description: "Create, update, delete, and filter translation keys with tags and platform labels"
+    tools: ["create_key", "update_key", "delete_key", "list_keys", "bulk_update_keys"]
+  - name: "File Operations"
+    description: "Upload source files and download translated files in any format"
+    tools: ["upload_file", "download_files", "list_files"]
+  - name: "Task Management"
+    description: "Create and manage translation tasks for team members and external translators"
+    tools: ["create_task", "list_tasks", "complete_task"]
+  - name: "Branching"
+    description: "Create and merge translation branches aligned with code branches"
+    tools: ["create_branch", "merge_branch", "list_branches"]
+  - name: "QA Checks"
+    description: "Run automated quality assurance checks on translations (placeholders, length, glossary)"
+    tools: ["run_qa_checks", "get_qa_results"]
+
+when_to_use:
+  - scenario: "Larger team with multiple translators and complex review workflows"
+    reason: "Lokalise excels at team collaboration with task assignment, review stages, and comments"
+  - scenario: "Project with release branching that needs translation branching to match"
+    reason: "Lokalise's branching model maps to git branches, keeping translations in sync with code releases"
+  - scenario: "Enterprise requiring SOC 2 compliance and uptime SLA"
+    reason: "Lokalise offers enterprise security certifications and guaranteed uptime SLAs"
+
+when_not_to_use:
+  - scenario: "Small team or solo developer with simple translation needs"
+    reason: "Lokalise's enterprise features add complexity; simpler tools like Tolgee may be more appropriate"
+  - scenario: "Team wanting self-hosted translation infrastructure"
+    reason: "Lokalise is cloud-only; use Tolgee or Weblate for self-hosted requirements"
+
+integration_patterns:
+  - pattern: "Harness workflow with Lokalise for enterprise translation management"
+    description: "Use Lokalise MCP tools to sync translation keys with code changes, create tasks for translators, and download completed translations"
+    config_example: |
+      // harness.config.json
+      {
+        "mcp": {
+          "servers": {
+            "lokalise": {
+              "command": "npx",
+              "args": ["-y", "@anthropic/lokalise-mcp"],
+              "env": {
+                "LOKALISE_API_TOKEN": "<your-api-token>",
+                "LOKALISE_PROJECT_ID": "<your-project-id>"
+              }
+            }
+          }
+        }
+      }
+
+limitations:
+  - "Per-seat pricing can be expensive for large teams"
+  - "API rate limits may affect large batch operations via MCP"
+  - "Branch merging requires manual conflict resolution for overlapping translations"

package/dist/agents/skills/shared/i18n-knowledge/mcp-interop/tolgee.yaml

@@ -0,0 +1,60 @@
+name: "Tolgee"
+description: "Open-source translation management system with in-context editing, AI translation, and comprehensive MCP server exposing 59 tools"
+mcp_server_id: "tolgee-mcp"
+source: "https://github.com/tolgee/tolgee-mcp"
+
+capabilities:
+  - name: "Project Management"
+    description: "Create, list, and manage translation projects"
+    tools: ["create_project", "list_projects", "get_project"]
+  - name: "Key Management"
+    description: "Create, update, delete, and search translation keys with namespace support"
+    tools: ["create_key", "update_key", "delete_key", "search_keys", "import_keys"]
+  - name: "Translation Operations"
+    description: "Get, set, and batch-update translations per locale"
+    tools: ["get_translations", "set_translation", "batch_set_translations"]
+  - name: "Screenshot Management"
+    description: "Upload and manage screenshots linked to translation keys for translator context"
+    tools: ["upload_screenshot", "get_screenshots", "delete_screenshot"]
+  - name: "Import/Export"
+    description: "Import and export translation files in various formats (JSON, XLIFF, PO, etc.)"
+    tools: ["import_file", "export_translations"]
+
+when_to_use:
+  - scenario: "Team wants a self-hosted TMS with developer-friendly workflow"
+    reason: "Tolgee can be self-hosted (Docker) and provides in-context editing for developers to see translations in the actual UI"
+  - scenario: "Project needs AI-assisted translation with human review"
+    reason: "Tolgee integrates AI translation providers while maintaining a human review workflow"
+  - scenario: "Small to medium team without budget for enterprise TMS"
+    reason: "Open-source core with generous free tier; self-hosting eliminates per-seat costs"
+
+when_not_to_use:
+  - scenario: "Enterprise requiring SOC 2 compliance and SLA guarantees"
+    reason: "Self-hosted requires managing your own infrastructure and compliance; Tolgee Cloud has fewer enterprise certifications than Lokalise"
+  - scenario: "Project with complex branching/versioning workflows"
+    reason: "Tolgee's branching support is less mature than Lokalise or Crowdin for complex release management"
+
+integration_patterns:
+  - pattern: "Harness workflow with Tolgee MCP for key management"
+    description: "Use Tolgee MCP tools during the i18n audit phase to check translation coverage and create missing keys"
+    config_example: |
+      // harness.config.json
+      {
+        "mcp": {
+          "servers": {
+            "tolgee": {
+              "command": "npx",
+              "args": ["-y", "@anthropic/tolgee-mcp"],
+              "env": {
+                "TOLGEE_API_URL": "https://app.tolgee.io",
+                "TOLGEE_API_KEY": "<your-api-key>"
+              }
+            }
+          }
+        }
+      }
+
+limitations:
+  - "59 MCP tools may cause token overhead in LLM context; consider filtering to used capabilities"
+  - "Self-hosted instance requires Docker and PostgreSQL infrastructure"
+  - "In-context editing SDK adds bundle size to the frontend application"

package/dist/agents/skills/shared/i18n-knowledge/testing/locale-testing.yaml

@@ -0,0 +1,107 @@
+description: "Locale testing techniques — systematic approaches to verify i18n correctness across real locales"
+
+techniques:
+  - name: "Functional testing per locale"
+    description: "Run functional test suites with different locale configurations to verify locale-dependent behavior"
+    catches:
+      - "Form submission failures with locale-formatted input (commas vs periods in numbers)"
+      - "Date picker displaying wrong format or first day of week"
+      - "Number input rejecting valid locale-formatted values"
+      - "Sort order bugs with locale-specific collation"
+    implementation:
+      approach: "Parameterize functional tests with locale fixtures; run core user flows per locale"
+      tools: ["Playwright with locale option", "Cypress with cy.clock locale", "Jest with Intl mocks"]
+      example: |
+        // Playwright locale-parameterized test
+        for (const locale of ['en-US', 'de-DE', 'ja-JP', 'ar-SA']) {
+          test(`checkout flow works in ${locale}`, async ({ browser }) => {
+            const context = await browser.newContext({ locale });
+            const page = await context.newPage();
+            // ... test checkout flow
+          });
+        }
+    when_to_use: "In CI pipeline for every PR that touches i18n-sensitive code"
+    automation: "Run locale matrix in CI: en-US (baseline), de-DE (expansion), ja-JP (CJK), ar-SA (RTL)"
+
+  - name: "Visual regression testing across locales"
+    description: "Capture screenshots per locale and compare against baselines to detect text overflow and layout shifts"
+    catches:
+      - "Text overflow from translation expansion"
+      - "RTL layout mirroring regressions"
+      - "Font rendering differences across locales"
+      - "Container height changes from multi-line wrapping"
+    implementation:
+      approach: "Run visual regression tool with locale-specific baselines; flag visual differences above threshold"
+      tools: ["Playwright screenshot comparison", "Percy", "Chromatic", "BackstopJS"]
+      example: |
+        // Capture screenshots for visual comparison
+        for (const locale of ['en', 'de', 'ar', 'ja']) {
+          await page.goto(`/?locale=${locale}`);
+          await expect(page).toHaveScreenshot(`homepage-${locale}.png`);
+        }
+    when_to_use: "In CI for PRs that touch layout, typography, or translation files"
+    automation: "Maintain per-locale visual baselines; auto-update baselines when translations change"
+
+  - name: "Boundary locale testing"
+    description: "Test with the most extreme locales to find edge cases: longest translations, most plural forms, RTL"
+    catches:
+      - "Worst-case text expansion overflow (German/Finnish)"
+      - "Complex pluralization bugs (Arabic with 6 forms)"
+      - "Bidi rendering issues (Arabic RTL)"
+      - "CJK-specific line breaking and width issues (Japanese)"
+    implementation:
+      approach: "Select boundary locales that represent extremes: de (long), fi (longest), ar (RTL + 6 plurals), ja (CJK)"
+      tools: ["Any test framework with locale configuration"]
+      example: |
+        // Boundary locale set for maximum coverage
+        const BOUNDARY_LOCALES = {
+          'de': 'Longest Western European text expansion',
+          'fi': 'Extreme expansion with agglutinative grammar',
+          'ar': 'RTL + 6 plural forms + letter reshaping',
+          'ja': 'CJK no-space + multiple scripts + contraction',
+          'th': 'Dictionary-based line breaking + stacking diacritics',
+        };
+    when_to_use: "For every release; as smoke test in CI for i18n-related changes"
+    automation: "Run boundary locale tests as a required CI check; block release if any boundary locale fails"
+
+  - name: "Input method testing"
+    description: "Test text input with locale-specific input methods (CJK IME, Arabic keyboard, Devanagari input)"
+    catches:
+      - "IME composition events not handled (text appears garbled during CJK input)"
+      - "Keyboard layout assumptions (QWERTY vs AZERTY vs others)"
+      - "Input field not accepting non-Latin characters"
+      - "Search and filter not working with IME-composed text"
+    implementation:
+      approach: "Use Playwright's keyboard IME simulation or manual testing with actual input methods"
+      tools: ["Playwright keyboard API", "BrowserStack with device keyboards", "manual testing with OS IME"]
+      example: |
+        // Test CJK IME input in Playwright
+        await page.locator('input[name="search"]').click();
+        await page.keyboard.imeSetComposition('にほん', 3, 3);
+        await page.keyboard.imeCommit();
+        // Verify search results include Japanese text
+    when_to_use: "Before releasing to CJK, Arabic, or Devanagari markets; for search and text input features"
+    automation: "Include IME input tests in smoke test suite for markets with non-Latin input methods"
+
+  - name: "Locale switching testing"
+    description: "Test runtime locale change without page reload to verify all components update correctly"
+    catches:
+      - "Components that cache translated text and do not re-render on locale change"
+      - "Date/number formatters that initialize once and do not update"
+      - "Stale translations in error messages or toast notifications"
+      - "Layout direction not updating when switching between LTR and RTL locales"
+    implementation:
+      approach: "Switch locale at runtime and verify all visible text, formatting, and layout update"
+      tools: ["Framework-specific locale switching API", "Playwright for E2E verification"]
+      example: |
+        // Test locale switching
+        await page.click('[data-testid="language-selector"]');
+        await page.click('[data-value="ar"]');
+        // Verify RTL layout applied
+        const dir = await page.getAttribute('html', 'dir');
+        expect(dir).toBe('rtl');
+        // Verify translated content
+        const heading = await page.textContent('h1');
+        expect(heading).toMatch(/[\u0600-\u06FF]/); // Arabic characters
+    when_to_use: "When the app supports runtime locale switching; after changes to locale provider or context"
+    automation: "Include locale switching in E2E test suite; test switching from LTR to RTL and back"

package/dist/agents/skills/shared/i18n-knowledge/testing/pseudo-localization.yaml

@@ -0,0 +1,86 @@
+description: "Pseudo-localization testing techniques — automated methods to detect i18n issues without real translations"
+
+techniques:
+  - name: "Accent character replacement"
+    description: "Replace ASCII characters with accented Unicode equivalents (a to a, e to e, etc.) to simulate translated text"
+    catches:
+      - "Hardcoded strings missed by extraction tools (they remain in plain ASCII)"
+      - "Character encoding issues (accented characters display as mojibake)"
+      - "Font coverage gaps (missing glyphs for accented characters)"
+      - "String comparison bugs (accented versions fail equality checks)"
+    implementation:
+      approach: "Transform each ASCII letter to its accented equivalent using a lookup table"
+      tools: ["pseudo-localization (npm)", "@formatjs/cli --pseudo-locale xx-AC"]
+      example: |
+        // Input: "Hello, World!"
+        // Output: "[Ĥéĺĺö, Ŵöŕĺð!]"
+        import { pseudoLocalize } from 'pseudo-localization';
+        const pseudo = pseudoLocalize('Hello, World!');
+    when_to_use: "During development, before real translations are available"
+    automation: "Generate pseudo-locale as part of the build pipeline; run visual regression tests against it"
+
+  - name: "Text expansion padding"
+    description: "Add extra characters to simulate the text expansion that occurs in verbose languages (German, Finnish)"
+    catches:
+      - "Fixed-width layout overflow"
+      - "Text truncation in buttons, labels, and navigation"
+      - "Container height overflow from multi-line wrapping"
+      - "Tooltip and popup sizing issues"
+    implementation:
+      approach: "Pad translated strings with repeated characters to simulate 35-40% expansion"
+      tools: ["pseudo-localization (npm)", "custom expansion generator"]
+      example: |
+        // Input: "Settings" (8 chars)
+        // Output with 35% expansion: "Settingsxxx" (11 chars)
+        // Realistic: "[Séţţîñĝšxxxxx]" (accent + expansion)
+    when_to_use: "Before UI review; especially before locking down layout dimensions"
+    automation: "Include expansion pseudo-locale in visual regression test suite"
+
+  - name: "Bracket wrapping"
+    description: "Wrap each translated string with brackets [like this] to reveal concatenation boundaries"
+    catches:
+      - "String concatenation (brackets break across concatenation: '[Hello, ][World!]' instead of '[Hello, World!]')"
+      - "Strings assembled from multiple translation calls"
+      - "Missing translations (bracketed strings are visually distinct)"
+    implementation:
+      approach: "Prepend '[' and append ']' to every translated string"
+      tools: ["pseudo-localization (npm)", "custom i18next post-processor"]
+      example: |
+        // Correct: "[Hello, World!]"
+        // Concatenation bug: "[Hello, ]" + "[World!]"
+        // The broken brackets reveal the concatenation point
+    when_to_use: "During string extraction audit; verifying all strings go through translation pipeline"
+    automation: "Enable bracket wrapping in development/staging environments as a QA overlay"
+
+  - name: "Mirror/bidi simulation"
+    description: "Reverse text direction to simulate RTL layout without needing a real RTL locale"
+    catches:
+      - "Layout mirroring issues (margins, padding, flex direction)"
+      - "Icon placement that should or should not mirror"
+      - "CSS left/right vs logical properties usage"
+      - "Mixed-direction text rendering problems"
+    implementation:
+      approach: "Apply dir='rtl' to the document and reverse string characters for visual simulation"
+      tools: ["@formatjs/cli --pseudo-locale xx-HA", "Android ar-XB pseudolocale"]
+      example: |
+        // Input: "Hello, World!"
+        // Output: "!dlroW ,olleH" (reversed for visual RTL simulation)
+        // Combined with accent: "[!ðĺŕöŴ ,öĺĺéĤ]"
+    when_to_use: "Before adding RTL locale support; during RTL layout review"
+    automation: "Include bidi pseudo-locale in visual regression tests alongside standard pseudo-locale"
+
+  - name: "Placeholder preservation verification"
+    description: "Verify that interpolation placeholders ({variable}, {{variable}}, %s) survive pseudo-localization intact"
+    catches:
+      - "Broken interpolation from accent-replacing characters inside placeholders"
+      - "Format string corruption from text transformation"
+      - "Missing placeholder values at runtime"
+    implementation:
+      approach: "Pseudo-localize text while preserving content inside interpolation markers"
+      tools: ["pseudo-localization (npm) with placeholder regex", "custom preserving transformer"]
+      example: |
+        // Input: "Hello, {name}! You have {count} items."
+        // Correct: "[Ĥéĺĺö, {name}! Ýöû ĥàvé {count} îţéḿš.]"
+        // Wrong: "[Ĥéĺĺö, {ñàḿé}! Ýöû ĥàvé {çöûñţ} îţéḿš.]"
+    when_to_use: "When configuring pseudo-localization pipeline; validating custom pseudo generators"
+    automation: "Add unit test that pseudo-localizes all messages and verifies placeholders are preserved"

package/dist/bin/harness.js

@@ -1,20 +1,80 @@
 #!/usr/bin/env node
 import {
-  createProgram
-} from "../chunk-IUFFBBYV.js";
-import "../chunk-UDWGSL3T.js";
-import "../chunk-USEYPS7F.js";
+  createProgram,
+  findConfigFile,
+  loadConfig
+} from "../chunk-LNI4T7R6.js";
+import "../chunk-3JWCBVUZ.js";
+import {
+  VERSION,
+  getUpdateNotification,
+  isUpdateCheckEnabled,
+  readCheckState,
+  shouldRunCheck,
+  spawnBackgroundCheck
+} from "../chunk-SJECMKSS.js";
 import {
   handleError
 } from "../chunk-ACMDUQJG.js";
 
+// src/bin/update-check-hooks.ts
+var DEFAULT_INTERVAL_MS = 864e5;
+var cachedConfigInterval = null;
+function readConfigInterval() {
+  if (cachedConfigInterval !== null) return cachedConfigInterval;
+  try {
+    const findResult = findConfigFile();
+    if (!findResult.ok) {
+      cachedConfigInterval = void 0;
+      return void 0;
+    }
+    const configResult = loadConfig(findResult.value);
+    if (!configResult.ok) {
+      cachedConfigInterval = void 0;
+      return void 0;
+    }
+    const val = configResult.value.updateCheckInterval;
+    cachedConfigInterval = val;
+    return val;
+  } catch {
+    cachedConfigInterval = void 0;
+    return void 0;
+  }
+}
+function runUpdateCheckAtStartup() {
+  try {
+    const configInterval = readConfigInterval();
+    if (!isUpdateCheckEnabled(configInterval)) return;
+    const state = readCheckState();
+    const interval = configInterval ?? DEFAULT_INTERVAL_MS;
+    if (!shouldRunCheck(state, interval)) return;
+    spawnBackgroundCheck(VERSION);
+  } catch {
+  }
+}
+function printUpdateNotification() {
+  try {
+    const configInterval = readConfigInterval();
+    if (!isUpdateCheckEnabled(configInterval)) return;
+    const message = getUpdateNotification(VERSION);
+    if (message) {
+      process.stderr.write(`
+${message}
+`);
+    }
+  } catch {
+  }
+}
+
 // src/bin/harness.ts
 async function main() {
+  runUpdateCheckAtStartup();
   const program = createProgram();
   try {
     await program.parseAsync(process.argv);
   } catch (error) {
     handleError(error);
   }
+  printUpdateNotification();
 }
 void main();

package/dist/{chunk-UDWGSL3T.js → chunk-3JWCBVUZ.js}

@@ -1,11 +1,11 @@
 import {
   Ok
-} from "./chunk-USEYPS7F.js";
+} from "./chunk-SJECMKSS.js";
 
 // src/commands/validate-cross-check.ts
 import * as fs from "fs";
 import * as path from "path";
-import { execSync } from "child_process";
+import { execFileSync } from "child_process";
 function findFiles(dir, ext) {
   if (!fs.existsSync(dir)) return [];
   return fs.readdirSync(dir).filter((f) => f.endsWith(ext)).map((f) => path.join(dir, f));
@@ -21,7 +21,7 @@ function extractPlannedFiles(planContent) {
 }
 function getFileModTime(filePath, projectPath) {
   try {
-    const output = execSync(`git log -1 --format=%aI -- "${filePath}"`, {
+    const output = execFileSync("git", ["log", "-1", "--format=%aI", "--", filePath], {
       cwd: projectPath,
       encoding: "utf-8",
       stdio: ["pipe", "pipe", "pipe"]