v0.2.30

Doca 0.2.30 — independent MCP executions and tiered SDD

简体中文

MCP tool use now creates standalone execution tasks. It shares authorization, leases, cancellation, operation receipts and actual provider usage with chat tools, while creating no conversation or memory thread. Personal settings → MCP → Execution history provides status, authorized resources, stopping and removal of closed history. Saved documents/files and host audit/usage facts remain intact.

Current DDL makes task conversation/model associations and the retained MCP conversation reference nullable, and adds the empty ai_task_resources ledger through the approved reconciler. Existing rows are preserved without conversion; historical MCP conversations disappear from chat entry points and cannot resume. The compatibility generation is unchanged.

Plugin SDK source is 0.2.0 with ai.v2 / ai.continuations.v2. Task identity is always jobId; sessionId exists only for real conversations. Rebuild plugins with sdkRange: "^0.2.0" and update host/Web/plugins together. Old ranges and services are rejected without adapters. Back up before upgrade; automatic application downgrade is not provided.

SQLite and PostgreSQL 17/18 checks include actual released 0.2.29 data, retained rows, repeated/concurrent startup and review rejection. See verification. Publication receipts are recorded separately after successful remote verification; publishing artifacts does not deploy a running installation.

The repository adopts tiered SDD, with full/standard/light records, a module index, pinned Spec Kit 1.0.4, and PR traceability checks. This process change does not alter runtime data.

GitHub Release includes the built plugin SDK 0.2.0 tarball and checksum for rebuilding plugins. This release does not publish the SDK to npm. Docker Hub targets are smartdoca/doca:0.2.30 and latest for native Linux amd64/arm64. The browser extension remains 0.2.11.

Web assets are attached as doca-web-assets-v0.2.30.tar.gz.
Extract it and publish the assets directory unchanged.
Set DOCA_ASSET_BASE to the HTTPS prefix that contains that assets directory, with no trailing slash.

Fresh installations can use the attached doca-compose-v0.2.30.yaml: edit the origin and generated master key, then run docker compose up -d. Administrator initialization is built into the image. A SHA-256 checksum is attached. Existing installations must preserve their project, volumes and key.

Image-only deployment files and initialization instructions are attached as doca-deploy-v0.2.30.tar.gz with a SHA-256 checksum.
The built plugin SDK and its SHA-256 checksum are also attached for rebuilding plugins against this release's public contract; this does not publish an npm package.
Transfer this bundle to servers without GitHub access; no source checkout is needed.
The container image is separate. Pull the matching smartdoca/doca image or transfer it with docker save/load.