fix: drop redundant chunk_vectors chunk_id unique constraint

docs_v1.0/M4_workspace/2026-05-13_chunk_vectors_unique_response.md

@@ -0,0 +1,19 @@
+# chunk_vectors unique constraint — 回覆
+
+**Date**: 2026-05-13
+**From**: M5
+**To**: M4
+**Ref**: `2026-05-13_chunk_vectors_unique_conflict.md`
+
+---
+
+| 問題 | 狀態 |
+|------|:--:|
+| `chunk_vectors_chunk_id_key` 多餘 unique | ✅ `dev` + `public` 皆已移除 |
+
+SQL 已執行：
+```sql
+ALTER TABLE dev.chunk_vectors DROP CONSTRAINT IF EXISTS chunk_vectors_chunk_id_key;
+```
+
+M4 可重新 deploy 23b1c87。

docs_v1.0/M4_workspace/2026-05-13_release_sop_draft.md

@@ -74,6 +74,9 @@ ALTER TABLE public.chunk DROP COLUMN IF EXISTS chunk_index;
 
 -- Add new columns (v1.0.3+)
 ALTER TABLE public.face_detections ADD COLUMN IF NOT EXISTS timestamp_secs float8;
+
+-- Drop redundant unique constraint (cross-file chunk_id collision)
+ALTER TABLE public.chunk_vectors DROP CONSTRAINT IF EXISTS chunk_vectors_chunk_id_key;
 ```
 
 ### 3.2 Verify Schema