Plan U6 vector slice (KTD11 correctness step): v25 adds model/content_hash identity columns and a best-effort pgvector extension + vec_pg column (absence degrades to in-process scan); dual-write BLOB + vec_pg; model-filtered SQL exact top-k with degradation; embedders expose Model() threaded through the rag pipeline; storage-migrate excludes the derived vec_pg. Green on SQLite and real PG 18.6 + pgvector. Refs: plan U6 slice 3, R9.
Plan U6 vector slice (KTD11 correctness step): v25 adds model/content_hash identity columns and a best-effort pgvector extension + vec_pg column (absence degrades to in-process scan); dual-write BLOB + vec_pg; model-filtered SQL exact top-k with degradation; embedders expose Model() threaded through the rag pipeline; storage-migrate excludes the derived vec_pg. Green on SQLite and real PG 18.6 + pgvector. Refs: plan U6 slice 3, R9.
Why: plan U6 vector slice (KTD11 correctness step) - same-dimension vectors from different models must never mix, and PG tiers should run filtered exact top-k in the database instead of scanning every row in-process.
Evidence: full suite green on SQLite and real PostgreSQL 18.6 with pgvector (35 packages each tier) - pgvector_test covers model-identity and dimension isolation, update/delete atomicity (BLOB and vec_pg swap together), shared top-5 with score monotonicity, Recall@10 = exact-scan parity, deny-all predicate leakage; storage-migrate tests green after excluding the derived vec_pg column.
Impact: v25 migration adds model/content_hash columns and (PG, best-effort DO block) the pgvector extension plus vec_pg column - absence degrades to in-process scan; UpsertKnowledgeVectorExt dual-writes BLOB (cross-tier authority) and vec_pg; SearchKnowledgeVectorsModel/SharedModel filter by model identity and use SQL exact top-k (ORDER BY vec_pg <=> q) with automatic degradation; embedders expose Model() and the rag pipeline threads it through indexing and both retrieve paths; storage-migrate excludes vec_pg as a derived column.
Refs: proposals/2026-10-11-collaboration-storage-and-distribution.md U6 slice 3, KTD11; R9.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Plan U6 vector slice (KTD11 correctness step): v25 adds model/content_hash identity columns and a best-effort pgvector extension + vec_pg column (absence degrades to in-process scan); dual-write BLOB + vec_pg; model-filtered SQL exact top-k with degradation; embedders expose Model() threaded through the rag pipeline; storage-migrate excludes the derived vec_pg. Green on SQLite and real PG 18.6 + pgvector. Refs: plan U6 slice 3, R9.