implement-tasklisted

# Implement task Build exactly one Task from a Spec folder. The Task file defines the slice, acceptance criteria, and Verification contract. Standalone execution owns the full lifecycle; a Roundfix Daemon-assigned turn hands back implementation-ready work for Daemon Verification and settlement. **Being assigned the Task — by the user, a loop, or a Daemon — is the authorization to start.** Begin immediately: no greeting, no plan-approval question, no waiting for a "go". Contradictory requirements, or a stale standalone `in_progress` status, are the only reasons to pause before implementing. ## Execution modes Standalone execution and a Roundfix Daemon-assigned turn share the same Task slice, Result, and evidence requirements, but they have different settlement owners. - In standalone execution, the Agent updates Task status, runs every command in `## Verification`, settles the Task from fresh evidence, and commits only when the user has authorized a commit. - In a Roundfix Daemon-assigned turn, the Daemon is the sole Task-status writer. The Agent must not edit status, run the declared `## Verification` commands, claim a terminal verdict, or commit. It may run focused checks, records implementation and focused-check evidence in `## Result`, and hands back implementation-ready work. The Daemon then runs the complete declared Verification verbatim before settlement. - A Daemon Verification command failure releases Verification Capacity before one Verification