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>
This commit is contained in:
elpresidank 2026-04-06 01:02:10 -05:00
parent 515fc0c264
commit 25d4227cb5
8 changed files with 147 additions and 98 deletions

View file

@ -13,12 +13,14 @@
"llm:openai": "tsx scripts/run-llm-openai.ts",
"test:pipeline": "tsx scripts/test-pipeline.ts",
"seed": "tsx scripts/seed-config.ts",
"prompt": "tsx scripts/run-prompt.ts",
"agent": "tsx scripts/run-agent.ts",
"librarian": "tsx scripts/run-librarian.ts",
"knowledge": "tsx scripts/run-knowledge.ts",
"flow-manager": "tsx scripts/run-flow-manager.ts"
},
"devDependencies": {
"nats": "^2.29.0",
"tsx": "^4.21.0",
"turbo": "^2.5.0",
"typescript": "^5.8.0"