fix(confidence-engine): retain successful provider path
This commit is contained in:
@@ -73,6 +73,11 @@
|
||||
- The detector fix remains unverified live; a subsequent HTTP 500 left the actually attempted provider path unobservable.
|
||||
- Case-start failure diagnostics now preserve `providerApiPath` only when the provider reports an endpoint actually attempted during that request. The next step remains one production call.
|
||||
|
||||
## Successful provider-path observability
|
||||
|
||||
- The 502 live run at `dabd9e2` was PATH NOT OBSERVABLE ON FAILURE: provider path survived provider errors but not successful-provider/later-validation failures.
|
||||
- Successful provider results now retain their factual attempted path through later reconstruction-validation failure diagnostics. This corrects only that observability seam; the next unknown remains one real `/api/cases/start` call establishing `/api/chat` versus `/api/generate`.
|
||||
|
||||
## Current product architecture
|
||||
|
||||
Three distinct routes, not a single page:
|
||||
|
||||
Reference in New Issue
Block a user