afb536f21f2804ac9efbbbd39057669c48c144df
Tool availability is a strict per-stage allowlist, so the task doctrine was inert in role_pipeline — no stage granted the tools. Add them where they fit each stage's tier and role, and point the stage prompts at the lifecycle: - analyst (read-only): task_search/task_context to find related or duplicate work and ground the analysis. - implementer: full set — claim before working, submit_for_review once verification passes, create one if the work warrants tracking. - reviewer: task_context to judge against the task's own criteria, task_update to complete it on an approved verdict. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
fix: workflow inference chain — surface llama-server errors, user-turn-last, bundle-relative prompts
Description
No description provided
Languages
Kotlin
88.4%
Go
11.4%
Python
0.2%