[austinjiann]

New uploads could stop for a cleaned-frame approval or an agent question, requiring the operator to return to the console before processing could continue. This adds a persisted hands-off mode, selected by the upload form, that continues under the submitted options and ends with a scene or an explicit failure report without a question/answer loop.

• Skip the human cleaned-frame pause while preserving all reconstruction and acceptance checks. Disable extra runner flags, unrequested stages, and automatic paid-stage resubmission.
• Record questions, stalled sessions and idle stops as durable terminal outcomes. Retain a source-verified packaged preview when available, with failed/blocked quality recorded separately; never invent a human approval or label a rejected preview successful.
• Preserve pause/cancel, detached attempt ownership and terminal status through restart and late stage events. Existing manual stage retries remain supported and record an explicit resume; saved-input runs retain their one-attempt boundary.
• Show the final reason and preview availability in the dashboard. Missing or rejected delivery assets cannot leave a misleading preview link.

#67 is merged. This PR now targets main and contains only the automatic-upload change.

Validation: 1,353 Python tests and 11 admin tests passed, including real upload/API/SQLite/runner/packager integration with simulated model providers and failure/restart/duplicate-submission cases. The isolated admin production build, Ruff and repository formatting passed. All four CI jobs passed on 1e70cd9 after reconciling with merged main. Independent code review has no outstanding findings. No paid provider calls were made. The Bugbot-specific tool was unavailable; no Bugbot pass is claimed.

Limits: this automates processing and preview delivery, not automatic quality acceptance or geometry repair. Static-world success still requires the existing genuine manual review. The current bottle reconstruction remains a failed-quality preview. A configured running worker is required; this does not deploy a hosted service or add an enforced per-run dollar cap.