Summary

• When a BUD is created via the remote MCP create_bud tool, the caller supplies requirements_md directly, so the PRD agent never runs. The PRD agent's completion handler in backend/app/services/agent_result_handlers.py::handle_prd_result is the only path that calls estimate_bud_dates(trigger="prd_completed") for the first snapshot, so MCP-created BUDs land on the "No estimates yet" empty state with no way to populate it from the UI.
• Surface a manual "Run estimation" button in the empty-state branch of BUDEstimateTimeline.vue that emits the same recalculate event the populated header already uses. The button reuses the existing recalculating prop for its loading spinner — no new store action, composable wiring, or endpoint.
• No backend change: POST /v1/buds/{id}/estimates/recalculate runs estimate_bud_dates with no precondition on prior snapshots, so it is first-run safe.

Test plan

• Create a BUD via the remote MCP create_bud tool with non-empty requirements_md.
• Open the BUD in the UI; the Estimates section should show "No estimates yet" with a "Run estimation" button.
• Click the button; spinner should appear, then the populated stepper + range bar render with the first snapshot.
• Existing populated-state Recalculate button still works on an already-estimated BUD (no regression).
• npx vue-tsc --noEmit is clean.