Upgrade notice: SQLite defaults and in-place migration / SQLite 默认存储与原地升级提醒 #6810

2026-10-23 update: LoopX v2.1.1 is released and available on PyPI. The original 2.0.0a1 checkpoint below is historical. Select an exact target version; the released package and the current main branch are separate.

2026-10-23 更新： LoopX v2.1.1 已正式发布，PyPI 2.1.1 包也已可用。下文 2.0.0a1 是原公告的历史快照。请明确目标版本，区分正式版本与当前 main。

For developers tracking main

This notice was first checked on 2026-10-18 at f37d0d9, when main was on the LoopX 2.0 development line and the package version was 2.0.0a1. The release status is updated above; the following notes distinguish new-Goal defaults from upgrading existing data.

For new Goals on devices without an explicit storage setting, the default is canonical SQLite with hard_lease. Existing Goals and valid explicit provider/policy settings are preserved. Pulling main, updating the CLI, or changing new-Goal defaults does not migrate existing Goal data.

Upgrade an existing 1.x workspace

1. Select the intended 2.0 version or source revision.
2. Open the Agent-assisted upgrade guide and give its complete English or Chinese prompt to your Agent, replacing the target-version placeholder.
3. Let the Agent inspect the installation owner and actual Goal state, stop affected old writers through their owners, reconcile pending operations, and make and verify a private backup before applying the necessary upgrade steps.
4. Verify the original Goals, Agents, complete active/archived Tasks, configuration and receipts; activate the intended runtime and continue one useful step of the original work.

The upgrade is in place: retain the same machine, project, registry/runtime routes and Goal identities. An already current canonical Goal needs no import. Keep valid explicit providers and policies; SQLite becoming the new-Goal default is not a requirement to force every existing File Goal to SQLite.

Use the existing upgrade/import/policy owners described in the guide. Do not hand-edit registry/SQL, replace the project with empty Goals, or overwrite newer writes with an old backup. A successful package update alone does not prove that data migration and runtime activation succeeded.

If an upgrade step fails, preserve the source and report the specific failing stage, selected/installed versions, OS, and a redacted error. Do not upload private databases, raw Goal state, credentials or private work content.

给使用 main 的开发者

本公告最初核对的是 2026-10-18 的 f37d0d9：当时 main 处于 LoopX 2.0 开发线，版本为 2.0.0a1。正式发布状态已在顶部更新；以下说明区分新 Goal 默认值与已有数据升级。

未显式配置存储的新 Goal 默认使用 canonical SQLite 和 hard_lease。已有 Goal 不会因拉取 main、更新 CLI 或修改新 Goal 默认值而自动完成迁移；有效的显式 provider/policy 保持不变。

需要从 1.x 升级的开发者，请打开：

Agent 原地升级指南：复制其中完整的中文或英文提示给 Agent

先填明要升级到的 2.0 版本或源码 revision。Agent 应通过原安装及数据 owner，处理旧写方和未完成操作，先私有备份并校验，再按实际状态执行必要的格式升级、Markdown 导入或历史所有权策略迁移。

保持同一机器、项目、registry/runtime 路由和 Goal/Agent 身份，保留完整活动与归档任务、关系、材料、配置及原操作回执。已经是当前 canonical 格式的 Goal 无需再次导入；已有有效 File 配置也不因默认值变化而被强制切换。

升级后应读回原数据、激活目标 runtime，并继续原任务的一步、检查真实结果。仅安装新版包不等于迁移完成。不要手改 registry/SQL、新建空 Goal 冒充升级，或用旧备份覆盖后续写入。

遇到失败时保留原数据，反馈具体阶段、目标/实际版本、操作系统和脱敏错误；不要公开上传私人数据库、原始 Goal 状态、凭据或工作内容。

Verified baseline: main at f37d0d9, 2026-10-18. Guide at that revision · New-Goal defaults implementation.

The linked main-branch guide is the maintained procedure; this issue is the developer notice, not a second migration implementation or a request to migrate anyone's installation automatically.

Release-source recheck / 正式版本源码复核（2026-10-23）：1.x→2.0 guide shipped in v2.1.1 · new-Goal defaults at v2.1.1.