mirror of
https://github.com/deepseek-ai/deepseek-harness.git
synced 2026-08-29 04:26:38 +00:00
docs(todo): add the owning subsystem reference
This commit is contained in:
@@ -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 packages/todo/README.md
|
||||
README.md: 6bbc9fe4f04cc4a82573c643c5c00bbecde069ed
|
||||
README.zh.md: fa2bd8a6cde5c322151b37b066f0d718c52dfcd0
|
||||
README.md: 85499ac2382ec0f220a7fafda0acbbed369f9ca2
|
||||
README.zh.md: 9056208e82d4abc1db51bcae21205f4e5afd8bf9
|
||||
|
||||
@@ -10,4 +10,4 @@ The model-facing todo capability. It is a single **product** package because one
|
||||
|
||||
The child README owns the tool, persistence, and rendering contract.
|
||||
|
||||
The event payload is documented on [docs/subsystems/session.md](../../docs/subsystems/session.md).
|
||||
The event payload is documented on [docs/subsystems/todo.md](../../docs/subsystems/todo.md).
|
||||
|
||||
@@ -10,4 +10,4 @@
|
||||
|
||||
子级 README 负责工具、持久化和渲染约定。
|
||||
|
||||
事件载荷记录在 [docs/subsystems/session.md](../../docs/subsystems/session.zh.md)。
|
||||
事件载荷记录在 [docs/subsystems/todo.md](../../docs/subsystems/todo.zh.md)。
|
||||
|
||||
@@ -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 packages/todo/tool-todo/README.md
|
||||
README.md: 7e236348432a5e428392d97fd74ec91cf1752de7
|
||||
README.zh.md: 60f799030cfe58a3c015cb9ebb1012808b28e9f4
|
||||
README.md: 498b817c3eacd1e56c6b1b72b4fb863018c2207b
|
||||
README.zh.md: 6c77e3c78e858d270a7764bfd82df2212cb31a69
|
||||
|
||||
@@ -24,7 +24,7 @@ The flag moves the model-facing instruction and the accepted input together —
|
||||
|
||||
Beyond the schema's type/required/enum checks, `execute` rejects an empty or duplicate `content`, and any item key beyond `content`/`status` — an extended item shape (ids, nesting) fails loud instead of silently flattening, keeping the logged snapshot equal to what the model believes it wrote. How many tasks may be `in_progress` at once is the deployment's call (§ Configuration): a composition that chooses `true` permits parallel work (concurrent subagents, background commands) to mark several tasks simultaneously. Ordering and the discipline of keeping the list current are left to the model via the tool description.
|
||||
|
||||
This package's invariant companion validates every durable `todo/write` payload and requires the event to occur inside an open turn, both for live appends and for existing logs inspected at plugin load. Core session treats declaration-merged events generically; the producing package owns these todo-specific rules ([event ownership](../../../.agents/notes/implemented/architecture/2026-07-20-todo-event-ownership.md)).
|
||||
This package's invariant companion validates every durable `todo/write` payload and requires the event to occur inside an open turn. It validates existing and newly announced sessions once, then advances a committed per-session turn trace for live appends. Core session treats declaration-merged events generically; the producing package owns these todo-specific rules ([event ownership](../../../.agents/notes/implemented/architecture/2026-07-20-todo-event-ownership.md)).
|
||||
|
||||
## Rendering
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@
|
||||
|
||||
除 schema 的类型/必填/枚举检查外,`execute` 还会拒绝空或重复的 `content`,以及 `content`/`status` 之外的任何条目键——扩展条目形状(id、嵌套)会明确报错而不是被静默压平,保证落日志的快照与模型自认为写入的内容一致。同时可以有多少任务处于 `in_progress` 由部署决定(见 § 配置):选择 `true` 的组合允许并行工作(并发 subagent、后台命令)同时将多个任务标记为 `in_progress`。列表的顺序及及时更新由模型依照工具描述负责。
|
||||
|
||||
本包的不变量配套插件会校验每个持久 `todo/write` payload,并要求事件位于开放轮次内;这些规则同时适用于实时追加和插件加载时检查的现有日志。核心会话只会通用处理声明合并事件,todo 专属规则由生产该事件的包负责(见[事件所有权](../../../.agents/notes/implemented/architecture/2026-07-20-todo-event-ownership.zh.md))。
|
||||
本包的不变量配套插件会校验每个持久 `todo/write` payload,并要求事件位于开放轮次内。它会各自单次校验现有会话与新发布的会话,随后为实时追加推进逐会话的已提交轮次追踪状态。核心会话只会通用处理声明合并事件,todo 专属规则由生产该事件的包负责(见[事件所有权](../../../.agents/notes/implemented/architecture/2026-07-20-todo-event-ownership.zh.md))。
|
||||
|
||||
## 渲染
|
||||
|
||||
|
||||
Reference in New Issue
Block a user