v0.1.18

Doca 0.1.18 统一发布已发布在线表格子包对接及工作区全部改动，包含 0.1.16、0.1.17 的已有修复。

• 接入 @smartdoca/sheet@0.2.0-rc.19，区分数据验证和插入下拉列表入口，插件元素使用原生菜单；修复阅读切回编辑后工具栏能力未刷新的问题。
• 知识册原流水线断点续跑、冻结配置、画布与运行切换、阅读目录、溯源分组和生成内容覆盖检查。
• 原生图示插入、整块评论与 AI 引用、图示预览失效、实际上传进度，以及登录图标、预览和 AI 布局改善。
• Web 延迟加载、Markdown PDF 依赖拆分、完整字形 WOFF2、Brotli/gzip 静态压缩及 CAD 生产资源路由。

全量 267 个文件、2,648 项通过，3 项环境测试跳过；最终表格与保存队列回归另有 27 项通过。冻结安装、类型检查、生产构建及 55 页双语文档检查通过。隔离宿主浏览器验证中英文入口、只读及编辑恢复；61 秒监听零内容写入。Linux amd64、arm64 均启动正常，470 个 Web 资源逐文件一致，Brotli/gzip 与 CAD 资源检查通过。

Docker smartdoca/doca:0.1.18 与 latest 同步发布。Web 资源包、逐文件摘要、SHA256SUMS 和验证清单随发行提供；资源包与通过验收的镜像逐文件一致。

数据库基线和 SDK 0.1.10 保持现有协议，没有新增兼容适配、格式转换或数据库迁移。保留数据库、文件、配置与凭证主密钥；更早基线继续遵守 0.1.15 升级要求。既有 PostgreSQL 图片候选字段长度限制未修改，相关生成／修订用例不宣称通过。

双语发行说明 · 表格宿主验收

v0.1.17

Doca 0.1.17 修复 PostgreSQL 图片字节数误判，以及 AI 发送后输入框等待后端才清空的问题。发送立即清空，后写草稿保留；失败恢复原稿，重试沿用稳定标识。

• 全量：265 个文件、2,589 项通过，3 项环境测试跳过；21 项 PostgreSQL 附件测试通过。
• Linux amd64、arm64 镜像均通过真实 PostgreSQL 私有上传、PNG 提取、损坏检测和失败重试验收；437 个 Web 资源与本 Release 附件逐文件一致。
• Docker smartdoca/doca:0.1.17 与 latest 已同步。SDK 仍为已发布的 @smartdoca/plugin-sdk@0.1.10，源码树无变化。

已有 PostgreSQL assets.purpose varchar(16) 容量问题仍会影响生成候选保存；扩大回归中的 100 项通过、19 项因此阻塞。列扩容及显式离线升级待独立同意，本版没有修改数据库结构或转换历史数据。

双语发行说明 · 验收截图及记录

数据库基线与凭证主密钥要求沿用 0.1.16；更早基线请先阅读 0.1.15 升级要求。Web 资源压缩包、SHA256SUMS、逐文件摘要和验证清单随发行提供。

v0.1.16

知识册流程设置统一从流程图节点进入编辑，左侧节点面板的图标和文字统一左对齐。

• 移除流程图下方重复的节点编辑卡片，点击节点打开现有编辑抽屉，修改后保存。
• 修正全局按钮居中样式对节点面板的影响，让图标、名称和说明从相同位置开始。

Docker Hub 已发布 smartdoca/doca:0.1.16 和 smartdoca/doca:latest，均支持 Linux amd64、arm64。数据库、配置格式和 SDK 保持原状，已有 0.1.15 部署沿用原数据与配置。详见发行说明。

附件 doca-web-assets-v0.1.16.tar.gz 含完整 Web 资源。解压后保留 assets 目录，437 个文件的内容已经与两个平台的镜像逐一校验一致。SHA256SUMS 和 doca-verification-v0.1.16.json 记录资源校验和、镜像摘要及验证结果。

验证通过：TypeScript、Web 构建、45 个知识册测试、53 页双语文档，以及两个平台连续三轮隔离容器检查。界面预览验证了节点点击编辑和修改后保存按钮启用；验证期间未编辑用户文档。

Knowledge-book workflows now use graph nodes as the single editing entry point, with consistent left alignment in the palette. Docker images and GitHub Web assets contain the same verified files. English release notes.

v0.1.15

本批会话的最终统一发行版：Doca 0.1.15、Docker 0.1.15/latest，以及 npm @smartdoca/plugin-sdk 0.1.10。v0.1.14 的代码与标签保留，最终版修正等待扫描边界，历史损坏或未标记结果不会被扫描修改。

知识册每次整理是一条流水线：左侧显示成功、失败、待审核/待发布确认、触发人或定时任务、开始时间和持续时间；点击节点在右侧查看日志、错误和人工待办。通用 ai.continuations.v1 服务允许其他安装插件通过公开 SDK 注册来源、等待和唤醒；后台完成及人工决定后继续原 AI 任务，重启保留新等待，恢复时重新授权。文档工具参数、知识册上下文/选择、助手预填和修复入口一并修正。

整合其他完成会话的历史存储、AI 附件发送重试、视频与上传反馈、文档/通知布局、知识册与知识库列表区分、S3 冻结凭据修复。详情：双语发行说明。

验证：264 个文件、2,587 项测试通过，3 项环境测试跳过；TypeScript、Web、52 页双语文档和独立 SDK JavaScript/声明通过。隔离真实模型跑通失败修复、流水线、人工发布、原任务两次自动继续，等待时重启无重复运行。两个架构实际容器通过启动、原源码校验、私有上传下载、知识册来源、DOCX/XLSX/PPTX 与启用沙箱的 Chromium PDF 验收；437 个 Web 资源与 GitHub 附件逐文件相同。没有操作用户文档或生产数据库；移动端仅编译，未做本版真机验收。

部署前阅读升级说明。新基线为 doca-2026-10-09-history-storage-v1；仅准确的 0.1.13 基线可停机备份后显式离线升级。启动不会自动迁移或重置。最近 20 个完整快照留数据库，更旧的每十个只保留最新一个到文件存储；其余九个在转存验证后淘汰，完整历史依赖抽稀前备份。保留原 DOCA_CREDENTIAL_MASTER_KEY，所有部署均必填。通用唤醒不转换或唤醒历史任务。

分发：

• Docker docker.io/smartdoca/doca:0.1.15 与 latest，linux/amd64、linux/arm64；两个标签索引均为 sha256:05f924104ad18d89430417132573f04c9bb20393bec97ea618d72464f5446449。
• npm @smartdoca/plugin-sdk@0.1.10，实际公开安装与完整性验证通过。
• 附件包含 Web 资源、SDK tarball、SHA256SUMS 和 release-manifest.json，后者记录源提交、各架构摘要、完整验收与限制。

v0.1.14 (superseded by v0.1.15)

本批改动的最终统一发行版为 v0.1.15，请使用它部署。

v0.1.14 的标签和代码保留；最终核对修正了后台等待扫描的边界，避免影响无法解析或没有新协议标记的历史任务。没有生产数据转换或重置。SDK 0.1.10 已发布且接口不受此修正影响。

此版 Web 资源保留用于审计；Docker 的最终分发与完整验证记录提供在 v0.1.15。升级前阅读 v0.1.15 的数据库基线、离线历史升级及原凭证主密钥要求。

v0.1.13

Doca 0.1.13 已包含图片工作流优化与知识册。

• 图片工具分为文生图、参考图生成和底图编辑，支持明确的厂商/模型适配、逐文档和逐页分片、持久候选与费用记录，以及有上限的返修和候选选择。
• AI 支持简化上传、可配置上传限制、持久附件和浏览器草稿，PDF/Office 同时读取文字、结构和完整页面。
• 知识册支持多人维护来源和编排、网页及插件来源、验收与人工待办、只读 Markdown 成果版本及真实执行溯源。旧整理和问答机器人移除，文档库、来源订阅、索引和搜索保留。
• 内网部署支持显式 HTTP/HTTPS 服务地址，包括 S3/RustFS、站点及 CDN；登录期限可配置，Web 默认 24 小时。经批准的浏览器适配只补充缺失的 UUID、SHA-256 和文本复制能力，不转换已有数据。

数据库基线变为 doca-2026-10-08-knowledge-books-v2。0.1.12 及更早数据库会在结构变更前被拒绝；不迁移、不转换、不重置。保留原部署和数据，新版使用独立空数据库与独立存储。 详见发行说明。

整合回归 2523 项通过、3 项环境测试跳过；最终浏览器/复制/会话增量 13 项通过。类型检查、Web 构建、49 页双语文档与独立 SDK 验证通过。两个 Linux 架构的实际容器均通过 HTTP、登录期限、上传原始字节、目录隔离、私有读取与知识册验证；DOCX/XLSX/PPTX 转换及带沙箱的 PDF 导出通过。GitHub Web 发行资源与两个架构镜像中的 437 个文件逐一核对一致。

Docker 镜像：smartdoca/doca:0.1.13 和 smartdoca/doca:latest，支持 Linux amd64、arm64。插件 SDK/契约公开接口未变，无需单独重发 SDK。本机图片服务保持关闭；镜像不包含模型权重。

本版发布图片工作流改造，两组整本故事书图片的全部合格交付验收仍未完成，不宣称通过该质量验收。

Demo · 插件商城 · 完整改动

Demo 数据会不定期清理，请不要存放重要数据。

Web assets: extract doca-web-assets-v0.1.13.tar.gz and publish the assets directory unchanged. Set DOCA_ASSET_BASE to its configured HTTP or HTTPS prefix, without a trailing slash. release-manifest.json and SHA256SUMS record the source, image and asset checksums.

v0.1.12

Doca 0.1.12 修复 AI 助手上传文件的范围问题：本地上传同名文件夹会创建独立目录，避免混入之前上传的内容；切换目录后，旧请求不会覆盖当前文件列表；上传返回实际文件 ID，AI 可直接使用本次附件与文件夹清单中的 ID 读取内容。

本版包含文件修复，不包含尚未完成整批验收的图片工作流改造。公开插件 SDK 接口没有变化，无需单独发布 SDK。

Docker 镜像：smartdoca/doca:0.1.12 和 smartdoca/doca:latest，支持 Linux amd64、arm64。已通过 1,221 项测试、类型检查、Web 构建及两个架构的隔离容器上传/读取验证。发行附件含 release-manifest.json 和 SHA256SUMS；Web 静态资源与两个架构镜像中的资源已逐文件核对一致。

Demo 体验 · 插件商城 · 中文文档

Demo 数据会不定期清理，请不要存放重要数据。

Web assets are attached as doca-web-assets-v0.1.12.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.

Full changelog · File upload fix · Demo and marketplace documentation

v0.1.11

Doca 0.1.11 adds reference-image editing to the existing image-generation tool and improves attachment uploads and settings controls. All current workspace changes are included in this release.

• The model can choose uploaded or previously generated conversation images as references, including multiple images and continued editing in later turns. Users do not need a mode switch. GPT Image/compatible services use image edits; Seedream 4.x/5.x sends references through image generations. Unsupported editing fails explicitly.
• Five visible native select controls now use the shared dropdown, including Meilisearch settings. Required-field validation opens and focuses the control.
• Browser uploads queue at concurrency two. AI attachments show image previews and progress, and removing an attachment cancels its upload. Upload failures retain diagnostic details.
• Docker storage documentation explains writable /data/storage paths and upload permission errors. The bilingual Docsify documentation is included.

From 0.1.10, this release requires no database migration or storage conversion. The database baseline remains doca-2026-10-03-credentials-v2; plugin SDK remains 0.1.9 and contracts remain 0.1.7. Installations from 0.1.9 or earlier must still follow the 0.1.10 deployment requirements, preserving their original deployment and data.

Validation passed TypeScript, the Web production build, 1,217 tests across 183 files (three environment-conditional tests skipped), and 48 bilingual documentation pages. Isolated Linux amd64 and arm64 containers passed readiness, administrator bootstrap/login, static-asset serving, reference-image upload/download and anonymous-access rejection. Both architectures contain identical Web assets. External AI providers were mocked in regression tests.

Docker Hub: smartdoca/doca:0.1.11 and smartdoca/doca:latest, for Linux amd64 and arm64.

Web assets are attached as doca-web-assets-v0.1.11.tar.gz. Extract and publish the assets directory unchanged. Set DOCA_ASSET_BASE to the HTTPS prefix that contains it, with no trailing slash. release-manifest.json records source/image digests and verification results; SHA256SUMS verifies the attached artifacts.

中文：本版合并全部改动，原有生成图片工具自动选择会话参考图进行图生图，统一五处下拉框，补充附件上传排队、预览、进度和取消，以及 Docker 存储路径排障说明。从 0.1.10 升级无需迁移数据库或转换存储。完整发行说明：中文 · English；合并记录：PR #35。

v0.1.10

Doca 0.1.10

Changes

• Add host-managed plugin credentials through storage.credentials.v1: server-only encrypted create/read/inspect, revision-checked update/delete, plugin identity and installation generation isolation, and cleanup on uninstall. The environment supplies a shared DOCA_CREDENTIAL_MASTER_KEY; missing, invalid or mismatched keys fail explicitly without generating or replacing a key.
• Add material collections in SDK 0.1.9 / contracts 0.1.7. Materials may belong to zero or multiple collections. Search and AI retrieval return separate material/collection groups with independent tags and pagination. Collection metadata is lightweight; members are queried separately and permissions/revisions are checked before use.
• Unify template and material browsing: two compact rows for sources and tags, defaulting to All, with source multi-selection. The filter icon opens keyword/smart search and sorting. Submitted search terms remain visible and can be cleared. Cards show previews and source information; blank document creation remains available.
• Forward database, Redis, cloud file storage and credential-key settings through Compose. Storage backends remain deployment-owned; the administration interface displays storage state without accepting backend credentials.
• Drain both material/collection query groups before returning a rejection, so a provider being disposed cannot leave its sibling using a database connection after the request ends.
• Keep host version reporting in the application module and exclude local plugin ZIP archives from Git.
• Rebuild the storage acceptance example as 1.0.5 against SDK 0.1.9, with a materials.v2 provider and explicit collection capability.

Breaking deployment requirements

The database baseline is doca-2026-10-03-credentials-v2. Databases from 0.1.9 and earlier are rejected without migration, conversion, automatic table creation or data deletion. Preserve the old deployment, database and storage for rollback; use a new empty database and separate persistent storage for this release. New deployment data remains separate when rolling back.

Material providers now implement materials.v2, declare version: 2, and explicitly declare their collections capability (methods or null). materials.v1 is rejected without an adapter. Existing files, documents and resource references are preserved. Template providers remain on templates.v1.

Plugins must declare doca.storage: "host" and an SDK range covering 0.1.9 whose minimum meets the existing 0.1.7 installation floor. Rebuild material providers against SDK 0.1.9. Plugins using managed credentials must require the public credential token and deployments must retain the same master key across restarts and replicas. Restart every instance manually after plugin changes.

Packages and distribution

• @smartdoca/plugin-sdk@0.1.9
• @smartdoca/plugin-contracts@0.1.7
• File/search/knowledge capability packages remain 0.1.1; web plugin registry remains 0.1.3.
• GitHub tag v0.1.10; Docker images docker.io/smartdoca/doca:0.1.10 and latest, for Linux amd64 and arm64.
• GitHub Release attaches Web assets, SDK/contract tarballs, SHA-256 checksums and a release manifest. The manifest records final registry digests and verification results.

Validation and limits

The default suite passed 1,193 tests across 182 files, with three environment-conditional tests skipped. All 71 targeted PostgreSQL/Redis checks passed, including the three conditional cases. TypeScript, Web production build, the independent SDK JavaScript/declaration consumer and the packed npm consumer passed. Source browser acceptance covered material/template filters, smart search, previews, and narrow-screen filter positioning in isolated fixtures. Credential browser acceptance used isolated databases and synthetic secrets; see the report.

Release artifact verification includes packed/public npm consumers and fresh-database container startup for both supported Linux architectures. Final results are recorded in the release manifest. Real external AI/mail/SSO/Webhook/S3/CDN services and native mobile builds are not claimed as verified. No production user data is used for release checks.

Downloads

• DockerHub: smartdoca/doca:0.1.10 / latest.
• SDK 0.1.9 and contracts 0.1.7.
• Release PR #33.

Extract doca-web-assets-v0.1.10.tar.gz and publish its assets directory unchanged. Set DOCA_ASSET_BASE to the HTTPS prefix containing that directory, without a trailing slash. release-manifest.json records package integrity, image digest, source revisions and artifact verification; SHA256SUMS covers the attached files.

v0.1.9

Doca 0.1.9

Changes

• Store immutable plugin ZIPs in host-managed file storage. The shared database holds the desired installation list, archive references and file hashes. Each instance verifies its local code cache and restores missing or damaged files at startup, without contacting the plugin store or running package installation/build scripts.
• Add public SDK services for plugin-owned structured SQL databases and private binary objects. Bind handles to the plugin ID, data version and installation generation; namespace tables, ordinary files and object paths to avoid host/plugin collisions. Disabling preserves data; uninstalling fences old handles and clears private data while retaining user files and historical releases.
• Move file-store configuration and credentials to DOCA_FILE_STORE_ID and DOCA_FILE_STORES_JSON. The administration page displays the selected backend read-only. Container defaults use local storage at /data/storage; replicas must use the same persistent backend.
• Add public rich-text/spreadsheet plugin elements, host assistant launch APIs, template/material retrieval and reusable pickers. Include prebuilt SDK examples for elements and storage; these are not installed in the production image by default.
• Fix Markdown's first-edit checkpoint handling, same-version reinstall restart status, immediate knowledge-source subscription refresh, and the retired template administration navigation entry.
• Report the host package version consistently in health, readiness, liveness and OpenAPI responses.

Breaking deployment requirements

This release intentionally does not support old versions. The host baseline is doca-2026-10-03-storage-v1, the shared plugin registry is version 2, and plugin packages must declare doca.storage: "host" with an SDK range whose minimum is at least 0.1.7. Old databases, installation lists, storage configuration and SDK ranges are rejected, without migration, conversion or deletion of old data.

Deploy to a new empty database and a separate persistent storage location. Preserve the old deployment, database and storage for rollback; new deployment data remains separate. Rebuild business plugins against SDK 0.1.7 and supply the required storage declaration. Shared PostgreSQL, Redis and file storage are required for multiple instances. Restart every instance manually after plugin changes; a response only reports the serving instance's running selection, not cluster-wide completion.

SDK scope enforces public service isolation, but trusted Node.js plugins are not operating-system sandboxes. Private object uploads whose database commit fails can leave unreferenced bytes; automatic orphan scanning is not provided.

Public npm packages

• @smartdoca/plugin-sdk@0.1.7
• @smartdoca/plugin-contracts@0.1.6
• @smartdoca/web-plugin-registry@0.1.3

File, search and knowledge capability packages remain at 0.1.1. Package publication is verified separately from source version changes.

Validation

The default suite passed 1,166 tests across 179 files, with three environment-conditional tests skipped. PostgreSQL/Redis checks separately passed all three conditional cases. TypeScript, the web build and independent SDK JavaScript/declaration consumers passed. Local browser acceptance used two independent instances with shared PostgreSQL, Redis and file storage; see the detailed report.

Both Linux amd64 and arm64 container images passed fresh-database bootstrap, healthy startup, login, SDK database writes/reads, private object roundtrip, ordinary file creation, content source discovery, static assets and restart with persisted state. Health/OpenAPI versions were checked against 0.1.9.

Real AI/mail/SSO/Webhook/S3/CDN services, mobile device builds, slideshow fullscreen and every editor menu are not claimed as completed acceptance. No production user data was used.

Distribution

GitHub tag: v0.1.9. Docker images: docker.io/smartdoca/doca:0.1.9 and docker.io/smartdoca/doca:latest, for Linux amd64 and arm64. The GitHub Release includes web assets and SHA-256 checksums; publish the unpacked assets directory unchanged when using DOCA_ASSET_BASE.

Web assets are attached as doca-web-assets-v0.1.9.tar.gz. Verify SHA256SUMS, extract the archive and publish its assets directory unchanged. Set DOCA_ASSET_BASE to the HTTPS prefix containing that directory, with cross-origin module access enabled. Do not use the GitHub download URL as the asset base.

Release source: PR #32. Docker manifest and npm package checksums are recorded in release-manifest.json.