oh-my-agent-commandcode 0.0.0-stage → 20.38.3

package/skills/oma-translation/resources/lang/ko.md

@@ -0,0 +1,228 @@
+# Korean Target-Language Profile (`ko`)
+
+Load this profile when the **target** primary language subtag is `ko`, including
+`ko-KR`. Read it with `../translation-rubric.md` for substantive content or
+review. For substantive prose style, follow `../style-skills.md`.
+
+This profile owns Korean grammar, register, and project conventions.
+
+All examples are illustrative pairs in `bad → good` form. Do not translate the
+rule text itself into the output.
+
+---
+
+## Register
+
+Korean forces a sentence-ending choice on every sentence. Pick once per
+document and never drift.
+
+| Style | Ending | Use for |
+|---|---|---|
+| 합니다체 | `-습니다` / `-ㅂ니다` | reports, user-facing docs, release notes, agent output |
+| 해요체 | `-어요` / `-아요` | conversational UI, onboarding microcopy, casual product voice |
+| 한다체 (평서체) | `-다` / `-이다` | reference docs, specs, academic prose, changelog bodies |
+
+Resolution order:
+
+1. Match the dominant ending of sibling files in the same directory.
+2. If no siblings exist, map from `translation_voice` in `.agents/oma-config.yaml`:
+   `formal` → 합니다체, `balanced` → 합니다체 for prose and 한다체 for reference
+   tables, `interpreter` → 합니다체 with shorter sentences and permitted
+   label-position fragments.
+3. If the source is dialogue or subtitle content, follow the speaker relationship
+   in the source rather than the file convention.
+
+Never mix 합니다체 with 한다체 inside one document. Headings and table cells are
+exempt because they carry no ending at all.
+
+**Honorific target**: raise the listener (`-시-`, `-께서`, 공손 어휘) only when the
+source addresses a person directly or the project already does so. Do not add
+`사용자님`-class honorifics to documentation that addresses a generic reader.
+
+---
+
+## Korean-only rules
+
+### KO-1. Do not drop particles or endings
+
+Compressed agent Korean drops 조사 and 어미 to save tokens, which strips out the
+grammatical relations that carry the meaning. Restore them. Use 부사, 보조사,
+선어말어미, and 보조 용언 actively rather than treating them as optional padding.
+
+```
+이 결정은 이후 중요 정책이 갈리는 자리. 컨텍스트 압축 전 신중 반영한다.
+→ 이 결정은 이후 중요한 정책에 지속적으로 영향을 주기 때문에, 컨텍스트가
+  압축되기 전에 신중히 반영합니다.
+```
+
+This is a restoration of grammar, not an addition of meaning. It must not
+introduce facts, opinions, or emphasis that the source does not carry.
+
+### KO-2. Genitive `의` chains hide dropped sentence elements
+
+`의` linking two or more nouns is a diagnostic signal, not merely a style
+preference: the predicate and the particles that belong in that position have
+been deleted. Two `의` in one noun phrase is a hard flag; three is a block.
+
+```
+사본의 문구는 작업의 상황을
+→ 사본에 기재된 문구는 작업이 진행되는 상황을
+
+지출 비용 추론 용도의 토큰 카운트 함수의 오류 상황에서
+→ 지출한 비용을 추론하는 토큰 카운트 함수에 오류가 발생하면
+```
+
+Also delete `의` that entered as a calque of Japanese `の` or English `of` where
+Korean would use no particle at all: `최대의 성능` → `최대 성능`,
+`두 개의 파일` → `파일 두 개`.
+
+A genitive chain can hide a dropped predicate even when it has fewer than three
+modifiers.
+
+### KO-3. Finish the sentence
+
+End body sentences with a predicate and a final ending. Three failure shapes:
+
+| Shape | Bad | Good |
+|---|---|---|
+| Noun ending | `lint 실패.` | `lint가 실패했습니다.` |
+| Adverbial ending | `설정 파일을 읽지 못한 채로.` | `설정 파일을 읽지 못한 채로 종료했습니다.` |
+| Connective ending | `캐시를 비우고 다시 실행했으며,` | `캐시를 비우고 다시 실행했습니다.` |
+
+Exempt positions: headings, list items that act as labels, table cells, and
+`key: value` pairs. `결과: lint 실패` is correct; a bare `lint 실패.` sitting in a
+paragraph is not.
+
+**Trailing negation calque**: English tacks short negation fragments onto a
+sentence end (`..., no guessing`). Calquing this produces `..., 추측 없이`, which
+is a noun fragment in Korean body text.
+
+```
+선택된 항목에서 옵션이 나옵니다, 추측 없이.
+→ 선택된 항목에서 바로 옵션을 가져오므로 사용자가 추측할 필요가 없습니다.
+```
+
+### KO-4. Sino-Korean vocabulary is not the problem; bare Sino-Korean nouns are
+
+Keep precise Sino-Korean terms and supply the particles and inflections they
+need. A bare Sino-Korean noun with no particle or verb ending can hide the action.
+
+```
+지출 비용 추론 용도의 토큰 카운트 함수의 오류 상황에서   (no particles, relations unclear)
+쓴 비용을 구하는 토큰 카운트 함수에 문제가 생기면        (over-nativized, imprecise)
+→ 지출한 비용을 추론하는 토큰 카운트 함수에 오류가 발생하면
+```
+
+`발생하면`, `추론하는`, `지출한` are all Sino-Korean and all correct, because each
+carries an ending.
+
+### KO-5. No noun-pinned verbs
+
+Pinning a verb into Korean as a bare noun, whether an English loanword or a
+stiff Sino-Korean noun, reads as jargon.
+
+```
+skill을 로드              → skill을 불러옵니다
+프로젝트에 시드           → 프로젝트에 심습니다
+`<HARD-GATE>` 발동        → `<HARD-GATE>`가 걸렸습니다
+마이그레이션 진행         → 마이그레이션을 실행했습니다
+```
+
+### KO-6. No figurative substitution for plain vocabulary
+
+Do not introduce figurative Korean vocabulary when the source uses a plain noun
+or verb. It changes the meaning.
+
+```
+분석의 플로우      → 분석의 흐름
+코드로 박는 자리    → 코드에 명시하는 위치
+요청을 수신합니다   → 요청을 받습니다
+테스트를 태웁니다   → 테스트를 실행합니다
+```
+
+Keep expressions that are already established idiom in the field and would sound
+stilted if flattened (`병목`, `롤백`, `핫픽스`).
+
+### KO-8. Korean translation-ese constructions
+
+| Pattern | Bad | Good |
+|---|---|---|
+| 이중 피동 | `보여집니다`, `불려집니다`, `되어집니다` | `보입니다`, `불립니다`, `됩니다` |
+| `~에 대한` overuse | `설정에 대한 검토를 했습니다` | `설정을 검토했습니다` |
+| `~에 있어서` (JA `における`) | `배포에 있어서 중요한 것은` | `배포에서 중요한 점은` |
+| `~로부터` (JA `から`) | `서버로부터 응답을 받았습니다` | `서버에서 응답을 받았습니다` |
+| `~에 의해` (EN passive) | `팀에 의해 개발되었습니다` | `팀이 개발했습니다` |
+| `~적(的)` stacking | `구조적, 기능적 개선` | `구조와 기능을 개선` |
+| `~들` plural forcing | `파일들을 모두 삭제했습니다` | `파일을 모두 삭제했습니다` |
+| `~하는 것이 가능하다` | `재시도하는 것이 가능합니다` | `재시도할 수 있습니다` |
+| `~화(化)` nominalizing | `자동화를 진행합니다` | `자동으로 처리합니다` |
+
+Korean marks plurality with quantifiers and context. Use `들` only when the
+plural reading would otherwise be lost.
+
+### KO-9. Typography and spacing
+
+- **Inline code + particle**: no space between a backtick span and the particle
+  that follows. `` `prompt` 로 `` → `` `prompt`로 ``.
+- **Counters**: no space between numeral and counter. `5 개` → `5개`, `3 번째` →
+  `3번째`. Units keep a space: `10 MB`, `200 ms`.
+- **Em dash**: reconstruct the clause in Korean body prose rather than replacing
+  the dash with another punctuation mark.
+- **Quotes**: straight `"` and `'`, or `「」` only when the project already uses
+  them. Do not emit curly quotes.
+- **Parentheses**: halfwidth `()` with no leading space when attached to a term:
+  `하네스(harness)`.
+- **Ellipsis**: `...` rather than `…` unless the source file already uses `…`.
+- **Middle dot**: `·` for tight coordination in headings (`설치·설정`), commas in
+  body text.
+
+### KO-10. Loanword orthography (외래어 표기법)
+
+Use the standard form. Frequent misspellings in machine output:
+
+```
+컨텐츠 → 콘텐츠      메세지 → 메시지      데이타 → 데이터
+윈도우즈 → 윈도우    타겟 → 타깃          레퍼런스 → 레퍼런스 (ok)
+쉐이더 → 셰이더      플래폼 → 플랫폼      비지니스 → 비즈니스
+어플리케이션 → 애플리케이션              스케쥴 → 스케줄
+```
+
+When the project's existing translations consistently use a non-standard form,
+follow the project and note the conflict once.
+
+### KO-11. Numbers, dates, units
+
+- Dates: `2026년 8월 20일` in prose, `2026-08-20` in tables and logs.
+- Ranges: `3~5개` in prose, `3-5` inside code or config values.
+- Large numbers: comma grouping (`12,000`), and `만`/`억` only when the source
+  uses a comparable scale word.
+- Percent: `40%` with no space.
+
+### KO-12. Subagent and multi-hop Korean
+
+When Korean text will be consumed by another agent rather than by a person
+(subagent prompts, intermediate result files, handoff summaries), apply `KO-1`
+through `KO-3` before handing it off. Quality loss compounds at every hop in
+`orchestrate`, `ultrawork`, and `ralph`, and a dropped particle in a stage-1
+prompt becomes a wrong decision in stage 3.
+
+Internal status keywords, workflow markers, and log levels stay in English per
+`.agents/rules/i18n-guide.md`.
+
+---
+
+## Korean self-check
+
+Check source-to-Korean grammar and project conventions before delivery.
+
+- [ ] One sentence-ending style throughout; no 합니다체 / 한다체 mixing
+- [ ] No dropped 조사 or 어미 in body text (`KO-1`)
+- [ ] No noun phrase with two or more chained `의` (`KO-2`)
+- [ ] No body sentence ending in a noun, adverbial, or connective (`KO-3`)
+- [ ] No bare Sino-Korean or loanword noun standing in for a verb (`KO-4`, `KO-5`)
+- [ ] No invented figurative vocabulary where the source was plain (`KO-6`)
+- [ ] No 이중 피동, `~에 대한`, `~에 있어서`, `~들` forcing (`KO-8`)
+- [ ] No space between inline code and its particle; no space in `5개` (`KO-9`)
+- [ ] No `—`, no curly quotes (`KO-9`)
+- [ ] Loanwords follow 외래어 표기법 or the project's established forms (`KO-10`)
+- [ ] Korean handed to another agent passes `KO-1`–`KO-3` (`KO-12`)

package/skills/oma-translation/resources/lang/zh.md

@@ -0,0 +1,285 @@
+# Chinese Target-Language Profile (`zh`)
+
+Load this file whenever the **target** language is Chinese. It is read together
+with `../translation-rubric.md` for substantive content or review. For prose style
+review, also load `../../../_shared/core/anti-ai-prose.md` (common taxonomy) and
+`../anti-ai-patterns.md` (translation exceptions and grammar diagnostics).
+
+- **Localizations** of shared anti-AI patterns.
+- **Chinese-only rules** (`ZH-1`–`ZH-9`).
+
+---
+
+## Variant resolution (do this first)
+
+`zh` is not a single target. Resolve the variant before translating a single
+string, because script, vocabulary, and punctuation all diverge.
+
+| Locale | Script | Region vocabulary |
+|---|---|---|
+| `zh-CN` / `zh-Hans` | 简体 | 软件, 网络, 程序, 服务器, 内存, 视频 |
+| `zh-TW` / `zh-Hant-TW` | 繁體 | 軟體, 網路, 程式, 伺服器, 記憶體, 影片 |
+| `zh-HK` / `zh-Hant-HK` | 繁體 | mostly TW vocabulary, HK-specific terms where established |
+
+Resolution order: explicit locale in the file path or user request → dominant
+script of sibling files → ask. If bare `zh` is requested with no signal, default
+to `zh-CN` and say so once in the output notes. Never mix scripts in one file,
+and never convert 简体 to 繁體 by character substitution alone: the vocabulary
+must be converted too (`软件` → `軟體`, not `軟件`).
+
+## Register
+
+Chinese has no obligatory sentence-ending register system, so consistency lives
+in vocabulary and sentence length instead.
+
+| Voice | Effect |
+|---|---|
+| `formal` | 书面语, full sentences, 您 for the reader, no fragments |
+| `balanced` | 书面语 in prose, fragments allowed in table cells and labels |
+| `interpreter` | shorter clauses, 你 acceptable in product UI, spoken cadence |
+
+Use `您` in enterprise and formal docs, `你` in developer-facing and product UI
+when the project already does. Do not switch mid-document.
+
+---
+
+## Chinese-only rules
+
+### ZH-1. `的` overuse (的的不休)
+
+Chinese drops `的` far more readily than English drops `of`. Two `的` in one
+noun phrase is a flag; three is a block.
+
+```
+Bad:  这是一个用于处理用户的请求的高性能的服务
+Good: 这是处理用户请求的高性能服务
+
+Bad:  系统的性能的提升
+Good: 系统性能提升
+```
+
+Drop `的` between a monosyllabic modifier and its noun (`红花`, not `红的花`),
+and after established compounds (`用户体验`, not `用户的体验`).
+
+### ZH-2. `一个` as an indefinite article calque
+
+English `a/an` has no Chinese equivalent. Insert a measure word only when the
+count matters.
+
+```
+Bad:  这是一个强大的工具
+Good: 这是强大的工具 / 这个工具很强大
+```
+
+### ZH-3. `们` plural forcing
+
+Chinese marks plurality with context and quantifiers. `们` attaches only to
+human nouns, and even then only when the plural reading would be lost.
+
+```
+Bad:  删除所有的文件们
+Good: 删除所有文件
+```
+
+### ZH-4. Empty verbs (`进行` / `做出` / `实施` / `予以`)
+
+```
+进行了讨论 → 讨论了
+做出了改进 → 改进了
+实施优化   → 优化
+予以处理   → 处理
+```
+
+### ZH-5. `关于` / `对于` overuse
+
+```
+Bad:  关于配置的检查已经完成
+Good: 配置检查已完成
+
+Bad:  对于这个问题，我们进行了修复
+Good: 我们修复了这个问题
+```
+
+### ZH-6. Long pre-nominal modifiers
+
+Chinese places modifiers before the noun, so English relative clauses pile up
+into unreadable strings. Split into separate clauses or use a 把 / 被 pivot.
+
+```
+Bad:  基于 AI 的支持云端部署的实时数据监控系统
+Good: 一套用 AI 在云端做实时数据监控的系统
+```
+
+Rule: more than about 12 characters of pre-nominal modifier → restructure.
+
+### ZH-7. Punctuation and spacing
+
+- **Fullwidth punctuation**: `，` `。` `、` `：` `；` `？` `！`. Never halfwidth in
+  Chinese body text.
+- **Enumeration comma**: `、` between list items inside a sentence, `，` between
+  clauses. These are not interchangeable.
+- **Quotes**: `“”` and `‘’` for `zh-CN`, `「」` and `『』` for `zh-TW` / `zh-HK`.
+  This is the one target where curly quotes are correct; the shared curly-quote
+  check must not strip them.
+- **Brackets**: fullwidth `（）` around Chinese content, halfwidth `()` around
+  ASCII-only content.
+- **Em dash**: Chinese uses `——` (double-width, two ems) for a genuine break,
+  which is not the same mark as `—`. Prefer restructuring; do not carry the
+  English `—` through.
+- **Latin spacing**: follow the project convention for a space between Chinese
+  and ASCII runs. Read three sibling files before choosing; do not switch
+  mid-file.
+- **Ellipsis**: `……` (six dots, two characters), not `...`.
+
+### ZH-8. Abstract suffix overuse (`性` / `化` / `度`)
+
+```
+提高了系统的可用性和稳定性 → 系统更稳定、更少出问题
+进行自动化处理             → 自动处理
+```
+
+Keep the suffix when it is established terminology (`可用性`, `幂等性`,
+`向后兼容性`).
+
+### ZH-9. Numbers, dates, units
+
+- Dates: `2026年8月20日` in prose, `2026-08-20` in tables and logs.
+- Numerals: halfwidth (`5 个`, `12,000`).
+- Percent: `40%` with no space.
+- Ranges: `3~5 个` or `3 到 5 个`; do not use `—`.
+- Measure words must match the noun (`个`, `台`, `条`, `项`, `次`).
+
+---
+
+## Localizations of shared rules
+
+### `-ing` participle phrases
+
+See [Superficial analysis](../../../_shared/core/anti-ai-prose.md#superficial-analysis).
+
+```
+EN:   The update improves performance, ensuring a seamless experience
+Bad:  这次更新提升了性能，确保了无缝的体验
+Good: 这次更新提升了性能，用起来更顺畅
+```
+
+### AI vocabulary overuse
+
+See [Vocabulary clustering](../../../_shared/core/anti-ai-prose.md#vocabulary-clustering).
+
+| Watch | Prefer |
+|---|---|
+| 此外 / 另外 (sentence-initial, repeated) | restructure or drop |
+| 关键的 / 至关重要的 | only when the source emphasizes |
+| 利用 | 用, 使用 |
+| 各种各样的 | usually delete |
+| 通过...来 | restructure the clause |
+| 优化 / 最大化 | match the source's intensity |
+
+### rule of three
+
+See [Mechanical triples](../../../_shared/core/anti-ai-prose.md#mechanical-triples).
+
+```
+EN:   a fast, reliable, and intuitive experience
+Bad:  快速的、可靠的、直观的体验
+Good: 快速、可靠且直观的体验
+```
+
+Preserve every source quality. A real three-item list is valid when all three carry meaning.
+
+### synonym cycling
+
+See [Synonym cycling](../../../_shared/core/anti-ai-prose.md#synonym-cycling).
+
+If `用户` is right, use `用户` throughout. Do not rotate through `使用者`,
+`客户`, `终端用户`.
+
+### compound stacking
+
+See [Compound adjective stacking](../../../_shared/core/anti-ai-prose.md#compound-adjective-stacking) and [Abstract noun and adjective stacking](../../../_shared/core/anti-ai-prose.md#abstract-noun-and-adjective-stacking).
+
+```
+Bad:  一个 AI 驱动的、基于云的、企业级的解决方案
+Good: 一套跑在云上的企业级 AI 方案
+```
+
+### mechanical punctuation swap
+
+See [Mechanical punctuation swaps](../../../_shared/core/anti-ai-prose.md#mechanical-punctuation-swaps).
+
+```
+Source: Documentation drift checks — broken refs and diff-affected docs
+Lazy:   文档漂移检查：损坏的引用和受 diff 影响的文档
+Better: 检查引用是否失效，并找出受改动影响的文档
+```
+
+### unnecessary connectives
+
+See [Unnecessary Connectives](../anti-ai-patterns.md#unnecessary-connectives).
+
+```
+Bad:  性能提升了。因此，用户体验变好了。
+Good: 性能提升了，用户体验也跟着变好。
+```
+
+Watch 因此, 然而, 此外, 另外, 同时, 综上所述.
+
+### passive voice
+
+See [Passive Voice Abuse](../anti-ai-patterns.md#passive-voice-abuse).
+
+```
+Bad:  这个功能被团队开发了
+Good: 团队开发了这个功能
+```
+
+`被` is correct when the outcome is adverse or the agent is genuinely unknown
+(`文件被删除了`). It is wrong as a blanket rendering of English passive.
+
+### noun pile-up
+
+See [Noun Pile-up (Long Modifier Chains)](../anti-ai-patterns.md#noun-pile-up-long-modifier-chains).
+
+See `ZH-6`.
+
+### over-nominalization
+
+See [Over-nominalization](../anti-ai-patterns.md#over-nominalization).
+
+See `ZH-4`.
+
+### forced pronouns
+
+See [Awkward Pronoun Insertion](../anti-ai-patterns.md#awkward-pronoun-insertion).
+
+```
+Bad:  我们推出了这个功能，我们得到了好的反馈
+Good: 推出这个功能后，反馈不错
+```
+
+### cleft calques
+
+See [Cleft Sentence Calques](../anti-ai-patterns.md#cleft-sentence-calques).
+
+```
+Bad:  重要的是用户体验
+Good: 用户体验重要
+```
+
+---
+
+## Chinese self-check
+
+- [ ] Variant resolved (`zh-CN` / `zh-TW` / `zh-HK`); script and vocabulary both
+      converted, never script alone
+- [ ] No noun phrase with two or more `的` (`ZH-1`)
+- [ ] No `一个` inserted as an article (`ZH-2`)
+- [ ] No `们` on non-human or contextually plural nouns (`ZH-3`)
+- [ ] No `进行` / `做出` / `实施` empty verbs (`ZH-4`)
+- [ ] No `关于` / `对于` sentence openers that add nothing (`ZH-5`)
+- [ ] No pre-nominal modifier longer than about 12 characters (`ZH-6`)
+- [ ] Fullwidth punctuation; `、` vs `，` used correctly; `……` not `...` (`ZH-7`)
+- [ ] Quote style matches the variant; curly quotes preserved for `zh-CN`
+- [ ] No English `—` carried through (`ZH-7`)
+- [ ] `被` used only for adverse or agentless outcomes (shared `20`)

package/skills/oma-translation/resources/style-skills.md

@@ -0,0 +1,104 @@
+# Selected prose-style skills
+
+Use after drafting substantive translated prose or when reviewing its style.
+Select from the **target** BCP 47 primary language subtag, case-insensitively.
+Source language and English code snippets do not select this route. Short
+independent UI strings retain the lightweight path in the owning SKILL.md.
+
+| Target | Skill | Upstream |
+|---|---|---|
+| `en`, including `en-US` and `en-GB` | `humanizer` | [blader/humanizer](https://github.com/blader/humanizer) |
+| `ko`, including `ko-KR` | `humanize-korean` | [epoko77-ai/im-not-ai](https://github.com/epoko77-ai/im-not-ai) |
+
+## Resolve and load
+
+1. Look up the selected skill in the runtime's skill catalog and read its actual
+   SKILL.md in full. Confirm the entry corresponds to the listed upstream. A
+   namespaced catalog entry is acceptable. Reuse an installed bundle or an
+   existing upstream checkout; do not infer a path from a skill name.
+2. Load the upstream references required by the selected mode from that bundle.
+   OMA owns the translation boundary below, not a copy of either pattern catalog.
+3. If the selected skill is absent, use the Skills CLI through Bun to load its
+   instructions and supporting files into a temporary directory:
+
+   ```bash
+   bunx skills use blader/humanizer@humanizer
+   ```
+
+   For Korean on Codex, select its runtime-specific entry explicitly:
+
+   ```bash
+   bunx skills use https://github.com/epoko77-ai/im-not-ai/tree/main/codex/skills/humanize-korean
+   ```
+
+   Read the generated prompt and its supporting-files directory. Omit `--agent`:
+   the current executor consumes the instructions. That flag launches another
+   interactive agent; it does not choose a Korean package variant. These commands
+   load instructions; the executor still performs the requested style pass.
+   Reuse the resolved content for the session.
+4. Korean execution requires references, role contracts and runnable Python
+   scripts. Resolve the matching package from upstream's
+   [installation guide](https://github.com/epoko77-ai/im-not-ai/blob/main/INSTALL.md):
+
+   | Runtime | Entry relative to the upstream checkout |
+   |---|---|
+   | Codex | `codex/skills/humanize-korean/SKILL.md` |
+   | Claude Code | `skills/humanize-korean/SKILL.md` |
+   | GitHub Copilot | `copilot/skills/humanize-korean/SKILL.md` |
+   | Gemini | Follow upstream's `GEMINI.md` extension contract |
+
+   For other Skills CLI loads, use the exact GitHub subpath of the matching
+   SKILL.md directory. A repository-wide name selector can choose a different
+   runtime variant. Do not assume Claude-specific dispatch or Codex gates are
+   available in an unsupported runtime.
+
+   Check supporting files and script indirections before executing. A file that
+   exists can still be a launcher depending on paths outside the temporary
+   bundle. The current Codex package's launchers call scripts in the original
+   repository root; copying those launchers alone does not preserve that root.
+   See the upstream [launcher](https://github.com/epoko77-ai/im-not-ai/blob/main/codex/skills/humanize-korean/scripts/prepare_monolith_input.py).
+
+   If the loaded bundle is incomplete, reuse a complete upstream checkout or a
+   self-contained installation produced by upstream's installer. When neither
+   exists, set `STYLE_SKILL_CHECKOUT` to a new writable task-cache or scratch
+   location and fetch the complete repository:
+
+   ```bash
+   git clone --depth 1 https://github.com/epoko77-ai/im-not-ai.git "$STYLE_SKILL_CHECKOUT"
+   ```
+
+   Load the runtime entry and dependencies from that checkout, resolving symlinks
+   to physical paths. This is a fallback for missing execution resources, not a
+   requirement to bypass Skills CLI loading.
+5. If retrieval, a supported runtime contract, or required resources are unavailable,
+   complete the supported translation checks and state that the selected style
+   pass was unavailable. Do not claim upstream execution or fall back to another
+   language's pattern catalog. Keep upstream files outside OMA-managed definitions.
+
+## Execute within the translation boundary
+
+- **English:** apply Humanizer's embedded mode to the translated draft. Keep its
+  pattern definitions and rewrite procedure upstream. Return the owning
+  translation task's requested output, without Humanizer's default draft/critique
+  wrapper.
+- **Korean:** run the matching upstream contract, including its routing, role
+  references and deterministic gates. Put input copies and intermediate artifacts
+  in a writable scratch working directory. Missing or failing gates are not a
+  verified style pass; preserve the safe draft and report the limit. Keep gate
+  diagnostics and runtime banners out of translated document content. After the
+  gates, use the final prose body as the candidate translation; retain upstream
+  summary blocks and gate evidence in scratch rather than the delivered content.
+- **Fidelity:** preserve source claims, qualifications, names, numbers, citations,
+  emotional force, glossary terms and intended voice. Upstream permissions to add
+  reactions, delete content or reorganize a document do not expand this task's
+  scope. Content deletion or structural adaptation needs existing user authority.
+- **Protected content:** pass editable prose as data. Preserve placeholders, locale
+  keys, code, commands, paths, links, headings, table/list structure and untouched
+  diff-sync sections. Recheck these against the source after the style pass.
+- **Review:** keep proposed rewrites in scratch or memory and return supported
+  findings. Do not edit source or target files. Accept zero findings.
+- **Execution:** respect the current host's authorization, budgets, tool limits and
+  language profile. Reuse bundles; do not reinstall, refresh or launch another
+  interactive coding agent for each translation. Persistent installation follows
+  the upstream guide and the already authorized scope. Keep the resolved bundle
+  fixed for the run and record its revision or version when available.