From 5e798c59f1df8c013af2062556e3cb3918834f7f Mon Sep 17 00:00:00 2001 From: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> Date: Tue, 17 Nov 2026 13:49:08 +0800 Subject: [PATCH] docs(release): document Core 2.4 upgrade and optional workflows Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com> --- docs/product/releases/v2.4.0.md | 472 ++++++++++++++++++++++++++++++++ 1 file changed, 472 insertions(+) create mode 100644 docs/product/releases/v2.4.0.md diff --git a/docs/product/releases/v2.4.0.md b/docs/product/releases/v2.4.0.md new file mode 100644 index 0000000000..d317dd0a36 --- /dev/null +++ b/docs/product/releases/v2.4.0.md @@ -0,0 +1,472 @@ +# LoopX v2.4.0 + +Keep the original work and its evidence connected after interruption. Core 2.4.0 adds one-confirmation Goal creation, searchable loaded conversations and more precise task recovery. Installation, data compatibility and optional host integrations retain their own checks. + +## At a Glance + +Create a Goal from a conversation with one confirmation. Find the original message in a loaded chat. Recover existing work through its original task and receipt after an interrupted run. + +### Upgrade + +After `v2.4.0` appears on your current distribution channel, check and apply the upgrade through that installation's owner. Review the migration below first if your registry still uses the legacy paused or stopped status. + +```bash +loopx update check +loopx update plan +loopx update apply +loopx --version +loopx doctor +``` + +### Highlights + +- **Create a Goal from Chat.** Review the draft and confirm it once. The workspace creates the Goal and opens the corresponding conversation when the required runtime and permissions are ready. [#8780](https://github.com/loopx-project/loopx/pull/8780) +- **Return to the original message.** Search a loaded conversation and open the matching message in context. [#8676](https://github.com/loopx-project/loopx/pull/8676) +- **Recover existing work in an installed workspace.** Discover the Manager through the installed CLI and resume the original authorized Task through its existing record. [#8615](https://github.com/loopx-project/loopx/pull/8615), [#8802](https://github.com/loopx-project/loopx/pull/8802), [#8830](https://github.com/loopx-project/loopx/pull/8830) +- **Keep private Lark replies tied to their conversation.** The existing private connector preserves queued messages on reconnect, exposes read-only Steward shortcuts and can return verified native images. [#8668](https://github.com/loopx-project/loopx/pull/8668), [#8695](https://github.com/loopx-project/loopx/pull/8695), [#8741](https://github.com/loopx-project/loopx/pull/8741) +- **Evaluate a remote task gateway in an isolated environment.** The source-checkout example serves scoped task commands over authenticated TLS, with per-Goal opt-in for a read-only scheduler observation. [#8508](https://github.com/loopx-project/loopx/pull/8508), [#8765](https://github.com/loopx-project/loopx/pull/8765) +- **Read a saved result after reopening.** Research results stay in place across desktop reopening. Opening a selected saved answer reads its original Turn, and quoted messages retain readable Markdown. [#8868](https://github.com/loopx-project/loopx/pull/8868), [#8863](https://github.com/loopx-project/loopx/pull/8863), [#8880](https://github.com/loopx-project/loopx/pull/8880), [#8892](https://github.com/loopx-project/loopx/pull/8892) + +### Replan Fixes + +- Intentional watches remain in replan history so the next Turn can see what it was waiting for. [#8672](https://github.com/loopx-project/loopx/pull/8672) +- When the only work in scope is blocked, the scheduler waits for its dependency. A stale heartbeat receipt is rejected before follow-up. [#8511](https://github.com/loopx-project/loopx/pull/8511), [#8708](https://github.com/loopx-project/loopx/pull/8708) + +### Contributors + +19 community contributors are credited below, including 8 first merged contributions. [Community Contributors](#community-contributors) + +## Release Decision + +**Who should upgrade:** Chat users who create Goals or revisit source messages, operators resuming installed work, and users relying on the private Lark connector benefit directly. Teams with legacy registry tooling should first update it to the current activation contract. + +**What this release solves:** It opens the conversation and Goal after one user confirmation, makes already-loaded messages searchable and improves recovery of the original work when a host or connector is interrupted. + +**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) + +**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 19 contributors credited below. [Community Contributors](#community-contributors) + +```bash +loopx --version +loopx doctor +loopx status --goal-id "$LOOPX_GOAL_ID" +loopx authority-archive upgrade --all-known --require-current +``` + +## State Kernel & Control Plane + +- Recovery retains the original Turn and debit identity while rechecking a fresh selection's gates. A validated Todo-less original Turn can recover its own receipt without a second spend. [#8894](https://github.com/loopx-project/loopx/pull/8894), [#8860](https://github.com/loopx-project/loopx/pull/8860), [#8900](https://github.com/loopx-project/loopx/pull/8900) +- Ordinary Todo edits preserve a compatible stored declaration. Once actual new fields require a newer reader, archive rollback checks the target's Todo read before switching; a failed check leaves the current runtime and data in place. [#8902](https://github.com/loopx-project/loopx/pull/8902), [#8906](https://github.com/loopx-project/loopx/pull/8906) +- Goal storage import follows the registered source and serializes the final source check with registry writers. Global discovery does not substitute another runtime for that source. An already canonical Goal needs no cold import. [#8864](https://github.com/loopx-project/loopx/pull/8864) +- Installed task recovery uses the original execution lease and receipt through the shared task lifecycle. Current host dispatch reads the complete authorized work contract, and standalone heartbeat settlement uses the installed route. [#8615](https://github.com/loopx-project/loopx/pull/8615), [#8707](https://github.com/loopx-project/loopx/pull/8707), [#8827](https://github.com/loopx-project/loopx/pull/8827) +- PostgreSQL authority archives preserve checkpoint history beyond 20,000 commits for backup and restore. Use the existing provider administration path for recovery. [#8759](https://github.com/loopx-project/loopx/pull/8759) + +## Capabilities & Workflows + +- Saved Research results retain their original answer when reopened, including historical answers whose complete snapshot must be read from its original source. [#8868](https://github.com/loopx-project/loopx/pull/8868), [#8863](https://github.com/loopx-project/loopx/pull/8863) +- The packaged workspace supplies the draft, confirmation and readback for conversational Goal creation. Its existing runtime readiness and access checks govern the authorized operation. [#8780](https://github.com/loopx-project/loopx/pull/8780) +- The material lifecycle capability can preview an evidence-bounded rerank in waves through its existing CLI. Applying a ranking remains a separately authorized owner operation. [#8579](https://github.com/loopx-project/loopx/pull/8579) + +## Quality & Testing + +- SQLite regression coverage includes lagging consumers, backup lineage, concurrent compare-and-swap and recovery after a lost response. [#8367](https://github.com/loopx-project/loopx/pull/8367), [#8482](https://github.com/loopx-project/loopx/pull/8482), [#8498](https://github.com/loopx-project/loopx/pull/8498) + +## 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) +- 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 + +- A Japanese README joins the existing public reading entrypoints. [#8839](https://github.com/loopx-project/loopx/pull/8839) +- The next DSH plugin initializer requires Core 2.4.0 for the original-Turn `quota receipt` reader. Core and the plugin have separate releases and support matrices. Updating Core does not publish or upgrade a plugin package. [#8899](https://github.com/loopx-project/loopx/pull/8899) +- A backed-up upgrade converts legacy Goal pause metadata to `activation.state`. A raw pip or source install can run `loopx authority-archive upgrade --all-known --require-current` as a read-only check. For a registry you own that requires migration, run `loopx authority-archive upgrade --all-known --execute` and retain its returned backup path. Conflicting pause metadata stays stopped pending owner review. [#8431](https://github.com/loopx-project/loopx/pull/8431) + +## Community Contributors + +- [@2430468136](https://github.com/2430468136) (first merged contribution) — Unified report and testing field ownership. [#8832](https://github.com/loopx-project/loopx/pull/8832), [#8833](https://github.com/loopx-project/loopx/pull/8833), [#8629](https://github.com/loopx-project/loopx/pull/8629) +- [@BigDataDZ](https://github.com/BigDataDZ) — Handled Windows clock skew in source leases and stabilized lease inventory ordering. [#8761](https://github.com/loopx-project/loopx/pull/8761), [#8762](https://github.com/loopx-project/loopx/pull/8762) +- [@Duang777](https://github.com/Duang777) — Rejected invalid quota clocks and timestamps, preserved same-second recovery and handled truncated history rows. [#8371](https://github.com/loopx-project/loopx/pull/8371), [#8632](https://github.com/loopx-project/loopx/pull/8632), [#8804](https://github.com/loopx-project/loopx/pull/8804), [#8681](https://github.com/loopx-project/loopx/pull/8681) +- [@GZY-SUPER-HACKER](https://github.com/GZY-SUPER-HACKER) — Decoded Codex App CLI output as UTF-8. [#8485](https://github.com/loopx-project/loopx/pull/8485) +- [@Jim-jimu](https://github.com/Jim-jimu) — Preserved Mermaid node identity and introduced authenticated remote task commands. [#8370](https://github.com/loopx-project/loopx/pull/8370), [#8508](https://github.com/loopx-project/loopx/pull/8508) +- [@LIHUA919](https://github.com/LIHUA919) — Covered SQLite consumer and recovery boundaries and rejected superseded heartbeat receipts. [#8367](https://github.com/loopx-project/loopx/pull/8367), [#8482](https://github.com/loopx-project/loopx/pull/8482), [#8498](https://github.com/loopx-project/loopx/pull/8498), [#8708](https://github.com/loopx-project/loopx/pull/8708) +- [@Luoluoluo0110](https://github.com/Luoluoluo0110) (first merged contribution) — Unified issue-close events, project-ID grammar and backlog bullet parsing. [#8636](https://github.com/loopx-project/loopx/pull/8636), [#8637](https://github.com/loopx-project/loopx/pull/8637), [#8638](https://github.com/loopx-project/loopx/pull/8638) +- [@Seyamalam](https://github.com/Seyamalam) (first merged contribution) — Repaired Issue Fix reviewer protocol links. [#8834](https://github.com/loopx-project/loopx/pull/8834) +- [@ZaynQuinn](https://github.com/ZaynQuinn) (first merged contribution) — Preserved quiet Codex App completion receipts. [#8454](https://github.com/loopx-project/loopx/pull/8454) +- [@cocolord](https://github.com/cocolord) — Migrated legacy Goal pause metadata, added one-confirmation Goal creation and repaired installed Manager discovery. [#8431](https://github.com/loopx-project/loopx/pull/8431), [#8780](https://github.com/loopx-project/loopx/pull/8780), [#8830](https://github.com/loopx-project/loopx/pull/8830) +- [@eltociear](https://github.com/eltociear) (first merged contribution) — Added the Japanese README and linked it from the existing public entrypoints. [#8839](https://github.com/loopx-project/loopx/pull/8839) +- [@gcl-coder](https://github.com/gcl-coder) — Preserved exact Git paths through Issue Fix, canary and Change Quality. [#8426](https://github.com/loopx-project/loopx/pull/8426), [#8585](https://github.com/loopx-project/loopx/pull/8585), [#8645](https://github.com/loopx-project/loopx/pull/8645) +- [@lurenxiao1998](https://github.com/lurenxiao1998) (first merged contribution) — Preserved intentional watches in replan history. [#8672](https://github.com/loopx-project/loopx/pull/8672) +- [@mojunzi](https://github.com/mojunzi) (first merged contribution) — Enabled owner closeout of an exact linked user gate for a single-agent Goal. [#8844](https://github.com/loopx-project/loopx/pull/8844) +- [@psychologister](https://github.com/psychologister) (first merged contribution) — Routed recall hashes and review vocabulary through their canonical owners. [#8611](https://github.com/loopx-project/loopx/pull/8611), [#8826](https://github.com/loopx-project/loopx/pull/8826) +- [@songoow](https://github.com/songoow) — Proposed context policy based on billion-context research. [#8453](https://github.com/loopx-project/loopx/pull/8453) +- [@steven-kid](https://github.com/steven-kid) — Exposed Host failure evidence and made original chat messages searchable. [#8642](https://github.com/loopx-project/loopx/pull/8642), [#8676](https://github.com/loopx-project/loopx/pull/8676) +- [@xiaobaifly7](https://github.com/xiaobaifly7) — Preserved blocked waits, hard pauses and the separation of monitor observations from user-gate completion. [#8510](https://github.com/loopx-project/loopx/pull/8510), [#8511](https://github.com/loopx-project/loopx/pull/8511), [#8533](https://github.com/loopx-project/loopx/pull/8533), [#8770](https://github.com/loopx-project/loopx/pull/8770) +- [@xyx2002OvO](https://github.com/xyx2002OvO) — Fixed pinned settlement quoting on Windows and bounded error payloads. [#8641](https://github.com/loopx-project/loopx/pull/8641), [#8643](https://github.com/loopx-project/loopx/pull/8643) + +## Optional Capability Activation & Use + +### Remote task gateway + +**Activation:** From a source checkout with a qualified Node runtime and `npm ci --ignore-scripts`, provision an isolated PostgreSQL authority schema, a restricted runtime role, a service policy and TLS credentials. Start the service as shown below. Optional scheduler observation requires an explicit `remote_authority.enabled: true` for one registered Goal plus its HTTPS origin, verified tenant and store identity, scoped actor, stable existing probe Todo and private CA path when applicable. + +**Validation:** Recover a known operation receipt with the example client and a prepared `command.json`. For the configured Goal, use `quota should-run` to read the bounded remote observation through the normal scheduler. + +**Disable / rollback:** Set `remote_authority.enabled: false` on the affected Goal. Stop the listener and remove its access grants to retire the service. PostgreSQL retains its receipts. + +**Authority boundary:** The scoped principal and restricted PostgreSQL role define task mutation rights. Host observation is read-only. For a resource-scoped read-only listener, select `loopx_remote_authority_scoped_read_policy_v1` and authorize each exact Goal lifetime, Todo and audience. Supply its original creation or first-adoption receipt; absent proof stays unavailable. That listener rejects writes and withholds free-form notes, lease keys and global provider revisions. Remove the matching grant or ACL entry to revoke subsequent admissions. Local admission, owner Stop and quota remain authoritative. [#8861](https://github.com/loopx-project/loopx/pull/8861) + +**Docs:** [Remote authority task service](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/remote-authority-task-service-v0.md) + +```bash +node --experimental-strip-types examples/coordination/remote-authority-service.ts \ + --policy "$SERVICE_POLICY" --cert "$TLS_CERT" --key "$TLS_KEY" --host 127.0.0.1 --port 8443 +# In the scoped client environment, with the service credential loaded privately: +node --experimental-strip-types examples/coordination/remote-authority-client.ts \ + --endpoint "$SERVICE_HTTPS_ORIGIN" --ca "$TLS_CA" --recover < command.json +loopx --format json quota should-run --goal-id "$LOOPX_GOAL_ID" --agent-id "$LOOPX_AGENT_ID" +``` + +### 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. + +**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. + +**Disable / rollback:** Omit `--complete-turn` from subsequent requests to return to the prior context path. Keep the original 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) + +```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 +``` + +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. + +```bash +loopx --format json quota context-read --reference-file "$CAPTURE_READER" --list --list-depth 2 +loopx --format json quota context-read --reference-file "$CAPTURE_READER" --select /selected_todo +``` + +A selected Todo is only part of the contract. Read its applicable Goal requirements, constraints and required sources before work. Keep the original Turn, capture and settlement identity after compaction or recovery. A diagnostic-only recovery response grants no execution. + +### Material wave rerank preview + +**Activation:** Supply a request with ordered material references and exact-read annotations to `plan-wave-rerank`. + +**Validation:** Review proposed ordering, protected items and coverage of the exact input. The preview uses the material lifecycle contract. + +**Disable / rollback:** Stop invoking the preview or discard its output. If an operator separately applies a plan, recover through the original material lifecycle rollback receipt. + +**Authority boundary:** The command is stateless. Applying or rolling back a ranking uses the material owner's authorized operation and current revision. + +**Docs:** [Material lifecycle capability](https://github.com/loopx-project/loopx/blob/v2.4.0/loopx/capabilities/material_lifecycle/README.md) + +```bash +loopx material-lifecycle architecture --format json +loopx material-lifecycle plan-wave-rerank --input request.json --format json +``` + +### Private Lark conversations + +**Activation:** In an authorized local installation, install the bundled `loopx-lark` provider if needed, then enable that provider and connect the private conversation in the workspace's Lark settings using its existing authorized account. + +**Validation:** Read the provider doctor result. From your own configured private conversation, send an authorized test request and verify that the reply, shortcut or returned image appears in that same conversation. After a reconnect, check that a queued request appears once and reaches its original destination. + +**Disable / rollback:** Disconnect the configured conversation. To retire this local provider, disable it and stop its host-managed collector if one is running. + +**Authority boundary:** The connector uses the established conversation binding, provider identity and granted permissions. The Steward shortcuts are read-only. Image delivery follows the original private reply scope. + +**Docs:** [The Lark extension lifecycle](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/extensions.md#runtime-lifecycle) + +```bash +loopx extension install --bundled loopx-lark --execute --format json +loopx extension enable loopx-lark --execute --format json +loopx extension doctor loopx-lark --execute --format json +# To retire the local provider: +loopx extension disable loopx-lark --execute --format json +``` + +### Staged benchmark CLI activation + +**Activation:** An existing authorized Docker benchmark controller stages a qualified source revision into its versioned release directory and previews its existing owned launcher with `activate_cli_source(..., execute=False)`. Provide the exact run identity, archive digest and required source, native receipt and current Stop callbacks. Revalidate those inputs before any explicitly authorized execution. + +**Validation:** Run the source-checkout receipt-readback test below. For an authorized actual change, follow the source identity and launcher readback and observe the next real Host input separately. + +**Disable / rollback:** Omit activation to keep the current launcher. For an interrupted switch, reconcile the original owned receipt with `reconcile=True`. An explicitly authorized `repair="old"` uses current control and reverified source identity. + +**Authority boundary:** The existing controller owns the worker lock, Stop policy and finite allowance. The activation changes its future CLI subprocesses and requires separate execution authorization. + +**Docs:** [Host CLI source activation](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/protocols/host-cli-source-activation-v0.md) + +```bash +uv run --extra test python -m pytest -q tests/control_plane/test_cli_source_activation_readback.py +``` + +### Private backup inspection + +**Activation:** In Settings → Capability Center → device defaults → Configuration backup and recovery, choose Full archive inspection for the original archive and matching external manifest. Unsupported services/platforms leave the operation unavailable. The CLI operations below are per-command. Preview a private full-state backup for the project and the selected configuration cohort before creating it. Retain the matching archive, external manifest and compatible package. [#8864](https://github.com/loopx-project/loopx/pull/8864) + +**Validation:** Verify the pair before extraction. Only `--execute` creates the new inert inspection directory; it does not activate an authority or start a Host. Review included and missing sources. + +**Disable / rollback:** Stop invoking the commands or omit `--execute`. Preserve retained backups privately. Reinstalling an older runtime does not reverse newer data writes; keep the current runtime when a target reader cannot verify them, and use the owning recovery process for further changes. + +**Authority boundary:** An archive or restored historical lease is evidence, not a new execution grant. Full modern reactivation requires its own identity, pending-effect and admission checks. Never unpack an old archive over live state. + +**Docs:** [Configuration backup and recovery](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/configuration-backup.md#full-state-recovery-after-cold-import), [Agent-assisted in-place upgrade](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/guides/agent-upgrade.md) + +```bash +loopx backup-state --project "$PROJECT_ROOT" --current-project-only \ + --configuration-goal-id "$LOOPX_GOAL_ID" --no-automations --no-skills \ + --output-dir "$PRIVATE_BACKUP_DIR" +# After reviewing the plan and within the existing authorization, repeat with --execute. +loopx backup-state verify --archive "$BACKUP_ARCHIVE" --manifest "$BACKUP_MANIFEST" \ + --destination "$NEW_INSPECTION_DIR" +``` + +## Install / Update + +For a new PyPI install, run the following once `2.4.0` is available, then restart the agent host. + +```bash +python3 -m pip install --upgrade 'loopx==2.4.0' +loopx workflow-skills --install +loopx slash-commands --install +loopx doctor +``` + +For an existing pip, pipx or archive install, use the explicit update commands above. To revalidate enabled extensions, use the existing operator path. + +```bash +loopx extension doctor --all-enabled --execute +``` + +## Verification boundaries + +- 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. +- This release describes reliability and workflow changes. No net long-horizon outcome gain is asserted. + +## 中文摘要 + +本页说明 Core 2.4.0 的升级与可选能力用法:在对话中确认 Goal、回到原消息,并按原任务及回执恢复工作。安装、数据兼容与可选 Host 集成分别核验。 + +在对话里确认一次即可创建 Goal。搜索已载入的会话并回到原消息。中断后可通过原任务和原回执继续。 + +### 升级 + +现有安装渠道提供 2.4.0 后,依次执行 `loopx update check`、`loopx update plan`、`loopx update apply`,再运行 `loopx --version` 和 `loopx doctor`。仍使用旧暂停字段的 registry 先核对下方迁移路径。 + +### 主要变化 + +- 在 Chat 检查并确认 Goal 草稿一次,运行环境和权限就绪后打开对应会话。搜索也可以从已载入会话直接定位原消息。 [#8780](https://github.com/loopx-project/loopx/pull/8780), [#8676](https://github.com/loopx-project/loopx/pull/8676) +- 已安装工作台可经 CLI 发现 Manager,按原任务记录继续已授权工作。 [#8615](https://github.com/loopx-project/loopx/pull/8615), [#8802](https://github.com/loopx-project/loopx/pull/8802), [#8830](https://github.com/loopx-project/loopx/pull/8830) +- 现有飞书私聊连接器在重连时保留排队消息,提供 Steward 只读快捷卡片,并支持带回读确认的原生图片回复。 [#8668](https://github.com/loopx-project/loopx/pull/8668), [#8695](https://github.com/loopx-project/loopx/pull/8695), [#8741](https://github.com/loopx-project/loopx/pull/8741) +- 源码检出可在隔离环境试用经过 TLS 认证的远程任务网关,并为指定 Goal 显式开启调度器只读观测。 [#8508](https://github.com/loopx-project/loopx/pull/8508), [#8765](https://github.com/loopx-project/loopx/pull/8765) +- 重开桌面时保留原研究结果,打开指定已保存回答时读回其原 Turn;引用消息继续使用清晰的 Markdown 正文。 [#8868](https://github.com/loopx-project/loopx/pull/8868), [#8863](https://github.com/loopx-project/loopx/pull/8863), [#8880](https://github.com/loopx-project/loopx/pull/8880), [#8892](https://github.com/loopx-project/loopx/pull/8892) + +### 重规划修复 + +- 保留重规划历史中的主动监控事项。唯一范围内任务被依赖阻塞时等待,已被替换的 heartbeat 回执会在后续执行前拒绝。 [#8672](https://github.com/loopx-project/loopx/pull/8672), [#8511](https://github.com/loopx-project/loopx/pull/8511), [#8708](https://github.com/loopx-project/loopx/pull/8708) + +### 升级决策 + +**谁需要升级:**在 Chat 创建 Goal 或回看原消息、使用已安装运行时恢复工作、通过飞书私聊收发的用户可优先升级。仍有脚本直接编辑旧 registry 状态的团队先迁移调用。 + +**解决了什么:**把创建 Goal 和打开对应会话压到一次确认,并改善已载入消息检索及 Host 或连接器中断后的原任务恢复。 + +**是否有破坏性变更:**有。Registry 停用旧 `status: paused/stopped`,暂停与恢复统一使用 `activation.state` 和 Goal lifecycle 命令。通过备份迁移保留原暂停意图。直接 pip 安装、源码运行或恢复旧备份后,可先只读检查,持有相应权限的 owner 再执行迁移。 [#8431](https://github.com/loopx-project/loopx/pull/8431) + +**如何验证:**确认版本为 2.4.0 和 `loopx doctor` 状态,打开既有 Goal 与原任务,或在 Chat 确认新草稿。迁移旧 registry 后确认英文段的只读命令通过。 + +**贡献者:**发布维护者 @huangruiteng 与下文列出的 19 位社区贡献者。 [社区贡献者](#社区贡献者) + +### 状态内核与控制面 + +- 恢复原 Turn 和扣额身份时仍核对新选择的门禁;已验证的无 Todo 原 Turn 可以读取自己的回执,避免再次扣额。 [#8894](https://github.com/loopx-project/loopx/pull/8894), [#8860](https://github.com/loopx-project/loopx/pull/8860), [#8900](https://github.com/loopx-project/loopx/pull/8900) +- 普通 Todo 修改保留兼容声明;实际新字段需要新版读取器时,归档回退先由目标版本读取 Todo,失败则保留当前运行时与数据。 [#8902](https://github.com/loopx-project/loopx/pull/8902), [#8906](https://github.com/loopx-project/loopx/pull/8906) +- 存储导入沿已注册的真实源执行,并与 registry 写方串行完成最后检查;全局发现不以其他 runtime 代替源。已采用 canonical authority 的 Goal 无需再次导入。 [#8864](https://github.com/loopx-project/loopx/pull/8864) +- 安装环境的任务恢复继续使用原执行租约和回执。Host 从完整工作契约获取当前调度,standalone heartbeat 可经现有安装入口完成结算。PostgreSQL 支持超过 20,000 条提交历史的 checkpoint 备份和恢复。 [#8615](https://github.com/loopx-project/loopx/pull/8615), [#8707](https://github.com/loopx-project/loopx/pull/8707), [#8827](https://github.com/loopx-project/loopx/pull/8827), [#8759](https://github.com/loopx-project/loopx/pull/8759) + +### 能力与工作流 + +- 研究结果重开后保留原回答;历史回答的完整快照按其原来源读取。 [#8868](https://github.com/loopx-project/loopx/pull/8868), [#8863](https://github.com/loopx-project/loopx/pull/8863) +- 打包工作台交付 Goal 草稿、确认与读回流程。材料能力提供分波排序预览,应用排序仍经过材料 owner 的授权操作。 [#8780](https://github.com/loopx-project/loopx/pull/8780), [#8579](https://github.com/loopx-project/loopx/pull/8579) + +### 质量与测试 + +- SQLite 回归覆盖落后消费者、备份 lineage、并发 CAS 和响应丢失恢复。 [#8367](https://github.com/loopx-project/loopx/pull/8367), [#8482](https://github.com/loopx-project/loopx/pull/8482), [#8498](https://github.com/loopx-project/loopx/pull/8498) + +### 基准与集成 + +- 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) + +### 文档与兼容性 + +- 新增日文 README,并接入现有公开阅读入口。 [#8839](https://github.com/loopx-project/loopx/pull/8839) +- 下一版 DSH 插件初始化器需要 Core 2.4.0 的原 Turn `quota receipt` 读取能力。Core 与插件分别发布并核对支持矩阵,升级 Core 不会自动发布或升级插件包。 [#8899](https://github.com/loopx-project/loopx/pull/8899) +- 用 `loopx authority-archive upgrade --all-known --require-current` 检查旧暂停字段。如果需要迁移,获授权的 registry owner 可运行 `loopx authority-archive upgrade --all-known --execute`,并保留返回的备份路径。字段冲突时保持停止,交由 owner 核对。 [#8431](https://github.com/loopx-project/loopx/pull/8431) + +### 社区贡献者 + +- [@2430468136](https://github.com/2430468136)(首次获合并) — 统一报告 schema、可见范围和测试字段的 owner。 [#8832](https://github.com/loopx-project/loopx/pull/8832), [#8833](https://github.com/loopx-project/loopx/pull/8833), [#8629](https://github.com/loopx-project/loopx/pull/8629) +- [@BigDataDZ](https://github.com/BigDataDZ) — 处理 Windows 来源租约时钟偏差,固定租约清单排序。 [#8761](https://github.com/loopx-project/loopx/pull/8761), [#8762](https://github.com/loopx-project/loopx/pull/8762) +- [@Duang777](https://github.com/Duang777) — 拒绝异常额度时钟和时间,保留同秒恢复,并处理截断的历史行。 [#8371](https://github.com/loopx-project/loopx/pull/8371), [#8632](https://github.com/loopx-project/loopx/pull/8632), [#8804](https://github.com/loopx-project/loopx/pull/8804), [#8681](https://github.com/loopx-project/loopx/pull/8681) +- [@GZY-SUPER-HACKER](https://github.com/GZY-SUPER-HACKER) — 按 UTF-8 读取 Codex App CLI 输出。 [#8485](https://github.com/loopx-project/loopx/pull/8485) +- [@Jim-jimu](https://github.com/Jim-jimu) — 保留 Mermaid 节点身份,新增带认证的远程任务命令。 [#8370](https://github.com/loopx-project/loopx/pull/8370), [#8508](https://github.com/loopx-project/loopx/pull/8508) +- [@LIHUA919](https://github.com/LIHUA919) — 覆盖 SQLite 消费与恢复边界,并拒绝被替换的 heartbeat 回执。 [#8367](https://github.com/loopx-project/loopx/pull/8367), [#8482](https://github.com/loopx-project/loopx/pull/8482), [#8498](https://github.com/loopx-project/loopx/pull/8498), [#8708](https://github.com/loopx-project/loopx/pull/8708) +- [@Luoluoluo0110](https://github.com/Luoluoluo0110)(首次获合并) — 统一 issue 关闭事件、project ID 规则和 backlog 条目语法。 [#8636](https://github.com/loopx-project/loopx/pull/8636), [#8637](https://github.com/loopx-project/loopx/pull/8637), [#8638](https://github.com/loopx-project/loopx/pull/8638) +- [@Seyamalam](https://github.com/Seyamalam)(首次获合并) — 修复 Issue Fix 的评审协议链接。 [#8834](https://github.com/loopx-project/loopx/pull/8834) +- [@ZaynQuinn](https://github.com/ZaynQuinn)(首次获合并) — 保留 Codex App 静默完成回执。 [#8454](https://github.com/loopx-project/loopx/pull/8454) +- [@cocolord](https://github.com/cocolord) — 迁移旧 Goal 暂停元数据,交付一次确认创建 Goal,并修复安装环境的 Manager 发现。 [#8431](https://github.com/loopx-project/loopx/pull/8431), [#8780](https://github.com/loopx-project/loopx/pull/8780), [#8830](https://github.com/loopx-project/loopx/pull/8830) +- [@eltociear](https://github.com/eltociear)(首次获合并) — 新增日文 README,并接入已有公开入口。 [#8839](https://github.com/loopx-project/loopx/pull/8839) +- [@gcl-coder](https://github.com/gcl-coder) — 让 Issue Fix、canary 和 Change Quality 保留准确的 Git 路径。 [#8426](https://github.com/loopx-project/loopx/pull/8426), [#8585](https://github.com/loopx-project/loopx/pull/8585), [#8645](https://github.com/loopx-project/loopx/pull/8645) +- [@lurenxiao1998](https://github.com/lurenxiao1998)(首次获合并) — 在重规划历史中保留主动监控。 [#8672](https://github.com/loopx-project/loopx/pull/8672) +- [@mojunzi](https://github.com/mojunzi)(首次获合并) — 让 owner 可以收口单 Agent Goal 中精确关联的用户门禁。 [#8844](https://github.com/loopx-project/loopx/pull/8844) +- [@psychologister](https://github.com/psychologister)(首次获合并) — 将召回摘要与评审词汇交回对应的 canonical owner。 [#8611](https://github.com/loopx-project/loopx/pull/8611), [#8826](https://github.com/loopx-project/loopx/pull/8826) +- [@songoow](https://github.com/songoow) — 提出基于 billion-context 研究的上下文策略。 [#8453](https://github.com/loopx-project/loopx/pull/8453) +- [@steven-kid](https://github.com/steven-kid) — 呈现 Host 失败证据,支持检索原会话消息。 [#8642](https://github.com/loopx-project/loopx/pull/8642), [#8676](https://github.com/loopx-project/loopx/pull/8676) +- [@xiaobaifly7](https://github.com/xiaobaifly7) — 保留依赖等待与硬暂停,并区分监控观测和用户门禁完成。 [#8510](https://github.com/loopx-project/loopx/pull/8510), [#8511](https://github.com/loopx-project/loopx/pull/8511), [#8533](https://github.com/loopx-project/loopx/pull/8533), [#8770](https://github.com/loopx-project/loopx/pull/8770) +- [@xyx2002OvO](https://github.com/xyx2002OvO) — 修复 Windows 固定入口结算命令引号,并控制错误载荷大小。 [#8641](https://github.com/loopx-project/loopx/pull/8641), [#8643](https://github.com/loopx-project/loopx/pull/8643) + +### 可选能力启用与使用 + +#### Remote task gateway + +**启用:**从源码检出准备合格的 Node、`npm ci --ignore-scripts`、隔离 PostgreSQL authority schema、受限角色、服务策略与 TLS 证书,运行服务示例。调度器观测另需在某个已注册 Goal 显式设置 `remote_authority.enabled: true`,绑定 HTTPS origin、已核验的 tenant 和 store identity、授权 Agent、既有 probe Todo 和所需私有 CA。 + +**验证:**用示例客户端和已准备的 `command.json` 读取既有操作回执。通过 `quota should-run` 查看当前 Goal 的远程只读观测。 + +**停用 / 回退:**在该 Goal 设置 `remote_authority.enabled: false`。停止监听器并撤销访问授权可停用服务。PostgreSQL 保留已写回执。 + +**权限边界:**远程写入由受限 principal、数据库角色和策略控制。Host 观测提供只读输入。逐资源只读 listener 选择 `loopx_remote_authority_scoped_read_policy_v1`,精确授权 Goal lifetime、Todo 与接收者,并提供原创建或首次采用回执;缺少来源证明时保持不可用。该 listener 拒绝写命令,不返回自由文本、租约密钥或全局 provider revision。移除对应 grant 或 ACL 项可撤销后续准入,继续遵循本地准入、Stop 和额度约束。 [#8861](https://github.com/loopx-project/loopx/pull/8861) + +**文档:**[远程任务网关](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/remote-authority-task-service-v0.md) + +```bash +node --experimental-strip-types examples/coordination/remote-authority-service.ts \ + --policy "$SERVICE_POLICY" --cert "$TLS_CERT" --key "$TLS_KEY" --host 127.0.0.1 --port 8443 +# 另在受授权的客户端环境私下加载服务凭据后执行: +node --experimental-strip-types examples/coordination/remote-authority-client.ts \ + --endpoint "$SERVICE_HTTPS_ORIGIN" --ca "$TLS_CA" --recover < command.json +loopx --format json quota should-run --goal-id "$LOOPX_GOAL_ID" --agent-id "$LOOPX_AGENT_ID" +``` + +#### Complete Turn context for external hosts + +**启用:**可消费完整 v1 契约的外部 Host 在 JSON `quota should-run` 上显式传入 `--complete-turn`,提供新的 Turn ID 和可写捕获目录。 + +**验证:**在本次决策或保存的捕获中确认 `loopx_turn_envelope_v1`,完成其必读 Goal/上下文,并沿同一 Turn 的执行和结算契约推进。如返回分段导航,使用随决策返回的固定 reader,核对原摘要和 Turn 身份。 + +**停用 / 回退:**后续请求省略 `--complete-turn`,恢复原上下文路径。原捕获保留原摘要绑定的读取命令。 + +**权限边界:**继续遵循本次 Goal、Agent、准入、权限、必读内容和 Stop 条件。 + +**文档:**[Turn envelope](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/protocols/turn-envelope-v0.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 +``` + +reader 的 JSON Pointer 指向捕获 JSON 内的字段,不是文件路径。将返回的当前 reader 引用赋给 `CAPTURE_READER` 后可目录查看或选读;读取当前捕获不要求先读旧差分基线,也不需要重新准入。 + +```bash +loopx --format json quota context-read --reference-file "$CAPTURE_READER" --list --list-depth 2 +loopx --format json quota context-read --reference-file "$CAPTURE_READER" --select /selected_todo +``` + +选中的 Todo 只占契约的一部分。工作前仍需读取适用的 Goal 要求、限制与必读来源;压缩或恢复后保留原 Turn、capture 和结算身份。仅用于诊断的恢复结果不授予执行权。 + +#### Material wave rerank preview + +**启用:**向 `plan-wave-rerank` 提供有序材料引用与准确读取后形成的标注。 + +**验证:**检查预览中的排序建议、受保护项和输入覆盖范围。 + +**停用 / 回退:**停止调用或丢弃预览。若另经授权应用过,以原变更回执走材料生命周期回退。 + +**权限边界:**预览是无状态的。应用或回退需要材料 owner 授权并核对当前 revision。 + +**文档:**[材料生命周期](https://github.com/loopx-project/loopx/blob/v2.4.0/loopx/capabilities/material_lifecycle/README.zh-CN.md) + +```bash +loopx material-lifecycle architecture --format json +loopx material-lifecycle plan-wave-rerank --input request.json --format json +``` + +#### Private Lark conversations + +**启用:**已获授权的本地安装可按需安装并启用内置 `loopx-lark`,然后在工作台的 Lark 设置中用已获授权的账号绑定私聊来源。 + +**验证:**读取 provider doctor。用自己已配置的私聊发出获授权的测试请求,确认回复、快捷卡片或图片回到同一会话。重连后核对排队消息只出现一次并回到原会话。 + +**停用 / 回退:**断开已配置的会话。退役本地 provider 时执行 disable,并停止还在运行的采集进程。 + +**权限边界:**沿用既有会话绑定、provider 身份和授权范围。Steward 快捷卡片只读,图片交付沿原私聊回复范围。 + +**文档:**[Lark 扩展生命周期](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/extensions.md#runtime-lifecycle) + +```bash +loopx extension install --bundled loopx-lark --execute --format json +loopx extension enable loopx-lark --execute --format json +loopx extension doctor loopx-lark --execute --format json +# 退役本地 provider 时执行: +loopx extension disable loopx-lark --execute --format json +``` + +#### Staged benchmark CLI activation + +**启用:**由已有授权的 Docker benchmark controller 将通过资格检查的源码放入版本目录,用 `activate_cli_source(..., execute=False)` 预览所持有的 launcher。传入精确运行身份、归档摘要、源码/原生回执和当前 Stop 回调。实际切换需明确授权并重新核对输入。 + +**验证:**运行下方源码检出的回执读回用例。获授权的实际切换另需验证源码与 launcher,观察下一次真实 Host 输入。 + +**停用 / 回退:**省略调用可延用当前 launcher。切换中断后用 `reconcile=True` 收敛原回执。在当前控制规则与源码一致性均通过时,由授权 owner 用 `repair="old"` 恢复旧目标。 + +**权限边界:**worker lock、Stop 与有限预算沿用原 controller。此接口作用于后续 CLI 子进程,执行需要单独授权。 + +**文档:**[Host CLI 源切换](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/protocols/host-cli-source-activation-v0.md) + +```bash +uv run --extra test python -m pytest -q tests/control_plane/test_cli_source_activation_readback.py +``` + +#### Private backup inspection + +**启用:**在 Settings → Capability Center → device defaults → Configuration backup and recovery 选择 Full archive inspection,提供原归档及匹配的外部 manifest。不支持的服务或平台保持不可用。下方 CLI 按次调用。先预览项目及所选配置范围的私有完整备份,再在现有授权内创建;保留匹配的 archive、外部 manifest 和兼容版本。 [#8864](https://github.com/loopx-project/loopx/pull/8864) + +**验证:**先验证文件对,再提取。只有 `--execute` 创建新的隔离检查目录,不激活 authority 或启动 Host;核对 included 和 missing 范围。 + +**停用 / 回退:**停止调用或省略 `--execute`,已有备份继续私有保留。重装旧运行时不会撤销新版数据写入;目标读取器无法核验时保持当前运行时,后续数据操作沿原恢复 owner。 + +**权限边界:**归档和历史租约是证据,不是新的执行授权。现代再激活另需身份、未决 effect 与准入检查;不能把旧归档直接覆盖到现用状态。 + +**文档:**[配置备份与恢复](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/reference/configuration-backup.md#full-state-recovery-after-cold-import)、[Agent 原地升级](https://github.com/loopx-project/loopx/blob/v2.4.0/docs/guides/agent-upgrade.md) + +```bash +loopx backup-state --project "$PROJECT_ROOT" --current-project-only \ + --configuration-goal-id "$LOOPX_GOAL_ID" --no-automations --no-skills \ + --output-dir "$PRIVATE_BACKUP_DIR" +# 核对预览后,在现有授权内重复命令并加 --execute。 +loopx backup-state verify --archive "$BACKUP_ARCHIVE" --manifest "$BACKUP_MANIFEST" \ + --destination "$NEW_INSPECTION_DIR" +``` + +### 发布验证 + +- 软件包版本与标签为 `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)分别记录。此用法文档不替代这些结果。 +- 本版列出可靠性和工作流改动,不宣称已获得可比长程任务的净效果提升。 + +[版本源码范围](https://github.com/loopx-project/loopx/compare/v2.3.0...v2.4.0)