fix(confidence-engine): resolve synthesis model configuration

2026-08-31 07:32:04 +01:00
parent 75f7c6bafd
commit 8e941b0c7b
4 changed files with 114 additions and 3 deletions
@@ -2845,3 +2845,58 @@ Fix synthesis route to pass `modelName: process.env.OLLAMA_MODEL`; then integrat
 #### Exact first trace question

 What is the minimal server-side fix to the synthesis route so it passes `modelName` to `synthesizeCurrentUnderstanding`, enabling live CU reconstruction verification?
+
+---
+
+## v0.50 — FOCUSED-FINDING SYNTHESIS TRIGGER (2026-08-31)
+
+### Model-resolution repair — CLOSED
+
+The synthesis route now supplies the configured `OLLAMA_MODEL` and the domain resolves explicit dependency / config / environment model with correct priority.
+
+**Changes:**
+- `app/api/cases/synthesis/route.js` — passes `modelName: process.env.OLLAMA_MODEL ?? null` to `synthesizeCurrentUnderstanding`
+- `lib/graph/current-understanding-synthesis.js` — resolves modelName by priority: explicit dep > config dep (assertConfig) > process.env > null
+- `tests/graph/current-understanding-synthesis.test.js` — two new tests confirming configured model resolution and explicit override
+
+**Deterministic gate:**
+- synthesis + route tests: 54/54 PASS
+- focused integration tests: 19/19 PASS
+- build: PASS (pre-existing reasoning-workspace warning unchanged)
+
+**Direct API evidence:**
+- small canonical fixture → HTTP 200
+- exact persisted onboarding investigation:
+  - 13 nodes, 10 edges, 21 canonical Findings
+  - 21,301-byte request
+  - → HTTP 200 in 46.181s
+  - → coherent reconstructed CU
+  - → no Evidence append/repetition observed
+
+**Static ownership:**
+- one successful focused deconstruction owns one synthesis call
+- no automatic duplicate synthesis
+- newly derived Findings are included explicitly
+- HTTP synthesis failure does not propagate into focused-deconstruction error handling
+- no static lifecycle defect was proved
+
+**Final live runtime (classification RUN-A):**
+- one focused deconstruction → HTTP 200
+- exactly one `/api/cases/synthesis` request → HTTP 200
+- Current Understanding visibly replaced
+- newly submitted evidence incorporated
+- generic workspace error absent
+
+### NEXT BOUNDED ISSUE (for future reference)
+
+#### Name
+
+Focused → global integration — carry synthesized understanding back through case/update path and persist across cold return.
+
+#### Next branch
+
+to be determined
+
+#### Exact first trace question
+
+How does the reconstructed Current Understanding from synthesis reach the ScenarioForm state on cold return without re-fetching or losing narrative continuity?