hailin c2b4fe19cc refactor(evolution): use knowledge-service API for system_experiences ... Follow proper microservices architecture: - knowledge-service owns system_experiences table - evolution-service uses KnowledgeClient API to save experiences - Deleted SystemExperienceORM from evolution-service - Added internal API endpoints in knowledge-service - Disabled synchronize in all services for safety Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>		2026-01-24 20:20:30 -08:00
..
conversation-service	refactor(evolution): use API instead of shared database tables	2026-01-24 19:48:09 -08:00
evolution-service	refactor(evolution): use knowledge-service API for system_experiences	2026-01-24 20:20:30 -08:00
file-service	fix(file-service): specify explicit column types for TypeORM entities	2026-01-10 06:05:36 -08:00
knowledge-service	refactor(evolution): use knowledge-service API for system_experiences	2026-01-24 20:20:30 -08:00
payment-service	fix(payment): use PORT env variable instead of PAYMENT_SERVICE_PORT	2026-01-10 02:48:44 -08:00
user-service	fix(health): exclude /health endpoint from API prefix	2026-01-10 02:30:24 -08:00