fix(confidence-engine): sanitize focused reasoning outage

2026-09-09 17:34:56 +01:00
parent 6974b710de
commit ed033e71d5
5 changed files with 56 additions and 1 deletions
@@ -3,6 +3,12 @@
 > **Role:** Concise operational snapshot for resuming work today. Not a historical diary.
 > The design evolution archive index at `docs/design-evolution/README.md` provides progressive loading of experiment history; load the relevant chapter only when a specific historical question requires it.

+## Focused-investigation provider outage boundary
+
+- Focused-investigation outage handling now sanitizes provider failure at the API boundary: unavailable focused reasoning returns a controlled HTTP 503, and raw provider/Ollama diagnostics no longer leave that boundary.
+- The existing generic Retry UX remains unchanged. A live deployed outage had already proven investigation preservation.
+- `/api/cases/start` and `/api/cases/update` outage sanitization remain separately unverified; this change does not claim those routes are fixed.
+
 ## v0.62d production Docker packaging — LIVE PROVEN

 - `Dockerfile` — minimal multi-stage Alpine build (Node 22), Next.js standalone output mode
@@ -1,5 +1,11 @@
 # Current Project State — Confidence Engine

+## Focused-Investigation Provider Outage Boundary
+
+- Focused-investigation outage handling now sanitizes provider failure at the API boundary: unavailable focused reasoning returns a controlled HTTP 503, and raw provider/Ollama diagnostics no longer leave that boundary.
+- The existing generic Retry UX remains unchanged. A live deployed outage had already proven investigation preservation.
+- `/api/cases/start` and `/api/cases/update` outage sanitization remain separately unverified; this change does not claim those routes are fixed.
+
 ## v0.62d Production Docker Packaging — LIVE PROVEN

 - `Dockerfile` created: multi-stage Alpine build (Node 22), Next.js standalone output, configurable port 3000, health-check boundary via `/api/health`