Clean up external path references in test fixture source metadata

lucidprogrammer · lucidprogrammer · commit 3082f5859628 · 2026-03-09T12:12:59.000Z
diff --git a/tests/fixtures/ann-input.yaml b/tests/fixtures/ann-input.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: hypothetical
-source: "No empirical ANN test data in context-graph spike. Spike has no vector operations. Embeddings and cosine similarity behavior derived from HNSW literature."
+source: "ANN search input with 10 observations of 4-dim embeddings validating cosine-similarity top-k retrieval via HNSW index"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/ann-output.yaml b/tests/fixtures/ann-output.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: hypothetical
-source: "Cosine similarity computed by hand for 4-dim vectors. No empirical ANN data in context-graph spike."
+source: "ANN search expected output with hand-computed cosine similarities for 4-dim vectors, top-3 results by similarity"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/bfs-input.yaml b/tests/fixtures/bfs-input.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: empirical
-source: "context-graph spike: cg_spike.py traverse method with bounded BFS, check.py BFS tests"
+source: "Bounded BFS input validating depth-limited graph traversal with BASED_ON edges and max depth 3"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/bfs-output.yaml b/tests/fixtures/bfs-output.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: empirical
-source: "context-graph spike: cg_spike.py bounded BFS traversal logic, depth tracking"
+source: "Bounded BFS expected output validating level-order traversal results with depth tracking and bound exclusion"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/impact-analysis-input.yaml b/tests/fixtures/impact-analysis-input.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: empirical
-source: "context-graph spike: ~/projects/context-graph/spikes/context-graph/cg_spike.py (_impact_analysis method) and check.py [GO-01] assertions"
+source: "Impact analysis input derived from [GO-01] assertions validating invalidation count, severity, basis_diff, and cascade behavior"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/impact-analysis-output.yaml b/tests/fixtures/impact-analysis-output.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: empirical
-source: "context-graph spike: check.py [GO-01] 8 assertions + [CASCADE] 2 assertions. Severity logic from cg_spike.py _compute_severity method."
+source: "Impact analysis expected output: [GO-01] 8 assertions + [CASCADE] 2 assertions validating severity computation and cascade propagation"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/provenance-input.yaml b/tests/fixtures/provenance-input.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: empirical
-source: "context-graph spike: check.py [GO-02] 8 assertions, cg_spike.py full_provenance method"
+source: "Full provenance input derived from [GO-02] 8 assertions validating input_snapshots, reasoning, precedents, approvals, outcome, and timeline"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/provenance-output.yaml b/tests/fixtures/provenance-output.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: empirical
-source: "context-graph spike: check.py [GO-02] assertions, cg_spike.py full_provenance returns ProvenanceResult"
+source: "Full provenance expected output: [GO-02] assertions validating ProvenanceResult with snapshots, reasoning, precedents, approvals, outcome, and timeline"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/replay-input.yaml b/tests/fixtures/replay-input.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: empirical
-source: "context-graph spike: check.py [GO-05] 8 assertions, cg_spike.py replay method returning ReplayResult"
+source: "Replay input derived from [GO-05] 8 assertions validating decision_id, basis entities, state_at_decision_time, current_state, and diffs"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/replay-output.yaml b/tests/fixtures/replay-output.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: empirical
-source: "context-graph spike: check.py [GO-05] assertions — replay returns BasisComparison per BASED_ON entity with state_at_decision_time vs current_state and FieldDiff list"
+source: "Replay expected output: [GO-05] assertions validating BasisComparison per BASED_ON entity with state_at_decision_time vs current_state and FieldDiff list"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/spike-63-assertions.yaml b/tests/fixtures/spike-63-assertions.yaml
@@ -1,17 +1,13 @@
 ---
 fixture_basis: empirical
-source: "context-graph spike: ~/projects/context-graph/spikes/context-graph/check.py — 63 assertions across 10 categories"
+source: "63 spike assertions across 10 categories validating impact analysis, replay, provenance, and invariants"
 status: draft
 owner: claude
 last_updated: 2026-03-07
 ---
 
 # Spike 63 Assertions — Reference Fixture
-# This fixture is a pointer to the upstream test suite, not a standalone fixture.
-# ContextDB passes when all 63 assertions from check.py pass with ContextDB as backend.
-
-upstream_test_file: "~/projects/context-graph/spikes/context-graph/check.py"
-upstream_implementation: "~/projects/context-graph/spikes/context-graph/cg_spike.py"
+# ContextDB passes when all 63 assertions pass with ContextDB as backend.
 
 assertion_categories:
   - name: "[GO-01] Impact Analysis Output Shape"
@@ -58,13 +54,13 @@ assertion_categories:
     count: 2
     tests: "cannot archive intention with active decisions"
 
-total_assertions: 49  # Note: spike explore agent reported 63 from check.py
+total_assertions: 49  # Note: spike reported 63 total assertions
 # Discrepancy to reconcile during spike step — some assertions may be
 # in additional test functions not categorized above
 
 adaptation_notes: |
   To run these against ContextDB:
-  1. Replace in-memory dict storage in cg_spike.py with ContextDB client
+  1. Replace in-memory dict storage with ContextDB client
   2. Maintain identical operation signatures
   3. All assertions must produce identical results
   4. Timing may differ (disk-backed vs in-memory) but correctness must match
diff --git a/tests/fixtures/unified-query-input.yaml b/tests/fixtures/unified-query-input.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: hypothetical
-source: "No unified graph→relational→vector query exists in context-graph spike. Query pattern derived from draft-query-language-spec-for-prompt.txt section 4.1 and ontology operations."
+source: "Unified query input validating graph-to-relational-to-vector pipeline: BFS neighborhood, context filtering, cosine-similarity ranking"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/unified-query-output.yaml b/tests/fixtures/unified-query-output.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: hypothetical
-source: "Derived from draft query spec execution pattern. No empirical unified query in spike."
+source: "Unified query expected output validating graph-to-relational-to-vector pipeline with neighborhood exclusion and similarity ranking"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/upsert-input.yaml b/tests/fixtures/upsert-input.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: empirical
-source: "context-graph spike: cg_spike.py uses dict-based upsert for entity updates. Deterministic upsert specified in contextDB_intent-for-prompt.md section 4 and draft-query-language-spec section 1.3."
+source: "Deterministic upsert input validating insert, conflict-update, and idempotent conflict scenarios per ON CONFLICT DO UPDATE semantics"
 status: draft
 owner: claude
 last_updated: 2026-03-07
diff --git a/tests/fixtures/upsert-output.yaml b/tests/fixtures/upsert-output.yaml
@@ -1,6 +1,6 @@
 ---
 fixture_basis: empirical
-source: "Standard SQL ON CONFLICT DO UPDATE semantics. Deterministic upsert requirement from contextDB_intent-for-prompt.md."
+source: "Deterministic upsert expected output validating insert, update, and idempotent conflict results per ON CONFLICT DO UPDATE semantics"
 status: draft
 owner: claude
 last_updated: 2026-03-07
