From 22de6d29a4aabeaa89a05bcdda65adf80ebaff70 Mon Sep 17 00:00:00 2001 From: Stephen Zhou <38493346+hyoban@users.noreply.github.com> Date: Tue, 25 Aug 2026 17:57:05 +0800 Subject: [PATCH] fix(knowledge_fs): refresh contract subtree lock --- api/knowledge-fs-contract.lock.json | 2 +- .../changes/2026-08-25-research-score-threshold-test-intent.md | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/api/knowledge-fs-contract.lock.json b/api/knowledge-fs-contract.lock.json index 7a1bb35a34d..8502bed353f 100644 --- a/api/knowledge-fs-contract.lock.json +++ b/api/knowledge-fs-contract.lock.json @@ -1,6 +1,6 @@ { "schemaVersion": 5, - "subtreeTree": "2e01cd3cfd3040c77f8087584bc4c7ab606ab2b1", + "subtreeTree": "a21b00e699a9a8bf20730affed89c00808959888", "openapiSha256": "2cf348c68bbe65dd51bbde9a0a4f91398beeebd79e89e9288c9386b26ae09796", "capabilityV2AuthManifestSha256": "fc0a47e23cce12544882f0298522b4933002e892b84ce1815df7e81d36a7a0c7", "capabilityV2AuthTestVectorSha256": "ae0de37b1ff05c40f905cf17a7b410d8971acacf64db07d5ee3d6fecfa559ce3", diff --git a/knowledge-fs/.harness/changes/2026-08-25-research-score-threshold-test-intent.md b/knowledge-fs/.harness/changes/2026-08-25-research-score-threshold-test-intent.md index 8bc995c5cc8..26ce762624d 100644 --- a/knowledge-fs/.harness/changes/2026-08-25-research-score-threshold-test-intent.md +++ b/knowledge-fs/.harness/changes/2026-08-25-research-score-threshold-test-intent.md @@ -4,6 +4,7 @@ - Updated the score-threshold retrieval test plan to use the supported `direct` research intent. - Applied the repository formatter's required layout to the associated retrieval metric expression. +- Refreshed the reviewed Dify KnowledgeFS contract lock for the corrected subtree. ## Why @@ -14,6 +15,7 @@ - `pnpm --filter @knowledge/api typecheck` - `pnpm --filter @knowledge/api test -- research-evidence-retrieval.test.ts` - `pnpm lint:backend` +- `uv run --project api python api/dev/generate_knowledge_fs_contract.py --check` ## Risks and follow-up