fix(confidence-engine): use configured model for chat detection
This commit is contained in:
@@ -63,6 +63,11 @@
|
||||
- Caught exceptions log their actual exception, message, and stack while the client response remains generic; successful responses are not logged. No reasoning, status, or response semantics changed.
|
||||
- Next restart point: one production-default manufacturing call while observing the Next.js dev-server terminal.
|
||||
|
||||
## Chat capability detection
|
||||
|
||||
- Direct POST `/api/chat` was proven supported. The false-negative cause was the capability probe using model `dummy-check`, which conflated model availability with endpoint capability.
|
||||
- The probe now uses the configured model; live behaviour after this fix remains untested.
|
||||
|
||||
## Current product architecture
|
||||
|
||||
Three distinct routes, not a single page:
|
||||
|
||||
Reference in New Issue
Block a user