kami
e0f623a10c
role_pipeline.toml is now analyst → architect → decomposer → loop(claim → implement → review) → done. The decomposer (require_task_decompose) breaks the design into a task graph; the implementer stage claims the next ready task on entry (claim_task = true, kernel-driven) with writes auto-scoped to the task's affected_paths and propose_scope as the operator-approved widen valve. The loop is gated by the tasks_ready predicate. Loop precedence rides the resolver's by-id transition ordering (review-1/2/3) to avoid composite all_of/not conditions in the flat TOML schema: changes → implementer, approved+tasks_ready → implementer, else → done. TomlWorkflowLoader gains a claim_task stage field (→ claimTask metadata) and extracts the metadata build into StageSection.toMetadata. RolePipelineWorkflowTest rewritten for the tasked graph.