refactor: apply repository naming contract

Apply the accepted pre-release package, service, type, directory, and role renames as one repository-wide change.

docs/user/develop/framework/events.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write docs/user/develop/framework/events.md
-events.md: 4b5f9ee215186398ee5aee7a438f792f9b5a3639
-events.zh.md: f800857dca08844326e47fae0b8e24984dbc74f2
+events.md: 4a6ecbad614cf2debccaee9ace1086273d8fb95b
+events.zh.md: c77747bf6ac767c69e4f2d9cfe7375b71bd388e6

docs/user/develop/framework/events.md

@@ -103,7 +103,7 @@ declare module '@deepseek-ai/cordis' {
 
 Harness Cordis events use `namespace/action` names, including `agent/step`, `agent/request`, `agent/request-error`, `tools/result`, and `session/event`. The generated `cordis-surface` regions on the [subsystem pages](../../../subsystems/core.md) record complete signatures and modes.
 
-`turn/*`, `step/*`, `tool/call`, `tool/result`, and `compact/*` are durable session-event types, not same-named Cordis events. To observe them, listen to `session/event` and inspect `event.type`.
+`turn/*`, `step/*`, `tool/call`, `tool/result`, and `compaction/*` are durable session-event types, not same-named Cordis events. To observe them, listen to `session/event` and inspect `event.type`.
 
 ## Event listeners are effects
 

docs/user/develop/framework/events.zh.md

@@ -103,7 +103,7 @@ declare module '@deepseek-ai/cordis' {
 
 Harness 的 Cordis 事件遵循 `namespace/action` 命名，例如 `agent/step`、`agent/request`、`agent/request-error`、`tools/result` 和 `session/event`。完整签名与触发模式见[子系统页面](../../../subsystems/core.md)上生成的 `cordis-surface` 区块。
 
-`turn/*`、`step/*`、`tool/call`、`tool/result` 和 `compact/*` 是持久化的会话事件类型，不是同名 Cordis 事件。需要观察它们时，监听 `session/event` 并检查 `event.type`。
+`turn/*`、`step/*`、`tool/call`、`tool/result` 和 `compaction/*` 是持久化的会话事件类型，不是同名 Cordis 事件。需要观察它们时，监听 `session/event` 并检查 `event.type`。
 
 ## 事件监听器也是效果
 

docs/user/develop/framework/service.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write docs/user/develop/framework/service.md
-service.md: 3358f82ca5391741a7f531b7504de7335959ad03
-service.zh.md: c8a644b3cc53a2d05b431dfdc64aa8c15959ba55
+service.md: a9e873f1ba969b1f2d22266f8ec03207f84eeddc
+service.zh.md: a201280bc38176f57f5354ab205ae700c7b04a89

docs/user/develop/framework/service.md

@@ -9,7 +9,7 @@ A service is a capability one plugin exposes to other plugins. `inject` declares
 In Harness, `tools`, `llm`, and `agents` are services. Each is a named capability mounted on `ctx`:
 
 ```ts ignore-check
-ctx.tools    // ToolRegistry service
+ctx.tools    // ToolRuntime service
 ctx.llm      // LLM service
 ctx.agents   // Agent service
 ```

docs/user/develop/framework/service.zh.md

@@ -9,7 +9,7 @@
 在 Harness 中，`tools`、`llm`、`agents` 都是服务。服务是挂载在 `ctx` 上的命名能力：
 
 ```ts ignore-check
-ctx.tools    // ToolRegistry service
+ctx.tools    // ToolRuntime service
 ctx.llm      // LLM service
 ctx.agents   // Agent service
 ```

docs/user/develop/practice/index.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write docs/user/develop/practice/index.md
-index.md: 7ca9f0b1abe472dc90c6d4e56543e43b6d2ec727
-index.zh.md: 6d340e0cecfcc31517464323e5d536fc62edc132
+index.md: 3619a39f4a39b42cf4269d3778f233ecc1731933
+index.zh.md: 8bd378af5eaf2741c34d76a152fa8a62a947bf41

docs/user/develop/practice/index.md

@@ -12,13 +12,13 @@ When a capability is general enough to need replaceable providers, such as Bash
 
 The Bash execution capability consists of:
 
-- **Service Definition** (`dsh-bash`) — defines the Cordis service and Bash request and result types
+- **Service Definition** (`dsh-shell`) — defines the Cordis service and Bash request and result types
 - **Service provider** (`dsh-bash-local`) — executes commands on the local machine
 - **Consumer** (`dsh-tool-bash`) — exposes the capability as a model-callable tool
 
 ```
 ┌─────────────┐     ┌──────────────────┐     ┌──────────────┐
-│  dsh-bash   │────▶│  dsh-bash-local  │     │ dsh-tool-bash│
+│  dsh-shell   │────▶│  dsh-bash-local  │     │ dsh-tool-bash│
 │(definition) │     │    (provider)     │     │(consumer/tool)│
 └─────────────┘     └──────────────────┘     └──────────────┘
        ▲                                            │

docs/user/develop/practice/index.zh.md

@@ -12,13 +12,13 @@
 
 以 Bash 执行能力为例：
 
-- **Service Definition** (`dsh-bash`)：定义 Cordis 服务以及 Bash 请求和结果类型
+- **Service Definition** (`dsh-shell`)：定义 Cordis 服务以及 Bash 请求和结果类型
 - **Service provider** (`dsh-bash-local`)：在本地计算机上执行命令
 - **Consumer** (`dsh-tool-bash`)：将该能力公开为模型可调用的工具
 
 ```
 ┌─────────────┐     ┌──────────────────┐     ┌──────────────┐
-│  dsh-bash   │────▶│  dsh-bash-local  │     │ dsh-tool-bash│
+│  dsh-shell   │────▶│  dsh-bash-local  │     │ dsh-tool-bash│
 │(definition) │     │    (provider)     │     │(consumer/tool)│
 └─────────────┘     └──────────────────┘     └──────────────┘
        ▲                                            │