From ecd434d02847ef25013f89de70833ab9897eb1db Mon Sep 17 00:00:00 2001 From: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> Date: Thu, 19 Nov 2026 12:08:29 +0800 Subject: [PATCH] docs: align Complete Turn guidance with the live v1 contract Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> --- docs/product/releases/v2.4.0.md | 30 +++-- docs/reference/protocols/turn-envelope-v0.md | 118 ++++++++++++------- docs/reference/required-work-context.md | 11 +- 3 files changed, 98 insertions(+), 61 deletions(-) diff --git a/docs/product/releases/v2.4.0.md b/docs/product/releases/v2.4.0.md index 9d9d5a51f4..adaa723e73 100644 --- a/docs/product/releases/v2.4.0.md +++ b/docs/product/releases/v2.4.0.md @@ -44,6 +44,8 @@ loopx doctor **Breaking changes:** Yes. Legacy registry `status` values `paused` and `stopped` are retired. Use `activation.state` and the Goal lifecycle commands for pause and resume. The backed-up migration preserves pause intent and returns the original registry backup path. For direct pip/source installs and restored backups, review the read-only check before running the owner-authorized migration. [#8431](https://github.com/loopx-project/loopx/pull/8431) +The 2.4.0 candidate also composes `loopx_turn_envelope_v1` for live JSON guard decisions (with default progressive delivery returning `context_capture_navigation_v1` on stdout unless `--context-delivery off` is set). External Hosts that parse the earlier quota packet or v0 envelope need a v1 reader before upgrading. Read saved decisions with their original schema and digest. [#8956](https://github.com/loopx-project/loopx/pull/8956) + **How to verify:** Verify `2.4.0` and the owning environment, then open an existing Goal and its original task or confirm a new draft in Chat. For a registry with legacy metadata, the following check must pass after migration. **Contributors:** Release maintainer @huangruiteng and the 20 contributors credited below. [Community Contributors](#community-contributors) @@ -77,7 +79,7 @@ loopx authority-archive upgrade --all-known --require-current ## Benchmarks & Integrations - Private App feedback delivery stays off the reply's blocking path. Recovered native mentions retain their original frozen Turn and reply destination. [#8858](https://github.com/loopx-project/loopx/pull/8858), [#8893](https://github.com/loopx-project/loopx/pull/8893) -- External hosts can explicitly ask for the complete Turn envelope. If the response is progressive, use the supplied digest-bound reader to select the current section. Recovery verifies the original saved capture and mode. Windows gets fixes for PowerShell quoting and CLI output probing. [#8489](https://github.com/loopx-project/loopx/pull/8489), [#8529](https://github.com/loopx-project/loopx/pull/8529), [#8535](https://github.com/loopx-project/loopx/pull/8535), [#8641](https://github.com/loopx-project/loopx/pull/8641), [#8817](https://github.com/loopx-project/loopx/pull/8817) +- New JSON guard decisions use the complete v1 contract. If a Host enables progressive presentation, use the supplied digest-bound reader to open the current section. Recovery verifies the original saved capture and mode. Windows gets fixes for PowerShell quoting and CLI output probing. [#8956](https://github.com/loopx-project/loopx/pull/8956), [#9017](https://github.com/loopx-project/loopx/pull/9017), [#8489](https://github.com/loopx-project/loopx/pull/8489), [#8529](https://github.com/loopx-project/loopx/pull/8529), [#8535](https://github.com/loopx-project/loopx/pull/8535), [#8641](https://github.com/loopx-project/loopx/pull/8641), [#8817](https://github.com/loopx-project/loopx/pull/8817) - An existing Docker benchmark controller can preview changing its staged CLI source at an owned idle boundary. The adapter delivers source provenance. Effectiveness and efficiency require comparable completed outcomes and total-cost evidence. [#8501](https://github.com/loopx-project/loopx/pull/8501) ## Documentation & Compatibility @@ -134,20 +136,20 @@ loopx --format json quota should-run --goal-id "$LOOPX_GOAL_ID" --agent-id "$LOO ### Complete Turn context for external hosts -**Activation:** Add `--complete-turn` to JSON `quota should-run` in an external host that can consume the complete v1 contract. Give it an explicit fresh Turn ID and a writable capture directory. +**Activation:** An external Host that consumes complete v1 can enable stateless progressive presentation with `--context-delivery on --delta-delivery off` (omitting `--delta-delivery off` with `--context-delivery on` requires a supported declared Codex or benchmark run mode). Supply a fresh Turn ID and a new private capture directory. Either compatibility alias, `--complete-turn` or `--turn-envelope`, composes the same v1 decision as the ordinary JSON guard. -**Validation:** Confirm `loopx_turn_envelope_v1` on the returned or saved decision. Finish its required Goal/context reads and follow the same Turn's execution and settlement contract. Follow the pinned reader supplied with a progressive response and verify the original digest and Turn identity. +**Validation:** Confirm `loopx_turn_envelope_v1` on the returned plain decision or saved `decision.json` capture. Finish its required Goal/context reads and follow the same Turn's execution and settlement contract. Follow the pinned reader supplied with a progressive `context_capture_navigation_v1` response and verify the original digest and Turn identity. -**Disable / rollback:** Omit `--complete-turn` from subsequent requests to return to the prior context path. Keep the original digest-bound commands for existing captures. +**Disable / rollback:** Use `--context-delivery off --delta-delivery off` for plain v1 JSON. To resume with the earlier live contract, use the installation owner's compatible rollback procedure. Verify that the target can read current authority state and keep the digest-bound commands for existing captures. **Authority boundary:** The current Goal, Agent, admission, permissions, required reads and Stop conditions govern the Turn. -**Docs:** [Turn envelope reference](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/protocols/turn-envelope-v0.md) +**Docs:** [Turn envelope reference](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/protocols/turn-envelope-v0.md), [In-place upgrade and recovery](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/guides/agent-upgrade.md) ```bash loopx --format json quota should-run --goal-id "$LOOPX_GOAL_ID" \ --agent-id "$LOOPX_AGENT_ID" --turn-instance-id "$LOOPX_TURN_ID" \ - --complete-turn --decision-output-dir ./complete-001 + --context-delivery on --delta-delivery off --decision-output-dir ./complete-001 ``` The reader's JSON Pointer selects a field inside the captured JSON; it is not a filesystem path. Copy the returned current reader reference into `CAPTURE_READER`. Listing and selecting the current capture does not require reading an older delta baseline or creating another admission. @@ -255,6 +257,7 @@ loopx extension doctor --all-enabled --execute - The package version and tag are `2.4.0` / `v2.4.0`. Confirm availability through the current installation owner, then verify the same Goal and original task after upgrading. - Check ordinary File/SQLite write compatibility, original receipts and lease records, and rejection of a newer incompatible field set separately. Historical reads from an inert backup do not reactivate a modern Goal. - Final clean commit/tree/version/tag, complete packaged pages, native Host, platform artifacts, real-model checks, the personal illustrated guide and public distribution remain separately evidenced under the [release contract](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/product/release-readiness.md). This usage guide is not a qualification receipt. +- Public runtime archives and signed desktop packages check their committed default contract. Promoting complete v1 as the public default requires matched single-session outcomes, full cost and qualification of the supported profiles. [#9018](https://github.com/loopx-project/loopx/pull/9018) - This release describes reliability and workflow changes. No net long-horizon outcome gain is asserted. ## 中文摘要 @@ -287,6 +290,8 @@ loopx extension doctor --all-enabled --execute **是否有破坏性变更:** 有。Registry 停用旧 `status: paused/stopped`,暂停与恢复统一使用 `activation.state` 和 Goal lifecycle 命令。通过备份迁移保留原暂停意图。直接 pip 安装、源码运行或恢复旧备份后,可先只读检查,持有相应权限的 owner 再执行迁移。 [#8431](https://github.com/loopx-project/loopx/pull/8431) +2.4.0 候选的 JSON guard 默认组合 `loopx_turn_envelope_v1`(默认渐进交付下 stdout 可返回 `context_capture_navigation_v1`,传入 `--context-delivery off` 返回完整 JSON)。仍解析旧 quota packet 或 v0 envelope 的外部 Host,需要在升级前支持 v1。已保存的决策按原 schema 和摘要读取。 [#8956](https://github.com/loopx-project/loopx/pull/8956) + **如何验证:** 确认版本为 2.4.0 和 `loopx doctor` 状态,打开既有 Goal 与原任务,或在 Chat 确认新草稿。迁移旧 registry 后确认英文段的只读命令通过。 **贡献者:** 发布维护者 @huangruiteng 与下文列出的 20 位社区贡献者,其中 9 位首次获合并。 [社区贡献者](#社区贡献者) @@ -312,7 +317,7 @@ loopx extension doctor --all-enabled --execute ### 基准与集成 - App 私聊反馈不再阻塞主回复;恢复的原生 mention 保持原冻结 Turn 和回复位置。 [#8858](https://github.com/loopx-project/loopx/pull/8858), [#8893](https://github.com/loopx-project/loopx/pull/8893) -- 外部 Host 可显式选择完整 Turn envelope,分段结果可用随附的摘要绑定 reader 读取当前所需片段,恢复会核对原捕获和模式。Windows 修复 PowerShell 引号和 CLI 输出探针。现有 Docker 基准控制器可在已持有的空闲边界预览 staged CLI 源切换。效果和效率需用可比任务结果和完整成本单独验收。 [#8489](https://github.com/loopx-project/loopx/pull/8489), [#8641](https://github.com/loopx-project/loopx/pull/8641), [#8817](https://github.com/loopx-project/loopx/pull/8817), [#8501](https://github.com/loopx-project/loopx/pull/8501) +- 新的 JSON guard 使用完整 v1 契约。Host 开启渐进交付后可用随附的摘要绑定 reader 读取当前片段,恢复时核对原捕获和模式。Windows 修复 PowerShell 引号和 CLI 输出探针。现有 Docker 基准控制器可在已持有的空闲边界预览 staged CLI 源切换。效果和效率需用可比任务结果和完整成本单独验收。 [#8956](https://github.com/loopx-project/loopx/pull/8956), [#9017](https://github.com/loopx-project/loopx/pull/9017), [#8489](https://github.com/loopx-project/loopx/pull/8489), [#8641](https://github.com/loopx-project/loopx/pull/8641), [#8817](https://github.com/loopx-project/loopx/pull/8817), [#8501](https://github.com/loopx-project/loopx/pull/8501) ### 文档与兼容性 @@ -368,20 +373,20 @@ loopx --format json quota should-run --goal-id "$LOOPX_GOAL_ID" --agent-id "$LOO #### Complete Turn context for external hosts -**启用:** 可消费完整 v1 契约的外部 Host 在 JSON `quota should-run` 上显式传入 `--complete-turn`,提供新的 Turn ID 和可写捕获目录。 +**启用:** 支持完整 v1 的外部 Host 可在 JSON `quota should-run` 上加 `--context-delivery on --delta-delivery off` 开启无状态渐进交付(单独传入 `--context-delivery on` 要求受支持的 Codex 或基准运行模式声明),提供新的 Turn ID 和私有捕获目录。`--complete-turn` 和 `--turn-envelope` 是兼容别名,分别使用时都组合与普通 JSON guard 相同的 v1 决策。 -**验证:** 在本次决策或保存的捕获中确认 `loopx_turn_envelope_v1`,完成其必读 Goal/上下文,并沿同一 Turn 的执行和结算契约推进。如返回分段导航,使用随决策返回的固定 reader,核对原摘要和 Turn 身份。 +**验证:** 在返回的完整 JSON 或保存的 `decision.json` 捕获中确认 `loopx_turn_envelope_v1`,完成其必读 Goal/上下文,并沿同一 Turn 的执行和结算契约推进。如 stdout 返回 `context_capture_navigation_v1` 分段导航,使用随决策返回的固定 reader,核对原摘要和 Turn 身份。 -**停用 / 回退:** 后续请求省略 `--complete-turn`,恢复原上下文路径。原捕获保留原摘要绑定的读取命令。 +**停用 / 回退:** 用 `--context-delivery off --delta-delivery off` 返回普通 v1 JSON。需要恢复旧实时契约时,沿安装 owner 的兼容回退流程核验目标能否读取当前权威状态。保留原捕获的摘要绑定读取命令。 **权限边界:** 继续遵循本次 Goal、Agent、准入、权限、必读内容和 Stop 条件。 -**文档:** [Turn envelope](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/protocols/turn-envelope-v0.md) +**文档:** [Turn envelope](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/protocols/turn-envelope-v0.md)、[原地升级与恢复](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/guides/agent-upgrade.md) ```bash loopx --format json quota should-run --goal-id "$LOOPX_GOAL_ID" \ --agent-id "$LOOPX_AGENT_ID" --turn-instance-id "$LOOPX_TURN_ID" \ - --complete-turn --decision-output-dir ./complete-001 + --context-delivery on --delta-delivery off --decision-output-dir ./complete-001 ``` reader 的 JSON Pointer 指向捕获 JSON 内的字段,不是文件路径。将返回的当前 reader 引用赋给 `CAPTURE_READER` 后可目录查看或选读;读取当前捕获不要求先读旧差分基线,也不需要重新准入。 @@ -472,6 +477,7 @@ loopx backup-state verify --archive "$BACKUP_ARCHIVE" --manifest "$BACKUP_MANIFE - 软件包版本与标签为 `2.4.0` / `v2.4.0`。先确认当前安装渠道已提供该版本,再升级并读回相同 Goal 与原任务。 - File/SQLite 的普通写入兼容、原回执与租约记录,以及实际新字段的旧版拒读分别核对。隔离备份的历史读回不等于现代 Goal 恢复执行。 - 最终干净 commit/tree/version/tag、完整打包页面、原生 Host、平台制品、真实模型、个人飞书图文及公开渠道验收沿[发布契约](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/product/release-readiness.md)分别记录。此用法文档不替代这些结果。 +- 公开运行时归档和签名桌面包会核验提交源码的实际默认契约。将完整 v1 设为公开默认需要可比单会话成果、完整成本以及所支持 profile 的资格证据。 [#9018](https://github.com/loopx-project/loopx/pull/9018) - 本版列出可靠性和工作流改动,不宣称已获得可比长程任务的净效果提升。 [版本源码范围](https://github.com/loopx-project/loopx/compare/v2.3.0...v2.4.0) diff --git a/docs/reference/protocols/turn-envelope-v0.md b/docs/reference/protocols/turn-envelope-v0.md index 10198cc56e..bebefc2c05 100644 --- a/docs/reference/protocols/turn-envelope-v0.md +++ b/docs/reference/protocols/turn-envelope-v0.md @@ -1,43 +1,56 @@ # TurnEnvelope v0 -`loopx_turn_envelope_v0` is an additive, bounded read model over an already -computed `quota should-run` decision. It gives an agent the next action and its -safety contract without replaying every diagnostic lane in the full quota -payload. +`loopx_turn_envelope_v0` was an additive, bounded view of an already computed +quota decision. Existing captures keep their original schema and signature. +In 2.3.0, an ordinary JSON guard returns a quota packet and the explicit +`--turn-envelope` spelling renders its v0 view. This page documents the historical representation and its current read and recovery boundaries. New quota decisions with an interaction contract compose the complete v1 source before capture and encoding. Historical captures retain their original schema and signature. An action signature compares its -registered projection; complete source-clause preservation requires its own -verification. +registered projection; full caller qualification also checks source clauses, +readback and matched use through the actual Host. The RFC's [C1 caller replacement](../../architecture/rfcs/controller-executor-unified-contract-v0.md#c1-caller-replacement-and-cutover-unit) -also covers the direct Turn producer and final host prompts. Quota CLI output +also covers the direct Turn producer and final Host prompts. Quota CLI output parity alone cannot qualify those consumers. -中文:本页记录历史版本及当前读回与恢复边界。包含交互契约的新 quota 决策在捕获 -与编码前组合完整 v1 来源。历史捕获保留原 schema 和签名。动作签名比较其注册投影, -完整来源条款的保留需要独立验证。 -RFC 的 [C1 消费链替换](../../architecture/rfcs/controller-executor-unified-contract-v0.zh-CN.md#c1-消费链替换与切换单元) +中文:`loopx_turn_envelope_v0` 是已计算 quota 决策的有界视图,本页记录历史版本及 +当前读回与恢复边界。历史捕获保留原 schema 与签名。2.3.0 的普通 JSON guard 返回 +quota packet,显式使用 `--turn-envelope` 时呈现 v0。 + +包含交互契约的新 JSON guard 在捕获与编码前组合完整 `loopx_turn_envelope_v1` 来源。 +action signature 比较其注册投影;完整调用方验收还需检查来源条款、读回以及实际 +Host 中的可比用法。RFC 的 +[C1 消费链替换](../../architecture/rfcs/controller-executor-unified-contract-v0.zh-CN.md#c1-消费链替换与切换单元) 也覆盖直接组合契约的 Turn 入口和最终 Host prompt,这两处分别验收。 ### Complete v1 Host entry / 完整 v1 Host 入口 -JSON `quota should-run` composes `loopx_turn_envelope_v1` before capture. The -saved source retains original work, acceptance, Stop, required reads and -permission facts. When progressive or Delta delivery returns navigation, -follow its pinned reader for the same admission. +Ordinary JSON `quota should-run` composes `loopx_turn_envelope_v1` before +capture. Under the default progressive presentation setting, stdout may return +a `context_capture_navigation_v1` envelope rather than the inline full document, +while the saved `decision.json` holds `loopx_turn_envelope_v1`. `--turn-envelope` +and `--complete-turn` remain mutually exclusive compatibility aliases for saved +commands, and both compose v1 in the current CLI. The saved source retains +original work, acceptance, Stop, required reads and permission facts. When +progressive or Delta delivery returns navigation, follow its pinned reader for +the same admission. ```bash loopx --format json quota should-run --goal-id --agent-id \ - --turn-instance-id --decision-output-dir ./complete-001 + --turn-instance-id --context-delivery on --delta-delivery off \ + --decision-output-dir ./complete-001 ``` -`--turn-envelope` and `--complete-turn` remain mutually exclusive inputs -for saved commands. Both use v1 in the current CLI. With no independent -Delta request, `--context-delivery off` returns the complete inline v1 -document. Read existing captures with their original digest-bound -`quota context-read` or `context-project` recovery. +Use `--context-delivery off --delta-delivery off` for plain inline v1 JSON (or +`--context-delivery off` when no independent Delta request is set). A Host that +needs the earlier live contract requires a prior runtime that can read the +current authority state. Follow the installation owner's [in-place upgrade and +recovery guidance](../../guides/agent-upgrade.md) and keep compatible backup and +runtime pairs. Read existing captures with their original digest-bound +`quota context-read` or `context-project` recovery. On 2.3.0, the parser +rejects `--complete-turn` before guard execution. `quota context-project` checks a saved complete decision before presenting it as current context, including with Delta alone or with context delivery off. @@ -61,17 +74,26 @@ the original `settlement_owed` recovery instead of a second debit. Contract composition failure preserves the decided receipt and available original capture, reports failure, and grants no work or automatic retry. -Newly generated heartbeat and same-Turn commands use the default v1 entry. -Historical benchmark runs use the recorded runner and contract version. -User task time requirements remain task context. Caller-private deadlines -and runtime guidance stay with the caller. Live Host adoption and efficiency -require separate verification. - -中文:JSON guard 在 capture 前组合完整 v1 来源。新生成的 heartbeat 和同 Turn -命令直走默认入口,旧命令仍可传入两个互斥别名之一。渐进与差分交付独立控制, -分页按原摘要读回原准入。保留原验收、Stop、权限、必读和用户任务时间要求。 -原 Todo 计划保留 effect id,原结算由同一 typed owner 投影为一条写回命令。 -部分失败沿原 `settlement_owed` 恢复。 +Newly generated heartbeat and same-Turn selection commands use the default v1 +entry. Regenerate expanded prompts against the chosen runtime after an upgrade +or compatible rollback. Historical benchmark runs use the recorded runner and +contract version, and profile-specific benchmark runners retain their own input +validation. Settings, model requests, child workers and execution allowance +remain governed by their owners. User task time requirements remain task +context; caller-private current deadlines and runtime guidance stay with the +caller. Live Host adoption and efficiency require separate verification. + +中文:包含交互契约的新 JSON guard 在 capture 前组合完整 v1 来源;默认渐进呈现下 +stdout 可能返回 `context_capture_navigation_v1` 导航,完整 v1 决策保存在 +`decision.json`。新生成的 heartbeat 和同 Turn 命令直走默认入口,旧命令仍可传入 +`--complete-turn` 与 `--turn-envelope` 两个互斥兼容别名之一。渐进与差分交付独立控制; +使用 `--context-delivery off --delta-delivery off` 可返回普通内联 v1 JSON,分页按原 +摘要读回原准入。保留原验收、Stop、权限、必读与用户任务时间要求;调用方私有倒计时 +或常驻 runtime 指导由调用方保管。可执行的原 Todo 结算复用同一 typed owner 投影为 +一条写回命令,原 effect id 保留,部分失败沿原 `settlement_owed` 恢复。升级或兼容 +回退后按所选运行时重新生成 prompt;需要旧实时契约时,沿安装 owner 的流程切到能读取 +当前权威状态的旧运行时,并保留匹配的备份和原 reader。2.3.0 会在 guard 执行前拒绝 +`--complete-turn`。 `quota context-project` 先校验已保存的完整决定,再将它呈现为当前上下文。仅开启差分 或关闭上下文交付时同样校验。来源校验失败或中断时,返回的摘要绑定 @@ -117,9 +139,12 @@ the CLI reports that boundary rather than claiming rollback. An empty capture directory is not a usable decision. Omit the option to disable capture; remove unneeded local captures through ordinary file management. -In a historical v0 capture, `detail_ref.full_decision` points to the saved -file using a quoted POSIX `cat --` command. A file-capable host -can read `detail_ref.captured_decision.path` directly instead. The typed projector +#### Historical quota and v0 display / 历史 quota 与 v0 展示 + +In a historical v0 capture (in 2.3.0, requesting both capture and +`--turn-envelope`), `detail_ref.full_decision` points to the saved file using a +quoted POSIX `cat --` command. A file-capable Host can read +`detail_ref.captured_decision.path` directly instead. The typed projector includes the expected Goal/Agent/Turn and a reference to the existing canonical source-decision hash (a hash of the JSON value, not the formatted file bytes). Verify those against the read observation, including `ok`; the link itself does @@ -134,7 +159,7 @@ coverage. New CLI captures use the complete v1 source described above. 为补读上下文重跑 guard。读取前核对身份和源哈希;旧观察不提供新的执行权限。 文件损坏或丢失不能自动重跑,选 Todo、lease 变化等仍需按原契约重新准入。 -The default ordinary quota CLI view may replace an exactly identical nested +The historical quota packet view could replace an exactly identical nested `heartbeat_recommendation.blocked_priority_fallback` diagnostic with `blocked_priority_fallback_ref="$.blocked_priority_fallback"`. Read the complete root field in that same packet; resolving this reference needs no new guard or @@ -533,16 +558,22 @@ loopx --format json heartbeat-prompt --thin --runtime-profile generic_cli \ ``` Capture and context delivery are independent. `--decision-output-root` saves -the complete decision. `--decision-handoff-socket` can hold its output for a -caller-owned checkpoint. Explicit `--context-delivery off` retains the complete -inline contract when no independent Delta delivery is requested. +the complete decision using the runtime's live schema. +`--decision-handoff-socket` can hold its output for a caller-owned checkpoint. +Explicit `--context-delivery off` retains the complete inline contract when no +independent Delta delivery is requested. New bootstrap, guard, selection and settlement-recovery commands use the complete v1 source. Saved callers can still pass `--turn-envelope` or `--complete-turn` to the current CLI under their existing input restrictions. Saved captures and their original read commands retain the recorded version and digest. Follow the original capture for selection, replan or required -detail. A persistent bootstrap binds each Turn on wake. +detail. Historical Short prompts used `--turn-envelope` with a pinned runtime +that returned v0 and `detail_ref.full_decision` for that **same invocation** +when selection, replan, an `agent_context.detail_ref` or truncation needed the +full decision; that historical renderer required thin mode, an explicit Turn +identity, a valid root and an external Host, while replan history keeps its +existing owner. A persistent bootstrap binds each Turn at wake time. 当前生成的 bootstrap、guard、选择和结算恢复命令统一使用完整 v1 来源。原先 保存的两个别名仍可按原输入限制使用,原捕获和读回命令保留其版本与摘要。 @@ -591,10 +622,9 @@ diagnostic remain unchanged. This is an output qualification, not a full-cost SL 源签名,只能补读原观察,不能重跑 quota。证据缺失或失效时暂停依赖它的规划,独立 工作保留原权限。捕获及后续写入校验仍归原 owner;输入到达不证明模型实际采用。 -中文:捕获和模型输入投影独立。`--decision-output-root` 仅保存完整决策, -`--decision-handoff-socket` 仅保留检查点交接;二者均不隐式开启 TurnEnvelope。 -历史 Short 使用曾交付 v0 的产品版本,并保留原请求与捕获。当前 C1 中 -`--turn-envelope` 是完整契约的兼容别名,已有实验按其记录版本解释。 +中文:捕获和模型输入投影独立。`--decision-output-root` 保存该运行时产生的完整决策, +`--decision-handoff-socket` 保留检查点交接。历史 Short 使用交付 v0 的固定产品版本, +保留原请求与捕获。当前 `--turn-envelope` 是完整契约的兼容别名,已有实验按记录版本解释。 The benchmark heartbeat worker verifies a historical `turn_envelope` request against the pinned CLI's v0 response before launching a model. Its read-only diff --git a/docs/reference/required-work-context.md b/docs/reference/required-work-context.md index 7ccc94349b..8792c788dc 100644 --- a/docs/reference/required-work-context.md +++ b/docs/reference/required-work-context.md @@ -701,11 +701,12 @@ Explore writeback and monitor settlement use the exact record rather than a removed list alias. No second authority store or selection rule is introduced. This changes default exact CLI/API output and Heartbeat/Turn context delivery. Regenerate saved expanded heartbeat prompts after installing the -change. Bootstrap prompts load installed rules on the next wake. TurnEnvelope -transport remains an explicit projection choice; this change alone neither -upgrades installed automations nor proves model adoption or token/latency gains. -To roll back, install the prior revision and regenerate prompts; changing a -transport flag does not restore the old exact Todo schema. +change. Bootstrap prompts load installed rules on the next wake. The +[complete v1 Host entry](protocols/turn-envelope-v0.md#complete-v1-host-entry--完整-v1-host-入口) +describes the live schema and presentation options. Model adoption and +token or latency gains require their own evidence. To restore the earlier +exact Todo schema, use a state-compatible prior release and regenerate its +prompts. ## Experimental compaction working memory