v0.10.0

🎪 v0.10.0 — the interview learns to juggle

One thing changed for the better, and you'll feel it in the first minute of your next /dobby:scope session: the interview stops dripping questions one per turn and starts asking in frontier rounds — every question that's answerable right now travels together, and only the ones that genuinely depend on an open answer wait their turn.

❓ Frontier rounds in /dobby:interview

The old interview was thorough but slow on purpose: one focused question per turn, always. That rule was right about focus and wrong about cadence — when four open questions don't depend on each other, four round-trips are three too many.

The interview now models your task as a design tree and asks the frontier — every open decision whose prerequisites are already settled — in rounds:

• 🪟 Popup rounds first: up to 4 independent questions in one AskUserQuestion call, each still fully self-contained (its own 1–3 lines of context inside the question — the popup covers the turn's text, so nothing load-bearing lives outside it), each with a recommended answer.
• ✍️ Text rounds after: open-ended questions arrive as their own numbered ❓ **Q1**… / ➡️ recommended list, so you answer several in one typed message.
• ⛓️ Dependent chains still arrive one at a time — a question whose premise hangs on an open answer belongs to a later round. The old one-question interview didn't die; it's the degenerate case of the new mechanism.
• 🔬 Fact-finding no longer stalls the conversation: when a claim needs checking against the code, a researcher is dispatched and only the questions downstream of that fact wait — the rest of the frontier ships now.
• ♻️ And if an answer invalidates a sibling answered in the same round, the orphaned answer is discarded and the question re-asked with the corrected premise — no decision ever stands on a premise that moved under it.

The closing machinery you rely on — the litmus test, the infra-assumption gate, the glossary term offer, the STATE.md persistence — is untouched. frontier, round, and design tree joined the glossary, ADR 0020 records the why, and the mechanism is adapted from mattpocock/skills' productivity/grilling (the attribution now points at the skill's current home — it was renamed upstream from batch-grill-me).

🤝 /dobby:finish closes the deal — literally

The other hop that stopped hurting: finish no longer makes you detour to GitHub to press the merge button. When your PR is merge-ready and the tree is clean, the finish gate now offers "Merge & finish" — it re-verifies merge-readiness (dobby pr watch), merges squashed, re-runs the preflight, and rolls straight into the teardown: dobby down, worktree + branch removed, main pulled. Your explicit selection is the merge decision — no path merges on its own, feedback-present still routes to /dobby:address-review, and /dobby:commit still never merges. The commit → (merge on GitHub) → finish lifecycle is now just commit → finish.

⬆️ Upgrading

Nothing is asked of you: no new config keys, no hook changes, no rules that can go red. Update the devDependency and enjoy the shorter conversations:

bun update @kvnwolf/dobby

The plugin side ships with your marketplace auto-update; the batched interview and the merging finish are live the next time the skills load.