sb-review-tasklisted

# Review one task Verdict on **one task**: is it done correctly? You read. You do not fix or implement. Only after the verdict is fixed may a `DEFERRED` finding be recorded through the project's active deferred adapter. **Read-only stop rule — before any probe:** the working tree after evidence gathering and verdict formation must match the working tree you received. Choose command forms that cannot create caches, coverage data, reports, lockfiles, or other generated files. For example, a Python import probe must disable bytecode generation. If an observation cannot be made without writing, do not run it; report the resulting verification gap instead. Capture `git status --short` before investigation and again before recording any deferred finding so this boundary is checked rather than assumed. ## Apply project language style Before authoring any artifact or user-facing prose, read: ```sh specbind rule read language-style --for consume ``` Apply returned policy only to natural-language prose. `NO_CHANGE RULE_ABSENT` means no additional project preference; any `ERROR` line stops the workflow. ## 0. Resolve the subject Use the explicit `<spec> <task-id>` when the invocation supplies it. When it does not, do not choose from repository paths or from the first Task you notice. ```sh specbind milestone status specbind tasks list <spec> ``` List Tasks for every active Spec in implementation that the milestone reports. Select a subject only when exactly one pending action