v0.12.0

🧭 One recipe, one build run, one trustworthy review boundary

Dobby 0.12.0 replaces execution-time guesswork with a fixed, inspectable workflow recipe. Every plan now enters one native Claude Workflow with the same agent roles, limits, and verification posture—so runs are easier to understand, compare, and improve from evidence instead of configuration theory.

🧪 A baseline you can actually measure

The new baseline-v1 recipe is exposed by bunx dobby env --json with a deterministic fingerprint. It pins the five worker roles to their intended model and effort, caps outer attempts and concurrency at two, and requires mechanical-first verification.

That contract is checked before any worker starts. If the recipe drifts between the plugin, agent definitions, and CLI, execution refuses early rather than silently running a different experiment. Dobby also records the evidence it can observe—attempts, retries, outcomes, role calls, and verification sources—while leaving unavailable provider and cost data honestly marked as unknown.

🏗️ A leaner build loop

/dobby:execute now runs the whole approved plan through a single native Workflow. Tasks move through optional spec-only test authoring, implementation, and independent verification; a failed verification gets at most one bounded fix-and-retry when another verifier attempt remains.

The duplicate per-task reviewer loop is gone. That saves context and calls without weakening the boundary: implementors still cannot verify their own work, terminal fixes are forbidden, blocked dependents do not run, and a write-capable worker with no usable work log triggers an independent safety review before the task is marked needs-human.

🔎 Review the complete change, not fragments

Holistic review now lives where the full story exists: the external PR boundary. dobby pr watch requires review evidence for the current PR HEAD, including Greptile's Last reviewed commit marker when Greptile is the configured gate. A stale summary or an old green review no longer makes a newer push look merge-ready.

This gives each layer one job: the build loop proves task behavior, the PR reviewer judges the complete diff, and merge readiness fails closed when either proof is missing.

🚀 Upgrade

bun update @kvnwolf/dobby

Reload the plugin after updating so the revised worker definitions are active:

/reload-plugins