hidb4ai · Oct 12, 2026 · Oct 12, 2026 · Oct 12, 2026 · Oct 12, 2026 · Oct 12, 2026
@@ -16,7 +16,7 @@ PowerContext keeps context with the work across conversations. When you return,
 
 [Website](https://powercontext.oceanbase.io/) · [Installation walkthrough](https://powercontext.oceanbase.io/en/docs/get-started/quickstart/)
 
-PowerContext 1.2.0 includes the guided setup. The commands below install this version and connect
+PowerContext 1.3.0 includes the guided setup. The commands below install this version and connect
 the matching Agent integration.
 
 ## Pick up where the work left off
@@ -33,10 +33,10 @@ evaluation. See the [configuration reference](docs/en/docs/operate/configuration
 You need Git, [uv](https://docs.astral.sh/uv/getting-started/installation/), and your Agent's CLI.
 Python 3.11+ is required; uv can provision it. macOS and Linux are supported; Windows support is `experimental`.
 
-Install 1.2.0 and open the interactive configuration wizard in a dedicated directory:
+Install 1.3.0 and open the interactive configuration wizard in a dedicated directory:
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
+uv tool install --force "powercontext[cli,server]==1.3.0"
 mkdir -p powercontext-config
 cd powercontext-config
 powercontext config init --language en --output .env
@@ -74,7 +74,7 @@ covers Codex and Claude Code, Dashboard login, SSH forwarding, HTTPS prerequisit
 For example, the matching Codex installation is:
 
 ```bash
-powercontext setup codex --ref powercontext-v1.2.0
+powercontext setup codex --ref powercontext-v1.3.0
 powercontext doctor codex
 ```
 

@@ -16,7 +16,7 @@ PowerContext 让上下文跟随工作，跨越不同的对话。你回来时，
 
 [网站](https://powercontext.oceanbase.io/zh/) · [完整安装流程](https://powercontext.oceanbase.io/zh/docs/get-started/quickstart/)
 
-PowerContext 1.2.0 包含交互式配置向导。下面的命令安装这一版本，并接入相同版本的 Agent 集成。
+PowerContext 1.3.0 包含交互式配置向导。下面的命令安装这一版本，并接入相同版本的 Agent 集成。
 
 ## 从当前进展继续
 
@@ -32,10 +32,10 @@ PowerContext 1.2.0 包含交互式配置向导。下面的命令安装这一版
 准备 Git、[uv](https://docs.astral.sh/uv/getting-started/installation/) 和你使用的 Agent CLI。
 需要 Python 3.11+，uv 可以按需安装。支持 macOS 和 Linux；Windows 支持为 `experimental`。
 
-安装 1.2.0，然后在独立目录里打开交互式配置向导：
+安装 1.3.0，然后在独立目录里打开交互式配置向导：
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
+uv tool install --force "powercontext[cli,server]==1.3.0"
 mkdir -p powercontext-config
 cd powercontext-config
 powercontext config init --language zh --output .env
@@ -69,7 +69,7 @@ powercontext capabilities
 SSH 隧道、HTTPS 前提及逐项验收。例如，匹配本版本的 Codex 安装命令是：
 
 ```bash
-powercontext setup codex --ref powercontext-v1.2.0
+powercontext setup codex --ref powercontext-v1.3.0
 powercontext doctor codex
 ```
 

@@ -16,7 +16,7 @@ PowerContext は、会話をまたいでもコンテキストを作業ととも
 
 [Web サイト](https://powercontext.oceanbase.io/en/) · [インストール手順](https://powercontext.oceanbase.io/en/docs/get-started/quickstart/)
 
-PowerContext 1.2.0 には対話式セットアップが含まれています。
+PowerContext 1.3.0 には対話式セットアップが含まれています。
 以下のコマンドでこのバージョンの PowerContext と、対応する Agent 連携をインストールします。
 
 ## 作業の続きをそのまま引き継ぐ
@@ -27,10 +27,10 @@ PowerContext 1.2.0 には対話式セットアップが含まれています。
 
 ## 利用中の Agent と接続する
 
-Git、uv、Agent CLI を用意して、1.2.0 をインストールします：
+Git、uv、Agent CLI を用意して、1.3.0 をインストールします：
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
+uv tool install --force "powercontext[cli,server]==1.3.0"
 mkdir -p powercontext-config
 cd powercontext-config
 powercontext config init --language en --output .env
@@ -50,7 +50,7 @@ Server を起動したまま、別のターミナルで同じ設定ディレク
 クライアント環境の読み込み、Scope の作成・紐付け、同じバージョンの Agent プラグインのインストールを行います。例：
 
 ```bash
-powercontext setup codex --ref powercontext-v1.2.0
+powercontext setup codex --ref powercontext-v1.3.0
 powercontext doctor codex
 ```
 

@@ -1,5 +1,5 @@
 {
-  "contractSha256": "16eff718a6607ab6ff3d03c2a279ee92c26d8895ac804e7259fc11173ac8e3c8",
+  "contractSha256": "7aa91ae9af78300e7bdbcc2e8b2135da5749469290a1aee67bc255c3e9a07b0c",
   "operations": {
     "get_liveness": {
       "method": "GET",

@@ -15,7 +15,7 @@
  */
 
 // Generated from openapi/powercontext.yaml. Do not edit.
-export const contractSha256 = "16eff718a6607ab6ff3d03c2a279ee92c26d8895ac804e7259fc11173ac8e3c8";
+export const contractSha256 = "7aa91ae9af78300e7bdbcc2e8b2135da5749469290a1aee67bc255c3e9a07b0c";
 export const operations = {
   "get_liveness": {
     "method": "GET",

@@ -1,6 +1,6 @@
 ---
 title: Install and run
-description: Install PowerContext 1.2.0 and run the local Server.
+description: Install PowerContext 1.3.0 and run the local Server.
 ---
 
 # Install and run
@@ -24,12 +24,12 @@ Embedded seekDB is unavailable on Windows.
 
 ## Choose a version
 
-These instructions use PowerContext 1.2.0. Keep the package and Agent integration on
-the same version: package `1.2.0` and Git tag `powercontext-v1.2.0`.
+These instructions use PowerContext 1.3.0. Keep the package and Agent integration on
+the same version: package `1.3.0` and Git tag `powercontext-v1.3.0`.
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
-powercontext setup codex --ref powercontext-v1.2.0
+uv tool install --force "powercontext[cli,server]==1.3.0"
+powercontext setup codex --ref powercontext-v1.3.0
 ```
 
 Check the [capability matrix](../integrations/capabilities.md) for host support and maintenance status.
@@ -41,13 +41,13 @@ You need Python 3.11 or newer, Git, and [`uv`](https://docs.astral.sh/uv/) on ma
 PowerContext from PyPI:
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
+uv tool install --force "powercontext[cli,server]==1.3.0"
 ```
 
 For a source installation of the same version:
 
 ```bash
-uv tool install --force "powercontext[cli,server] @ git+https://github.com/oceanbase/powercontext.git@powercontext-v1.2.0"
+uv tool install --force "powercontext[cli,server] @ git+https://github.com/oceanbase/powercontext.git@powercontext-v1.3.0"
 ```
 
 The Git command does not leave a repository checkout for you to manage. Git uses its normal credential configuration,
@@ -122,7 +122,7 @@ Embedded seekDB is available on Linux and macOS when a compatible `pylibseekdb`
 support this embedded backend. Install or replace the tool with the optional seekDB extra:
 
 ```bash
-uv tool install --force "powercontext[cli,server,seekdb]==1.2.0"
+uv tool install --force "powercontext[cli,server,seekdb]==1.3.0"
 ```
 
 When switching from SQLite, remove `POWERCONTEXT_SERVER_DATABASE_URL` from the Server process environment. An explicit
@@ -174,15 +174,18 @@ Before upgrading an existing deployment, back up its database and configuration.
 tag-table constraints during Server startup to support Topic Memory tags. Stop the old Server instances and start
 one upgraded instance first so the schema upgrade completes before other instances connect. Databases from before
 1.0.0 also need the [Artifact processing migration](../operate/artifact-processing-migration.md) if it has not already
-been completed. Upgrade the Server, clients, and Agent integrations together.
+been completed. Upgrading to 1.3.0 also requires the [offline Atomic Memory migration](../operate/atomic-memory-migration.md)
+for existing collection databases. Complete any required Artifact processing migration first, stop all writers, then
+apply and verify the Atomic Memory migration. Start the new service only after verification returns `ready: true`.
+Upgrade the Server, clients, and Agent integrations together.
 The Dashboard must be explicitly enabled; static Bearer authentication is optional for local use. See
 [Deploy the Server](../operate/deploy-server.md). Remote plaintext HTTP connections require explicit client consent;
 see [Connect to a remote Server](../operate/connect-remote-server.md).
 
-To upgrade to 1.2.0:
+To upgrade to 1.3.0:
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
+uv tool install --force "powercontext[cli,server]==1.3.0"
 ```
 
 To replace the installed tool with another Git ref:
@@ -200,7 +203,7 @@ changes.
 An application that imports the async Client SDK should add it to that application's environment:
 
 ```bash
-uv add "powercontext[client]==1.2.0"
+uv add "powercontext[client]==1.3.0"
 ```
 
 Use `builtin` for in-process Python composition, `server` for the service, `client` for the Python SDK, or `cli` for

@@ -6,8 +6,8 @@ description: Configure full memory, connect Codex, and verify Source capture, To
 # Quick Start
 
 Start with installation, discuss a project in Codex, watch its input become Source evidence and an evolving topic,
-then recover the decisions in a new session. These instructions use PowerContext 1.2.0,
-with the Agent plugin from the matching `powercontext-v1.2.0` tag.
+then recover the decisions in a new session. These instructions use PowerContext 1.3.0,
+with the Agent plugin from the matching `powercontext-v1.3.0` tag.
 
 You need macOS or Linux, Python 3.11+, Git, [uv](https://docs.astral.sh/uv/getting-started/installation/),
 and an installed Codex CLI. Full memory also needs working Generation and Embedding model APIs:
@@ -18,7 +18,7 @@ and recall; that does not enable automatic Topic Memory.
 ## 1. Install and open the wizard
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
+uv tool install --force "powercontext[cli,server]==1.3.0"
 mkdir -p ~/powercontext-demo
 cd ~/powercontext-demo
 powercontext config init --language en --output .env
@@ -96,7 +96,7 @@ Reload the client settings and install the matching plugin:
 set -a
 . ./.env
 set +a
-powercontext setup codex --ref powercontext-v1.2.0
+powercontext setup codex --ref powercontext-v1.3.0
 powercontext doctor codex
 codex
 ```

@@ -1,6 +1,6 @@
 ---
 title: 安装和运行
-description: 安装 PowerContext 1.2.0，并运行本地 Server。
+description: 安装 PowerContext 1.3.0，并运行本地 Server。
 ---
 
 # 安装和运行
@@ -22,12 +22,12 @@ Windows 的 CLI、Server 和个人服务支持为试验性；各 Agent Host 仍
 
 ## 选择版本
 
-本页使用 PowerContext 1.2.0。包与 Agent 集成保持版本一致：
-Python 包版本为 `1.2.0`，对应 Git tag 为 `powercontext-v1.2.0`。
+本页使用 PowerContext 1.3.0。包与 Agent 集成保持版本一致：
+Python 包版本为 `1.3.0`，对应 Git tag 为 `powercontext-v1.3.0`。
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
-powercontext setup codex --ref powercontext-v1.2.0
+uv tool install --force "powercontext[cli,server]==1.3.0"
+powercontext setup codex --ref powercontext-v1.3.0
 ```
 
 宿主支持范围和维护状态见[能力矩阵](../integrations/capabilities.md)。
@@ -39,13 +39,13 @@ powercontext setup codex --ref powercontext-v1.2.0
 [`uv`](https://docs.astral.sh/uv/)，然后从 PyPI 安装 PowerContext：
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
+uv tool install --force "powercontext[cli,server]==1.3.0"
 ```
 
 如需从源码安装同一版本：
 
 ```bash
-uv tool install --force "powercontext[cli,server] @ git+https://github.com/oceanbase/powercontext.git@powercontext-v1.2.0"
+uv tool install --force "powercontext[cli,server] @ git+https://github.com/oceanbase/powercontext.git@powercontext-v1.3.0"
 ```
 
 Git 安装命令不会留下需要自行管理的仓库工作副本。Git 会沿用本机的凭据配置，包括 credential helper 和 SSH 设置。
@@ -112,7 +112,7 @@ powercontext server run --env-file /path/to/powercontext.env
 后端。安装或替换工具时加入可选的 seekDB extra：
 
 ```bash
-uv tool install --force "powercontext[cli,server,seekdb]==1.2.0"
+uv tool install --force "powercontext[cli,server,seekdb]==1.3.0"
 ```
 
 从 SQLite 切换时，需要从 Server 进程环境中删除 `POWERCONTEXT_SERVER_DATABASE_URL`；seekDB 不接受显式的
@@ -160,14 +160,16 @@ Agent 诊断见[各自的集成文档](../integrations/index.md)；Server 状态
 升级已有部署前，先备份数据库和配置。1.1.0 会在 Server 启动时升级旧标签表约束，以支持 Topic Memory 标签。
 先停止旧 Server 实例，再启动一个升级后的实例，待结构升级完成后再启动其他实例。对于 1.0.0 之前的数据库，
 如果尚未完成[Artifact 处理迁移](../operate/artifact-processing-migration.md)，还需要先执行该迁移。
+升级到 1.3.0 时，已有集合式 Memory 数据库还需完成[Atomic Memory 离线迁移](../operate/atomic-memory-migration.md)。
+先完成所需的 Artifact 处理迁移，再停止所有写入进程，执行 Atomic Memory 迁移并验证 `ready: true` 后启动新服务。
 Server、客户端和 Agent 集成需一起升级。Dashboard 需要显式启用，本地使用可选择静态 Bearer 认证，
 见[部署 Server](../operate/deploy-server.md)；远程明文 HTTP 连接需要客户端明确同意，
 见[连接远程 Server](../operate/connect-remote-server.md)。
 
-升级到 1.2.0：
+升级到 1.3.0：
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
+uv tool install --force "powercontext[cli,server]==1.3.0"
 ```
 
 使用其他 Git ref 替换现有工具：
@@ -184,7 +186,7 @@ uv tool install --force "powercontext[cli,server] @ git+https://github.com/ocean
 如果应用需要导入异步 Client SDK，应把它加入该应用自己的环境：
 
 ```bash
-uv add "powercontext[client]==1.2.0"
+uv add "powercontext[client]==1.3.0"
 ```
 
 进程内 Python 组合使用 `builtin`，服务使用 `server`，Python SDK 使用 `client`，基于 Server 的命令行使用

@@ -6,8 +6,8 @@ description: 通过配置向导安装完整记忆能力，接入 Codex，并验
 # 快速开始
 
 本页从安装开始，带你完成一次真实的记忆体验：在 Codex 中讨论项目，看到原始输入进入 Source、主题记忆生成并演进，
-再在新会话中找回决策。以下命令使用 PowerContext 1.2.0，Agent 插件使用对应的
-`powercontext-v1.2.0` tag。
+再在新会话中找回决策。以下命令使用 PowerContext 1.3.0，Agent 插件使用对应的
+`powercontext-v1.3.0` tag。
 
 需要 macOS 或 Linux、Python 3.11+、Git、[uv](https://docs.astral.sh/uv/getting-started/installation/) 和已安装的 Codex CLI。
 完整记忆还需要可用的 Generation 和 Embedding 模型 API；准备好各自的地址、模型名和 API key。
@@ -17,7 +17,7 @@ Codex 或 Claude 的订阅登录不会自动为 PowerContext Server 提供这些
 ## 1. 安装并进入配置向导
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
+uv tool install --force "powercontext[cli,server]==1.3.0"
 mkdir -p ~/powercontext-demo
 cd ~/powercontext-demo
 powercontext config init --language zh --output .env
@@ -92,7 +92,7 @@ POWERCONTEXT_CODEX_SCOPE_ID=替换为返回的scope_id
 set -a
 . ./.env
 set +a
-powercontext setup codex --ref powercontext-v1.2.0
+powercontext setup codex --ref powercontext-v1.3.0
 powercontext doctor codex
 codex
 ```

@@ -1,5 +1,5 @@
 {
-  "api_version": "1.2.0",
+  "api_version": "1.3.0",
   "operations": {
     "list_atomic_memories": {
       "method": "POST",

@@ -5,8 +5,8 @@ This plugin is a thin DeepSeek Harness integration for a running PowerContext Se
 Install the released Server and plugin together:
 
 ```bash
-uv tool install --force "powercontext[cli,server]==1.2.0"
-powercontext setup dsh --source oceanbase/powercontext --ref powercontext-v1.2.0
+uv tool install --force "powercontext[cli,server]==1.3.0"
+powercontext setup dsh --source oceanbase/powercontext --ref powercontext-v1.3.0
 ```
 
 `setup dsh` calls `dsh plugin --profile web add`. The plugin talks HTTP only. It does not use MCP.

@@ -16,7 +16,7 @@ openapi: 3.0.3
 info:
   title: PowerContext API
   description: Remote PowerContext transport. Runtime behavior is reported by /v1/capabilities.
-  version: 1.2.0
+  version: 1.3.0
 x-powercontext-feature-contracts:
   access.principal: {major: 1, minor: 0}
   scope.selection: {major: 1, minor: 0}

@@ -195,7 +195,7 @@
 OPENAPI_VERSION = "3.0.3"
 API_TITLE = "PowerContext API"
 API_DESCRIPTION = "Remote PowerContext transport. Runtime behavior is reported by /v1/capabilities."
-API_VERSION = "1.2.0"
+API_VERSION = "1.3.0"
 FEATURE_CONTRACTS: dict[str, dict[str, JsonValue]] = {
     "access.principal": {"version": {"major": 1, "minor": 0}, "operations": ["get_access_principal"]},
     "scope.selection": {

@@ -7,7 +7,7 @@
     "info": {
         "title": "PowerContext API",
         "description": "Remote PowerContext transport. Runtime behavior is reported by /v1/capabilities.",
-        "version": "1.2.0",
+        "version": "1.3.0",
     },
     "paths": {
         "/v1/atomic-memory/list": {

@@ -188,7 +188,7 @@ def test_contract_uses_the_namespaced_request_id_header() -> None:
 def test_server_info_contract_is_observable_and_forward_compatible() -> None:
     contract = yaml.safe_load(CONTRACT_PATH.read_text())
 
-    assert contract["info"]["version"] == "1.2.0"
+    assert contract["info"]["version"] == "1.3.0"
     operation = contract["paths"]["/v1/server-info"]["get"]
     assert operation["operationId"] == "get_server_info"
     assert operation["x-powercontext-access"] == {

@@ -289,7 +289,7 @@ def test_server_info_uses_one_durable_identity_across_restarts(tmp_path) -> None
     assert first.status_code == second.status_code == 200
     assert first.json() == second.json()
     assert first.json()["schema_version"] == {"major": 1, "minor": 0}
-    assert first.json()["api_contract_version"] == {"major": 1, "minor": 2}
+    assert first.json()["api_contract_version"] == {"major": 1, "minor": 3}
 
 
 def test_server_startup_fails_when_identity_initialization_fails(tmp_path, monkeypatch) -> None: