Feature/stream final answer

[yonadavGit]

No description provided.

[gitvelocity-reviewer]

📊 Code Quality Score: 35/100

58 × 0.6 = 34.8 ≈ 35

Category	Score	Factors
🔭 Scope	13/20	22 files across frontend/backend/tests/config; two distinct features (streaming + tool rename); cross-cutting change touching API, SSE, metrics, prompts
🏗️ Architecture	11/20	Consolidates ai.sefaria.org into sefaria.org base URL; introduces new SSE event type 'partial'; new on_text_delta callback pattern threaded through SDK runner → orchestrator → view → frontend
⚙️ Implementation	12/20	Streaming delta extraction with dual-path logic; SSE event routing; nonlocal closure for TTFC metric; incremental markdown rendering; tool rename across all layers
⚠️ Risk	10/20	Tool renames are breaking changes for existing clients; hardcoded prompt slug is deployment risk; streaming adds new code path to critical response flow; XSS risk with @html rendering
✅ Quality	10/15	New test files for streaming (test_sdk_runner_streaming.py) and metrics (test_metrics_mapper.py); existing tests updated for renames; frontend streaming untested; hardcoded slug is quality concern
🔒 Perf / Security	2/5	TTFC metric improves observability; streaming improves perceived latency; XSS risk with @html renderMarkdown not fully addressed; no sanitization verification

Was this score accurate? 👍 Yes · 👎 No

_{Scored by GitVelocity · How are scores calculated?}

[coolify-sefaria-github]

The preview deployment for sefaria/ai-chatbot:server is ready. 🟢

Open app | Open Build Logs | Open Application Logs

Last updated at: 2026-07-08 07:32:37 CET