Running Claude Code Unattended as a Working Java Developer — Hooks, Skills, Scheduled Headless Execution, and Safeguards

When you run Claude Code unattended, the person who would normally approve and monitor it is gone. This shows how to fill those two roles with hooks, skills, headless `claude -p`, scheduled runs, permission allowlists, review gates, and usage budgets, using excerpts from operational files that run every day and examples of failures.