loopx-project · huangruiteng · Sep 2, 2026 · Sep 2, 2026
@@ -103,7 +103,7 @@ lifecycle 选择，不是所有贡献的默认终点。
 
 ## 版本基线
 
-当前内容以 LoopX GitHub release `v0.5.3` 为发布锚点；本地命令示例已按 `loopx 0.5.3` 的
+当前内容以 LoopX GitHub release `v0.5.4` 为发布锚点；本地命令示例已按 `loopx 0.5.4` 的
 公开 CLI 与协议表面复核。该版本要求 Python 3.11+ 与 Node.js 22.6+；后者运行由 LoopX 自动管理、
 空闲后退出的 TypeScript Effect runtime，用户不需要手工维护 daemon。
 
@@ -129,7 +129,7 @@ node --version
 
 ### 如何理解当前 TypeScript 改造
 
-`v0.5.3` 不是“已经把 LoopX 全部重写成 TypeScript”。当前发布基线是：
+`v0.5.4` 不是“已经把 LoopX 全部重写成 TypeScript”。当前发布基线是：
 
 - TypeScript 已拥有 Effect Program、Turn settlement、Todo completion、quota delivery routing、
   workspace causality、scheduler transition/state 等迁移切片的 canonical semantics；
@@ -140,18 +140,18 @@ node --version
 - 当前 `main` 已进入 transaction-payoff phase：后续以完整 transaction cutover 和删除旧语义
   为进展单位，不继续堆 leaf helper 与 bridge。
 
-发布态以 `v0.5.3` tag 和 release notes 为准；迁移阶段、下一批 cutover 与最终 CLI/App 收敛以
+发布态以 `v0.5.4` tag 和 release notes 为准；迁移阶段、下一批 cutover 与最终 CLI/App 收敛以
 [TypeScript Control-Plane Migration RFC](/loopx/docs/architecture/rfcs/typescript-control-plane-migration-v0/)
 的当前状态为准。RFC 中的 Stage 3/4 仍是后续方向，不应写成已经发布。
 
-### 从 `v0.4.4` 阅读基线升级到 `v0.5.3`
+### 从 `v0.4.4` 阅读基线升级到 `v0.5.4`
 
 如果你读过旧版 Dev Book，优先校准四个变化：
 
-| 主题 | `v0.5.3` 已发布事实 | 深入入口 |
+| 主题 | `v0.5.4` 已发布事实 | 深入入口 |
 | --- | --- | --- |
 | Control Plane | 多个高风险 decision/effect 已迁入 typed TypeScript transaction owner；Python facade 仍承担迁移期边界 | [迁移 RFC](/loopx/docs/architecture/rfcs/typescript-control-plane-migration-v0/) |
-| Operator surface | Personal Workspace 已提供 Goal、Task、Chat 和 read-only status source 入口；界面不是新的事实源 | [Dashboard README](https://github.com/huangruiteng/loopx/blob/v0.5.3/apps/presentation/dashboard/README.md) |
+| Operator surface | Personal Workspace 已提供 Goal、Task、Chat 和 read-only status source 入口；界面不是新的事实源 | [Dashboard README](https://github.com/huangruiteng/loopx/blob/v0.5.4/apps/presentation/dashboard/README.md) |
 | Host runtime | Codex、Claude Code、OpenCode、Pi、KunlunCode、DeepSeek Harness 与 custom runner 具有不同 activation/stop contract | [Runtime Connector Catalog](/loopx/docs/integrations/runtime-connector-catalog/) |
 | Capability / Provider | Capability 由 package-owned catalog entry、真实 command 和 durable validation 共同定义；Provider/Extension 不继承 Kernel authority | [Capability Catalog](/loopx/docs/capabilities/) |
 

@@ -114,8 +114,8 @@ Do not bypass a newer permission or lifecycle check just to make an older exampl
 
 ## Version baseline
 
-The current release anchor is LoopX GitHub release `v0.5.3`. Local command examples were checked against
-the public `loopx 0.5.3` CLI and protocol surface. This release requires Python 3.11+ and Node.js 22.6+.
+The current release anchor is LoopX GitHub release `v0.5.4`. Local command examples were checked against
+the public `loopx 0.5.4` CLI and protocol surface. This release requires Python 3.11+ and Node.js 22.6+.
 LoopX starts and reuses its managed, idle-exiting TypeScript Effect runtime automatically; users do not
 operate that runtime as a manual daemon.
 
@@ -143,7 +143,7 @@ different version identifiers imply.
 
 ### How to read the TypeScript migration
 
-`v0.5.3` does not mean that all of LoopX has been rewritten in TypeScript. The current release baseline is:
+`v0.5.4` does not mean that all of LoopX has been rewritten in TypeScript. The current release baseline is:
 
 - TypeScript owns the canonical semantics for migrated slices of the Effect Program, Turn settlement,
   Todo completion, quota delivery routing, workspace causality, and scheduler transition/state;
@@ -154,19 +154,19 @@ different version identifiers imply.
 - current `main` is in the transaction-payoff phase: later progress is measured by complete transaction
   cutovers and deleted legacy semantics, not by accumulating leaf helpers and bridge calls.
 
-Treat the `v0.5.3` tag and release notes as the shipped baseline. Use the current status of the
+Treat the `v0.5.4` tag and release notes as the shipped baseline. Use the current status of the
 [TypeScript Control-Plane Migration RFC](/loopx/docs/architecture/rfcs/typescript-control-plane-migration-v0/)
 for later cutovers and final CLI/App convergence. RFC Stages 3 and 4 remain future direction, not shipped
 behavior.
 
-### Updating your mental model from `v0.4.4` to `v0.5.3`
+### Updating your mental model from `v0.4.4` to `v0.5.4`
 
 If you read an earlier edition of the Dev Book, recalibrate these four areas first:
 
-| Area | Shipped in `v0.5.3` | Continue with |
+| Area | Shipped in `v0.5.4` | Continue with |
 | --- | --- | --- |
 | Control Plane | Several high-risk decisions and effects have typed TypeScript transaction owners; Python facades still carry migration-time boundaries | [Migration RFC](/loopx/docs/architecture/rfcs/typescript-control-plane-migration-v0/) |
-| Operator surface | Personal Workspace exposes Goal, Task, Chat, and read-only status-source entrypoints; the UI is not a new source of truth | [Dashboard README](https://github.com/huangruiteng/loopx/blob/v0.5.3/apps/presentation/dashboard/README.md) |
+| Operator surface | Personal Workspace exposes Goal, Task, Chat, and read-only status-source entrypoints; the UI is not a new source of truth | [Dashboard README](https://github.com/huangruiteng/loopx/blob/v0.5.4/apps/presentation/dashboard/README.md) |
 | Host runtime | Codex, Claude Code, OpenCode, Pi, KunlunCode, DeepSeek Harness, and custom runners have distinct activation and stop contracts | [Runtime Connector Catalog](/loopx/docs/integrations/runtime-connector-catalog/) |
 | Capability and Provider | A Capability is defined by a package-owned catalog entry, a real command, and durable validation; a Provider or Extension does not inherit Kernel authority | [Capability Catalog](/loopx/docs/capabilities/) |
 

@@ -79,16 +79,16 @@ versioned or optional functionality, not the default shape of every contribution
 - Source format: Markdown
 - Site generator: MkDocs Material
 - Hosting: GitHub Pages
-- LoopX release anchor: `v0.5.3`
+- LoopX release anchor: `v0.5.4`
 - Runtime prerequisites: Python 3.11+ and Node.js 22.6+
 
 The official public protocols remain authoritative for protocol facts. Commands that change across
 releases remain authoritative in the release you use, its current `--help`, and official documentation.
 This book owns the learning path and explanatory model, not another complete command reference.
 
-In `v0.5.3`, key semantics for the Effect Program, Turn settlement, Todo completion, quota delivery
+In `v0.5.4`, key semantics for the Effect Program, Turn settlement, Todo completion, quota delivery
 routing, workspace causality, and scheduler state sit behind typed TypeScript owners. During the
 migration, the Python CLI still owns transport, legacy projections, external Provider calls, and some
 durable writeback. These are not two independently evolving control planes. Treat the
 [TypeScript Control-Plane Migration RFC](/loopx/docs/architecture/rfcs/typescript-control-plane-migration-v0/)
-on current `main` as the direction for later stages, not as shipped `v0.5.3` behavior.
+on current `main` as the direction for later stages, not as shipped `v0.5.4` behavior.
@@ -70,15 +70,15 @@ Extension 只是可独立版本化和交付的一种路径。
 - 正文格式：Markdown；
 - 站点生成器：MkDocs Material；
 - 在线发布：GitHub Pages；
-- LoopX 发布锚点：`v0.5.3`；
+- LoopX 发布锚点：`v0.5.4`；
 - 运行时前提：Python 3.11+ 与 Node.js 22.6+。
 
 协议解释以 LoopX 官方公开合同为事实源。易变化的命令仍以对应发布物、官方文档和当前
 `--help` 为准；本书负责教学顺序与心智模型，不成为另一份完整命令参考。
 
-`v0.5.3` 已把 Effect Program、Turn settlement、Todo completion、quota delivery routing、
+`v0.5.4` 已把 Effect Program、Turn settlement、Todo completion、quota delivery routing、
 workspace causality 与 scheduler state 等关键语义放到 typed TypeScript owner 后面。Python CLI
 仍负责迁移期 transport、兼容投影、外部 Provider 调用和部分持久化写回；这不是两套可独立演进的
 控制面。当前 `main` 的后续迁移阶段以
 [TypeScript Control-Plane Migration RFC](/loopx/docs/architecture/rfcs/typescript-control-plane-migration-v0/)
-为准，不应倒推为 `v0.5.3` 已发布行为。
+为准，不应倒推为 `v0.5.4` 已发布行为。
@@ -103,7 +103,7 @@ points:
 | Runtime connectors and content workflows | DeepSeek Harness Turn adapter with real e2e smoke landed (#3188); OpenCode 1 and OpenCode 2 continuous goal loops ship (#3151); content-ops gained a layout template library and dense-cover defaults (#3222, #3223); provider-neutral PR program snapshots ship (#2814); `computer_use_runtime_v0` is now a machine-checkable protocol contract (#3279); a `loopx-community-discussion` public source provider (#3299) and a `loopx-repo-health` provider (#3272) extend public source coverage; goal-channel botmux runtime integration lands with terminal dispatches preserved and uncertain dispatches persisted, desktop chat routes through a loopback service, chat-wide routing and contextual inbox replies land (#3555), and managed and queued turn creation are serialized (#3542, #3562); the desktop added workspace language settings, localized write previews, and preserved heartbeat schedule and off-hours semantics (#3594); host parity, skill-delivery, and observable-handle thin pytest now cover the expanded host list. Post-v0.5.3, bot document comment scopes read from the published app (#3722), turn-start reaction replay is bounded (#3733), and the DSH plugin is one-step ready (#3725). | Add one provider-neutral parity slice for DeepSeek Harness, OpenCode 1/2, goal-channel botmux, content-ops delivery/readback, or desktop locale parity; keep raw transcripts, provider payloads, credentials, and host-local paths out of fixtures. |
 | Benchmark boundary | Benchmark research was reset around native runners (#3267): native Codex Goal connects to the real runtime (#3271), workers are isolated from the host (#3277), provider env binds to installed Goal profiles (#3276) with formally verified treatments (#3275) and live continuations (#3273), runtime evidence binds to the exact container (#3303), a post-run case analyst brief ships (#3289), an integrity qualification toolkit landed (#3241), source-env usage is distinguished from credential probes (#3298, #3278), and accountable closeout requires Todo validation (#3229). A provider-neutral four-arm study contract ships (#3516), alongside restricted task-source access (#3504), non-http git clones classified as network with loopback integrity probes allowed (#3510), namespaced public case ids (#3532), locked git-clone integrity boundaries (#3515), orchestrator runtime provenance, and fail-closed runtime closeout drift (#3503). Deterministic fixtures already cover GH-C99 without live scoring or uploads: `tests/capabilities/test_benchmark_four_arm_contract.py`, `tests/capabilities/test_benchmark_experiment_board.py` (orchestrator runtime provenance negatives), `tests/capabilities/test_benchmark_runtime_continuity.py` (fail-closed closeout drift), and integrity/network/task-source cases in `tests/capabilities/test_benchmark_toolkit.py`; the covered GH-C99 fixture task was retired (#3653). Public native Goal trajectory summaries now derive from compact lifecycle facts without retaining raw artifacts (#3327), completing the GH-C16 slice. Post-v0.5.3, an external agent phase ships (#3565), restricted-access suspicion adjudicates by causal use (#3747), the plan-role fidelity gate is removed (#3753), and retired fidelity references are cleaned up (#3756). Shared lifecycle, readiness, ledger, and reducer contracts remain the public seam; generic Effect Program conformance and replay tests harden settlement infrastructure but do not change benchmark scoring or authorize live runs. Live scored comparisons stay held until a fresh task-free runner lifecycle receipt proves readiness. | Extend synthetic setup/termination attribution, derive the public trajectory summary for a second non-SkillsBench adapter, or add a SWE adapter only when a second SWE route needs shared launch/observe/ingest behavior. Do not launch scoring, duplicate the controller, or expose raw task text, logs, trajectories, verifier tails, credentials, uploads, or local paths. |
 | Validation and change quality | Python tests are green on the latest runtime-bearing `main` change; public smoke parity and the frontstage Pages build are restored, with Codex App fallback receipt identity isolated (#3233); public smoke reliability was restored again (#3302), stargazer history now fetches through REST (#3320), and a repository-hygiene smoke plus release-timeline ratchet landed (#3249). The Auto Research KNN evidence-normalization smoke now gates improved/contradicted status and protected-scope checks on semantics-derived public eval fixtures rather than wall-clock speedup, completing GH-C77. Post-v0.5.3, the remaining public smoke boundaries are repaired (#3740) and public smoke fixtures are fixed (#3739). | Retain negative/mutation coverage on deterministic fixtures, and distinguish infrastructure outages from product regressions. Keep live model/provider checks explicit and low-frequency. |
-| Release and install | v0.5.3 is the latest public tag and package version (v0.5.0-v0.5.3 landed after the last board refresh). PyPI remains the default complete install path (#3301) with explicit installation ownership (#3566); canonical project links are published (#3253), derived capability/manpage surfaces are synced (#3254), exact Miaoda releases are verified in periodic-report receipts (#3508) with governed delivery (#3401), extension doctor readiness recovers across releases (#3556), doctor deep checks validate by install kind (#3736), and the public release timeline covers v0.1.3 through v0.5.3. | Keep install, activation, and recovery guidance aligned with the PyPI default and tagged stable versus post-tag `main`, and continue contributor-safe update recovery without adding a parallel release checklist. |
+| Release and install | v0.5.4 is the latest public tag and package version (v0.5.0-v0.5.4 landed after the last board refresh). PyPI remains the default complete install path (#3301) with explicit installation ownership (#3566); canonical project links are published (#3253), derived capability/manpage surfaces are synced (#3254), exact Miaoda releases are verified in periodic-report receipts (#3508) with governed delivery (#3401), extension doctor readiness recovers across releases (#3556), doctor deep checks validate by install kind (#3736), and the public release timeline covers v0.1.3 through v0.5.4. | Keep install, activation, and recovery guidance aligned with the PyPI default and tagged stable versus post-tag `main`, and continue contributor-safe update recovery without adding a parallel release checklist. |
 | Public docs and onboarding | Hosted docs, a public homepage, the Dev Book, localized dashboard copy, public/private boundary examples, GitHub issue forms, and a PR/issue label taxonomy have landed. Slash-command installation now exposes all four canonical global manager commands through their shipped CLI wrappers; fresh-project onboarding and its regression fixture landed (#3093, #3103), and harness-above positioning (#3202), ecosystem adoption and derivatives inventory (#3224), GitHub maintenance and ops automation best practices (#3227), long-horizon/commercialization strategy docs (#3217-#3220), the TypeScript control-plane migration RFC (#3226), the open strategy review process (#3295), stale-issue reminders without auto-close (#3297), welcome-all-contribution-shapes guidance (#3294), consolidated community policy (#3238), Apache-2.0 open-core adoption (#3235), a capability implementation code map (#3252) with co-located docs (#3265), outcome/extension path clarifications (#3242), the NoKV semantic-authority RFC (#3263), the long-horizon benchmark research program RFC (#3240), the published technical directions (#3248), and a DCO sign-off reminder (#3316) are public. The Auto Research stop/takeover/state-aware-wake walkthrough (GH-C43) documents the shipped control cycle without a second launcher or README first-screen change. Post-v0.5.3, the planner-worker operator guide (#3630), the hosted-docs navigation and locale-parity check (#3632), and the atomic-promotion failure matrix (#3633) land; the GH-C49 frontstage legibility polish (#3663), host no-spend parity (#3661), reward-memory walkthrough (#3659), governance Stage-2 refresh (#3657), and KNN closeout (#3654) are merged. | Keep contributor, release, protocol, course, showcase, and RFC surfaces concise and linked to public evidence; add navigation, locale, and RFC-compatibility checks without appending status narratives or aliases. |
 
 ## Turn Loop Controller Plan
@@ -138,7 +138,7 @@ points for contributors who are still learning the repository.
 | ID | Area | Task | Validation |
 | --- | --- | --- | --- |
 | GH-C02 | tests | Claimed: a PR is open (#3623) extending the todo-lifecycle smoke with archive-completed coverage. Review it at exact head or add the omit/archive negative the review finds missing. | `python3 examples/control_plane/todo-lifecycle-cli-smoke.py` and `python3 -m py_compile loopx/*.py` |
-| GH-C04 | docs | Keep release docs current through v0.5.4: align install, activation, and recovery guidance with the PyPI default complete install path (#3301) and explicit installation ownership (#3566), preserve tagged stable vs post-tag `main` and release-snapshot vs canary distinctions, cover installed-runtime activation recovery and extension-doctor readiness (#3556), and keep the public release timeline (v0.1.3-v0.5.3) in sync with tagged evidence instead of duplicating the release body's bilingual optional-capability usage guidance. | `python3 examples/fresh-clone-quickstart-smoke.py`, `python3 examples/loopx-update-smoke.py`, `python3 examples/release/release-readiness-doc-smoke.py`, `python3 examples/release/release-version-contract-smoke.py`, and `loopx check --scan-path docs/product/release-readiness.md --scan-path CONTRIBUTING.md` |
+| GH-C04 | docs | Keep release docs current through v0.5.4: align install, activation, and recovery guidance with the PyPI default complete install path (#3301) and explicit installation ownership (#3566), preserve tagged stable vs post-tag `main` and release-snapshot vs canary distinctions, cover installed-runtime activation recovery and extension-doctor readiness (#3556), and keep the public release timeline (v0.1.3-v0.5.4) in sync with tagged evidence instead of duplicating the release body's bilingual optional-capability usage guidance. | `python3 examples/fresh-clone-quickstart-smoke.py`, `python3 examples/loopx-update-smoke.py`, `python3 examples/release/release-readiness-doc-smoke.py`, `python3 examples/release/release-version-contract-smoke.py`, and `loopx check --scan-path docs/product/release-readiness.md --scan-path CONTRIBUTING.md` |
 ### Focused Implementation
 
 Small-to-medium code changes with a clear validation surface. These are good