Skip to content

Harness engineering beginner tutorial, from 0 to 1

Fix Chinese text leaked into translated harness-designs pages

sanbuphya49aa744103d
diff --git a/docs/ar/harness-designs/deepseek/index.md b/docs/ar/harness-designs/deepseek/index.md
index b6db77f..deb15e1 100644
--- a/docs/ar/harness-designs/deepseek/index.md
+++ b/docs/ar/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@
يستخدم DeepSeek Harness مفهوم Service للتعبير عن «القدرة»، ويقسّم كل قدرة تقريبًا إلى ثلاث طبقات:
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
لنأخذ نظام الملفات مثالًا: يندرج تحت `FS Service` عدد من Provider مثل Local FS وE2B FS وRemote FS، وتُعرَض جميعها للأعلى بصورة موحّدة على هيئة file tools. وتتبع Shell وSubprocess وSandbox وWeb وLLM وSubAgent البنية نفسها. وهذه البنية الثلاثية ليست خلاصة من عندنا—بل تذكر [وثيقة البنية · Capability seams](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) حرفيًا: *فاصل القدرة هو قدرة قابلة للاستبدال ذات ثلاثة أدوار: Service Definition يعلن الواجهة، وService Provider ينفذها، وConsumer يستخدمها، وغالبًا ما يكون الأخير أداة ظاهرة للنموذج*.
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(المسار أعلاه إعادة صياغة لقسم [وثيقة البنية · Turn flow](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md): تمثل `turn/*` و`step/*` و`user/message` و`assistant/*` و`tool/*` أحداث جلسة دائمة، بينما تمثل `agent/pre-step` و`agent/request` و`llm/stream` و`tools/*` نقاط توسعة يمكن للإضافات الاستماع إليها.)
diff --git a/docs/de/harness-designs/claude-code/index.md b/docs/de/harness-designs/claude-code/index.md
index 0d4869e..8263993 100644
--- a/docs/de/harness-designs/claude-code/index.md
+++ b/docs/de/harness-designs/claude-code/index.md
@@ -59,13 +59,13 @@ Claude Codes Logs sind vollständige append-oriented Aufzeichnungen (history.jso
## Zuordnung zum Kurs-Framework
-| 子系统 | Claude Code 的实现 | 评价 |
+| Subsystem | Umsetzung von Claude Code | Bewertung |
| --- | --- | --- |
-| 指令 | 作用域分层(组织/用户/项目/本地)+ 自动记忆 | 分层记忆是标杆实现 |
-| 工具 | 技能 + MCP + 钩子 + 子智能体四类扩展 | 职责划分清晰,是核心亮点 |
-| 环境 | 项目内设置 + settings.json | 靠用户在 CLAUDE.md 里自描述 |
-| 状态 | 追加式会话存储 + 五层压缩 + resume/fork | 极强,长任务连续性的参考实现 |
-| 反馈 | 权限分类器 + PostToolUse 钩子强制检查 | 把"防提前宣告完成"变成确定性机制 |
+| Anweisungen | Schichtung nach Geltungsbereich (Organisation/Benutzer/Projekt/lokal) + automatisches Memory | Geschichtetes Memory ist eine Referenzimplementierung |
+| Werkzeuge | Skills + MCP + hooks + subagents als vier Erweiterungstypen | Klare Trennung der Verantwortlichkeiten; ein zentraler Pluspunkt |
+| Umgebung | Projekteinstellungen + settings.json | Basiert auf der Selbstbeschreibung des Benutzers in CLAUDE.md |
+| Zustand | Append-only session-Speicher + fünfstufige compaction + resume/fork | Sehr stark; eine Referenzimplementierung für die Kontinuität lang laufender Aufgaben |
+| Feedback | Permission-Klassifikator + durch PostToolUse-hooks erzwungene Prüfungen | Macht die Verhinderung verfrühter Fertigmeldungen zu einem deterministischen Mechanismus |
## Übernehmenswerte Designs
diff --git a/docs/de/harness-designs/codex/index.md b/docs/de/harness-designs/codex/index.md
index e82e7fd..d09b267 100644
--- a/docs/de/harness-designs/codex/index.md
+++ b/docs/de/harness-designs/codex/index.md
@@ -47,13 +47,13 @@ Approval Policies und Plan Mode bilden die andere Seite des Feedbacks: Vor risik
## Zuordnung zum Kurs-Framework
-| 子系统 | Codex 的实现 | 评价 |
+| Subsystem | Umsetzung von Codex | Bewertung |
| --- | --- | --- |
-| 指令 | AGENTS.md 目录页 + docs/ 拆分 + 执行不变量 | 教科书级,定义了"给地图不给说明书" |
-| 工具 | worktree 隔离 + spawn_agent 子智能体 | 边界靠环境硬隔离,很强 |
-| 环境 | 独立 worktree + 可观测性栈 | worktree 隔离是其招牌 |
-| 状态 | Write 策略(状态写进文件/文档) | 依赖约定而非内建记忆 |
-| 反馈 | 验证命令入规范 + 审批策略 + plan mode | 反馈路径默认化,值得抄 |
+| Anweisungen | AGENTS.md als Verzeichnisseite + Aufteilung in docs/ + Ausführungsinvarianten | Lehrbuchreif; definiert das Prinzip „eine Karte, keine Anleitung“ |
+| Werkzeuge | worktree-Isolation + spawn_agent-subagents | Grenzen werden durch harte Umgebungsisolation durchgesetzt; sehr stark |
+| Umgebung | Eigener worktree + Observability-Stack | worktree-Isolation ist das Markenzeichen |
+| Zustand | Write-Strategie (Zustand wird in Dateien/Dokumente geschrieben) | Beruht auf Konventionen statt auf integriertem Memory |
+| Feedback | Validierungsbefehle in der Spezifikation + Approval Policies + plan mode | Der Feedbackpfad ist standardmäßig vorgesehen; nachahmenswert |
Der Vergleich zwischen Codex und Claude Code ist aufschlussreich: Claude Code verfolgt „Addition“ – Memory, permissions und subagents werden in den Kernel eingebaut. Codex verfolgt „Subtraktion“ – der Kernel bleibt möglichst zurückhaltend, während mehr Verantwortung bei Repository-Konventionen und Context Engineering liegt. Deshalb heißt es in der Community oft: „Die harness-Philosophie von Codex ist wertvoller als sein Code.“
diff --git a/docs/de/harness-designs/deepseek/index.md b/docs/de/harness-designs/deepseek/index.md
index 1cf4f7d..557aeaf 100644
--- a/docs/de/harness-designs/deepseek/index.md
+++ b/docs/de/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@ Das ist die konsequenteste Umsetzung des Kurssatzes „Alles außerhalb der Mode
DeepSeek Harness stellt „Fähigkeiten“ als Services dar; fast jede Fähigkeit ist in drei Ebenen aufgeteilt:
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
Am Beispiel des Dateisystems: Unter dem `FS Service` stehen mehrere Provider wie Local FS, E2B FS und Remote FS, die nach oben einheitlich als file tools exponiert werden. Shell, Subprocess, Sandbox, Web, LLM und SubAgent folgen derselben Struktur. Diese Dreiteilung ist keine Zusammenfassung von uns. Die [Architekturdokumentation · Capability seams](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) sagt: *a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool* (Ein Capability Seam ist eine austauschbare Fähigkeit mit drei Rollen: einer Service Definition, die das Interface deklariert, einem Service Provider, der es implementiert, und einem Consumer, der es verwendet – üblicherweise ein dem Modell zugängliches Tool).
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(Die obige Pipeline ist eine Wiedergabe des Abschnitts [Architekturdokumentation · Turn flow](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md): `turn/*`, `step/*`, `user/message`, `assistant/*` und `tool/*` sind persistierte session-Events; `agent/pre-step`, `agent/request`, `llm/stream` und `tools/*` sind Erweiterungspunkte, die plugins beobachten können.)
@@ -58,13 +58,13 @@ Mit anderen Worten: Observability ist kein nachträglich ergänztes Logging, son
## Zuordnung zum Kurs-Framework
-| 子系统 | DeepSeek Harness 的实现 | 评价 |
+| Subsystem | Umsetzung von DeepSeek Harness | Bewertung |
| --- | --- | --- |
-| 指令 | 插件化;规则/技能均以插件形态注入 | 极自由,但没有内置的"CLAUDE.md"式惯例 |
-| 工具 | Service Definition → Provider → Consumer 能力接缝 | 工具子系统标准化的极致 |
-| 环境 | 沙箱/FS/Shell 全部可换 Provider(含远程 E2B) | 环境彻底可插拔 |
-| 状态 | append-only Session Event Log + Model-visible means logged | 可观测性是第一性约束 |
-| 反馈 | tools/pre-execute 上的 permission / guard / policy / hook | 反馈机制事件化 |
+| Anweisungen | Pluginbasiert; Regeln und Skills werden als plugins injiziert | Maximale Freiheit, aber keine integrierte Konvention nach Art von CLAUDE.md |
+| Werkzeuge | Service Definition → Provider → Consumer als Capability Seam | Konsequente Standardisierung des Werkzeugsubsystems |
+| Umgebung | Provider für Sandbox/FS/Shell sind vollständig austauschbar (einschließlich Remote-E2B) | Die Umgebung ist vollständig austauschbar |
+| Zustand | append-only Session Event Log + Model-visible means logged | Observability ist ein Constraint erster Ordnung |
+| Feedback | permission / guard / policy / hook auf tools/pre-execute | Der Feedbackmechanismus ist ereignisbasiert |
Der grundlegende Unterschied zwischen DeepSeek Harness und den drei anderen Produkten: Pi, Claude Code und Codex optimieren den harness jeweils „innerhalb eines bestimmten agent“. DeepSeek Harness definiert den harness dagegen als **modellunabhängiges Betriebssystem**; der agent selbst ist nur eine austauschbare Anwendung auf diesem OS. Der Preis ist offensichtlich: Hohe Freiheit verursacht hohen Konfigurationsaufwand. Das ist die unvermeidliche Kehrseite des Designs „harness als OS“ – und in der Developer Preview lautet die Positionierung ohnehin „früh ausprobieren, während sich die Mechanismen noch entwickeln“.
diff --git a/docs/de/harness-designs/pi/index.md b/docs/de/harness-designs/pi/index.md
index 37001fd..09066dc 100644
--- a/docs/de/harness-designs/pi/index.md
+++ b/docs/de/harness-designs/pi/index.md
@@ -63,13 +63,13 @@ Dasselbe Community-Repository bestätigt dieses Muster weiter: `VISION.md` (Ziel
Bewertung von Pi anhand der fünf Subsysteme des Kurses (subjektiv, zum Vergleich):
-| 子系统 | Pi 的实现 | 评价 |
+| Subsystem | Umsetzung von Pi | Bewertung |
| --- | --- | --- |
-| 指令 | AGENTS.md 分级加载 + SYSTEM.md | 层级清晰,但规则本身要靠用户写 |
-| 工具 | 技能按需加载 + 扩展全生命周期钩子 | 极强,把工具系统做成了可编程面 |
-| 环境 | SYSTEM.md 做环境自描述;运行时环境靠用户在 AGENTS.md 里声明 | 机制是开放的,但可复现性依赖用户自述 |
-| 状态 | 会话树 + 压缩可定制 + PROGRESS.md | 极强,跨会话与可恢复性是其核心 |
-| 反馈 | 验证命令靠用户定义;session-summary / extract-patterns 机制化 | 机制提供,内容靠用户 |
+| Anweisungen | Abgestuftes Laden von AGENTS.md + SYSTEM.md | Klare Hierarchie, die Regeln selbst müssen jedoch vom Benutzer verfasst werden |
+| Werkzeuge | Laden von Skills bei Bedarf + hooks für den gesamten Lebenszyklus von Extensions | Sehr stark; macht das Werkzeugsystem zu einer programmierbaren Oberfläche |
+| Umgebung | SYSTEM.md zur Selbstbeschreibung der Umgebung; die Runtime-Umgebung wird vom Benutzer in AGENTS.md deklariert | Der Mechanismus ist offen, die Reproduzierbarkeit hängt jedoch von der Selbstbeschreibung des Benutzers ab |
+| Zustand | session tree + anpassbare compaction + PROGRESS.md | Sehr stark; session-übergreifende Kontinuität und Wiederherstellbarkeit bilden den Kern |
+| Feedback | Validierungsbefehle werden vom Benutzer definiert; session-summary / extract-patterns sind als Mechanismen umgesetzt | Der Mechanismus wird bereitgestellt, der Inhalt kommt vom Benutzer |
Pis Trade-offs stehen in scharfem Kontrast zu Claude Code und Codex: Claude Code baut „Memory, permissions und subagents“ gebrauchsfertig in den Kernel ein; Codex macht „Repository-Konventionen und Umgebungsisolation“ zum Standard. Pi entscheidet sich dafür, **nichts an deiner Stelle zu entscheiden** – es macht die Entscheidungshoheit zu Erweiterungspunkten. Der Preis: Du musst Extensions entweder selbst schreiben oder Pakete anderer installieren.
diff --git a/docs/en/harness-designs/deepseek/index.md b/docs/en/harness-designs/deepseek/index.md
index 183ff94..c925dde 100644
--- a/docs/en/harness-designs/deepseek/index.md
+++ b/docs/en/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@ This is the most thorough implementation of the course's statement that "everyth
DeepSeek Harness represents "capabilities" as Services, and divides nearly every capability into three layers:
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
Take the file system as an example: under `FS Service` are multiple Providers—Local FS, E2B FS, and Remote FS—all exposed upward through a consistent set of file tools. Shell, Subprocess, Sandbox, Web, LLM, and SubAgent follow the same structure. This three-layer structure is not our own summary. The [architecture documentation · Capability seams](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) says: *a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool*.
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(The pipeline above is adapted from the [architecture documentation · Turn flow](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md): `turn/*`, `step/*`, `user/message`, `assistant/*`, and `tool/*` are persistent session events, while `agent/pre-step`, `agent/request`, `llm/stream`, and `tools/*` are extension points that plugins can observe.)
diff --git a/docs/es/harness-designs/claude-code/index.md b/docs/es/harness-designs/claude-code/index.md
index b5b3a6b..94c1731 100644
--- a/docs/es/harness-designs/claude-code/index.md
+++ b/docs/es/harness-designs/claude-code/index.md
@@ -59,13 +59,13 @@ Los logs de Claude Code son registros completos append-only en history.jsonl. Ju
## Correspondencia con el marco del curso
-| 子系统 | Claude Code 的实现 | 评价 |
+| Subsistema | Implementación de Claude Code | Evaluación |
| --- | --- | --- |
-| 指令 | 作用域分层(组织/用户/项目/本地)+ 自动记忆 | 分层记忆是标杆实现 |
-| 工具 | 技能 + MCP + 钩子 + 子智能体四类扩展 | 职责划分清晰,是核心亮点 |
-| 环境 | 项目内设置 + settings.json | 靠用户在 CLAUDE.md 里自描述 |
-| 状态 | 追加式会话存储 + 五层压缩 + resume/fork | 极强,长任务连续性的参考实现 |
-| 反馈 | 权限分类器 + PostToolUse 钩子强制检查 | 把"防提前宣告完成"变成确定性机制 |
+| Instrucciones | Ámbitos por capas (organización/usuario/proyecto/local) + auto memory | La memoria por capas es la implementación de referencia |
+| Herramientas | Cuatro tipos de extensión: Skills + MCP + hooks + subagents | La separación clara de responsabilidades es una fortaleza esencial |
+| Entorno | Ajustes dentro del proyecto + settings.json | Depende de que los usuarios describan el entorno en CLAUDE.md |
+| Estado | Almacenamiento append-only de sessions + compaction de cinco niveles + resume/fork | Muy potente; una implementación de referencia para la continuidad de tareas largas |
+| Retroalimentación | Clasificador de permissions + comprobaciones obligatorias mediante hooks PostToolUse | Convierte la «prevención de declaraciones prematuras de finalización» en un mecanismo determinista |
## Diseños que merece la pena adoptar
diff --git a/docs/es/harness-designs/codex/index.md b/docs/es/harness-designs/codex/index.md
index 79dfcc4..a135846 100644
--- a/docs/es/harness-designs/codex/index.md
+++ b/docs/es/harness-designs/codex/index.md
@@ -47,13 +47,13 @@ Las approval policies y plan mode llevan la retroalimentación en otra direcció
## Correspondencia con el marco del curso
-| 子系统 | Codex 的实现 | 评价 |
+| Subsistema | Implementación de Codex | Evaluación |
| --- | --- | --- |
-| 指令 | AGENTS.md 目录页 + docs/ 拆分 + 执行不变量 | 教科书级,定义了"给地图不给说明书" |
-| 工具 | worktree 隔离 + spawn_agent 子智能体 | 边界靠环境硬隔离,很强 |
-| 环境 | 独立 worktree + 可观测性栈 | worktree 隔离是其招牌 |
-| 状态 | Write 策略(状态写进文件/文档) | 依赖约定而非内建记忆 |
-| 反馈 | 验证命令入规范 + 审批策略 + plan mode | 反馈路径默认化,值得抄 |
+| Instrucciones | AGENTS.md como página de índice + división en docs/ + invariantes impuestos | De manual; define «dar el mapa, no el manual» |
+| Herramientas | Aislamiento mediante worktree + subagents con spawn_agent | Límites sólidos impuestos mediante el aislamiento del entorno |
+| Entorno | Worktrees independientes + stack de observabilidad | El aislamiento mediante worktree es su seña distintiva |
+| Estado | Estrategia Write (el estado se escribe en archivos/documentación) | Depende de convenciones en lugar de memoria integrada |
+| Retroalimentación | Comandos de verificación en la especificación + approval policies + plan mode | Convierte las rutas de retroalimentación en la opción predeterminada; merece la pena adoptarlo |
La comparación entre Codex y Claude Code es interesante: Claude Code aplica la «adición», integrando en el núcleo memoria, permissions y subagents; Codex aplica la «sustracción», mantiene el núcleo lo más contenido posible y deposita más responsabilidad en las convenciones del repositorio y la ingeniería de contexto. Por eso la comunidad suele decir que «la filosofía del harness de Codex vale más que su código».
diff --git a/docs/es/harness-designs/deepseek/index.md b/docs/es/harness-designs/deepseek/index.md
index 1ded1d4..edba218 100644
--- a/docs/es/harness-designs/deepseek/index.md
+++ b/docs/es/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@ Es la aplicación más radical de la frase del curso «todo lo que queda fuera d
DeepSeek Harness representa las «capacidades» mediante Services y divide casi todas ellas en tres capas:
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
Por ejemplo, debajo de `FS Service` hay varios Providers —Local FS, E2B FS y Remote FS— que se exponen de forma uniforme hacia arriba como file tools. Shell, Subprocess, Sandbox, Web, LLM y SubAgent siguen la misma estructura. Esta organización en tres capas no es una interpretación nuestra: el texto original de [Capability seams, en la documentación de arquitectura](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md), dice que *a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool* —un capability seam es una capacidad reemplazable con tres roles: Service Definition declara la interfaz, Service Provider la implementa y Consumer la utiliza, normalmente como una herramienta expuesta al modelo—.
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(La pipeline anterior es una transcripción de la sección [Turn flow de la documentación de arquitectura](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md): `turn/*`, `step/*`, `user/message`, `assistant/*` y `tool/*` son eventos persistentes de session; `agent/pre-step`, `agent/request`, `llm/stream` y `tools/*` son puntos de extensión que pueden escuchar los plugins.)
@@ -58,13 +58,13 @@ En otras palabras, la observabilidad no es un log añadido a posteriori, sino un
## Correspondencia con el marco del curso
-| 子系统 | DeepSeek Harness 的实现 | 评价 |
+| Subsistema | Implementación de DeepSeek Harness | Evaluación |
| --- | --- | --- |
-| 指令 | 插件化;规则/技能均以插件形态注入 | 极自由,但没有内置的"CLAUDE.md"式惯例 |
-| 工具 | Service Definition → Provider → Consumer 能力接缝 | 工具子系统标准化的极致 |
-| 环境 | 沙箱/FS/Shell 全部可换 Provider(含远程 E2B) | 环境彻底可插拔 |
-| 状态 | append-only Session Event Log + Model-visible means logged | 可观测性是第一性约束 |
-| 反馈 | tools/pre-execute 上的 permission / guard / policy / hook | 反馈机制事件化 |
+| Instrucciones | Basadas en plugins; las reglas/Skills se inyectan como plugins | Extremadamente flexible, pero carece de una convención integrada como CLAUDE.md |
+| Herramientas | Service Definition → Provider → Consumer como capability seam | Estandarización extrema del subsistema de herramientas |
+| Entorno | Los Providers de sandbox/FS/Shell son reemplazables (incluido E2B remoto) | El entorno es totalmente conectable |
+| Estado | append-only Session Event Log + Model-visible means logged | La observabilidad es una restricción de primer orden |
+| Retroalimentación | permission / guard / policy / hook en tools/pre-execute | Los mecanismos de retroalimentación se basan en eventos |
La diferencia fundamental entre DeepSeek Harness y los otros tres productos es que Pi, Claude Code y Codex optimizan el harness dentro de «un agent concreto», mientras que DeepSeek Harness define el harness como un **sistema operativo independiente del modelo** y trata al propio agent como una aplicación reemplazable que se ejecuta sobre ese OS. El coste también es evidente: una mayor libertad implica un mayor coste de configuración, la otra cara inherente al diseño «harness como OS» —en la etapa de Developer Preview, su posicionamiento también es «probar pronto mientras los mecanismos siguen evolucionando»—.
diff --git a/docs/es/harness-designs/pi/index.md b/docs/es/harness-designs/pi/index.md
index 868441c..c71ed0d 100644
--- a/docs/es/harness-designs/pi/index.md
+++ b/docs/es/harness-designs/pi/index.md
@@ -63,13 +63,13 @@ El mismo repositorio comunitario lleva aún más lejos este patrón: `VISION.md`
Evaluación de Pi según los cinco subsistemas del curso —subjetiva y pensada para la comparación—:
-| 子系统 | Pi 的实现 | 评价 |
+| Subsistema | Implementación de Pi | Evaluación |
| --- | --- | --- |
-| 指令 | AGENTS.md 分级加载 + SYSTEM.md | 层级清晰,但规则本身要靠用户写 |
-| 工具 | 技能按需加载 + 扩展全生命周期钩子 | 极强,把工具系统做成了可编程面 |
-| 环境 | SYSTEM.md 做环境自描述;运行时环境靠用户在 AGENTS.md 里声明 | 机制是开放的,但可复现性依赖用户自述 |
-| 状态 | 会话树 + 压缩可定制 + PROGRESS.md | 极强,跨会话与可恢复性是其核心 |
-| 反馈 | 验证命令靠用户定义;session-summary / extract-patterns 机制化 | 机制提供,内容靠用户 |
+| Instrucciones | Carga jerárquica de AGENTS.md + SYSTEM.md | Jerarquía clara, pero los usuarios deben escribir las reglas |
+| Herramientas | Skills bajo demanda + hooks de Extensions para todo el ciclo de vida | Muy potente; convierte el sistema de herramientas en una superficie programable |
+| Entorno | SYSTEM.md para la autodescripción del entorno; los usuarios declaran el entorno de ejecución en AGENTS.md | El mecanismo es abierto, pero la reproducibilidad depende de las descripciones escritas por los usuarios |
+| Estado | Árbol de sessions + compaction personalizable + PROGRESS.md | Muy potente; la continuidad entre sessions y la recuperabilidad son fundamentales |
+| Retroalimentación | Comandos de verificación definidos por el usuario; mecanismos estructurados de session-summary / extract-patterns | Se proporciona el mecanismo; los usuarios aportan el contenido |
La elección de Pi contrasta claramente con Claude Code y Codex: Claude Code integra en el núcleo la «memoria, permissions y subagents» para que funcionen de inmediato; Codex convierte las «convenciones del repositorio y el aislamiento del entorno» en valores predeterminados; Pi opta por **no decidir nada por ti** y convierte cada decisión en un punto de extensión. El precio es que tendrás que escribir tus propias Extensions o instalar paquetes creados por otros.
diff --git a/docs/fr/harness-designs/claude-code/index.md b/docs/fr/harness-designs/claude-code/index.md
index c53751c..28638ff 100644
--- a/docs/fr/harness-designs/claude-code/index.md
+++ b/docs/fr/harness-designs/claude-code/index.md
@@ -59,13 +59,13 @@ Les logs complets de Claude Code sont append-only (history.jsonl). Avec les comm
## Correspondance avec le cadre du cours
-| 子系统 | Claude Code 的实现 | 评价 |
+| Sous-système | Implémentation dans Claude Code | Évaluation |
| --- | --- | --- |
-| 指令 | 作用域分层(组织/用户/项目/本地)+ 自动记忆 | 分层记忆是标杆实现 |
-| 工具 | 技能 + MCP + 钩子 + 子智能体四类扩展 | 职责划分清晰,是核心亮点 |
-| 环境 | 项目内设置 + settings.json | 靠用户在 CLAUDE.md 里自描述 |
-| 状态 | 追加式会话存储 + 五层压缩 + resume/fork | 极强,长任务连续性的参考实现 |
-| 反馈 | 权限分类器 + PostToolUse 钩子强制检查 | 把"防提前宣告完成"变成确定性机制 |
+| Instructions | Hiérarchisation par portée (organisation/utilisateur/projet/local) + mémoire automatique | La mémoire hiérarchisée constitue une implémentation de référence |
+| Outils | Quatre types d’extensions : Skills + MCP + hooks + subagents | La séparation claire des responsabilités est un atout majeur |
+| Environnement | Paramètres du projet + settings.json | L’utilisateur doit le décrire lui-même dans CLAUDE.md |
+| État | Stockage append-only des sessions + compaction à cinq niveaux + resume/fork | Extrêmement puissant, une implémentation de référence pour la continuité des tâches longues |
+| Retour | Classificateur de permissions + contrôle imposé par le hook PostToolUse | Transforme la prévention des annonces prématurées de réussite en mécanisme déterministe |
## Conceptions à retenir
@@ -79,10 +79,10 @@ Les logs complets de Claude Code sont append-only (history.jsonl). Avec les comm
Chaque affirmation peut être reliée aux textes originaux ou au code source ci-dessous, afin d’éviter toute reformulation fondée sur de simples impressions :
-- **Claude Code 官方文档 · Memory** : nouveau contexte à chaque session, quatre portées de CLAUDE.md, chargement à la demande des sous-répertoires, auto memory — 200 lignes / 25KB — et génération de CLAUDE.md par `/init`.<br/>https://code.claude.com/docs/en/memory
-- **Claude Code 官方文档 · Skills / MCP / Hooks / Sub-agents** : définition des quatre mécanismes d’extension et événements PreToolUse / PostToolUse / Stop.<br/>https://code.claude.com/docs/en/skills | https://code.claude.com/docs/en/mcp | https://code.claude.com/docs/en/hooks | https://code.claude.com/docs/en/sub-agents
-- **VILA Lab《Dive into Claude Code》**(源码级拆解报告) : pipeline de compaction à cinq niveaux, sept modes de permissions avec classificateur ML, subagents sidechain et stockage de session append-only dans history.jsonl.<br/>https://zhiqiangshen.com/projects/Claude_Code_Report/Claude_Code_Report.pdf
-- **Anthropic《Effective harnesses for long-running agents》** : origine des idées selon lesquelles « la fiabilité vient du harness, et non du modèle », les agents vantent leur travail avec assurance et les hooks doivent assurer la vérification.<br/>https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents
-- **Claude Code Full Stack 导读**(社区,CLAUDE.md / Skills / MCP / Subagents / Hooks 分层) : lecture complémentaire sur la séparation des responsabilités entre mécanismes d’extension.<br/>https://jsmanifest.com/claude-code-full-stack-guide
+- **Documentation officielle de Claude Code · Memory** : nouveau contexte à chaque session, quatre portées de CLAUDE.md, chargement à la demande des sous-répertoires, auto memory — 200 lignes / 25KB — et génération de CLAUDE.md par `/init`.<br/>https://code.claude.com/docs/en/memory
+- **Documentation officielle de Claude Code · Skills / MCP / Hooks / Sub-agents** : définition des quatre mécanismes d’extension et événements PreToolUse / PostToolUse / Stop.<br/>https://code.claude.com/docs/en/skills | https://code.claude.com/docs/en/mcp | https://code.claude.com/docs/en/hooks | https://code.claude.com/docs/en/sub-agents
+- **VILA Lab « Dive into Claude Code »** (rapport d’analyse au niveau du code source) : pipeline de compaction à cinq niveaux, sept modes de permissions avec classificateur ML, subagents sidechain et stockage de session append-only dans history.jsonl.<br/>https://zhiqiangshen.com/projects/Claude_Code_Report/Claude_Code_Report.pdf
+- **Anthropic « Effective harnesses for long-running agents »** : origine des idées selon lesquelles « la fiabilité vient du harness, et non du modèle », les agents vantent leur travail avec assurance et les hooks doivent assurer la vérification.<br/>https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents
+- **Guide de lecture de Claude Code Full Stack** (communauté, hiérarchisation de CLAUDE.md / Skills / MCP / Subagents / Hooks) : lecture complémentaire sur la séparation des responsabilités entre mécanismes d’extension.<br/>https://jsmanifest.com/claude-code-full-stack-guide
Cours associés : [Leçon 03 · Faire du dépôt la source unique de vérité](../lectures/lecture-03-why-the-repository-must-become-the-system-of-record/) | [Leçon 09 · Empêcher l’agent d’annoncer prématurément sa réussite](../lectures/lecture-09-why-agents-declare-victory-too-early/) | [Leçon 10 · Seul le flux complet constitue une véritable vérification](../lectures/lecture-10-why-end-to-end-testing-changes-results/)
diff --git a/docs/fr/harness-designs/codex/index.md b/docs/fr/harness-designs/codex/index.md
index 4f4753f..33af3ff 100644
--- a/docs/fr/harness-designs/codex/index.md
+++ b/docs/fr/harness-designs/codex/index.md
@@ -47,13 +47,13 @@ Les approval policies et le plan mode apportent un autre type de feedback : prod
## Correspondance avec le cadre du cours
-| 子系统 | Codex 的实现 | 评价 |
+| Sous-système | Implémentation dans Codex | Évaluation |
| --- | --- | --- |
-| 指令 | AGENTS.md 目录页 + docs/ 拆分 + 执行不变量 | 教科书级,定义了"给地图不给说明书" |
-| 工具 | worktree 隔离 + spawn_agent 子智能体 | 边界靠环境硬隔离,很强 |
-| 环境 | 独立 worktree + 可观测性栈 | worktree 隔离是其招牌 |
-| 状态 | Write 策略(状态写进文件/文档) | 依赖约定而非内建记忆 |
-| 反馈 | 验证命令入规范 + 审批策略 + plan mode | 反馈路径默认化,值得抄 |
+| Instructions | AGENTS.md comme page d’index + découpage dans docs/ + invariants d’exécution | Exemplaire : le principe « donner une carte, pas un manuel » y est défini |
+| Outils | Isolation par worktree + subagents spawn_agent | Frontières imposées par une forte isolation de l’environnement |
+| Environnement | worktree indépendant + stack d’observabilité | L’isolation par worktree est sa marque distinctive |
+| État | Stratégie Write (l’état est écrit dans des fichiers ou des documents) | Repose sur des conventions plutôt que sur une mémoire intégrée |
+| Retour | Commandes de vérification intégrées aux conventions + approval policies + plan mode | Le parcours de retour est fourni par défaut, un modèle à reprendre |
La comparaison entre Codex et Claude Code est révélatrice : Claude Code procède par « addition », en intégrant au noyau mémoire, permissions et subagents ; Codex procède par « soustraction », en gardant un noyau aussi sobre que possible et en reportant davantage de responsabilités sur les conventions du dépôt et l’ingénierie du contexte. C’est pourquoi la communauté dit souvent que « la philosophie du harness de Codex vaut davantage que son code ».
@@ -69,10 +69,10 @@ La comparaison entre Codex et Claude Code est révélatrice : Claude Code procè
Chaque affirmation peut être reliée aux textes originaux ou au code source ci-dessous, afin d’éviter toute reformulation fondée sur de simples impressions :
-- **OpenAI《Harness Engineering》** : AGENTS.md comme page d’index et recommandation d’environ 100 lignes, executive invariants / don't micromanage, isolation par worktree avec stack d’observabilité, commandes de vérification intégrées aux conventions, exemple du produit de plus d’un million de lignes, approval policies et plan mode. Source principale de toutes les affirmations essentielles de cet article.<br/>https://openai.com/index/harness-engineering/
-- **OpenAI 官方《AGENTS.md》规范** (AGENTS.md comme convention standard entre outils) :<br/>https://openai.com/index/agents-md/
-- **Codex CLI 开源仓库** (binaire monolithique écrit en Rust) :<br/>https://github.com/openai/codex
-- **Context Engineering for Codex CLI**(社区) : cadre Write-Select-Compress-Isolate, `/compact` et `compact_prompt`, subagents `spawn_agent` / `wait_agent` et configuration `.codex/agents/*.toml`.<br/>https://codex.danielvaughan.com/2026/06/10/context-engineering-codex-cli-write-select-compress-isolate-june-2026/
-- **codex-harness-internals**(社区源码分析) : détails d’implémentation, dont le contexte environnemental incrémental de `build_environment_update_item`.<br/>https://github.com/AlexKenbo/codex-harness-internals
+- **OpenAI « Harness Engineering »** : AGENTS.md comme page d’index et recommandation d’environ 100 lignes, executive invariants / don't micromanage, isolation par worktree avec stack d’observabilité, commandes de vérification intégrées aux conventions, exemple du produit de plus d’un million de lignes, approval policies et plan mode. Source principale de toutes les affirmations essentielles de cet article.<br/>https://openai.com/index/harness-engineering/
+- **Spécification officielle d’OpenAI « AGENTS.md »** (AGENTS.md comme convention standard entre outils) :<br/>https://openai.com/index/agents-md/
+- **Dépôt open source de Codex CLI** (binaire monolithique écrit en Rust) :<br/>https://github.com/openai/codex
+- **Context Engineering for Codex CLI** (communauté) : cadre Write-Select-Compress-Isolate, `/compact` et `compact_prompt`, subagents `spawn_agent` / `wait_agent` et configuration `.codex/agents/*.toml`.<br/>https://codex.danielvaughan.com/2026/06/10/context-engineering-codex-cli-write-select-compress-isolate-june-2026/
+- **codex-harness-internals** (analyse communautaire du code source) : détails d’implémentation, dont le contexte environnemental incrémental de `build_environment_update_item`.<br/>https://github.com/AlexKenbo/codex-harness-internals
Cours associés : [Leçon 03 · Faire du dépôt la source unique de vérité](../lectures/lecture-03-why-the-repository-must-become-the-system-of-record/) | [Leçon 04 · Répartir les instructions entre plusieurs fichiers](../lectures/lecture-04-why-one-giant-instruction-file-fails/) | [Leçon 07 · Délimiter clairement chaque tâche de l’agent](../lectures/lecture-07-why-agents-overreach-and-under-finish/)
diff --git a/docs/fr/harness-designs/deepseek/index.md b/docs/fr/harness-designs/deepseek/index.md
index 5624afc..035737a 100644
--- a/docs/fr/harness-designs/deepseek/index.md
+++ b/docs/fr/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@ C’est l’application la plus radicale de l’idée du cours selon laquelle «
DeepSeek Harness représente une « capacité » par un Service et décompose presque toutes les capacités en trois couches :
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
Prenons le système de fichiers : sous `FS Service` se trouvent plusieurs Providers — Local FS, E2B FS et Remote FS — qui exposent vers le haut une interface uniforme sous forme de file tools. Shell, Subprocess, Sandbox, Web, LLM et SubAgent suivent tous la même structure. Cette architecture à trois couches n’est pas notre interprétation : la section [Capability seams de la documentation d’architecture](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) la définit ainsi : *a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool* (une capability seam est une capacité remplaçable qui réunit trois rôles : une Service Definition qui déclare l’interface, un Service Provider qui l’implémente et un Consumer qui l’utilise, généralement un outil exposé au modèle).
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(Le pipeline ci-dessus retranscrit la section [Turn flow de la documentation d’architecture](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) : `turn/*`, `step/*`, `user/message`, `assistant/*` et `tool/*` sont des événements de session persistants ; `agent/pre-step`, `agent/request`, `llm/stream` et `tools/*` sont des points d’extension que les plugins peuvent écouter.)
@@ -56,13 +56,13 @@ Autrement dit, l’observabilité n’est pas un log ajouté après coup, mais u
## Correspondance avec le cadre du cours
-| 子系统 | DeepSeek Harness 的实现 | 评价 |
+| Sous-système | Implémentation dans DeepSeek Harness | Évaluation |
| --- | --- | --- |
-| 指令 | 插件化;规则/技能均以插件形态注入 | 极自由,但没有内置的"CLAUDE.md"式惯例 |
-| 工具 | Service Definition → Provider → Consumer 能力接缝 | 工具子系统标准化的极致 |
-| 环境 | 沙箱/FS/Shell 全部可换 Provider(含远程 E2B) | 环境彻底可插拔 |
-| 状态 | append-only Session Event Log + Model-visible means logged | 可观测性是第一性约束 |
-| 反馈 | tools/pre-execute 上的 permission / guard / policy / hook | 反馈机制事件化 |
+| Instructions | Architecture par plugins ; règles et Skills injectées sous forme de plugins | Très grande liberté, mais aucune convention intégrée de type « CLAUDE.md » |
+| Outils | Jonction de capacité Service Definition → Provider → Consumer | Standardisation poussée à l’extrême du sous-système d’outils |
+| Environnement | Providers interchangeables pour le sandbox, FS et Shell, y compris E2B à distance | Environnement entièrement interchangeable |
+| État | append-only Session Event Log + Model-visible means logged | L’observabilité est une contrainte de premier principe |
+| Retour | permission / guard / policy / hook sur tools/pre-execute | Le mécanisme de retour repose sur des événements |
La différence fondamentale entre DeepSeek Harness et les trois autres produits est la suivante : Pi, Claude Code et Codex optimisent tous le harness « à l’intérieur d’un agent particulier » ; DeepSeek Harness, lui, définit le harness comme un **système d’exploitation indépendant du modèle**, l’agent n’étant qu’une application remplaçable exécutée sur cet OS. Le compromis est évident : une plus grande liberté entraîne un coût de configuration plus élevé, revers inhérent à cette conception du « harness comme OS » (la Developer Preview se présente d’ailleurs comme une première expérimentation de mécanismes encore en évolution).
@@ -77,9 +77,9 @@ La différence fondamentale entre DeepSeek Harness et les trois autres produits
Chaque affirmation peut être reliée aux textes originaux ou au code source ci-dessous, afin d’éviter toute reformulation fondée sur de simples impressions :
-- **DeepSeek Harness 官网** : définition du produit « Agent = Model + Environment + Tools + State », positionnement Developer Preview et commande `dsh`.<br/>https://deepseek.com/harness
-- **deepseek-ai/deepseek-harness 仓库** (commande `dsh`, licence MIT) :<br/>https://github.com/deepseek-ai/deepseek-harness
-- **架构文档 architecture.md** : source principale de cet article — « Every part of the product is a plugin », « There is no privileged core to patch », event pipeline Turn flow, trois rôles des Capability seams, « Model-visible means logged » et son runtime invariant, Session Event Log append-only, capability seams fs/tools/telemetry et sous-systèmes `ctx.*`.<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md
-- **架构文档 · 配套子文档** : présentation du noyau Cordis (plugins contribute services, typed events, reversible effects), détail des capability seams et sous-système Session.<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/cordis-primer.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/capability-seams.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/subsystems/session.md
+- **Site officiel de DeepSeek Harness** : définition du produit « Agent = Model + Environment + Tools + State », positionnement Developer Preview et commande `dsh`.<br/>https://deepseek.com/harness
+- **Dépôt deepseek-ai/deepseek-harness** (commande `dsh`, licence MIT) :<br/>https://github.com/deepseek-ai/deepseek-harness
+- **Documentation d’architecture architecture.md** : source principale de cet article — « Every part of the product is a plugin », « There is no privileged core to patch », event pipeline Turn flow, trois rôles des Capability seams, « Model-visible means logged » et son runtime invariant, Session Event Log append-only, capability seams fs/tools/telemetry et sous-systèmes `ctx.*`.<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md
+- **Documentation d’architecture · Documents complémentaires** : présentation du noyau Cordis (plugins contribute services, typed events, reversible effects), détail des capability seams et sous-système Session.<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/cordis-primer.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/capability-seams.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/subsystems/session.md
Cours associés : [Leçon 11 · Intégrer l’observabilité au cœur du harness](../lectures/lecture-11-why-observability-belongs-inside-the-harness/) | [Leçon 12 · Laisser un état propre à la fin de chaque session](../lectures/lecture-12-why-every-session-must-leave-a-clean-state/) | [Leçon 02 · Ce qu’est réellement un harness](../lectures/lecture-02-what-a-harness-actually-is/)
diff --git a/docs/fr/harness-designs/pi/index.md b/docs/fr/harness-designs/pi/index.md
index b5c8e3a..ac02e03 100644
--- a/docs/fr/harness-designs/pi/index.md
+++ b/docs/fr/harness-designs/pi/index.md
@@ -63,13 +63,13 @@ Le même dépôt communautaire confirme ce modèle : `VISION.md` (objectif), `PR
Évaluation de Pi selon les cinq sous-systèmes du cours (subjective, à titre comparatif) :
-| 子系统 | Pi 的实现 | 评价 |
+| Sous-système | Implémentation dans Pi | Évaluation |
| --- | --- | --- |
-| 指令 | AGENTS.md 分级加载 + SYSTEM.md | 层级清晰,但规则本身要靠用户写 |
-| 工具 | 技能按需加载 + 扩展全生命周期钩子 | 极强,把工具系统做成了可编程面 |
-| 环境 | SYSTEM.md 做环境自描述;运行时环境靠用户在 AGENTS.md 里声明 | 机制是开放的,但可复现性依赖用户自述 |
-| 状态 | 会话树 + 压缩可定制 + PROGRESS.md | 极强,跨会话与可恢复性是其核心 |
-| 反馈 | 验证命令靠用户定义;session-summary / extract-patterns 机制化 | 机制提供,内容靠用户 |
+| Instructions | Chargement hiérarchique d’AGENTS.md + SYSTEM.md | Hiérarchie claire, mais les règles elles-mêmes doivent être rédigées par l’utilisateur |
+| Outils | Chargement des Skills à la demande + hooks couvrant tout le cycle de vie des extensions | Extrêmement puissant : le système d’outils devient une surface programmable |
+| Environnement | SYSTEM.md assure l’auto-description de l’environnement ; l’environnement d’exécution doit être déclaré par l’utilisateur dans AGENTS.md | Le mécanisme est ouvert, mais la reproductibilité dépend de la description fournie par l’utilisateur |
+| État | Arbre de sessions + compaction personnalisable + PROGRESS.md | Extrêmement puissant : la continuité entre sessions et la reprise sont au cœur du système |
+| Retour | Commandes de vérification définies par l’utilisateur ; mécanismes session-summary / extract-patterns | Le mécanisme est fourni, le contenu revient à l’utilisateur |
Le compromis choisi par Pi contraste fortement avec Claude Code et Codex : Claude Code intègre directement au noyau la mémoire, les permissions et les subagents, prêts à l’emploi ; Codex fait des conventions du dépôt et de l’isolation de l’environnement ses valeurs par défaut ; Pi choisit de **ne rien décider à votre place** et transforme le pouvoir de décision en points d’extension. En contrepartie, vous devez soit écrire vos propres extensions, soit installer les packages d’autres développeurs.
@@ -84,11 +84,11 @@ Le compromis choisi par Pi contraste fortement avec Claude Code et Codex : Claud
Chaque affirmation peut être reliée aux textes originaux ou au code source ci-dessous, afin d’éviter toute reformulation fondée sur de simples impressions :
-- **pi.dev 官网** : formulation du positionnement « Ask Pi to build what you want, or install a package that does it your way », quatre couches personnalisables, arbre de sessions (« sessions are stored as trees », `/tree`, enregistrement dans un seul fichier, export HTML et partage par gist).<br/>https://pi.dev/
-- **pi.dev 官方文档 · Sessions** : compaction interchangeable — topic-based, code-aware ou autre modèle de résumé —, mécanismes de compaction automatique et d’injection dynamique du contexte.<br/>https://pi.dev/docs/usage/sessions
-- **pi.dev 官方文档 · Extensions** : les extensions peuvent injecter des messages avant chaque étape de raisonnement, filtrer l’historique, effectuer un RAG et construire une mémoire à long terme.<br/>https://pi.dev/docs/usage/extensions
-- **pi.dev 官方文档 · Project Context** : sémantique replace / append de SYSTEM.md.<br/>https://pi.dev/docs/usage/project-context
-- **Pi Coding Agent 源码 README**(badlogic/pi-mono) : ordre de chargement à trois niveaux d’AGENTS.md — global → répertoires parents → répertoire courant —, conditions de déclenchement de `/compact` et de la compaction automatique avec point de coupure à 20 000 tokens, chargement à la demande des Skills et standard Agent Skills, cycle de vie des Hooks et exemples d’usage officiels, Programmatic Usage — JSON / RPC / SDK.<br/>https://github.com/badlogic/pi-mono/blob/main/packages/coding-agent/README.md
-- **pi-agent-harness 社区仓库** : extensions skill-router / session-summary / extract-patterns / telemetry et organisation des fichiers VISION.md / PROGRESS.md / LESSONS.md / STANDARDS.md.<br/>https://github.com/LabidySabidy/pi-agent-harness
+- **Site officiel de pi.dev** : formulation du positionnement « Ask Pi to build what you want, or install a package that does it your way », quatre couches personnalisables, arbre de sessions (« sessions are stored as trees », `/tree`, enregistrement dans un seul fichier, export HTML et partage par gist).<br/>https://pi.dev/
+- **Documentation officielle de pi.dev · Sessions** : compaction interchangeable — topic-based, code-aware ou autre modèle de résumé —, mécanismes de compaction automatique et d’injection dynamique du contexte.<br/>https://pi.dev/docs/usage/sessions
+- **Documentation officielle de pi.dev · Extensions** : les extensions peuvent injecter des messages avant chaque étape de raisonnement, filtrer l’historique, effectuer un RAG et construire une mémoire à long terme.<br/>https://pi.dev/docs/usage/extensions
+- **Documentation officielle de pi.dev · Project Context** : sémantique replace / append de SYSTEM.md.<br/>https://pi.dev/docs/usage/project-context
+- **README du code source de Pi Coding Agent** (badlogic/pi-mono) : ordre de chargement à trois niveaux d’AGENTS.md — global → répertoires parents → répertoire courant —, conditions de déclenchement de `/compact` et de la compaction automatique avec point de coupure à 20 000 tokens, chargement à la demande des Skills et standard Agent Skills, cycle de vie des Hooks et exemples d’usage officiels, Programmatic Usage — JSON / RPC / SDK.<br/>https://github.com/badlogic/pi-mono/blob/main/packages/coding-agent/README.md
+- **Dépôt communautaire pi-agent-harness** : extensions skill-router / session-summary / extract-patterns / telemetry et organisation des fichiers VISION.md / PROGRESS.md / LESSONS.md / STANDARDS.md.<br/>https://github.com/LabidySabidy/pi-agent-harness
Cours associés : [Leçon 02 · Ce qu’est réellement un harness](../lectures/lecture-02-what-a-harness-actually-is/) | [Leçon 05 · Préserver la continuité du contexte dans les tâches longues](../lectures/lecture-05-why-long-running-tasks-lose-continuity/) | [Leçon 13 · Passer du pilotage manuel à la boucle automatisée](../lectures/lecture-13-loop-engineering/)
diff --git a/docs/ja/harness-designs/deepseek/index.md b/docs/ja/harness-designs/deepseek/index.md
index 6b734f0..c049564 100644
--- a/docs/ja/harness-designs/deepseek/index.md
+++ b/docs/ja/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@
DeepSeek Harness は「能力」を Service として表し、ほぼすべての能力を3層に分けています。
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
ファイルシステムを例にすると、`FS Service` の下には Local FS、E2B FS、Remote FS という複数の Provider があり、上位には統一された file tools として公開されます。Shell、Subprocess、Sandbox、Web、LLM、SubAgent も同じ構造です。この3層構造は、私たちの要約ではありません。[アーキテクチャドキュメント · Capability seams](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md)の原文に、*a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool*(capability seam は交換可能な能力であり、インターフェースを宣言する Service Definition、それを実装する Service Provider、それを使用する Consumer という3つの役割を持つ。Consumer は通常、モデル向けのツールである)とあります。
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(上記の pipeline は、[アーキテクチャドキュメント · Turn flow](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md)セクションの内容を書き換えたものです。`turn/*`、`step/*`、`user/message`、`assistant/*`、`tool/*` は永続化される session イベントであり、`agent/pre-step`、`agent/request`、`llm/stream`、`tools/*` は plugin が監視できる拡張点です。)
diff --git a/docs/ko/harness-designs/deepseek/index.md b/docs/ko/harness-designs/deepseek/index.md
index 4a85827..a56d4bf 100644
--- a/docs/ko/harness-designs/deepseek/index.md
+++ b/docs/ko/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@
DeepSeek Harness는 "능력"을 Service로 표현하며, 거의 모든 능력을 세 계층으로 나눕니다.
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
파일 시스템을 예로 들면, `FS Service` 아래에 Local FS, E2B FS, Remote FS 등의 Provider가 있고 위쪽에는 통일된 file tools로 노출됩니다. Shell, Subprocess, Sandbox, Web, LLM, SubAgent도 같은 구조를 사용합니다. 이 3계층 구조는 여기서 요약한 것이 아닙니다. [아키텍처 문서 · Capability seams](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md)의 원문은 *a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool*(능력 접합부는 교체 가능한 능력으로서 세 가지 역할, 즉 인터페이스를 선언하는 Service Definition, 이를 구현하는 Service Provider, 이를 사용하는 Consumer로 구성되며, Consumer는 일반적으로 모델에 노출되는 도구임)입니다.
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(위 파이프라인은 [아키텍처 문서 · Turn flow](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) 섹션을 옮긴 것입니다. `turn/*`, `step/*`, `user/message`, `assistant/*`, `tool/*`는 영속화되는 session 이벤트이며, `agent/pre-step`, `agent/request`, `llm/stream`, `tools/*`는 plugin이 수신할 수 있는 확장 지점입니다.)
diff --git a/docs/pt-BR/harness-designs/deepseek/index.md b/docs/pt-BR/harness-designs/deepseek/index.md
index 3c3fa17..431fca1 100644
--- a/docs/pt-BR/harness-designs/deepseek/index.md
+++ b/docs/pt-BR/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@ A estrutura tradicional de um coding agent é "LLM + loop de agent fixo + conjun
O DeepSeek Harness representa "capacidades" por meio de Service e divide quase todas elas em três camadas:
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
Tomando o sistema de arquivos como exemplo: sob `FS Service`, existem vários Provider — Local FS, E2B FS e Remote FS — expostos de maneira uniforme como file tools. Shell, Subprocess, Sandbox, Web, LLM e SubAgent seguem a mesma estrutura. Essa arquitetura de três camadas não é uma interpretação nossa. A seção [Capability seams da documentação de arquitetura](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) diz: *a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool* (uma interface de capacidade é uma capacidade substituível com três papéis: um Service Definition que declara a interface, um Service Provider que a implementa e um Consumer que a utiliza, normalmente uma ferramenta exposta ao modelo).
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(O pipeline acima é uma transcrição da seção [Turn flow da documentação de arquitetura](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md): `turn/*`, `step/*`, `user/message`, `assistant/*` e `tool/*` são eventos persistentes de sessão; `agent/pre-step`, `agent/request`, `llm/stream` e `tools/*` são pontos de extensão observáveis por plugins.)
diff --git a/docs/ru/harness-designs/claude-code/index.md b/docs/ru/harness-designs/claude-code/index.md
index 6ba5f99..2a190d1 100644
--- a/docs/ru/harness-designs/claude-code/index.md
+++ b/docs/ru/harness-designs/claude-code/index.md
@@ -59,13 +59,13 @@ Claude Code разделяет поверхность расширения на
## Сопоставление с фреймворком курса
-| 子系统 | Claude Code 的实现 | 评价 |
+| Подсистема | Реализация Claude Code | Оценка |
| --- | --- | --- |
-| 指令 | 作用域分层(组织/用户/项目/本地)+ 自动记忆 | 分层记忆是标杆实现 |
-| 工具 | 技能 + MCP + 钩子 + 子智能体四类扩展 | 职责划分清晰,是核心亮点 |
-| 环境 | 项目内设置 + settings.json | 靠用户在 CLAUDE.md 里自描述 |
-| 状态 | 追加式会话存储 + 五层压缩 + resume/fork | 极强,长任务连续性的参考实现 |
-| 反馈 | 权限分类器 + PostToolUse 钩子强制检查 | 把"防提前宣告完成"变成确定性机制 |
+| Инструкции | Иерархия областей действия (организация/пользователь/проект/локальная среда) + auto memory | Многоуровневая память — эталонная реализация |
+| Инструменты | Четыре типа расширений: skills + MCP + hooks + subagents | Чёткое разделение ответственности — ключевое преимущество |
+| Среда | Настройки проекта + settings.json | Пользователь самостоятельно описывает её в CLAUDE.md |
+| Состояние | Дописываемое хранилище session + пятиуровневая compaction + resume/fork | Очень мощная реализация и ориентир для непрерывности длительных задач |
+| Обратная связь | Классификатор permissions + принудительные проверки через hook PostToolUse | Превращает предотвращение преждевременного объявления о завершении в детерминированный механизм |
## Дизайнерские решения, которые стоит перенять
@@ -79,10 +79,10 @@ Claude Code разделяет поверхность расширения на
Каждое утверждение можно проверить по приведённому ниже оригинальному материалу или исходному коду — мы не пересказываем по памяти:
-- **Claude Code 官方文档 · Memory**: новый контекст для каждой session, четыре области действия CLAUDE.md, загрузка по требованию из подкаталогов, auto memory (200 строк / 25KB), создание CLAUDE.md командой `/init`.<br/>https://code.claude.com/docs/en/memory
-- **Claude Code 官方文档 · Skills / MCP / Hooks / Sub-agents**: определения четырёх механизмов расширения и событий (PreToolUse / PostToolUse / Stop).<br/>https://code.claude.com/docs/en/skills | https://code.claude.com/docs/en/mcp | https://code.claude.com/docs/en/hooks | https://code.claude.com/docs/en/sub-agents
-- **VILA Lab《Dive into Claude Code》** (отчёт с разбором исходного кода): пятиуровневый конвейер compaction, семь режимов permissions + ML-классификатор, sidechain для subagent и дописываемое хранилище session history.jsonl.<br/>https://zhiqiangshen.com/projects/Claude_Code_Report/Claude_Code_Report.pdf
-- **Anthropic《Effective harnesses for long-running agents》**: источник тезисов «надёжность обеспечивает harness, а не модель», о склонности agent уверенно хвалить собственную работу и об использовании hooks для верификации.<br/>https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents
-- **Claude Code Full Stack 导读** (сообщество; разделение CLAUDE.md / Skills / MCP / Subagents / Hooks): дополнительное чтение о разделении ответственности между механизмами расширения.<br/>https://jsmanifest.com/claude-code-full-stack-guide
+- **Официальная документация Claude Code · Memory**: новый контекст для каждой session, четыре области действия CLAUDE.md, загрузка по требованию из подкаталогов, auto memory (200 строк / 25KB), создание CLAUDE.md командой `/init`.<br/>https://code.claude.com/docs/en/memory
+- **Официальная документация Claude Code · Skills / MCP / Hooks / Sub-agents**: определения четырёх механизмов расширения и событий (PreToolUse / PostToolUse / Stop).<br/>https://code.claude.com/docs/en/skills | https://code.claude.com/docs/en/mcp | https://code.claude.com/docs/en/hooks | https://code.claude.com/docs/en/sub-agents
+- **VILA Lab «Dive into Claude Code»** (отчёт с разбором исходного кода): пятиуровневый конвейер compaction, семь режимов permissions + ML-классификатор, sidechain для subagent и дописываемое хранилище session history.jsonl.<br/>https://zhiqiangshen.com/projects/Claude_Code_Report/Claude_Code_Report.pdf
+- **Anthropic «Effective harnesses for long-running agents»**: источник тезисов «надёжность обеспечивает harness, а не модель», о склонности agent уверенно хвалить собственную работу и об использовании hooks для верификации.<br/>https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents
+- **Обзор Claude Code Full Stack** (сообщество; разделение CLAUDE.md / Skills / MCP / Subagents / Hooks): дополнительное чтение о разделении ответственности между механизмами расширения.<br/>https://jsmanifest.com/claude-code-full-stack-guide
Связанные лекции: [лекция 3 «Как сделать репозиторий единственным источником истины»](../lectures/lecture-03-why-the-repository-must-become-the-system-of-record/) | [лекция 9 «Как не дать agent преждевременно объявить о победе»](../lectures/lecture-09-why-agents-declare-victory-too-early/) | [лекция 10 «Настоящая верификация требует прохождения полного процесса»](../lectures/lecture-10-why-end-to-end-testing-changes-results/)
diff --git a/docs/ru/harness-designs/codex/index.md b/docs/ru/harness-designs/codex/index.md
index e9881c8..b8a703e 100644
--- a/docs/ru/harness-designs/codex/index.md
+++ b/docs/ru/harness-designs/codex/index.md
@@ -47,13 +47,13 @@
## Сопоставление с фреймворком курса
-| 子系统 | Codex 的实现 | 评价 |
+| Подсистема | Реализация Codex | Оценка |
| --- | --- | --- |
-| 指令 | AGENTS.md 目录页 + docs/ 拆分 + 执行不变量 | 教科书级,定义了"给地图不给说明书" |
-| 工具 | worktree 隔离 + spawn_agent 子智能体 | 边界靠环境硬隔离,很强 |
-| 环境 | 独立 worktree + 可观测性栈 | worktree 隔离是其招牌 |
-| 状态 | Write 策略(状态写进文件/文档) | 依赖约定而非内建记忆 |
-| 反馈 | 验证命令入规范 + 审批策略 + plan mode | 反馈路径默认化,值得抄 |
+| Инструкции | AGENTS.md как страница-оглавление + разделение по docs/ + инварианты выполнения | Эталонная реализация принципа «дайте карту, а не инструкцию» |
+| Инструменты | Изоляция worktree + subagent через spawn_agent | Границы жёстко изолированы средой; очень мощная реализация |
+| Среда | Отдельный worktree + стек наблюдаемости | Изоляция worktree — отличительная черта Codex |
+| Состояние | Стратегия Write (состояние записывается в файлы и документацию) | Опирается на соглашения, а не на встроенную память |
+| Обратная связь | Команды верификации в стандарте + политики подтверждения + plan mode | Путь обратной связи задан по умолчанию и заслуживает заимствования |
Сравнение Codex и Claude Code особенно интересно. Claude Code следует «сложению», встраивая память, permissions и subagent в ядро. Codex следует «вычитанию»: ядро остаётся сдержанным, а больше ответственности возлагается на соглашения репозитория и инженерию контекста. Поэтому сообщество часто говорит, что «философия harness в Codex ценнее его кода».
@@ -69,9 +69,9 @@
Каждое утверждение можно проверить по приведённому ниже оригинальному материалу или исходному коду — мы не пересказываем по памяти:
-- **OpenAI《Harness Engineering》**: AGENTS.md как страница-оглавление и рекомендация примерно 100 строк, executive invariants / don't micromanage, изоляция worktree + стек наблюдаемости, включение команд верификации в стандарт, пример продукта объёмом более миллиона строк, политики подтверждения и plan mode. Основной источник всех ключевых тезисов статьи.<br/>https://openai.com/index/harness-engineering/
-- **OpenAI 官方《AGENTS.md》规范** (AGENTS.md как стандарт соглашений между инструментами):<br/>https://openai.com/index/agents-md/
-- **Codex CLI 开源仓库** (монолитный бинарный файл, реализованный на Rust):<br/>https://github.com/openai/codex
+- **OpenAI «Harness Engineering»**: AGENTS.md как страница-оглавление и рекомендация примерно 100 строк, executive invariants / don't micromanage, изоляция worktree + стек наблюдаемости, включение команд верификации в стандарт, пример продукта объёмом более миллиона строк, политики подтверждения и plan mode. Основной источник всех ключевых тезисов статьи.<br/>https://openai.com/index/harness-engineering/
+- **Официальная спецификация OpenAI «AGENTS.md»** (AGENTS.md как стандарт соглашений между инструментами):<br/>https://openai.com/index/agents-md/
+- **Репозиторий исходного кода Codex CLI** (монолитный бинарный файл, реализованный на Rust):<br/>https://github.com/openai/codex
- **Context Engineering for Codex CLI** (сообщество): фреймворк Write-Select-Compress-Isolate, `/compact` и `compact_prompt`, subagent `spawn_agent` / `wait_agent` и конфигурация `.codex/agents/*.toml`.<br/>https://codex.danielvaughan.com/2026/06/10/context-engineering-codex-cli-write-select-compress-isolate-june-2026/
- **codex-harness-internals** (сообщественный анализ исходного кода): подробности реализации, включая инкрементальный контекст среды в `build_environment_update_item`.<br/>https://github.com/AlexKenbo/codex-harness-internals
diff --git a/docs/ru/harness-designs/deepseek/index.md b/docs/ru/harness-designs/deepseek/index.md
index 2681e0e..fe578cb 100644
--- a/docs/ru/harness-designs/deepseek/index.md
+++ b/docs/ru/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@
DeepSeek Harness представляет «возможность» с помощью Service и разделяет почти каждую возможность на три уровня:
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
Возьмём файловую систему: под `FS Service` находятся несколько Provider — Local FS, E2B FS и Remote FS, — а выше они единообразно представлены как file tools. Shell, Subprocess, Sandbox, Web, LLM и SubAgent используют ту же структуру. Это трёхуровневое разделение не наше обобщение: в оригинальном разделе [Architecture · Capability seams](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) сказано: *a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool* — шов возможностей является заменяемой возможностью с тремя ролями: Service Definition объявляет интерфейс, Service Provider реализует его, а Consumer использует, обычно в виде инструмента, доступного модели.
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(Этот конвейер воспроизводит раздел [Architecture · Turn flow](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md): `turn/*`, `step/*`, `user/message`, `assistant/*` и `tool/*` — сохраняемые события session; `agent/pre-step`, `agent/request`, `llm/stream` и `tools/*` — точки расширения, доступные plugin.)
@@ -58,13 +58,13 @@ turn/start → claim input → assemble(system prompt / context / tools)
## Сопоставление с фреймворком курса
-| 子系统 | DeepSeek Harness 的实现 | 评价 |
+| Подсистема | Реализация DeepSeek Harness | Оценка |
| --- | --- | --- |
-| 指令 | 插件化;规则/技能均以插件形态注入 | 极自由,但没有内置的"CLAUDE.md"式惯例 |
-| 工具 | Service Definition → Provider → Consumer 能力接缝 | 工具子系统标准化的极致 |
-| 环境 | 沙箱/FS/Shell 全部可换 Provider(含远程 E2B) | 环境彻底可插拔 |
-| 状态 | append-only Session Event Log + Model-visible means logged | 可观测性是第一性约束 |
-| 反馈 | tools/pre-execute 上的 permission / guard / policy / hook | 反馈机制事件化 |
+| Инструкции | Плагины; правила и skills внедряются как плагины | Полная свобода, но нет встроенного соглашения наподобие CLAUDE.md |
+| Инструменты | Шов возможностей Service Definition → Provider → Consumer | Предельная стандартизация подсистемы инструментов |
+| Среда | Провайдеры Sandbox/FS/Shell полностью заменяемы, включая удалённый E2B | Среда полностью модульна |
+| Состояние | append-only Session Event Log + Model-visible means logged | Наблюдаемость — первичное ограничение |
+| Обратная связь | permission / guard / policy / hook в tools/pre-execute | Механизм обратной связи основан на событиях |
Принципиальное отличие DeepSeek Harness от остальных трёх продуктов состоит в том, что Pi, Claude Code и Codex оптимизируют harness «внутри конкретного agent», а DeepSeek Harness определяет harness как **независимую от модели операционную систему**, где сам agent — лишь заменяемое приложение. Цена очевидна: высокая свобода означает высокую стоимость конфигурации. Это неотъемлемая обратная сторона модели «harness как OS» — особенно на этапе Developer Preview, когда продукт предназначен для раннего знакомства, а механизмы ещё развиваются.
@@ -79,9 +79,9 @@ turn/start → claim input → assemble(system prompt / context / tools)
Каждое утверждение можно проверить по приведённому ниже оригинальному материалу или исходному коду — мы не пересказываем по памяти:
-- **DeepSeek Harness 官网**: определение продукта «Agent = Model + Environment + Tools + State», статус Developer Preview и команда `dsh`.<br/>https://deepseek.com/harness
-- **deepseek-ai/deepseek-harness 仓库** (команда `dsh`, лицензия MIT):<br/>https://github.com/deepseek-ai/deepseek-harness
-- **架构文档 architecture.md**: главный источник статьи — «Every part of the product is a plugin», «There is no privileged core to patch», конвейер событий Turn flow, три роли Capability seams, «Model-visible means logged» и инвариант runtime, append-only Session Event Log, швы возможностей fs/tools/telemetry и подсистемы `ctx.*`.<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md
-- **架构文档 · 配套子文档**: введение в ядро Cordis (plugins contribute services, typed events, reversible effects), подробности швов возможностей и подсистема Session.<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/cordis-primer.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/capability-seams.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/subsystems/session.md
+- **Официальный сайт DeepSeek Harness**: определение продукта «Agent = Model + Environment + Tools + State», статус Developer Preview и команда `dsh`.<br/>https://deepseek.com/harness
+- **Репозиторий deepseek-ai/deepseek-harness** (команда `dsh`, лицензия MIT):<br/>https://github.com/deepseek-ai/deepseek-harness
+- **Архитектурный документ architecture.md**: главный источник статьи — «Every part of the product is a plugin», «There is no privileged core to patch», конвейер событий Turn flow, три роли Capability seams, «Model-visible means logged» и инвариант runtime, append-only Session Event Log, швы возможностей fs/tools/telemetry и подсистемы `ctx.*`.<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md
+- **Архитектурная документация · Сопутствующие документы**: введение в ядро Cordis (plugins contribute services, typed events, reversible effects), подробности швов возможностей и подсистема Session.<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/cordis-primer.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/capability-seams.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/subsystems/session.md
Связанные лекции: [лекция 11 «Как сделать работу agent наблюдаемой»](../lectures/lecture-11-why-observability-belongs-inside-the-harness/) | [лекция 12 «Каждая session должна завершаться чистым handoff»](../lectures/lecture-12-why-every-session-must-leave-a-clean-state/) | [лекция 2 «Что такое harness на самом деле»](../lectures/lecture-02-what-a-harness-actually-is/)
diff --git a/docs/ru/harness-designs/pi/index.md b/docs/ru/harness-designs/pi/index.md
index 6ac3e71..7ae036d 100644
--- a/docs/ru/harness-designs/pi/index.md
+++ b/docs/ru/harness-designs/pi/index.md
@@ -63,13 +63,13 @@ Extensions — главное дизайнерское решение Pi: **по
Оценим Pi по пяти подсистемам курса (субъективно, для сравнения):
-| 子系统 | Pi 的实现 | 评价 |
+| Подсистема | Реализация Pi | Оценка |
| --- | --- | --- |
-| 指令 | AGENTS.md 分级加载 + SYSTEM.md | 层级清晰,但规则本身要靠用户写 |
-| 工具 | 技能按需加载 + 扩展全生命周期钩子 | 极强,把工具系统做成了可编程面 |
-| 环境 | SYSTEM.md 做环境自描述;运行时环境靠用户在 AGENTS.md 里声明 | 机制是开放的,但可复现性依赖用户自述 |
-| 状态 | 会话树 + 压缩可定制 + PROGRESS.md | 极强,跨会话与可恢复性是其核心 |
-| 反馈 | 验证命令靠用户定义;session-summary / extract-patterns 机制化 | 机制提供,内容靠用户 |
+| Инструкции | Иерархическая загрузка AGENTS.md + SYSTEM.md | Чёткая иерархия, но сами правила должен писать пользователь |
+| Инструменты | Загрузка skills по требованию + hooks полного жизненного цикла extensions | Очень мощная реализация, превращающая систему инструментов в программируемую поверхность |
+| Среда | SYSTEM.md для самоописания среды; среда runtime объявляется пользователем в AGENTS.md | Механизм открыт, но воспроизводимость зависит от описания пользователя |
+| Состояние | Дерево session + настраиваемая compaction + PROGRESS.md | Очень мощная реализация; непрерывность между session и восстанавливаемость — её основа |
+| Обратная связь | Команды верификации определяет пользователь; механизированные session-summary / extract-patterns | Механизм предоставлен, содержимое задаёт пользователь |
Выбор Pi резко контрастирует с Claude Code и Codex: Claude Code встраивает «память, permissions и subagent» в ядро и предоставляет их из коробки; Codex делает стандартными «соглашения репозитория и изоляцию среды»; Pi предпочитает **ничего не решать за вас**, превращая право выбора в точки расширения. Цена этого решения — необходимость писать extensions самостоятельно либо устанавливать чужие пакеты.
@@ -84,11 +84,11 @@ Extensions — главное дизайнерское решение Pi: **по
Каждое утверждение можно проверить по приведённому ниже оригинальному материалу или исходному коду — мы не пересказываем по памяти:
-- **pi.dev 官网**: исходная формулировка позиционирования «Ask Pi to build what you want, or install a package that does it your way», четыре настраиваемых уровня и дерево session («sessions are stored as trees», `/tree`, сохранение в одном файле, экспорт HTML и публикация gist).<br/>https://pi.dev/
-- **pi.dev 官方文档 · Sessions**: подключаемая compaction (topic-based / code-aware / другая модель для summary), автоматическая compaction и динамическое внедрение контекста.<br/>https://pi.dev/docs/usage/sessions
-- **pi.dev 官方文档 · Extensions**: extensions могут перед каждым раундом рассуждения внедрять сообщения, фильтровать историю, выполнять RAG и строить долговременную память.<br/>https://pi.dev/docs/usage/extensions
-- **pi.dev 官方文档 · Project Context**: семантика replace / append для SYSTEM.md.<br/>https://pi.dev/docs/usage/project-context
-- **Pi Coding Agent 源码 README** (badlogic/pi-mono): трёхуровневый порядок загрузки AGENTS.md (глобальный → родительские каталоги → текущий каталог), условия запуска `/compact` и автоматической compaction, точка разбиения в 20 тысяч token, загрузка Skills по требованию и стандарт Agent Skills, жизненный цикл Hooks с четырьмя официальными примерами, Programmatic Usage (JSON / RPC / SDK).<br/>https://github.com/badlogic/pi-mono/blob/main/packages/coding-agent/README.md
-- **pi-agent-harness 社区仓库**: extensions skill-router / session-summary / extract-patterns / telemetry и система файлов VISION.md / PROGRESS.md / LESSONS.md / STANDARDS.md.<br/>https://github.com/LabidySabidy/pi-agent-harness
+- **Официальный сайт pi.dev**: исходная формулировка позиционирования «Ask Pi to build what you want, or install a package that does it your way», четыре настраиваемых уровня и дерево session («sessions are stored as trees», `/tree`, сохранение в одном файле, экспорт HTML и публикация gist).<br/>https://pi.dev/
+- **Официальная документация pi.dev · Sessions**: подключаемая compaction (topic-based / code-aware / другая модель для summary), автоматическая compaction и динамическое внедрение контекста.<br/>https://pi.dev/docs/usage/sessions
+- **Официальная документация pi.dev · Extensions**: extensions могут перед каждым раундом рассуждения внедрять сообщения, фильтровать историю, выполнять RAG и строить долговременную память.<br/>https://pi.dev/docs/usage/extensions
+- **Официальная документация pi.dev · Project Context**: семантика replace / append для SYSTEM.md.<br/>https://pi.dev/docs/usage/project-context
+- **README исходного кода Pi Coding Agent** (badlogic/pi-mono): трёхуровневый порядок загрузки AGENTS.md (глобальный → родительские каталоги → текущий каталог), условия запуска `/compact` и автоматической compaction, точка разбиения в 20 тысяч token, загрузка Skills по требованию и стандарт Agent Skills, жизненный цикл Hooks с четырьмя официальными примерами, Programmatic Usage (JSON / RPC / SDK).<br/>https://github.com/badlogic/pi-mono/blob/main/packages/coding-agent/README.md
+- **Репозиторий сообщества pi-agent-harness**: extensions skill-router / session-summary / extract-patterns / telemetry и система файлов VISION.md / PROGRESS.md / LESSONS.md / STANDARDS.md.<br/>https://github.com/LabidySabidy/pi-agent-harness
Связанные лекции: [лекция 2 «Что такое harness на самом деле»](../lectures/lecture-02-what-a-harness-actually-is/) | [лекция 5 «Как сохранять непрерывность контекста в задачах между session»](../lectures/lecture-05-why-long-running-tasks-lose-continuity/) | [лекция 13 «От ручного управления к автоматическому циклу»](../lectures/lecture-13-loop-engineering/)
diff --git a/docs/tr/harness-designs/claude-code/index.md b/docs/tr/harness-designs/claude-code/index.md
index ccb31f5..96a5eff 100644
--- a/docs/tr/harness-designs/claude-code/index.md
+++ b/docs/tr/harness-designs/claude-code/index.md
@@ -79,10 +79,10 @@ Claude Code'un günlüğü ekleme tabanlı eksiksiz bir kayıttır (history.json
Her iddia, izlenime dayalı aktarımı önlemek için aşağıdaki özgün metne veya kaynak koda kadar izlenebilir:
-- **Claude Code 官方文档 · Memory**:每次会话全新上下文、CLAUDE.md 四类作用域、子目录按需加载、auto memory(200 行 / 25KB)、`/init` 生成 CLAUDE.md。<br/>https://code.claude.com/docs/en/memory
-- **Claude Code 官方文档 · Skills / MCP / Hooks / Sub-agents**:四类扩展机制的定义与事件(PreToolUse / PostToolUse / Stop)。<br/>https://code.claude.com/docs/en/skills | https://code.claude.com/docs/en/mcp | https://code.claude.com/docs/en/hooks | https://code.claude.com/docs/en/sub-agents
-- **VILA Lab《Dive into Claude Code》**(源码级拆解报告):五层压缩管线、权限七模式 + ML 分类器、sidechain 子智能体、追加式会话存储 history.jsonl。<br/>https://zhiqiangshen.com/projects/Claude_Code_Report/Claude_Code_Report.pdf
-- **Anthropic《Effective harnesses for long-running agents》**:"可靠性来自 harness 而非模型"、agent 会自信地夸赞自己的工作、用钩子做验证等观点出处。<br/>https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents
-- **Claude Code Full Stack 导读**(社区,CLAUDE.md / Skills / MCP / Subagents / Hooks 分层):作为扩展机制职责分离的补充阅读。<br/>https://jsmanifest.com/claude-code-full-stack-guide
+- **Claude Code Resmî Belgeleri · Memory**: Her session için yepyeni bir bağlam, CLAUDE.md'nin dört kapsam türü, alt dizinlerin gerektiğinde yüklenmesi, auto memory (200 satır / 25KB) ve `/init` ile CLAUDE.md oluşturulması.<br/>https://code.claude.com/docs/en/memory
+- **Claude Code Resmî Belgeleri · Skills / MCP / Hooks / Sub-agents**: Dört genişletme mekanizmasının tanımları ve olayları (PreToolUse / PostToolUse / Stop).<br/>https://code.claude.com/docs/en/skills | https://code.claude.com/docs/en/mcp | https://code.claude.com/docs/en/hooks | https://code.claude.com/docs/en/sub-agents
+- **VILA Lab, “Dive into Claude Code”** (kaynak kod düzeyinde inceleme raporu): Beş aşamalı compaction hattı, yedi permissions modu + ML sınıflandırıcısı, sidechain subagent'ları ve ekleme tabanlı session depolama history.jsonl.<br/>https://zhiqiangshen.com/projects/Claude_Code_Report/Claude_Code_Report.pdf
+- **Anthropic, “Effective harnesses for long-running agents”**: “Güvenilirlik modelden değil harness'tan gelir”, agent'ın kendi çalışmasını kendinden emin biçimde övmesi ve doğrulama için hooks kullanılması gibi görüşlerin kaynağı.<br/>https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents
+- **Claude Code Full Stack Rehberi** (topluluk; CLAUDE.md / Skills / MCP / Subagents / Hooks katmanları): Genişletme mekanizmalarındaki sorumluluk ayrımına ilişkin tamamlayıcı okuma.<br/>https://jsmanifest.com/claude-code-full-stack-guide
İlgili dersler: [Ders 3 · Kod Deposu Neden Tek Gerçeklik Kaynağı Olmalıdır?](../lectures/lecture-03-why-the-repository-must-become-the-system-of-record/) | [Ders 9 · Agent'lar Neden Zaferi Erken İlan Eder?](../lectures/lecture-09-why-agents-declare-victory-too-early/) | [Ders 10 · Uçtan Uca Test Sonuçları Neden Değiştirir?](../lectures/lecture-10-why-end-to-end-testing-changes-results/)
diff --git a/docs/tr/harness-designs/codex/index.md b/docs/tr/harness-designs/codex/index.md
index 2fc7e1b..3de92b2 100644
--- a/docs/tr/harness-designs/codex/index.md
+++ b/docs/tr/harness-designs/codex/index.md
@@ -69,10 +69,10 @@ Codex ile Claude Code karşılaştırması ilginçtir: Claude Code "ekleme" yakl
Her iddia, izlenime dayalı aktarımı önlemek için aşağıdaki özgün metne veya kaynak koda kadar izlenebilir:
-- **OpenAI《Harness Engineering》**:AGENTS.md 目录页与约 100 行建议、executive invariants / don't micromanage、worktree 隔离 + 可观测性栈、验证命令入规范、上百万行产品案例、审批策略与 plan mode。本篇所有核心论断的主要出处。<br/>https://openai.com/index/harness-engineering/
-- **OpenAI 官方《AGENTS.md》规范**(AGENTS.md 作为跨工具约定的标准):<br/>https://openai.com/index/agents-md/
-- **Codex CLI 开源仓库**(Rust 实现的单体二进制):<br/>https://github.com/openai/codex
-- **Context Engineering for Codex CLI**(社区):Write-Select-Compress-Isolate 框架、`/compact` 与 `compact_prompt`、`spawn_agent` / `wait_agent` 子智能体与 `.codex/agents/*.toml` 配置。<br/>https://codex.danielvaughan.com/2026/06/10/context-engineering-codex-cli-write-select-compress-isolate-june-2026/
-- **codex-harness-internals**(社区源码分析):`build_environment_update_item` 增量环境上下文等实现细节。<br/>https://github.com/AlexKenbo/codex-harness-internals
+- **OpenAI, “Harness Engineering”**: AGENTS.md'nin dizin sayfası olması ve yaklaşık 100 satır önerisi, executive invariants / don't micromanage, worktree yalıtımı + gözlemlenebilirlik yığını, doğrulama komutlarının kurallara eklenmesi, bir milyon satırı aşan ürün örneği, onay politikaları ve plan mode. Bu yazıdaki tüm temel iddiaların başlıca kaynağı.<br/>https://openai.com/index/harness-engineering/
+- **OpenAI'ın Resmî “AGENTS.md” Standardı** (AGENTS.md'nin araçlar arası bir convention standardı olması):<br/>https://openai.com/index/agents-md/
+- **Codex CLI Açık Kaynak Deposu** (Rust ile yazılmış monolitik ikili dosya):<br/>https://github.com/openai/codex
+- **Context Engineering for Codex CLI** (topluluk): Write-Select-Compress-Isolate çerçevesi, `/compact` ve `compact_prompt`, `spawn_agent` / `wait_agent` subagent'ları ve `.codex/agents/*.toml` yapılandırması.<br/>https://codex.danielvaughan.com/2026/06/10/context-engineering-codex-cli-write-select-compress-isolate-june-2026/
+- **codex-harness-internals** (topluluk kaynak kod analizi): `build_environment_update_item` ile artımlı ortam bağlamı gibi uygulama ayrıntıları.<br/>https://github.com/AlexKenbo/codex-harness-internals
İlgili dersler: [Ders 3 · Kod Deposu Neden Tek Gerçeklik Kaynağı Olmalıdır?](../lectures/lecture-03-why-the-repository-must-become-the-system-of-record/) | [Ders 4 · Talimatları Farklı Dosyalara Ayırmak](../lectures/lecture-04-why-one-giant-instruction-file-fails/) | [Ders 7 · Agent'ın Her Görevi İçin Net Sınırlar Çizmek](../lectures/lecture-07-why-agents-overreach-and-under-finish/)
diff --git a/docs/tr/harness-designs/deepseek/index.md b/docs/tr/harness-designs/deepseek/index.md
index 7ca4622..3be5aa6 100644
--- a/docs/tr/harness-designs/deepseek/index.md
+++ b/docs/tr/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@ Bu, dersteki "model ağırlıklarının dışındaki her şey harness'tır" ifad
DeepSeek Harness, "yeteneği" Service ile temsil eder ve neredeyse her yeteneği üç katmana ayırır:
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
Örneğin dosya sisteminde `FS Service` altında Local FS, E2B FS ve Remote FS gibi birden fazla Provider bulunur; üst katmana ise tek biçimli file tools sunulur. Shell, Subprocess, Sandbox, Web, LLM ve SubAgent aynı yapıyı kullanır. Bu üç katmanlı yapı bizim özetimiz değildir. [Mimari belgesinin Capability seams bölümündeki](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) özgün ifade şöyledir: *a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool* (yetenek eklemi, üç rolü olan değiştirilebilir bir yetenektir: arayüzü bildiren Service Definition, onu uygulayan Service Provider ve onu kullanan, genellikle modele dönük bir araç olan Consumer).
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(Yukarıdaki hat, [mimari belgesinin Turn flow bölümünün](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) aktarımıdır: `turn/*`, `step/*`, `user/message`, `assistant/*` ve `tool/*` kalıcı session olaylarıdır; `agent/pre-step`, `agent/request`, `llm/stream` ve `tools/*` ise plugin'lerin dinleyebildiği genişletme noktalarıdır.)
@@ -79,9 +79,9 @@ DeepSeek Harness ile diğer üç ürün arasındaki temel fark şudur: Pi, Claud
Her iddia, izlenime dayalı aktarımı önlemek için aşağıdaki özgün metne veya kaynak koda kadar izlenebilir:
-- **DeepSeek Harness 官网**:产品定义 "Agent = Model + Environment + Tools + State"、Developer Preview 定位与 `dsh` 命令。<br/>https://deepseek.com/harness
-- **deepseek-ai/deepseek-harness 仓库**(命令 `dsh`,MIT 协议):<br/>https://github.com/deepseek-ai/deepseek-harness
-- **架构文档 architecture.md**:本篇最核心的出处——"Every part of the product is a plugin"、"There is no privileged core to patch"、Turn flow 事件流水线、Capability seams 三层角色、"Model-visible means logged" 与运行时不变量、append-only Session Event Log、fs/tools/telemetry 等能力接缝与 `ctx.*` 子系统。<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md
-- **架构文档 · 配套子文档**:Cordis 内核简介(plugins contribute services, typed events, reversible effects)、能力接缝细节、Session 子系统。<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/cordis-primer.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/capability-seams.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/subsystems/session.md
+- **DeepSeek Harness Ana Sayfası**: "Agent = Model + Environment + Tools + State" ürün tanımı, Developer Preview konumlandırması ve `dsh` komutu.<br/>https://deepseek.com/harness
+- **deepseek-ai/deepseek-harness Deposu** (`dsh` komutu, MIT lisansı):<br/>https://github.com/deepseek-ai/deepseek-harness
+- **architecture.md Mimari Belgesi**: Bu yazının en temel kaynağı — "Every part of the product is a plugin", "There is no privileged core to patch", Turn flow olay hattı, Capability seams'in üç rolü, "Model-visible means logged" ve runtime değişmezi, append-only Session Event Log, fs/tools/telemetry gibi yetenek eklemleri ve `ctx.*` alt sistemleri.<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md
+- **Mimari Belgesi · Tamamlayıcı Alt Belgeler**: Cordis çekirdeğine giriş (plugins contribute services, typed events, reversible effects), yetenek eklemi ayrıntıları ve Session alt sistemi.<br/>https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/cordis-primer.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/capability-seams.md | https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/subsystems/session.md
İlgili dersler: [Ders 11 · Gözlemlenebilirlik Neden Harness'ın İçinde Yer Almalıdır?](../lectures/lecture-11-why-observability-belongs-inside-the-harness/) | [Ders 12 · Her Session Neden Temiz Bir Durum Bırakmalıdır?](../lectures/lecture-12-why-every-session-must-leave-a-clean-state/) | [Ders 2 · Harness Tam Olarak Nedir?](../lectures/lecture-02-what-a-harness-actually-is/)
diff --git a/docs/tr/harness-designs/pi/index.md b/docs/tr/harness-designs/pi/index.md
index 9db8f45..d8608ae 100644
--- a/docs/tr/harness-designs/pi/index.md
+++ b/docs/tr/harness-designs/pi/index.md
@@ -84,11 +84,11 @@ Pi'nin tercihi Claude Code / Codex ile belirgin bir karşıtlık oluşturur: Cla
Her iddia, izlenime dayalı aktarımı önlemek için aşağıdaki özgün metne veya kaynak koda kadar izlenebilir:
-- **pi.dev 官网**:定位原话 "Ask Pi to build what you want, or install a package that does it your way"、四层可定制物、会话树("sessions are stored as trees",`/tree`、单文件保存、导出 HTML / 分享 gist)。<br/>https://pi.dev/
-- **pi.dev 官方文档 · Sessions**:压缩可插拔(topic-based / code-aware / 换摘要模型)、自动压缩与动态上下文注入的机制描述。<br/>https://pi.dev/docs/usage/sessions
-- **pi.dev 官方文档 · Extensions**:扩展可在每轮推理前注入消息、过滤历史、做 RAG、构建长期记忆。<br/>https://pi.dev/docs/usage/extensions
-- **pi.dev 官方文档 · Project Context**:SYSTEM.md 的 replace / append 语义。<br/>https://pi.dev/docs/usage/project-context
-- **Pi Coding Agent 源码 README**(badlogic/pi-mono):AGENTS.md 三级加载顺序(全局 → 父目录 → 当前目录)、`/compact` 与自动压缩的触发条件与 2 万 token 切割点、Skills 按需加载与 Agent Skills 标准、Hooks 生命周期与四个官方示例用途、Programmatic Usage(JSON / RPC / SDK)。<br/>https://github.com/badlogic/pi-mono/blob/main/packages/coding-agent/README.md
-- **pi-agent-harness 社区仓库**:skill-router / session-summary / extract-patterns / telemetry 扩展,VISION.md / PROGRESS.md / LESSONS.md / STANDARDS.md 文件体系。<br/>https://github.com/LabidySabidy/pi-agent-harness
+- **pi.dev Ana Sayfası**: Özgün konumlandırma ifadesi "Ask Pi to build what you want, or install a package that does it your way", dört özelleştirilebilir katman ve session ağacı ("sessions are stored as trees", `/tree`, tek dosyada saklama, HTML olarak dışa aktarma / gist ile paylaşma).<br/>https://pi.dev/
+- **pi.dev Resmî Belgeleri · Sessions**: Takılabilir compaction (topic-based / code-aware / farklı bir özetleme modeli kullanma), otomatik compaction ve dinamik bağlam ekleme mekanizmalarının açıklaması.<br/>https://pi.dev/docs/usage/sessions
+- **pi.dev Resmî Belgeleri · Extensions**: Extensions'ın her muhakeme turundan önce mesaj eklemesi, geçmişi filtrelemesi, RAG uygulaması ve uzun vadeli bellek oluşturması.<br/>https://pi.dev/docs/usage/extensions
+- **pi.dev Resmî Belgeleri · Project Context**: SYSTEM.md'nin replace / append semantiği.<br/>https://pi.dev/docs/usage/project-context
+- **Pi Coding Agent Kaynak Kod README Dosyası** (badlogic/pi-mono): AGENTS.md'nin üç aşamalı yükleme sırası (genel → üst dizin → geçerli dizin), `/compact` ve otomatik compaction'ın tetiklenme koşulları ile 20 bin token'lık bölme noktası, Skills'in gerektiğinde yüklenmesi ve Agent Skills standardı, Hooks yaşam döngüsü ve dört resmî örnek kullanım alanı, Programmatic Usage (JSON / RPC / SDK).<br/>https://github.com/badlogic/pi-mono/blob/main/packages/coding-agent/README.md
+- **pi-agent-harness Topluluk Deposu**: skill-router / session-summary / extract-patterns / telemetry Extensions'ı ve VISION.md / PROGRESS.md / LESSONS.md / STANDARDS.md dosya sistemi.<br/>https://github.com/LabidySabidy/pi-agent-harness
İlgili dersler: [Ders 2 · Harness Tam Olarak Nedir?](../lectures/lecture-02-what-a-harness-actually-is/) | [Ders 5 · Uzun Süren Görevler Neden Bağlam Sürekliliğini Kaybeder?](../lectures/lecture-05-why-long-running-tasks-lose-continuity/) | [Ders 13 · Elle Yürütmeden Otomatik Döngüye](../lectures/lecture-13-loop-engineering/)
diff --git a/docs/uk/harness-designs/deepseek/index.md b/docs/uk/harness-designs/deepseek/index.md
index 5ad945c..dce9a57 100644
--- a/docs/uk/harness-designs/deepseek/index.md
+++ b/docs/uk/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@
У DeepSeek Harness поняття Service позначає «можливість», а майже кожну можливість поділено на три рівні:
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
Візьмімо файлову систему: під `FS Service` працюють кілька Provider — Local FS, E2B FS і Remote FS, а назовні вони надають єдиний інтерфейс file tools. Shell, Subprocess, Sandbox, Web, LLM і SubAgent мають таку саму структуру. Цю трирівневу схему не виведено в нашому аналізі — в оригіналі розділу [архітектурної документації · Capability seams](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) прямо сказано: *a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool* (шов можливості — замінна можливість із трьома ролями: Service Definition оголошує інтерфейс, Service Provider реалізує його, а Consumer використовує; останнім зазвичай є інструмент, доступний моделі).
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(Наведений вище конвеєр — це переказ розділу [архітектурної документації · Turn flow](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md): `turn/*`, `step/*`, `user/message`, `assistant/*` і `tool/*` є збережуваними подіями сесії, а `agent/pre-step`, `agent/request`, `llm/stream` і `tools/*` — точками розширення, які можуть прослуховувати плагіни.)
diff --git a/docs/uz/harness-designs/deepseek/index.md b/docs/uz/harness-designs/deepseek/index.md
index 66b5d84..362f999 100644
--- a/docs/uz/harness-designs/deepseek/index.md
+++ b/docs/uz/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@ Bu kursdagi “model ogʻirliklaridan tashqaridagi barcha narsa harness” ibora
DeepSeek Harness “imkoniyat”ni Service orqali ifodalaydi va deyarli har bir imkoniyatni uch qatlamga ajratadi:
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
Masalan, fayl tizimida `FS Service` ostida Local FS, E2B FS va Remote FS kabi bir nechta Provider mavjud; yuqorida esa ular yagona file tools koʻrinishida ochiladi. Shell, Subprocess, Sandbox, Web, LLM va SubAgent ham ayni tuzilishga ega. Ushbu uch qatlamli tuzilma bizning xulosamiz emas. [Arxitektura hujjatining Capability seams boʻlimida](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) aynan shunday yozilgan: *a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool* (imkoniyat tutashuvi — uchta roldan iborat almashtiriladigan imkoniyat: interfeysni eʼlon qiluvchi Service Definition, uni amalga oshiruvchi Service Provider va undan foydalanuvchi Consumer; oxirgisi odatda modelga koʻrinadigan vosita boʻladi).
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(Yuqoridagi pipeline [arxitektura hujjatining Turn flow boʻlimidagi](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md) maʼlumotning qayta bayonidir: `turn/*`, `step/*`, `user/message`, `assistant/*`, `tool/*` — doimiy saqlanadigan sessiya hodisalari; `agent/pre-step`, `agent/request`, `llm/stream`, `tools/*` esa plaginlar tinglashi mumkin boʻlgan kengaytma nuqtalaridir.)
diff --git a/docs/vi/harness-designs/deepseek/index.md b/docs/vi/harness-designs/deepseek/index.md
index ec3771f..3a8f064 100644
--- a/docs/vi/harness-designs/deepseek/index.md
+++ b/docs/vi/harness-designs/deepseek/index.md
@@ -17,11 +17,11 @@ Cấu trúc của coding agent truyền thống là “LLM + vòng lặp agent c
DeepSeek Harness dùng Service để biểu diễn “năng lực”, và gần như mọi năng lực đều được chia thành ba tầng:
```
-Service Definition(能力定义)
+Service Definition
↓
-Service Provider(能力提供者)
+Service Provider
↓
-Consumer(能力消费者)
+Consumer
```
Lấy hệ thống tệp làm ví dụ: bên dưới `FS Service` có nhiều Provider như Local FS, E2B FS, Remote FS, còn phía trên cung cấp thống nhất thành file tools. Shell, Subprocess, Sandbox, Web, LLM và SubAgent đều dùng cùng một cấu trúc. Cấu trúc ba tầng này không phải do chúng ta tự tổng kết — nguyên văn trong [tài liệu kiến trúc · Capability seams](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md): *a seam is a swappable capability with three roles: a Service Definition declaring the interface, a Service Provider implementing it, and a Consumer using it, commonly a model-facing tool* (đường nối năng lực = một năng lực có thể thay thế với ba vai trò: Service Definition khai báo giao diện, Service Provider triển khai giao diện và Consumer sử dụng nó; Consumer thường là công cụ hướng tới mô hình).
@@ -37,7 +37,7 @@ turn/start → claim input → assemble(system prompt / context / tools)
→ agent/pre-step → step/start → LLM request(agent/request)→ llm/stream
→ assistant/message → tool/call
→ tools/pre-execute(permission / guard / policy / hook)
- → tools/execute → tools/post-execute → tool/result → step/end → 下一轮
+ → tools/execute → tools/post-execute → tool/result → step/end → next turn
```
(Pipeline trên là bản chuyển lại từ phần [tài liệu kiến trúc · Turn flow](https://github.com/deepseek-ai/deepseek-harness/blob/master/docs/architecture.md): `turn/*`, `step/*`, `user/message`, `assistant/*`, `tool/*` là các sự kiện phiên được duy trì; `agent/pre-step`, `agent/request`, `llm/stream`, `tools/*` là các điểm mở rộng mà plugin có thể lắng nghe.)