@agent-native/core 0.77.3 → 0.77.4

package/corpus/core/docs/content/locales/ja-JP/workspace.md

@@ -13,7 +13,7 @@ description: "Claude ユーザーごとのコード レベルのカスタマイ
 
 ```an-diagram title="Claude-Code ワークスペースですが、SQL に保存されます" summary="同じカスタマイズ層 (命令、スキル、メモリ、エージェント、ジョブ、MCP) ですが、すべてのファイルが共有マルチテナント データベース内の行である点が異なります。"
 {
-  "html": "<div class=\"ws-map\"><div class=\"diagram-card cc\"><span class=\"diagram-pill warn\">Claude Code / Codex</span><small class=\"diagram-muted\">~/.claude/ on a local disk</small><div class=\"ws-files\"><span class=\"diagram-box\">CLAUDE.md</span><span class=\"diagram-box\">skills/</span><span class=\"diagram-box\">memory</span><span class=\"diagram-box\">mcp.json</span></div><small class=\"diagram-muted\">one codebase per developer</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-card an\"><span class=\"diagram-pill accent\">Agent-native workspace</span><small class=\"diagram-muted\">rows in one SQLデータベース</small><div class=\"ws-rows\"><span class=\"diagram-pill\">AGENTS.md</span><span class=\"diagram-pill\">skills/&hellip;</span><span class=\"diagram-pill\">memory/&hellip;</span><span class=\"diagram-pill\">mcp-servers/&hellip;</span></div><small class=\"diagram-muted\">one codebase, many users, scoped <code>u:&lt;email&gt;:&hellip;</code></small></div></div>",
+  "html": "<div class=\"ws-map\"><div class=\"diagram-card cc\"><span class=\"diagram-pill warn\">Claude Code / Codex</span><small class=\"diagram-muted\">~/.claude/ on a local disk</small><div class=\"ws-files\"><span class=\"diagram-box\">CLAUDE.md</span><span class=\"diagram-box\">skills/</span><span class=\"diagram-box\">memory</span><span class=\"diagram-box\">mcp.json</span></div><small class=\"diagram-muted\">one codebase per developer</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-card an\"><span class=\"diagram-pill accent\">Agent-nativeワークスペース</span><small class=\"diagram-muted\">rows in one SQLデータベース</small><div class=\"ws-rows\"><span class=\"diagram-pill\">AGENTS.md</span><span class=\"diagram-pill\">skills/&hellip;</span><span class=\"diagram-pill\">memory/&hellip;</span><span class=\"diagram-pill\">mcp-servers/&hellip;</span></div><small class=\"diagram-muted\">1つのコードベース、多数のユーザー、スコープ付き <code>u:&lt;email&gt;:&hellip;</code></small></div></div>",
   "css": ".ws-map{display:flex;align-items:center;gap:16px;flex-wrap:wrap}.ws-map .diagram-card{display:flex;flex-direction:column;gap:8px;padding:16px 18px;flex:1;min-width:220px}.ws-map .ws-files,.ws-map .ws-rows{display:flex;flex-wrap:wrap;gap:6px;margin:4px 0}.ws-map .diagram-arrow{font-size:24px}"
 }
 ```
@@ -53,7 +53,7 @@ description: "Claude ユーザーごとのコード レベルのカスタマイ
 
 ```an-diagram title="3 つのスコープ、1 つの有効なファイル" summary="ランタイムは、読み取り時にワークスペース、アプリ、および個人のスコープにわたる同じパスを解決します。最も具体的なスコープが優先されます。"
 {
-  "html": "<div class=\"ws-stack\"><div class=\"diagram-card\"><span class=\"diagram-pill\">Workspace</span><small class=\"diagram-muted\">company-wide defaults from Dispatch</small><code>context/brand.md</code></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&darr;</div><div class=\"diagram-card\"><span class=\"diagram-pill\">Organization / app</span><small class=\"diagram-muted\">team override for one app</small><code>context/brand.md</code></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&darr;</div><div class=\"diagram-card\"><span class=\"diagram-pill accent\">Personal</span><small class=\"diagram-muted\">per-user override &mdash; wins</small><code>context/brand.md</code></div><div class=\"diagram-arrow diagram-accent\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-box ok\">Effective <code>context/brand.md</code></div></div>",
+  "html": "<div class=\"ws-stack\"><div class=\"diagram-card\"><span class=\"diagram-pill\">Workspace</span><small class=\"diagram-muted\">Dispatchからの全社デフォルト</small><code>context/brand.md</code></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&darr;</div><div class=\"diagram-card\"><span class=\"diagram-pill\">組織 / アプリ</span><small class=\"diagram-muted\">team override for one app</small><code>context/brand.md</code></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&darr;</div><div class=\"diagram-card\"><span class=\"diagram-pill accent\">Personal</span><small class=\"diagram-muted\">per-user override &mdash; wins</small><code>context/brand.md</code></div><div class=\"diagram-arrow diagram-accent\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-box ok\">Effective <code>context/brand.md</code></div></div>",
   "css": ".ws-stack{display:flex;flex-direction:column;align-items:flex-start;gap:8px}.ws-stack .diagram-card{display:flex;flex-direction:column;gap:4px;padding:12px 16px;min-width:280px}.ws-stack .diagram-arrow{font-size:20px;align-self:center}.ws-stack code{font-size:.85em}.ws-stack .diagram-box{align-self:center;margin-top:4px}"
 }
 ```
@@ -74,7 +74,7 @@ description: "Claude ユーザーごとのコード レベルのカスタマイ
 3. 保存し、**チャット**に切り替えて、何でも質問してください。エージェントは新しいルールにすぐに従います。
 
 ```an-callout
-{ "tone": "info", "body": "No restart, no redeploy. `AGENTS.md` is read at the start of every turn, so an edit you save now changes the agent's behavior on the very next message." }
+{ "tone": "info", "body": "再起動や再デプロイは必要ありません。 `AGENTS.md` は各ターンの開始時に読み取られるため、編集内容を保存すると、次のメッセージでのエージェントの動作が変更されます。" }
 ```
 
 **次のステップは必要に応じて実行できます:**
@@ -96,10 +96,10 @@ description: "Claude ユーザーごとのコード レベルのカスタマイ
 新しいワークスペースに役立つスターター パック:
 
 ```text
-context/company.md              # what the company does, ICP, products, links
-context/brand.md                # voice, visual identity, spelling, forbidden usage
-context/messaging.md            # positioning, value props, proof points, objections
-instructions/guardrails.md      # compliance, escalation, and approval rules
+context/company.md              # 会社の内容、ICP、製品、リンク
+context/brand.md                # 声、ビジュアルアイデンティティ、スペル、禁止された使用法
+context/messaging.md            # ポジショニング、価値の裏付け、証拠のポイント、反論
+instructions/guardrails.md      # コンプライアンス、エスカレーション、承認ルール
 skills/company-voice/SKILL.md   # on-demand guidance for customer-facing writing
 agents/<slug>.md                # reusable custom agent profiles
 ```
@@ -119,7 +119,7 @@ workspace context/brand.md
 ```text
 <!-- context/brand.md -->
 
-# Brand
+# ブランド
 
 - Voice: direct, warm, concrete
 - Use: "workspace", "agent", "team"
@@ -183,18 +183,18 @@ instructions/legal-review-policy.md
 
 これらのサーフェス (`AGENTS.md`、skills、メモリ、カスタム エージェント、MCP サーバー) はすべて、同じ基盤となるリソース形状 (`path` + `scope` + `content`) であり、同じ方法でアドレス指定され、解決されます。
 
-```an-schema title="The workspace resource model" summary="One resource shape backs every workspace file. The runtime keys it by path and scope and resolves the effective value on read."
+```an-schema title="ワークスペースのリソースモデル" summary="1 つのリソース シェイプがすべてのワークスペース ファイルをサポートします。ランタイムはパスとスコープによってキーを設定し、読み取り時に有効な値を解決します。"
 {
   "entities": [
     {
       "id": "resource",
       "name": "workspace resource",
-      "note": "A single file in a user's workspace — instructions, skill, memory, agent, MCP config, or job.",
+      "note": "ユーザーのワークスペース内の 1 つのファイル - 指示、スキル、メモリ、エージェント、MCP 構成、またはジョブ。",
       "fields": [
         { "name": "path", "type": "string", "note": "Canonical path, e.g. AGENTS.md, skills/<slug>/SKILL.md" },
-        { "name": "scope", "type": "workspace | shared | personal", "note": "Which level this row lives at" },
+        { "name": "scope", "type": "workspace | shared | personal", "note": "この行が存在するレベル" },
         { "name": "owner", "type": "string", "nullable": true, "note": "u:<email> for personal scope" },
-        { "name": "content", "type": "text", "note": "Markdown / JSON / YAML body" }
+        { "name": "content", "type": "text", "note": "マークダウン / JSON / YAML ボディ" }
       ]
     }
   ]
@@ -221,12 +221,12 @@ Skills は、`skills/` パス (`skills/<name>/SKILL.md` が望ましい) にあ
 {
   "filename": "agents/design.md",
   "language": "markdown",
-  "code": "---\nname: Design\ndescription: >-\n  Reviews layouts, interaction patterns, and product UX decisions.\nmodel: inherit\ntools: inherit\ndelegate-default: false\n---\n\n# Role\n\nYou are a focused design agent.\n\n## Responsibilities\n\n- Review layouts and interaction flows\n- Suggest stronger visual direction\n- Be concise and opinionated",
+  "code": "---\nname: Design\ndescription: >-\n  Reviews layouts, interaction patterns, and product UX decisions.\nmodel: inherit\ntools: inherit\ndelegate-default: false\n---\n\n# 役割\n\nあなたは、重点を置いたデザイン エージェントです。\n\n## 責任\n\n- レイアウトとインタラクション フローを確認する\n- より強力な視覚的方向性を提案する\n- 簡潔かつ意見を述べてください。",
   "annotations": [
-    { "lines": "2", "label": "@mention handle", "note": "`name` is what appears in the `@`-dropdown and what the main agent delegates to." },
-    { "lines": "3-4", "label": "When to delegate", "note": "The `description` is what the orchestrator reads to decide this profile fits a task." },
-    { "lines": "5", "label": "Model", "note": "`inherit` reuses the main agent's model. Override only when the profile clearly needs a different one." },
-    { "lines": "6", "note": "`tools: inherit` for now — the field is reserved for future per-agent tool policies." }
+    { "lines": "2", "label": "@mention handle", "note": "`name` は、`@` ドロップダウンに表示されるもので、メイン エージェントが委任するものです。" },
+    { "lines": "3-4", "label": "いつ委任するか", "note": "`description` は、このプロファイルがタスクに適合するかどうかを判断するためにオーケストレーターが読み取るものです。" },
+    { "lines": "5", "label": "モデル", "note": "`inherit` はメイン エージェントのモデルを再利用します。プロファイルに明らかに別のプロファイルが必要な場合にのみオーバーライドします。" },
+    { "lines": "6", "note": "現時点では `tools: inherit` — このフィールドは将来のエージェントごとのツール ポリシー用に予約されています。" }
   ]
 }
 ```
@@ -303,21 +303,21 @@ REST エンドポイントは自動的にマウントされました:
 エージェントはこれらの組み込み actions を使用します。自分の actions から呼び出すこともできます:
 
 ```bash
-# List all resources
+# すべてのリソースをリストする
 pnpm action resource-list --scope all
 
-# Read a resource
+# リソースを読む
 pnpm action resource-read --path "skills/my-skill/SKILL.md"
 
-# Read inherited workspace context managed by Dispatch
+# Dispatch によって管理される継承されたワークスペース コンテキストを読み取る
 pnpm action resource-read --scope workspace --path "context/brand.md"
 
 # Show workspace -> organization/app -> personal precedence for a path
 pnpm action resource-effective --path "context/brand.md"
 
-# Write a resource
-pnpm action resource-write --path "notes/meeting.md" --content "# Meeting Notes..."
+# リソースを書く
+pnpm action resource-write --path "notes/meeting.md" --content "# 会議メモ…」
 
-# Delete a resource
+# リソースを削除する
 pnpm action resource-delete --path "notes/old.md"
 ```

package/corpus/core/docs/content/locales/ja-JP/writing-agent-instructions.md

@@ -1,15 +1,15 @@
 ---
-title: "エージェントの指示と Skills の作成"
+title: "エージェントの指示と スキル の作成"
 description: "エージェント ネイティブ アプリまたはテンプレートの優れたエージェント手順を作成する方法: AGENTS.md、skills、およびツールの説明。"
 ---
 
-# エージェントの指示と Skills の作成
+# エージェントの指示と スキル の作成
 
 エージェント ネイティブ アプリにおけるエージェントの動作は、ユーザーが与えた指示によって決まります。 `AGENTS.md` (マップ)、skills (詳細)、およびアクション/ツールの説明 (エージェントが適切なツールを選択する方法) の 3 つのサーフェスでそのガイダンスが伝えられます。散文ではなく、迅速に検索できるようにそれぞれを書きます。
 
 ```an-diagram title="3 つの作成済みサーフェス + 1 つのランタイム サーフェス" summary="AGENTS.md とツールの説明は毎ターンロードされます。スキルはオンデマンドでロードされます。 application_state は UI によってライブで書き込まれます。"
 {
-  "html": "<div class=\"diagram-surfaces\"><div class=\"diagram-card always\" data-rough><span class=\"diagram-pill accent\">Every turn</span><strong>AGENTS.md</strong><small class=\"diagram-muted\">the map: purpose, core rules, state keys, action + skills index</small></div><div class=\"diagram-card always\" data-rough><span class=\"diagram-pill accent\">Every turn</span><strong>Tool descriptions</strong><small class=\"diagram-muted\">drive tool selection — one precise sentence each</small></div><div class=\"diagram-card ondemand\" data-rough><span class=\"diagram-pill\">On demand</span><strong>Skills</strong><small class=\"diagram-muted\">deep how-to, loaded when the description fires</small></div><div class=\"diagram-card runtime\" data-rough><span class=\"diagram-pill ok\">Live</span><strong>application_state</strong><small class=\"diagram-muted\">written by your UI: navigation, selection, focus</small></div></div>",
+  "html": "<div class=\"diagram-surfaces\"><div class=\"diagram-card always\" data-rough><span class=\"diagram-pill accent\">毎ターン</span><strong>AGENTS.md</strong><small class=\"diagram-muted\">地図: 目的、基本ルール、状態キー、action + skills索引</small></div><div class=\"diagram-card always\" data-rough><span class=\"diagram-pill accent\">毎ターン</span><strong>ツール説明</strong><small class=\"diagram-muted\">ツール選択を導く — それぞれ1つの正確な文</small></div><div class=\"diagram-card ondemand\" data-rough><span class=\"diagram-pill\">オンデマンド</span><strong>スキル</strong><small class=\"diagram-muted\">詳細な手順、説明が一致したときに読み込み</small></div><div class=\"diagram-card runtime\" data-rough><span class=\"diagram-pill ok\">Live</span><strong>application_state</strong><small class=\"diagram-muted\">UIが書き込む: ナビゲーション、選択、フォーカス</small></div></div>",
   "css": ".diagram-surfaces{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:12px}.diagram-surfaces .diagram-card{display:flex;flex-direction:column;gap:6px;padding:14px 16px}"
 }
 ```
@@ -22,28 +22,28 @@ description: "エージェント ネイティブ アプリまたはテンプレ
 - **コア ルール** — 常に保持する必要がある少数の不変条件 (データは SQL、操作は actions を経由し、AI はエージェント チャットを経由し、スキーマの変更は追加的です)。短くて命令的な箇条書き。
 - **アプリケーション状態キー** — ユーザーが見ているものとその形状を知るためにエージェントが読み取る `navigation`/選択/フォーカス キー。
 - **アクション テーブル** — アクション名と目的をまとめたコンパクトなテーブル。
-- **Skills インデックス** — 存在する skills のリストと、それぞれをいつ読み取るか。
+- **スキル インデックス** — 存在する skills のリストと、それぞれをいつ読み取るか。
 
 セクションが画面を超えて拡大する場合、それはスキルに属します。 `AGENTS.md` は、「難しいことを具体的にどのようにすればよいか」ではなく、「このアプリは何ですか、何ができるでしょうか」と答えます。
 
 ```markdown
-# Projects App
+# プロジェクトアプリ
 
 One workspace for projects, tasks, and notes. Agent and UI share the same SQL
 data and the same actions.
 
-## Core Rules
+## コアルール
 
-- Data lives in SQL via Drizzle. Use actions for all writes.
+- Data lives in Drizzle 経由の SQL. Use actions for all writes.
 - All AI work goes through the agent chat; never call an LLM inline.
 - Schema changes are additive only.
 
-## Application State
+## アプリケーションの状態
 
 - `navigation.view`: `home` | `project`
 - `navigation.projectId`: selected project on a project page
 
-## Actions
+## アクション
 
 | Action           | Purpose                     |
 | ---------------- | --------------------------- |
@@ -51,7 +51,7 @@ data and the same actions.
 | `create-project` | Create a project            |
 | `update-project` | Rename or archive a project |
 
-## Skills
+## スキル
 
 - `project-imports` — read before importing legacy CSV exports.
 - `sharing` — read before exposing a project to other users.
@@ -84,12 +84,12 @@ description: >-
 
 ```text
 .agents/skills/project-imports/
-├── SKILL.md            # rule + happy path + do/don't
+├── SKILL.md            # ルール + ハッピー パス + do/don't
 └── references/
-    └── csv-format.md   # full column spec, encodings, edge cases
+    └── csv-format.md   # 完全な列仕様、エンコーディング、エッジケース
 ```
 
-これにより、常に読み込まれるサーフェスが小さく保たれ、コンテキストを肥大化させることなく深度をスケールできるようになります。完全なスキル形式については、[Skills Guide](/docs/skills-guide) を参照してください。
+これにより、常に読み込まれるサーフェスが小さく保たれ、コンテキストを肥大化させることなく深度をスケールできるようになります。完全なスキル形式については、[スキル Guide](/docs/skills-guide) を参照してください。
 
 ## アクション指向のテーブルを作成する {#action-tables}
 
@@ -114,9 +114,9 @@ defineAction({
 });
 ```
 
-## Skills 対 actions {#skills-vs-actions}
+## スキル 対 actions {#skills-vs-actions}
 
-Skills と actions は相補的です。スキルとは、エージェントが読むガイダンスです。
+スキル と actions は相補的です。スキルとは、エージェントが読むガイダンスです。
 アクションは、エージェントが実行できるコードです。
 
 | 必要                                                                                         | 使用                             |
@@ -151,7 +151,7 @@ Skills と actions は相補的です。スキルとは、エージェントが
 | 表面                             | 誰が書いたのか     | ロード時                                                       | そこに属するもの                                                                  |
 | -------------------------------- | ------------------ | -------------------------------------------------------------- | --------------------------------------------------------------------------------- |
 | `AGENTS.md` 命令                 | あなた（開発者）   | 毎ターン、オリエンテーションとして                             | 目的、コアルール、状態キー、アクションインデックス、skills インデックス           |
-| Skills (`SKILL.md`)              | あなた（開発者）   | エージェントがスキルが関連していると判断した場合のオンデマンド | 特定のパターンのステップバイステップのハウツー、やるべきこと/やらないことのリスト |
+| スキル (`SKILL.md`)              | あなた（開発者）   | エージェントがスキルが関連していると判断した場合のオンデマンド | 特定のパターンのステップバイステップのハウツー、やるべきこと/やらないことのリスト |
 | アクションの説明 (ツール)        | あなた（開発者）   | 毎ターン、ツールリストとして                                   | アクションの動作、アクションが返す内容、パラメータのセマンティクス                |
 | `application_state` コンテキスト | UI コード (実行時) | 毎ターン、アプリのライブ状態として                             | 現在のナビゲーション、選択範囲、フォーカスされたオブジェクト、URL                 |
 
@@ -163,11 +163,11 @@ Skills と actions は相補的です。スキルとは、エージェントが
 ## 何がどこに行くのか {#what-goes-where}
 
 - **AGENTS.md** — 毎ターン、アプリ全体に適用されます: 目的、コアルール、状態キー、アクションインデックス、skills インデックス。
-- **Skills** — オンデマンドでロードされる、特定のパターンの再利用可能なハウツー。アプリで作業している全員に適用されます。
+- **スキル** — オンデマンドでロードされる、特定のパターンの再利用可能なハウツー。アプリで作業している全員に適用されます。
 - **メモリ (`memory/MEMORY.md`)** — ユーザーごとの設定と修正。作成されたガイダンスではありません。
 
 ## 次は何ですか {#whats-next}
 
-- [Skills Guide](/docs/skills-guide) — スキル ファイル形式、フレームワーク skills、およびアプリベースの skills。
+- [スキル Guide](/docs/skills-guide) — スキル ファイル形式、フレームワーク skills、およびアプリベースの skills。
 - [Creating Templates](/docs/creating-templates) — `AGENTS.md` と skills を出荷可能なテンプレートにどのように適合させるか。
 - [The four-area checklist](/docs/key-concepts#four-area-checklist) — すべての特徴が満たさなければならない 4 エリア モデル。

package/corpus/core/docs/content/locales/ko-KR/a2a-protocol.md

@@ -22,7 +22,7 @@ A2A is the substrate for cross-app delegation in this framework — most promine
 
 ```an-diagram title="한 상담원이 다른 상담원에게 일을 맡깁니다." summary="메일 에이전트는 분석 에이전트의 카드를 발견하고 JSON-RPC 메시지를 보낸 다음 완료된 작업을 돌려받습니다."
 {
-  "html": "<div class=\"diagram-handoff\"><div class=\"diagram-card\"><strong>Mail agent</strong><small class=\"diagram-muted\">needs analytics</small></div><div class=\"diagram-col\"><div class=\"diagram-pill\">GET /.well-known/agent-card.json</div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-pill accent\">POST /_agent-native/a2a<br><small class=\"diagram-muted\">message/send</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&larr;</div><div class=\"diagram-pill ok\">task · completed</div></div><div class=\"diagram-card\" data-rough><strong>Analytics agent</strong><small class=\"diagram-muted\">runs run-query, returns result</small></div></div>",
+  "html": "<div class=\"diagram-handoff\"><div class=\"diagram-card\"><strong>Mail 에이전트</strong><small class=\"diagram-muted\">needs analytics</small></div><div class=\"diagram-col\"><div class=\"diagram-pill\">GET /.well-known/agent-card.json</div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-pill accent\">POST /_agent-native/a2a<br><small class=\"diagram-muted\">message/send</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&larr;</div><div class=\"diagram-pill ok\">작업 · 완료</div></div><div class=\"diagram-card\" data-rough><strong>Analytics 에이전트</strong><small class=\"diagram-muted\">run-query를 실행하고 결과 반환</small></div></div>",
   "css": ".diagram-handoff{display:flex;align-items:center;gap:16px;flex-wrap:wrap}.diagram-handoff .diagram-col{display:flex;flex-direction:column;align-items:center;gap:6px}.diagram-handoff .diagram-arrow{font-size:20px;line-height:1}"
 }
 ```
@@ -119,11 +119,11 @@ _(버전은 다를 수 있습니다. 현재 `protocolVersion`에 대해서는 `/
 | `tasks/get`      | ID로 작업 가져오기 — 비동기 작업을 완료하도록 폴링하는 데 사용됩니다.                                                | `id`                          |
 | `tasks/cancel`   | 실행 중인 작업 취소                                                                                                  | `id`                          |
 
-```an-api title="Primary A2A endpoint" summary="All JSON-RPC methods are POSTed here. message/send shown."
+```an-api title="기본 A2A 엔드포인트" summary="모든 JSON-RPC 메소드는 여기에 POSTed 있습니다. message/send가 표시됩니다."
 {
   "method": "POST",
   "path": "/_agent-native/a2a",
-  "summary": "Send a message and wait for the completed task",
+  "summary": "메시지를 보내고 완료된 작업을 기다립니다.",
   "description": "JSON-RPC 2.0 endpoint for `message/send`, `message/stream`, `tasks/get`, and `tasks/cancel`. Pass `async: true` to return immediately in `working` state and poll with `tasks/get`.",
   "auth": "JWT bearer signed with A2A_SECRET (or legacy apiKeyEnv static token)",
   "params": [
@@ -148,7 +148,7 @@ _(버전은 다를 수 있습니다. 현재 `protocolVersion`에 대해서는 `/
 
 ```an-diagram title="서버리스의 비동기 작업 수명 주기" summary="async:true는 밀리초 단위로 작업을 반환하고 호출자가 폴링하는 동안 새로 실행하면 에이전트 루프가 실행됩니다."
 {
-  "html": "<div class=\"diagram-async\"><div class=\"diagram-box\" data-rough>message/send<br><small class=\"diagram-muted\">async: true</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-panel\"><span class=\"diagram-pill\">enqueue task</span><span class=\"diagram-pill warn\">return working</span><small class=\"diagram-muted\">~milliseconds</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&darr;</div><div class=\"diagram-box\" data-rough>self-fire POST /_agent-native/a2a/_process-task<br><small class=\"diagram-muted\">HMAC token · fresh execution · full timeout</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-col\"><div class=\"diagram-pill\">tasks/get (poll)</div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&#8635;</div><div class=\"diagram-pill ok\">completed</div></div></div>",
+  "html": "<div class=\"diagram-async\"><div class=\"diagram-box\" data-rough>message/send<br><small class=\"diagram-muted\">async: true</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-panel\"><span class=\"diagram-pill\">enqueue task</span><span class=\"diagram-pill warn\">return working</span><small class=\"diagram-muted\">~밀리초</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&darr;</div><div class=\"diagram-box\" data-rough>자체 실행 POST /_agent-native/a2a/_process-task<br><small class=\"diagram-muted\">HMAC token · 새 실행 · 전체 타임아웃</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-col\"><div class=\"diagram-pill\">tasks/get (poll)</div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&#8635;</div><div class=\"diagram-pill ok\">completed</div></div></div>",
   "css": ".diagram-async{display:flex;align-items:center;gap:14px;flex-wrap:wrap}.diagram-async .diagram-panel{display:flex;flex-direction:column;align-items:center;gap:6px}.diagram-async .diagram-col{display:flex;flex-direction:column;align-items:center;gap:6px}.diagram-async .diagram-arrow{font-size:20px;line-height:1}",
   "caption": "A recurring sweeper re-claims any task left in flight if the function execution dies mid-run."
 }
@@ -165,9 +165,9 @@ _(버전은 다를 수 있습니다. 현재 `protocolVersion`에 대해서는 `/
   "language": "json",
   "code": "{\n  \"role\": \"user\",\n  \"parts\": [\n    { \"type\": \"text\", \"text\": \"Show signups by source\" },\n    { \"type\": \"data\", \"data\": { \"dateRange\": \"last-30d\" } },\n    {\n      \"type\": \"file\",\n      \"file\": { \"name\": \"report.csv\", \"mimeType\": \"text/csv\", \"bytes\": \"...\" }\n    }\n  ]\n}",
   "annotations": [
-    { "lines": "4", "label": "text part", "note": "Plain natural-language instruction the agent reads." },
-    { "lines": "5", "label": "data part", "note": "Structured JSON arguments — e.g. a date range — passed alongside the prompt." },
-    { "lines": "6-9", "label": "file part", "note": "Attach a file by name, `mimeType`, and base64 `bytes`." }
+    { "lines": "4", "label": "text part", "note": "에이전트가 읽는 일반 자연어 지침입니다." },
+    { "lines": "5", "label": "data part", "note": "구조화된 JSON 인수 — e.g. 날짜 범위 - 프롬프트와 함께 전달됩니다." },
+    { "lines": "6-9", "label": "file part", "note": "이름, `mimeType` 및 base64 `bytes`로 파일을 첨부합니다." }
   ]
 }
 ```

package/corpus/core/docs/content/locales/ko-KR/actions.md

@@ -21,7 +21,7 @@ embedded sidecar, or as a full app screen, see [Agent Surfaces](/docs/agent-surf
 
 ```an-diagram title="하나의 정의, 7명의 소비자" summary="단일 defineAction()은 하나의 검증된 스키마와 하나의 run() 본문을 사용하여 에이전트, UI, HTTP, MCP, A2A 및 CLI 등 모든 표면으로 확장됩니다."
 {
-  "html": "<div class=\"diagram-fanout\"><div class=\"diagram-panel center\" data-rough><span class=\"diagram-pill accent\">defineAction()</span><small class=\"diagram-muted\">schema + run(), defined once</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-grid\"><div class=\"diagram-node\">Agent tool<br><small class=\"diagram-muted\">JSON Schema in context</small></div><div class=\"diagram-node\">React hooks<br><small class=\"diagram-muted\">useActionQuery/Mutation</small></div><div class=\"diagram-node\">callAction()<br><small class=\"diagram-muted\">imperative client</small></div><div class=\"diagram-node\">HTTP<br><small class=\"diagram-muted\">/_agent-native/actions/:name</small></div><div class=\"diagram-node\">MCP tool<br><small class=\"diagram-muted\">external hosts</small></div><div class=\"diagram-node\">A2A tool<br><small class=\"diagram-muted\">other agent-native apps</small></div><div class=\"diagram-node\">CLI<br><small class=\"diagram-muted\">pnpm action &lt;name&gt;</small></div></div></div>",
+  "html": "<div class=\"diagram-fanout\"><div class=\"diagram-panel center\" data-rough><span class=\"diagram-pill accent\">defineAction()</span><small class=\"diagram-muted\">schema + run(), 한 번만 정의</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-grid\"><div class=\"diagram-node\">에이전트 도구<br><small class=\"diagram-muted\">컨텍스트의 JSON Schema</small></div><div class=\"diagram-node\">React 훅<br><small class=\"diagram-muted\">useActionQuery/Mutation</small></div><div class=\"diagram-node\">callAction()<br><small class=\"diagram-muted\">명령형 클라이언트</small></div><div class=\"diagram-node\">HTTP<br><small class=\"diagram-muted\">/_agent-native/actions/:name</small></div><div class=\"diagram-node\">MCP 도구<br><small class=\"diagram-muted\">외부 호스트</small></div><div class=\"diagram-node\">A2A 도구<br><small class=\"diagram-muted\">다른 agent-native 앱</small></div><div class=\"diagram-node\">CLI<br><small class=\"diagram-muted\">pnpm action &lt;name&gt;</small></div></div></div>",
   "css": ".diagram-fanout{display:flex;align-items:center;gap:14px;flex-wrap:wrap}.diagram-fanout .center{display:flex;flex-direction:column;align-items:center;gap:4px;padding:14px 16px}.diagram-fanout .diagram-arrow{font-size:22px;line-height:1}.diagram-fanout .diagram-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:8px}"
 }
 ```
@@ -155,7 +155,7 @@ export default defineAction({
   "method": "GET",
   "path": "/_agent-native/actions/get-lead",
   "summary": "모든 action은 여기에 자동으로 마운트됩니다. 파일 이름이 action 이름입니다.",
-  "description": "기본값은 POST입니다. `http: { method: \"GET\" }`는 이를 GET으로 만듭니다. React hooks와 `callAction`은 `http.path` override와 관계없이 항상 이름으로 이 경로를 호출합니다.",
+  "description": "기본값은 POST입니다. `http: { method: \"GET\" }`는 이를 GET으로 만듭니다. React 훅와 `callAction`은 `http.path` override와 관계없이 항상 이름으로 이 경로를 호출합니다.",
   "auth": "세션 쿠키; 프론트엔드 호출에는 `X-Agent-Native-Frontend: 1`이 포함됩니다",
   "params": [
     { "name": "leadId", "in": "query", "type": "string", "required": true, "description": "GET 인수는 query params로 도착하고 POST 인수는 JSON body로 도착합니다." }
@@ -434,7 +434,7 @@ export default defineAction({
 
 내장 판별자는 `"data-table"`, `"data-chart"` 및
 `"data-insights"`, 서버 안전 빌더 및 스키마 포함
-`@agent-native/core/data-widgets`. [Native Chat UI](/docs/native-chat-ui) 참조
+`@agent-native/core/data-widgets`. [Native 채팅 UI](/docs/native-chat-ui) 참조
 전체 결과 계약 및 BYO 런타임 지침
 같은 행동이 어떻게 유지될 수 있는지에 대한 [Agent Surfaces](/docs/agent-surfaces)
 헤드리스, 채팅에서 렌더링 또는 전체 화면으로 확장

package/corpus/core/docs/content/locales/ko-KR/agent-mentions.md

@@ -31,7 +31,7 @@ description: "@멘션을 사용하여 사용자 정의 에이전트, 연결된
 
 ```an-diagram title="@-멘션이 라우팅되는 위치" summary="서버는 각 멘션을 유형별로 분할합니다. 사용자 정의 에이전트는 로컬에서 실행되고 연결된 에이전트는 A2A을 통해 이동합니다. 두 응답 모두 기본 에이전트의 컨텍스트로 다시 접힙니다."
 {
-  "html": "<div class=\"diagram-mention\"><div class=\"diagram-node\">@-mention<br><small class=\"diagram-muted\">in the composer</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-panel center\" data-rough><span class=\"diagram-pill accent\">Server resolves</span><small class=\"diagram-muted\">extract refs by type</small></div><div class=\"diagram-col\"><div class=\"row\"><span class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</span><div class=\"diagram-box\">Custom agent<br><small class=\"diagram-muted\">agents/*.md &middot; runs local</small></div></div><div class=\"row\"><span class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</span><div class=\"diagram-box\">Connected agent<br><small class=\"diagram-muted\">A2A peer &middot; remote call</small></div></div></div><div class=\"diagram-arrow diagram-accent\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-box diagram-accent\">&lt;agent-response&gt;<br><small class=\"diagram-muted\">injected into main agent</small></div></div>",
+  "html": "<div class=\"diagram-mention\"><div class=\"diagram-node\">@-mention<br><small class=\"diagram-muted\">in the composer</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-panel center\" data-rough><span class=\"diagram-pill accent\">서버가 해석</span><small class=\"diagram-muted\">extract refs by type</small></div><div class=\"diagram-col\"><div class=\"row\"><span class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</span><div class=\"diagram-box\">사용자 지정 에이전트<br><small class=\"diagram-muted\">agents/*.md &middot; runs local</small></div></div><div class=\"row\"><span class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</span><div class=\"diagram-box\">연결된 에이전트<br><small class=\"diagram-muted\">A2A peer &middot; remote call</small></div></div></div><div class=\"diagram-arrow diagram-accent\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-box diagram-accent\">&lt;agent-response&gt;<br><small class=\"diagram-muted\">injected into main agent</small></div></div>",
   "css": ".diagram-mention{display:flex;align-items:center;gap:12px;flex-wrap:wrap}.diagram-mention .center{display:flex;flex-direction:column;align-items:center;gap:4px;padding:14px}.diagram-mention .diagram-col{display:flex;flex-direction:column;gap:10px}.diagram-mention .row{display:flex;align-items:center;gap:8px}.diagram-mention .diagram-arrow{font-size:22px;line-height:1}"
 }
 ```
@@ -123,9 +123,9 @@ You are a focused design agent.
 {
   "filename": "server/mentions/contacts.ts",
   "language": "ts",
-  "code": "import type { MentionProvider } from \"@agent-native/core/server\";\n\nconst contactsProvider: MentionProvider = {\n  id: \"contacts\",\n  label: \"Contacts\",\n\n  // Search for mentionable items\n  async search(query: string) {\n    const contacts = await db.query.contacts.findMany({\n      where: like(contacts.name, `%${query}%`),\n      limit: 10,\n    });\n    return contacts.map((c) => ({\n      id: c.id,\n      label: c.name,\n      description: c.email,\n      type: \"contact\",\n    }));\n  },\n\n  // Resolve a mention into context for the agent\n  async resolve(id: string) {\n    const contact = await db.query.contacts.findFirst({\n      where: eq(contacts.id, id),\n    });\n    return {\n      type: \"context\",\n      text: `Contact: ${contact.name} (${contact.email})`,\n    };\n  },\n};",
+  "code": "import type { MentionProvider } from \"@agent-native/core/server\";\n\nconst contactsProvider: MentionProvider = {\n  id: \"contacts\",\n  label: \"Contacts\",\n\n  // 검색 for mentionable items\n  async search(query: string) {\n    const contacts = await db.query.contacts.findMany({\n      where: like(contacts.name, `%${query}%`),\n      limit: 10,\n    });\n    return contacts.map((c) => ({\n      id: c.id,\n      label: c.name,\n      description: c.email,\n      type: \"contact\",\n    }));\n  },\n\n  // Resolve a mention into context for the agent\n  async resolve(id: string) {\n    const contact = await db.query.contacts.findFirst({\n      where: eq(contacts.id, id),\n    });\n    return {\n      type: \"context\",\n      text: `Contact: ${contact.name} (${contact.email})`,\n    };\n  },\n};",
   "annotations": [
-    { "lines": "4-5", "label": "Identity", "note": "`id` namespaces the provider; `label` is the section heading shown in the `@` popover." },
+    { "lines": "4-5", "label": "아이덴티티", "note": "`id` namespaces the provider; `label` is the section heading shown in the `@` popover." },
     { "lines": "8-9", "label": "search", "note": "Runs as the user types after `@`. Return up to a handful of matches as `{ id, label, description, type }`." },
     { "lines": "23-24", "label": "resolve", "note": "Called when the message is sent. Turns a picked id into `{ type: \"context\", text }` that is injected into the agent's context." }
   ]

package/corpus/core/docs/content/locales/ko-KR/agent-surfaces.md

@@ -13,13 +13,13 @@ Agent-Native는 의도적으로 구성 가능합니다. UI를 많이 사용하
 유용한 선택 방법은 프로토콜을 먼저 따르는 것이 아닙니다. 제품 표면을 선택하세요
 원하는 경우 일치하는 프리미티브를 사용하세요.
 
-| 표면                           | 다음 경우에 사용                                                                                            | 시작                                                                                        |
-| ------------------------------ | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
-| **헤드리스 에이전트**          | 코드, 작업, 스크립트, 다른 앱 또는 다른 에이전트가 작업을 직접 호출해야 합니다.                             | `agent-native create --headless`, `defineAction`, `agent-native agent`, HTTP, CLI, MCP, A2A |
-| **Agent-Native의 풍부한 채팅** | 내장된 에이전트 루프가 지원하는 독립형 또는 내장형 채팅을 원합니다.                                         | [Chat template](/docs/template-chat), `<AgentChatSurface>`, `<AssistantChat>`               |
-| **Rich chat on your agent**    | You built the agent elsewhere and want Agent-Native's composer, transcript, tool cards, and native widgets. | `AgentChatRuntime`, `<AssistantChat runtime={runtime}>`                                     |
-| **Embedded sidecar**           | You already have a SaaS app and want an agent beside it with page context and host commands.                | `createAgentNativeEmbeddedPlugin()`, `AgentNativeEmbedded`                                  |
-| **Full application**           | Humans and agents should share durable screens, data, navigation, and collaboration.                        | Templates, actions, SQL state, context awareness                                            |
+| 표면                           | 다음 경우에 사용                                                                                   | 시작                                                                                        |
+| ------------------------------ | -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
+| **헤드리스 에이전트**          | 코드, 작업, 스크립트, 다른 앱 또는 다른 에이전트가 작업을 직접 호출해야 합니다.                    | `agent-native create --headless`, `defineAction`, `agent-native agent`, HTTP, CLI, MCP, A2A |
+| **Agent-Native의 풍부한 채팅** | 내장된 에이전트 루프가 지원하는 독립형 또는 내장형 채팅을 원합니다.                                | [Chat template](/docs/template-chat), `<AgentChatSurface>`, `<AssistantChat>`               |
+| **리치 채팅 on your agent**    | You built the agent elsewhere and want Agent-Native's 작성기, 기록, 도구 카드, and native widgets. | `AgentChatRuntime`, `<AssistantChat runtime={runtime}>`                                     |
+| **임베디드 sidecar**           | You already have a SaaS app and want an agent beside it with page context and 호스트 명령.         | `createAgentNativeEmbeddedPlugin()`, `AgentNativeEmbedded`                                  |
+| **전체 애플리케이션**          | Humans and agents should share durable screens, data, navigation, and collaboration.               | Templates, actions, SQL state, context awareness                                            |
 
 Those are stages, not separate products. A workflow can start as a headless
 agent with one action, appear in chat as a table or chart, and later become a
@@ -27,7 +27,7 @@ full screen in an app without changing the operation the agent calls.
 
 ```an-diagram title="표면 스펙트럼" summary="하나의 작업 표면, 4개의 제품 모양 - 각각 아래의 작업을 변경하지 않고 UI를 추가합니다."
 {
-  "html": "<div class=\"diagram-spectrum\"><div class=\"diagram-card\"><strong>Headless</strong><small class=\"diagram-muted\">actions, jobs, scripts, other agents</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-card\"><strong>Rich chat</strong><small class=\"diagram-muted\">composer, transcript, tool cards</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-card\"><strong>Embedded sidecar</strong><small class=\"diagram-muted\">agent beside an existing app</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-card accent-card\"><span class=\"diagram-pill accent\">most UI</span><strong>Full application</strong><small class=\"diagram-muted\">durable screens, data, collaboration</small></div></div><div class=\"diagram-base\" data-rough><span class=\"diagram-muted\">same actions · same SQL · same agent loop</span></div>",
+  "html": "<div class=\"diagram-spectrum\"><div class=\"diagram-card\"><strong>Headless</strong><small class=\"diagram-muted\">actions, 작업, 스크립트, 다른 에이전트</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-card\"><strong>리치 채팅</strong><small class=\"diagram-muted\">작성기, 기록, 도구 카드</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-card\"><strong>임베디드 sidecar</strong><small class=\"diagram-muted\">agent beside an existing app</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-card accent-card\"><span class=\"diagram-pill accent\">대부분의 UI</span><strong>전체 애플리케이션</strong><small class=\"diagram-muted\">지속 화면, 데이터, 협업</small></div></div><div class=\"diagram-base\" data-rough><span class=\"diagram-muted\">같은 actions · 같은 SQL · 같은 에이전트 루프</span></div>",
   "css": ".diagram-spectrum{display:flex;align-items:stretch;gap:10px;flex-wrap:wrap}.diagram-spectrum .diagram-card{display:flex;flex-direction:column;gap:6px;padding:14px 16px;min-width:150px;flex:1}.diagram-spectrum .diagram-arrow{align-self:center;font-size:22px;line-height:1}.diagram-base{margin-top:12px;padding:10px 14px;text-align:center}"
 }
 ```
@@ -110,11 +110,11 @@ export default defineAction({
 - **UI** — `useActionQuery`, `useActionMutation` 또는 `callAction`를 통해
 - **에이전트 도구** — 내장된 채팅 루프에서
 
-```an-api title="Calling an action over HTTP"
+```an-api title="HTTP을 통해 작업 호출"
 {
   "method": "POST",
   "path": "/_agent-native/actions/summarize-week",
-  "summary": "Invoke any action by name over HTTP",
+  "summary": "HTTP에 대해 이름으로 모든 작업을 호출합니다.",
   "description": "Every `defineAction` is auto-mounted at `/_agent-native/actions/<name>`. The JSON body is validated against the action's zod schema before `run` executes.",
   "request": {
     "contentType": "application/json",
@@ -268,7 +268,7 @@ export function ProjectChat({ threadId }: { threadId: string }) {
 
 Actions는 명시적인 기본 위젯 결과를 반환할 수 있으므로 채팅 출력은 단순히
 텍스트. 표, 차트 및 입력된 제품 카드는 자사 React로 렌더링됩니다.
-iframe이 없는 채팅 구성요소. [Native Chat UI](/docs/native-chat-ui)를 참조하세요.
+iframe이 없는 채팅 구성요소. [Native 채팅 UI](/docs/native-chat-ui)를 참조하세요.
 
 ## 에이전트의 풍부한 채팅 {#byo-agent}
 
@@ -300,7 +300,7 @@ A2UI 지원을 요청하세요. ACP는 특정 장소에서 지원됩니다 —
 코딩 에이전트(Gemini CLI, Claude 코드, …)를 통해
 [harness layer](/docs/harness-agents#acp), 여기서는 채팅 런타임이 아닙니다.
 
-[Native Chat UI — BYO agent runtimes](/docs/native-chat-ui#byo-agent-runtimes)
+[Native 채팅 UI — BYO agent runtimes](/docs/native-chat-ui#byo-agent-runtimes)
 is the canonical home for the event shapes, the runtime helpers, and `chatUI`
 도구 결과 메타데이터. Start there when wiring an external agent into the chat.
 
@@ -309,7 +309,7 @@ is the canonical home for the event shapes, the runtime helpers, and `chatUI`
 Use the embedded sidecar when the main product already exists and you want an
 옆에 있는 요원
 
-The server plugin mounts Agent-Native routes into your host app and resolves
+The server plugin mounts Agent-Native 라우트 into your host app and resolves
 호스트 ID 서버측:
 
 ```ts
@@ -347,7 +347,7 @@ export function AppShell({ children }) {
 
 ```an-diagram title="사이드카가 호스트 앱에 연결되는 방법" summary="플러그인은 Agent-Native 경로를 서버 측에 마운트합니다. React 사이드카는 페이지 컨텍스트 입력 및 호스트 명령 출력을 스트리밍합니다."
 {
-  "html": "<div class=\"diagram-sidecar\"><div class=\"diagram-panel\"><strong>Host app</strong><small class=\"diagram-muted\">your existing SaaS</small><div class=\"diagram-node\">getContext()<br><small class=\"diagram-muted\">route · selection</small></div><div class=\"diagram-node\">onNavigate / onRefresh<br><small class=\"diagram-muted\">host commands</small></div></div><div class=\"diagram-col-arrows\"><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&larr;</div></div><div class=\"diagram-panel accent-panel\"><span class=\"diagram-pill accent\">AgentNativeEmbedded</span><small class=\"diagram-muted\">agent + workspace</small><div class=\"diagram-box\" data-rough>Agent-Native routes<br><small class=\"diagram-muted\">mounted by the server plugin</small></div></div></div>",
+  "html": "<div class=\"diagram-sidecar\"><div class=\"diagram-panel\"><strong>호스트 앱</strong><small class=\"diagram-muted\">기존 SaaS</small><div class=\"diagram-node\">getContext()<br><small class=\"diagram-muted\">라우트 · 선택</small></div><div class=\"diagram-node\">onNavigate / onRefresh<br><small class=\"diagram-muted\">호스트 명령</small></div></div><div class=\"diagram-col-arrows\"><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&larr;</div></div><div class=\"diagram-panel accent-panel\"><span class=\"diagram-pill accent\">AgentNativeEmbedded</span><small class=\"diagram-muted\">agent + workspace</small><div class=\"diagram-box\" data-rough>Agent-Native 라우트<br><small class=\"diagram-muted\">mounted by the server plugin</small></div></div></div>",
   "css": ".diagram-sidecar{display:flex;align-items:center;gap:14px;flex-wrap:wrap}.diagram-sidecar .diagram-panel{display:flex;flex-direction:column;gap:8px;padding:14px 16px;min-width:200px}.diagram-sidecar .diagram-col-arrows{display:flex;flex-direction:column;gap:6px}.diagram-sidecar .diagram-arrow{font-size:22px;line-height:1}"
 }
 ```
@@ -389,7 +389,7 @@ actions 주변 또는 도메인 [template](/docs/cloneable-saas)에서
 ## 관련 문서 {#related-docs}
 
 - [Actions](/docs/actions) — 헤드리스 작업을 한 번 정의합니다.
-- [Native Chat UI](/docs/native-chat-ui) — 채팅에서 입력된 작업 결과를 렌더링합니다.
+- [Native 채팅 UI](/docs/native-chat-ui) — 채팅에서 입력된 작업 결과를 렌더링합니다.
 - [Drop-in Agent](/docs/drop-in-agent) — 채팅, 사이드바 또는 패널 표면을 마운트합니다.
 - [Component API](/docs/components) — 하위 레벨 React 채팅/작곡가 부분.
 - [Embedding SDK](/docs/embedding-sdk) — 기존 앱에 Agent-Native를 추가합니다.

package/corpus/core/docs/content/locales/ko-KR/agent-teams.md

@@ -22,7 +22,7 @@ Agent Teams는 핵심 실행 관리자에서 실행됩니다. 이벤트 스트
 
 ```an-diagram title="오케스트레이터 및 전문가" summary="기본 채팅은 자체 스레드에서 실행되고 인라인 칩으로 다시 보고하는 하위 에이전트에 위임됩니다."
 {
-  "html": "<div class=\"at-orc\"><div class=\"diagram-card main\"><span class=\"diagram-pill accent\">Main chat</span><small class=\"diagram-muted\">orchestrator &mdash; reads your request, delegates</small></div><div class=\"at-fan\"><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&darr;</div><div class=\"at-subs\"><div class=\"diagram-box\">Code review<br><small class=\"diagram-muted\">own thread &amp; prompt</small></div><div class=\"diagram-box\">BigQuery analysis<br><small class=\"diagram-muted\">own tools</small></div><div class=\"diagram-box\">Email in voice<br><small class=\"diagram-muted\">own context</small></div></div></div><div class=\"diagram-pill\">each appears inline as a live chip &#8635;</div></div>",
+  "html": "<div class=\"at-orc\"><div class=\"diagram-card main\"><span class=\"diagram-pill accent\">기본 채팅</span><small class=\"diagram-muted\">orchestrator &mdash; reads your request, delegates</small></div><div class=\"at-fan\"><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&darr;</div><div class=\"at-subs\"><div class=\"diagram-box\">코드 리뷰<br><small class=\"diagram-muted\">own thread &amp; prompt</small></div><div class=\"diagram-box\">BigQuery 분석<br><small class=\"diagram-muted\">own tools</small></div><div class=\"diagram-box\">음성으로 이메일<br><small class=\"diagram-muted\">own context</small></div></div></div><div class=\"diagram-pill\">each appears inline as a live chip &#8635;</div></div>",
   "css": ".at-orc{display:flex;flex-direction:column;align-items:center;gap:12px}.at-orc .diagram-card{padding:14px 18px;display:flex;flex-direction:column;gap:4px;align-items:center}.at-orc .at-fan{display:flex;flex-direction:column;align-items:center;gap:8px}.at-orc .diagram-arrow{font-size:22px}.at-orc .at-subs{display:flex;gap:12px;flex-wrap:wrap;justify-content:center}.at-orc .diagram-box{text-align:center}"
 }
 ```
@@ -140,7 +140,7 @@ interface AgentTask {
 
 ```an-diagram title="위임 깊이 가드(기본 캡 2)" summary="각 레벨은 상한선까지 더 깊게 생성될 수 있습니다. 그 이후의 스폰은 서버 측에서 거부됩니다."
 {
-  "html": "<div class=\"at-depth\"><div class=\"diagram-card ok\"><span class=\"diagram-pill\">depth 0</span><strong>Top-level chat</strong><small class=\"diagram-muted ok\">may spawn &darr;</small></div><div class=\"diagram-card ok\"><span class=\"diagram-pill\">depth 1</span><strong>Sub-agent</strong><small class=\"diagram-muted ok\">may spawn &darr;</small></div><div class=\"diagram-card warn\"><span class=\"diagram-pill warn\">depth 2</span><strong>Sub-agent's sub-agent</strong><small class=\"diagram-muted\">at the cap &mdash; may NOT spawn</small></div><div class=\"diagram-card\"><span class=\"diagram-pill warn\">depth 3</span><strong>Refused</strong><small class=\"diagram-muted\">server-side error</small></div></div>",
+  "html": "<div class=\"at-depth\"><div class=\"diagram-card ok\"><span class=\"diagram-pill\">depth 0</span><strong>최상위 채팅</strong><small class=\"diagram-muted ok\">may spawn &darr;</small></div><div class=\"diagram-card ok\"><span class=\"diagram-pill\">depth 1</span><strong>하위 에이전트</strong><small class=\"diagram-muted ok\">may spawn &darr;</small></div><div class=\"diagram-card warn\"><span class=\"diagram-pill warn\">depth 2</span><strong>하위 에이전트's sub-agent</strong><small class=\"diagram-muted\">at the cap &mdash; may NOT spawn</small></div><div class=\"diagram-card\"><span class=\"diagram-pill warn\">depth 3</span><strong>Refused</strong><small class=\"diagram-muted\">server-side error</small></div></div>",
   "css": ".at-depth{display:flex;flex-direction:column;gap:8px}.at-depth .diagram-card{display:flex;flex-direction:column;gap:2px;padding:10px 14px}.at-depth .rung-1,.at-depth .diagram-card:nth-child(2){margin-inline-start:24px}.at-depth .diagram-card:nth-child(3){margin-inline-start:48px}.at-depth .diagram-card:nth-child(4){margin-inline-start:72px}"
 }
 ```
@@ -159,7 +159,7 @@ interface AgentTask {
 | 잘못됨 / `>16`    | 정수가 아닌 / 음수 / NaN 값은 `2`로 대체됩니다. `16` 이상의 모든 항목은 `16`로 고정되므로 오타로 인해 가드가 비활성화될 수 없습니다. |
 
 ```bash
-AGENT_NATIVE_MAX_SUBAGENT_DEPTH=1   # sub-agents allowed, but they can't sub-delegate
+AGENT_NATIVE_MAX_SUBAGENT_DEPTH=1   # 하위 대리인은 허용되지만 하위 대리인은 할 수 없습니다.
 ```
 
 하위 에이전트가 한도 이하인 경우 프레임워크는 런타임 컨텍스트에 라인을 삽입하여 얼마나 깊이 있는지, 추가 위임이 가능한지 여부를 알려주므로 모델은 예산을 적절하게 사용합니다.

package/corpus/core/docs/content/locales/ko-KR/agent-web-surfaces.md

@@ -21,7 +21,7 @@ description: "공개 경로를 에이전트(robots.txt, llms.txt, 마크다운
 
 ```an-diagram title="공개 경로가 게시하는 내용" summary="공개 경로는 상담원 친화적인 표현으로 전개됩니다. 경로 읽기는 통화 도구와 별개입니다. 도구 액세스는 선택적으로 유지됩니다."
 {
-  "html": "<div class=\"diagram-web\"><div class=\"diagram-box\" data-rough>Public route<br><small class=\"diagram-muted\">derived from route access settings</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-grid\"><span class=\"diagram-pill\">robots.txt</span><span class=\"diagram-pill\">sitemap.xml</span><span class=\"diagram-pill\">llms.txt</span><span class=\"diagram-pill\">.md mirror</span><span class=\"diagram-pill\">JSON-LD</span><span class=\"diagram-pill\">text/markdown</span></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-col gate\"><span class=\"diagram-pill warn\">Tools stay private</span><small class=\"diagram-muted\">publicMcp + publicAgent.expose required</small></div></div>",
+  "html": "<div class=\"diagram-web\"><div class=\"diagram-box\" data-rough>공개 라우트<br><small class=\"diagram-muted\">derived from route access settings</small></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-grid\"><span class=\"diagram-pill\">robots.txt</span><span class=\"diagram-pill\">sitemap.xml</span><span class=\"diagram-pill\">llms.txt</span><span class=\"diagram-pill\">.md mirror</span><span class=\"diagram-pill\">JSON-LD</span><span class=\"diagram-pill\">text/markdown</span></div><div class=\"diagram-arrow diagram-muted\" aria-hidden=\"true\">&rarr;</div><div class=\"diagram-col gate\"><span class=\"diagram-pill warn\">도구는 비공개 유지</span><small class=\"diagram-muted\">publicMcp + publicAgent.expose required</small></div></div>",
   "css": ".diagram-web{display:flex;align-items:center;gap:14px;flex-wrap:wrap}.diagram-web .diagram-arrow{font-size:22px;line-height:1}.diagram-web .diagram-grid{display:grid;grid-template-columns:repeat(2,minmax(0,1fr));gap:8px}.diagram-web .gate{display:flex;flex-direction:column;gap:4px;align-items:flex-start}"
 }
 ```
@@ -87,10 +87,10 @@ description: "공개 경로를 에이전트(robots.txt, llms.txt, 마크다운
 {
   "filename": "actions/search-docs.ts",
   "language": "ts",
-  "code": "export default defineAction({\n  description: \"Search published docs\",\n  readOnly: true,\n  publicAgent: {\n    expose: true,\n    readOnly: true,\n    requiresAuth: false,\n    isConsequential: false,\n    title: \"Search published docs\",\n  },\n  run: async (args) => {\n    // ...\n  },\n});",
+  "code": "export default defineAction({\n  description: \"검색 published docs\",\n  readOnly: true,\n  publicAgent: {\n    expose: true,\n    readOnly: true,\n    requiresAuth: false,\n    isConsequential: false,\n    title: \"검색 published docs\",\n  },\n  run: async (args) => {\n    // ...\n  },\n});",
   "annotations": [
-    { "lines": "4", "label": "Explicit opt-in", "note": "Without `publicAgent.expose === true`, the action never appears on any public agent surface — no matter how public its routes are." },
-    { "lines": "5-7", "label": "Self-describe safety", "note": "Mark it read-only, declare whether it needs auth, and flag whether it is consequential. Public MCP excludes consequential/write actions unless policy explicitly allows them." }
+    { "lines": "4", "label": "명시적 동의", "note": "Without `publicAgent.expose === true`, the action never appears on any public agent surface — no matter how public its routes are." },
+    { "lines": "5-7", "label": "자체 설명 안전", "note": "읽기 전용으로 표시하고, 인증이 필요한지 선언하고, 결과적인지 플래그를 지정합니다. 공개 MCP는 정책이 명시적으로 허용하지 않는 한 consequential/write 작업을 제외합니다." }
   ]
 }
 ```
@@ -122,7 +122,7 @@ const files = buildAgentWebStaticFiles({
       path: "/docs",
       title: "Docs",
       description: "Start here.",
-      markdown: "# Docs\n\nStart here.\n",
+      markdown: "# 문서\n\n여기서 시작하세요.\n",
       markdownPath: "/docs/getting-started.md",
       lastmod: new Date(),
     },