Skip to main content

EM10 Translation Validation & Deploy Plan

For Claude: REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.

Goal: Validate Japanese and Russian translations for EliteMobs 10 content updates, build, test with Puppeteer, and push to upstream.

Architecture: Team-based parallel validation of ja/ru translations against English source, followed by sequential build → test → commit → push pipeline.

Tech Stack: Docusaurus 3.8.1, Puppeteer, Git

Scope​

English Source Changes (38 modified + 3 new)​

  • 38 modified files in docs/EliteMobs/
  • 3 new files: gambling_system.md, skill_bonuses.md, skill_system.md

Japanese (ja) — 22 files​

  • 19 modified files
  • 3 new files: gambling_system.md, skill_bonuses.md, skill_system.md

Russian (ru) — 20 files (+ 2 junk test files)​

  • 15 modified files
  • 3 new files: gambling_system.md, skill_bonuses.md, skill_system.md
  • 2 JUNK files to exclude: elitescript_relative_vectors_test.md, test_cyrillic.md

Other junk files to NOT commit​

  • .idea/material_theme_project_new.xml
  • docs/plans/ (this plan)
  • german-validation-report.md
  • i18n/fr/.../test_base64.md
  • i18n/fr/.../test_python.md

Task 1: Validate Japanese Translations (PARALLEL with Task 2)​

Agent: ja-validator

Files to check: All 22 ja files vs their English counterparts

Validation criteria:

  1. File exists and is non-empty
  2. Content is actually in Japanese (contains Japanese characters, not English copy-paste)
  3. Frontmatter (sidebar_label, sidebar_position) matches English structure
  4. Markdown structure (headings, tables, code blocks) preserved
  5. YAML code blocks left untranslated (config keys stay English)
  6. Links/paths not broken
  7. No import statements changed (React components like import XPProgressionChart stay as-is)

Spot-check: For 3-5 files, compare key sections between en and ja to verify translation quality.

Task 2: Validate Russian Translations (PARALLEL with Task 1)​

Agent: ru-validator

Files to check: All 20 ru files (excluding 2 test files) vs their English counterparts

Same validation criteria as Task 1, but for Russian (Cyrillic characters).

Flag: elitescript_relative_vectors_test.md and test_cyrillic.md are test files — confirm they should be excluded from commit.

Task 3: Build Docusaurus Site (after Tasks 1-2)​

Step 1: Run npm run build in the project root Step 2: Verify build succeeds with no errors Step 3: Note any warnings related to ja/ru content

Run: cd nightbreak-wiki && npm run build Expected: Build completes successfully

Task 4: Puppeteer Validation (after Task 3)​

Step 1: Run Puppeteer tests against built site Step 2: Check for rendering issues on ja/ru pages

Run: node puppeteer-test.js or node validate-translations.js Expected: No critical failures

Task 5: Commit & Push (after Task 4)​

Step 1: Stage all relevant files (excluding junk) Step 2: Commit with descriptive message Step 3: Push to upstream

Files to EXCLUDE from staging:

  • .idea/material_theme_project_new.xml
  • docs/plans/
  • german-validation-report.md
  • i18n/fr/.../test_base64.md
  • i18n/fr/.../test_python.md
  • i18n/ru/.../elitescript_relative_vectors_test.md
  • i18n/ru/.../test_cyrillic.md