Use in QudJP when auditing Japanese translation quality for contextual correctness, obvious mistranslations, strange or overly literal phrasing, natural Japanese polish, terminology consistency, glossary alignment, style consistency, or cross-file wording variance in localization XML/JSON/corpus text. Use for translation diff reviews, single suspicious translation candidates, and broad inventory sweeps; pair with qudjp-localization-triage when route ownership or generated text implementation strategy is part of the decision.
Use when working in QudJP on untranslated or incorrectly translated Caves of Qud runtime text, player.log triage, owner-route vs sink-route decisions, generated/composed names, HistorySpice text, dictionary leaf additions, or localization patches that need decompiled producer tracing and focused verification.
Use in QudJP when designing, reviewing, or extending C# static analysis over decompiled Caves of Qud source, including coverage maps, inventories, and semantic classification.
Use in QudJP when closing issue-493 style static producer owner queue entries from docs/static-producer-inventory.json and scripts/static_producer_closure.py, including auditing existing patches, proving all callsite shapes, adding focused tests, and registering covered owner families.
Use in QudJP when auditing or fixing English function-word residue in localized runtime text, including articles, possessive pronouns, prepositions, direction phrases, bracketed display states, and stale tests that incorrectly preserve those tokens.