2 commits

Author	SHA1	Message	Date
elpresidank	25d4227cb5	fix: resolve FlowProcessor topic collisions, librarian timeout, tests ... Fix critical bug where all FlowProcessor services shared the same spec names ("request"/"response"), causing them to steal each other's NATS topics. Now each service uses unique spec names matching the flow config topic keys (e.g., "text-completion-request", "prompt-request", "agent-request"). Fix librarian NATS consumer timeout (500ms → 2000ms, below NATS minimum). Update seed-config and test-pipeline with correct flow topic mappings. Add prompt template runner script. Smoke test results: 11/11 passing (config CRUD, WebSocket, LLM, librarian CRUD). Agent routing verified via manual curl test. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-06 01:02:10 -05:00
elpresidank	7db5a1023e	feat: add flow manager, config seeding, and expanded integration tests ... Flow Management Service: - FlowManagerService (AsyncProcessor) handling list/get/start/stop flows and list/get blueprints via kebab-case wire format - Default blueprint with all service topic mappings - Pushes flow config to config service on start/stop Config Seeding: - seed-config.ts script pushes prompt templates (extract-relationships, extract-definitions, document-prompt, kg-prompt) and default flow definition via gateway REST API Integration Tests: - Librarian CRUD: add-document, list-documents, get-content, delete - Agent query: verifies routing through gateway to agent service - Skip flags: SKIP_LIBRARIAN=1, SKIP_AGENT=1 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-06 00:37:03 -05:00