1800e71229
After processing a new knowledge base spec, invalidate_cache() was clearing the DB spec from the cache without replacing it. The next analysis would then fall back to static prompts/*.md files instead of using the newly generated DB spec. Now invalidate_cache() accepts optional new_spec_content to immediately populate the DB cache, and knowledge_base_service passes the freshly distilled spec content so it's available for the next analysis without a server restart. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| analysis_service.py | ||
| auth_service.py | ||
| email_service.py | ||
| gemini_service.py | ||
| knowledge_base_service.py | ||
| llamaparse_service.py | ||
| pdf_service.py | ||
| reference_docs.py | ||
| storage_service.py | ||