fix(evidence): distinguish implicit corpus ownership

2026-07-12 05:59:13 +02:00
parent 6bb158233f
commit 950f88f23e
2 changed files with 13 additions and 1 deletions
@@ -135,3 +135,10 @@ run reached unrelated Task 6 immutable-file tamper tests; those files were delib
  manifest, and that mismatched job, GC, and search paths perform no vector/filesystem mutations.

 Focused workspace-binding, search-pack, preprocess JSON, and scoped Ruff/diff tests pass.
+
+Compatibility follow-up: direct/internal `CorpusPipeline` instances now distinguish an omitted
+workspace identity from an explicit config/job identity. An unbound instance adopts the persisted
+ACTIVE owner (or `default` only for a brand-new direct corpus), preserving safe resume/GC tests and
+the real pgvector lifecycle. Explicit config/job identities still fail closed on any mismatch. The
+two reported regressions, workspace mismatch guards, real Docker lifecycle, scoped Ruff/diff, and
+the full harness suite all pass.