Ship the Phase 4 accuracy eval suite with a manual Gitea workflow, emit
versioned WS status frames during grounded chat, and introduce opt-in
agent infrastructure (Redis/Celery, AgentRun/Step, tools, orchestrator)
gated by ALLOW_AGENTIC_TASKS so default chat behaviour stays unchanged.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
evals/suite.json(≥40 graded questions),run_evalsmanagement command, and manually-triggered.gitea/workflows/run-evals.yml.statusframes during grounded chat (evaluating / searching / reading_sources / refining / writing) for chat_web_app#96.AgentRun/AgentStep, tool registry (SSRF-safefetch_url, tenant-scoped docs), LangGraph orchestrator, progress frames, RESTGET/POST /api/agent_runs/…, gated byALLOW_AGENTIC_TASKS(default off).Test plan
SKIP_RAG_INIT=1 uv run python manage.py testfor evals, ws frames, agent tools, consumers, groundingALLOW_AGENTIC_TASKS=false, chat identical to todaypython manage.py run_evals --runs 3ALLOW_AGENTIC_TASKS=truemulti-step research prompt creates AgentRun + frames