feat(workflow-store): workflow 真相源 KV → KBDB API(entry_type=workflow) #13
Reference in New Issue
Block a user
Delete Branch "feat/workflow-store-kbdb"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
SDD kbdb-base §8.3/§8.4 P2+P3。總管裁定 2026-07-06:① upsert 走 KBDB base PUT /entries;② cron 掃 KBDB、不保留 KV cron-idx;③ 一 workflow=一筆 entry_type=workflow,content=description(保 embed)、graph+config+cron_expr 進 metadata_json。
不 merge、不部署、不動 production 那 7 筆 KV workflow。 改點清單、部署後驗證計畫(對真端點 curl)、剩餘 data 搬遷步驟(leo 寫入閘)全在 MIGRATION.md。
tsc 0 error;kbdb vitest 6/6 綠;cypher vitest 41/42 綠(1 失敗為 pre-existing、與本 PR 無關)。
[總管] 關閉——路走錯了(過度工程)。
leo 點破:KV→KBDB 是 cypher binding 等級,不是平台手術。正解=① 建
workflowtemplate(D6)② 7 個 workflow 當 entry 填進去(KBDB API)③ cypher 把 workflow 讀從KV.get換成GET /entries(換一個 API 呼叫,既有能力)④ 刪 KV+ak_。沒建新零件、沒 service binding → 不需要 PR。 本 PR 加 upsert 端點+雙軌+重寫儲存層=把「換一個 API 呼叫」做成平台手術,作廢。分支保留當參考(discovery 重複 entry bug 的定位有用)。
Pull request closed