Phase 22 - Dify 1.14.1 knowledge alignment

Highlights

• Aligned OpenKB knowledge processing with Dify 1.14.1 concepts: processing rules, explicit reprocess, retrieval model, segments, QA and summaries.
• Added Dify-like KB Settings tabs and document-side panels while keeping the OpenKB workbench style.
• Replaced README placeholder art with screenshots captured from a real local OpenKB instance.

What changed

• KB processing settings now cover doc form, indexing technique, process rule, retrieval model and summary index settings.
• Documents keep processing snapshots and require explicit reprocess when content or rules change.
• Retrieval model defaults are injected into Web Search, Retrieval Lab, MCP and Dify Adapter.
• Segment management supports enable/disable, override/reset and soft delete/restore without rewriting Markdown versions.
• QA and summary generated content maps back to original documents and chunks for Dify/MCP/Web search metadata.

Upgrade notes

• Run database migrations 0014 through 0016.
• Milvus index changes still require explicit blue-green index rebuild; document publish does not automatically switch aliases.
• Model secrets remain instance-level system-admin configuration; there is no KB-level model key.

Validation

• pnpm docs:check
• pnpm format:check
• pnpm typecheck
• pnpm lint
• pnpm build
• pnpm test

Phase 21 - Dify native external knowledge

Highlights

• Added a Dify-native External Knowledge setup flow in OpenKB Admin.
• Expanded Dify response metadata with document, dataset, path, score and retrieval fields.
• Added KB metadata schema and document metadata values as the OpenKB side of Dify-style filtering.

What changed

• Dify Adapter now returns richer metadata while keeping the official { records: [...] } contract.
• Admin Dify page shows endpoint, External Knowledge ID, mappings, allowed KB scope and filterable metadata without exposing raw keys.
• Documentation now includes the OpenKB ↔ Dify field matrix and setup guide.

Upgrade notes

• Run database migrations before starting the API.
• Existing Dify API keys remain app-key-bound and limited to explicitly allowed KBs.
• No Dify database writes are required; integration remains through External Knowledge API.

Validation

• pnpm test
• pnpm typecheck
• pnpm lint
• pnpm build
• pnpm docs:check