Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 18 additions & 12 deletions docs/product/releases/v2.4.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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.
Expand Down Expand Up @@ -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.

## 中文摘要
Expand Down Expand Up @@ -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 位首次获合并。 [社区贡献者](#社区贡献者)
Expand All @@ -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)

### 文档与兼容性

Expand Down Expand Up @@ -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` 后可目录查看或选读;读取当前捕获不要求先读旧差分基线,也不需要重新准入。
Expand Down Expand Up @@ -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)
Loading
Loading