fix(knowledge_fs): refresh contract subtree lock

This commit is contained in:
Stephen Zhou 2026-08-25 17:57:05 +08:00
parent 644e8f99bc
commit 22de6d29a4
No known key found for this signature in database
2 changed files with 3 additions and 1 deletions

View File

@ -1,6 +1,6 @@
{
"schemaVersion": 5,
"subtreeTree": "2e01cd3cfd3040c77f8087584bc4c7ab606ab2b1",
"subtreeTree": "a21b00e699a9a8bf20730affed89c00808959888",
"openapiSha256": "2cf348c68bbe65dd51bbde9a0a4f91398beeebd79e89e9288c9386b26ae09796",
"capabilityV2AuthManifestSha256": "fc0a47e23cce12544882f0298522b4933002e892b84ce1815df7e81d36a7a0c7",
"capabilityV2AuthTestVectorSha256": "ae0de37b1ff05c40f905cf17a7b410d8971acacf64db07d5ee3d6fecfa559ce3",

View File

@ -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