bot-backend
7b3d1a8f85
All checks were successful
CI Trade-In / changes (pull_request) Successful in 9s
CI / changes (pull_request) Successful in 9s
CI Trade-In / frontend-checks (pull_request) Has been skipped
CI / frontend-tests (pull_request) Has been skipped
CI Trade-In / backend-tests (pull_request) Has been skipped
CI / openapi-codegen-check (pull_request) Successful in 2m8s
CI / backend-tests (pull_request) Successful in 14m34s
Chat could not answer 'какая зона ПЗЗ?' — retrieval loaded only the §22 forecast run (schema 1.0); тер.зона/градрегламент/ЗОУИТ/ЕГРН live in the analyze-1.0 run and never reached the chat context. Add get_parcel_context_for_chat: a §19-safe whitelist slice of analyze (fixed keys AND scalar-only values — dict/list dropped at the boundary; ЗОУИТ zone names as a dedicated str-only capped list; no geometry/PII/raw sub-dicts) merged into a copy of report_dict under 'parcel_context'; expose it via the sixth sectional tool get_parcel_info. Bump chat_system prompt v2->v3 so the model uses it and no longer treats the parcel's own ПЗЗ zone as out of scope. |
||
|---|---|---|
| .. | ||
| analysis_runs | ||
| analytics | ||
| cadastre | ||
| chat | ||
| etl | ||
| exporters | ||
| forecasting | ||
| generative | ||
| llm | ||
| photos | ||
| scrapers | ||
| site_finder | ||
| __init__.py | ||
| analytics_queries.py | ||
| analytics_refresh.py | ||
| dadata_client.py | ||
| forecast_request_cache.py | ||
| insights.py | ||
| job_settings.py | ||
| objective_etl.py | ||
| objective_sync_config.py | ||
| own_projects.py | ||
| weather_cache.py | ||