Release phase-26 · qdivan/OpenKB

Highlights

Added Dify Hub for managing Dify external datasets and metadata through the Dify Dataset Service API.
Hardened Dify Hub dataset management: OpenKB only deletes imported, mapped provider=external Dify datasets and never deletes OpenKB knowledge base content.
Published the Yuque-style space and knowledge base roadmap: personal spaces and team spaces both map to OpenKB workspaces; no separate Team table is introduced.

Dify Hub stores a Dify Service API token encrypted with OPENKB_CONFIG_ENCRYPTION_KEY, probes /v1/datasets, lists datasets with pagination, imports existing external datasets, creates external datasets from existing External Knowledge API templates, and syncs OpenKB document metadata fields into Dify metadata filters.
Dify Admin now avoids stale External Knowledge IDs when switching OpenKB knowledge bases and clarifies that Hub base URLs must be reachable from the OpenKB API process/container, not just the browser.
Documentation now treats tenant as a backend/admin boundary and workspace as the implementation of user-facing personal/team spaces.
Added docs/32-yuque-space-kb-model.zh-CN.md with the Phase 27-31 roadmap for registration, personal spaces, team spaces, space homepages, knowledge-base ownership, permissions, and migration.

Apply migration 0020_dify_hub_connections.
Set OPENKB_CONFIG_ENCRYPTION_KEY before saving Dify Hub Service API tokens.
Dify Hub does not create Dify External Knowledge API templates; create one in Dify first, then use its template id in OpenKB Hub.
Existing workspaces are not automatically migrated to personal/team spaces. Follow the future Phase 31 runbook when it lands.
/health.phase is display-only. Validate by commit/tag, migrations, schema, API checks, and smoke tests.