fix: recognize Dutch evolution questions
This commit is contained in:
@@ -8389,11 +8389,15 @@ Validation evidence:
|
||||
- Focused temporal, source, Ollama, navigation and Unraid regression tests
|
||||
passed, including direct coverage for multi-metric history and DockerMan host
|
||||
mapping.
|
||||
- Full readiness passed 612 backend tests, backend compilation, 91 documented
|
||||
- Full readiness passed 615 backend tests, backend compilation, 91 documented
|
||||
API routes, one Alembic head, frontend TypeScript typecheck/build and all
|
||||
shell syntax gates.
|
||||
- Local Docker validation was deferred to the live Tower deployment because
|
||||
Docker is not installed on the Windows development host.
|
||||
- Tower deployment passed the all-in-one container health check, live PostGIS
|
||||
3.6 migration/schema smoke and frontend/API proxy smoke. The container reached
|
||||
host Ollama and exposed 10 installed models through the canonical API.
|
||||
- A live historical question revealed that the Dutch verb `evolueerden` did
|
||||
not activate history context. The intent stem was corrected to `evolu`, three
|
||||
direct regression cases were added and full readiness reran successfully.
|
||||
|
||||
Known limitations:
|
||||
- Water volume remains unavailable until a governed depth/bathymetry source is
|
||||
|
||||
Reference in New Issue
Block a user