fix: pipeline timeline log, chunk lookup, face processor no fallback, Qdrant UUID script, delete safety rules

AGENTS.md

@@ -11,6 +11,9 @@ Rust-based digital asset management system with video analysis and RAG capabilit
 - **絕對不可修改 n8n 工作流或設定**
 - **絕對不可修改 WordPress 或 n8n 的資料庫 table**
 - **除非是 release 作業，絕對不可動 port 3002 (production)**
+- **🔴 DELETE / REMOVE / DROP / CLEAR 任何資料前必須先問使用者「要刪嗎？」獲得明確同意後才能執行**
+- **🔴 Qdrant collection 刪除、DB truncate、檔案刪除、資料清空 — 一律要先問**
+- **🔴 不確定是否該刪 → 先問，不要自己決定**
 
 ### 開發範圍界定
 | 範圍 | 狀態 | 說明 |
@@ -52,7 +55,7 @@ Rust-based digital asset management system with video analysis and RAG capabilit
 |------|------|----------|
 | `sed` API doc 編號 | `sed -i '' 's/.../.../g'` 改到所有行 | 先 `grep -c` 確認匹配，`git diff` 再提交 |
 | 亂加 `/api/v1/register` route | 不必要的 API 別名，汙染路由表 | 角色切換：路由設計不該由實作方決定 |
-| `DESIGN/` vs `STANDARDS/` vs `REFERENCE/` | 文件放到錯誤分類 | 先確認文件性質（草稿/標準/參考/記錄） |
+| `API_WORKSPACE/` vs `GUIDES/` vs `REFERENCE/` vs `DESIGN/` vs `OPERATIONS/` vs `INTEGRATIONS/` | 文件放到錯誤分類 | API 文件改在 API_WORKSPACE/modules/ 編輯，`make deploy` 生成到 GUIDES/ |
 | Build release binary in plan mode | 浪費時間，無意義 | 嚴格遵守 plan/build mode 規定 |
 
 ### ⛔ 嚴格測試隔離規則 (Strict Test Isolation)
@@ -715,7 +718,8 @@ This applies to docs, code, API responses, and curl examples. Exceptions: intern
 
 ## Document Compliance Checklist
 
-Before creating any `REFERENCE/*.md` file, verify all items below.
+Before creating any file in `docs_v1.0/` (API_WORKSPACE, GUIDES, REFERENCE, DESIGN, OPERATIONS, INTEGRATIONS), verify all items below.
+**IMPORTANT**: API functional documents are generated from `API_WORKSPACE/modules/`. Edit modules there, then run `make deploy` in `API_WORKSPACE/` to update `GUIDES/`. Never edit generated files in `GUIDES/` directly. See `DESIGN/Modular_Doc_System_V1.0.md` for the full system design.
 
 ### P0 — Mandatory (7 items)
 
@@ -727,7 +731,7 @@ Before creating any `REFERENCE/*.md` file, verify all items below.
 | 4 | PascalCase filename | e.g. `DetectorRegistry.md`, not `detector_registry.md` |
 | 5 | `_` separator | Within filenames use `_`, never spaces or other chars |
 | 6 | English content | Entire file in English |
-| 7 | REFERENCE/ path | File must reside under `docs_v1.0/REFERENCE/` |
+| 7 | Correct directory | File must reside in appropriate directory: `API_WORKSPACE/modules/` (API endpoint modules), `GUIDES/` (user docs, generated), `REFERENCE/` (data models), `DESIGN/` (architecture), `OPERATIONS/` (infra/release), `INTEGRATIONS/` (n8n/tests) |
 
 ### P0b — UUID Naming
 
@@ -740,7 +744,7 @@ Before creating any `REFERENCE/*.md` file, verify all items below.
 
 | # | Check | Note |
 |---|-------|------|
-| 1 | Cross-references | Link to related REFERENCE docs |
+| 1 | Cross-references | Link to related docs in API_WORKSPACE/, GUIDES/, REFERENCE/, DESIGN/, OPERATIONS/ |
 | 2 | Glossary terms | Define non-obvious terms inline or link glossary |
 | 3 | Diagrams | Include Mermaid/ASCII diagram for complex topics |
 
@@ -754,4 +758,4 @@ Before creating any `REFERENCE/*.md` file, verify all items below.
 
 完整交付程序（M4_workspace → M5 → Release → Deploy → Public）見：
 
-`docs_v1.0/REFERENCE/DELIVERY_PROCEDURE.md`
+`docs_v1.0/OPERATIONS/DELIVERY_PROCEDURE.md`