feat(console): 收件夾改裝=全部待辦分流台(三欄 80/15/5 + per-project 過濾)(#9) #41
Reference in New Issue
Block a user
Delete Branch "feat/console-triage-inbox"
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?
對應 issue #9(kb-ingest SDD R7 消費端):console 頁 7「收件夾」改裝成「全部待辦分流台」。issue 的「UI 改裝 + task 資料模型可先做」那半——triage engine / ingest 實資料另案(#8 灌入中)。
實作說明
資料源二合一(
GET /console/triage-data,取代/console/inbox-data——後者唯一消費者就是本頁,一起改裝不留死端點;仍鎖 console session):entry_type=todo(Logseq 萃取,Arcrun#8 ingest 線):content JSON 契約{"text","marker","owner_tier":"ai|collab|leo","project","source","status":"new|done"}照 renderentry_type=inbox(Telegram):沿用{"text","from","status"}三欄分流 80/15/5:ai=AI 會幫我搞定/collab=AI 做完你接手/leo=非我不可。各項顯示 text、project 徽章、source、marker;
status:done預設隱藏、頁尾一鍵切換顯示。per-project 過濾:chips(全部/各 project/未分項),同一包資料前端過濾、零額外請求(leo 手機看,省來回)。手機直排沿 console 單檔薄殼;讀 KBDB 走既有 kbdbBase HTTP 慣例,不新增 binding。
分層:契約解析/分欄/計數=純函式
lib/console-triage-model.ts(比照 console-dashboard-model / PR#36-#40 模式),route 只做 IO,頁面只渲染。契約/設計偏移(兩處,皆有理由)
測試證據
tests/console-triage-model.test.ts11 測全綠;紅→綠驗證:抽掉實作模組同測試即紅(module not found)executor.test.ts「不存在的零件」訊息斷言(main 同紅,與本 PR 無關)tsc --noEmit:新增/修改檔零錯誤(main 既有 12 行 ExecutionContext 錯誤不變)<script>區塊還原跳脫後new Functionparse 全過wrangler dev --local端到端 smoke(未部署):/console200 且含分流台 UI;/console/triage-data無 session 401、真 session 回誠實空模型{"items":[],...counts 全 0}不部署:未跑 wrangler deploy / acr update,部署與 live 寫入閘依 issue 由總管與 leo 確認。
[總管-subagent]
🤖 Generated with Claude Code