docs(release): finalize 0.0.7 release metadata

CHANGELOG.md

@@ -2,8 +2,10 @@
 
 ## [Unreleased]
 
+## [0.0.7] — 2026-09-13
+
 - Set the source-build version to `0.0.7-SNAPSHOT`. Maven Central version `0.0.6` was published from the same source
-  commit as `0.0.5`; it does not contain the APIs listed in this Unreleased section.
+  commit as `0.0.5`; it does not contain the APIs listed in this `0.0.7` section.
 - Preserve the published `spring-boot-starter` artifact coordinate. The temporary, unpublished
   `spring-boot-a2a-starter` name is not a consumable Maven Central coordinate.
 

README.md

@@ -38,9 +38,7 @@ subscription remains open until the host-defined terminal event, explicit cancel
 
 ### 1. Add Maven dependency
 
-Maven Central currently contains `0.0.6`; it was published from the same source commit as `0.0.5` and adds no APIs.
-The current source tree builds as `0.0.7-SNAPSHOT`. APIs listed under `Unreleased` in the changelog, including `sendTask` and
-HTTP runtime customization, require this source build (or an internal snapshot repository) until the next release.
+The current engine release is `0.0.7` on [Maven Central](https://repo.maven.apache.org/maven2/net/openan/workflow/sdk/).
 
 A2A-T SDK `1.1.0` is published to Maven Central. Maven resolves it automatically; no SDK source checkout or local SDK
 build is required. The engine depends only on
@@ -53,7 +51,7 @@ upgrade guidance.
 <dependency>
     <groupId>net.openan.workflow.sdk</groupId>
     <artifactId>workflow-engine</artifactId>
-    <version>0.0.7-SNAPSHOT</version>
+    <version>0.0.7</version>
 </dependency>
 ```
 
@@ -63,7 +61,7 @@ For Spring Boot server-side integration:
 <dependency>
     <groupId>net.openan.workflow.sdk</groupId>
     <artifactId>spring-boot-starter</artifactId>
-    <version>0.0.7-SNAPSHOT</version>
+    <version>0.0.7</version>
 </dependency>
 ```
 

docs/en/DEVELOPER_GUIDE.md

@@ -11,12 +11,11 @@ Add to your `pom.xml`:
 <dependency>
     <groupId>net.openan.workflow.sdk</groupId>
     <artifactId>workflow-engine</artifactId>
-    <version>0.0.7-SNAPSHOT</version>
+    <version>0.0.7</version>
 </dependency>
 ```
 
-`0.0.7-SNAPSHOT` is the current source-build version and must be installed locally or supplied by an internal snapshot
-repository. Maven Central `0.0.6` is built from the same source as `0.0.5` and does not contain Unreleased APIs.
+Version `0.0.7` is published to Maven Central and contains the APIs documented in this guide.
 
 The engine pulls in A2A protocol transports and a2a-t-core only. Host agents generating A2A-T content explicitly add
 a2a-t-client; dispatched-agent services that validate received content also add a2a-t-server.

docs/en/INTEGRATION_GUIDE.md

@@ -22,12 +22,11 @@ callbacks own A2A-T generation, semantic validation, schemas and any LLM calls.
 <dependency>
     <groupId>net.openan.workflow.sdk</groupId>
     <artifactId>workflow-engine</artifactId>
-<version>0.0.7-SNAPSHOT</version>
+<version>0.0.7</version>
 </dependency>
 ```
 
-`0.0.7-SNAPSHOT` is the current source-build version. Install it locally or resolve it from an internal snapshot
-repository. Maven Central `0.0.6` is built from the same source as `0.0.5` and does not include Unreleased APIs.
+Version `0.0.7` is published to Maven Central and contains the APIs documented in this guide.
 
 ## 4. Quick Start
 
@@ -232,10 +231,10 @@ For production, obtain secrets securely in the host and use the Java encryption
 ```bash
 # Option 1: set env var first
 set A2AT_CRED_KEY=4f8a2b1c3d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b
-java -cp workflow-engine/target/workflow-engine-0.0.7-SNAPSHOT.jar dev.openan.workflow.engine.client.CredentialCrypto "Admin@123"
+java -cp workflow-engine/target/workflow-engine-0.0.7.jar dev.openan.workflow.engine.client.CredentialCrypto "Admin@123"
 
 # Option 2: pass key as second argument
-java -cp workflow-engine/target/workflow-engine-0.0.7-SNAPSHOT.jar dev.openan.workflow.engine.client.CredentialCrypto "Admin@123" 4f8a2b1c3d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b
+java -cp workflow-engine/target/workflow-engine-0.0.7.jar dev.openan.workflow.engine.client.CredentialCrypto "Admin@123" 4f8a2b1c3d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b
 ```
 
 Output:
@@ -251,7 +250,7 @@ Paste the output into the `value` field of the credentials JSON.
 1. Generate a new key: `openssl rand -hex 32`
 2. Update the host secret store / explicit `credentialEncryptionKey`, or its OS/JVM `A2AT_CRED_KEY`
 3. Re-encrypt all passwords:
-   `java -cp workflow-engine/target/workflow-engine-0.0.7-SNAPSHOT.jar dev.openan.workflow.engine.client.CredentialCrypto "plaintext" new-key`
+   `java -cp workflow-engine/target/workflow-engine-0.0.7.jar dev.openan.workflow.engine.client.CredentialCrypto "plaintext" new-key`
 4. Update the `enc:...` results in the credentials JSON file
 
 > The `.env` file should not be committed to version control. Add it to `.gitignore`.

docs/zh/DEVELOPER_GUIDE.md

@@ -10,12 +10,11 @@
 <dependency>
     <groupId>net.openan.workflow.sdk</groupId>
     <artifactId>workflow-engine</artifactId>
-    <version>0.0.7-SNAPSHOT</version>
+    <version>0.0.7</version>
 </dependency>
 ```
 
-`0.0.7-SNAPSHOT` 是当前源码构建版本，使用前需要先安装到本地 Maven 仓库，或由内部快照仓库提供。Maven Central
-中的 `0.0.6` 与 `0.0.5` 来自同一份源码，不包含 Unreleased 章节中的新接口。
+`0.0.7` 已发布到 Maven Central，包含本文说明的接口。
 
 引擎会传递性引入 A2A 协议 SDK（`a2a-java-sdk-client`，含 REST、JSON-RPC、gRPC 传输） 和最小 A2A-T 核心（`a2a-t-core`）。生成 A2A-T 内容的宿主智能体显式依赖 a2a-t-client，校验接收内容的被调度智能体服务另引入 a2a-t-server。
 

docs/zh/INTEGRATION_GUIDE.md

@@ -20,12 +20,11 @@ A2A-T 工作流执行引擎是一个 Java SDK，用于基于 A2A 协议和 A2A-T
 <dependency>
     <groupId>net.openan.workflow.sdk</groupId>
     <artifactId>workflow-engine</artifactId>
-<version>0.0.7-SNAPSHOT</version>
+<version>0.0.7</version>
 </dependency>
 ```
 
-`0.0.7-SNAPSHOT` 是当前源码构建版本，使用前需要先安装到本地 Maven 仓库，或由内部快照仓库提供。Maven Central
-中的 `0.0.6` 与 `0.0.5` 来自同一份源码，不包含 Unreleased 章节中的新接口。
+`0.0.7` 已发布到 Maven Central，包含本文说明的接口。
 
 ## 4. 快速上手
 
@@ -222,10 +221,10 @@ A2AT_CRED_KEY=4f8a2b1c3d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b
 ```bash
 # 方式一：先设置环境变量
 set A2AT_CRED_KEY=4f8a2b1c3d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b
-java -cp workflow-engine/target/workflow-engine-0.0.7-SNAPSHOT.jar dev.openan.workflow.engine.client.CredentialCrypto "Admin@123"
+java -cp workflow-engine/target/workflow-engine-0.0.7.jar dev.openan.workflow.engine.client.CredentialCrypto "Admin@123"
 
 # 方式二：密钥作为第二个参数
-java -cp workflow-engine/target/workflow-engine-0.0.7-SNAPSHOT.jar dev.openan.workflow.engine.client.CredentialCrypto "Admin@123" 4f8a2b1c3d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b
+java -cp workflow-engine/target/workflow-engine-0.0.7.jar dev.openan.workflow.engine.client.CredentialCrypto "Admin@123" 4f8a2b1c3d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b
 ```
 
 输出：
@@ -240,7 +239,7 @@ enc:uHQcTeKZMVNRM9Ga:o5vm4weRozBXBs04phrLq7j7+/yRVyDsrw==
 
 1. 生成新密钥：`openssl rand -hex 32`
 2. 更新集成方密钥存储及显式 `credentialEncryptionKey`，或 OS/JVM 的 `A2AT_CRED_KEY`；引擎不自动加载 `.env`
-3. 用新密钥重新加密所有密码：`java -cp workflow-engine/target/workflow-engine-0.0.7-SNAPSHOT.jar dev.openan.workflow.engine.client.CredentialCrypto "明文密码" 新密钥`
+3. 用新密钥重新加密所有密码：`java -cp workflow-engine/target/workflow-engine-0.0.7.jar dev.openan.workflow.engine.client.CredentialCrypto "明文密码" 新密钥`
 4. 将新的 `enc:...` 结果更新到凭证 JSON 文件
 
 > `.env` 文件不应提交到版本库，建议加入 `.gitignore`。