No Night result appeared
Look for that Project’s Night Card in Linear. A Night that started should leave a Night Card even when it produced no work. If no card exists, inspect the local schedule and recent runs:acme-checkout with your Project id. status examines seven past Nights by default and reports job state, sleep history, and missed-Night diagnoses. A sleeping Mac, missing or disabled jobs, or an invocation that failed before initialization require different fixes; follow the reported diagnosis.
For missing or stale jobs, inspect the report before using yh doctor --fix --check launchd --project acme-checkout. If it names a different app copy, review the executable path before using the explicit --repoint option. For other setup failures, use connection troubleshooting.
Logs are under ~/Library/Logs/Yellowhammer/, named <project-id>.author.log, <project-id>.build.log, and <project-id>.land.log. Read the first failure rather than assuming a later empty invocation means the original work succeeded.
Night stopped or work is Blocked
Read the Night Summary, then the affected Card’s Managed Block and Attempts. The Block Reason is prose in that block, not a separate label to search for.
A Waiting on You Card needs an answer or decision in Linear. Follow its explicit next action. Raising Bounds without resolving the cause can repeat the same failure. If authoring stops because implemented Features await merge, review and merge eligible pull requests; later Acts observe merges before authoring more work.
A usage-limited CLI may back off temporarily. Review the recorded usage-limit evidence and available fallback Routes; do not treat a temporary backoff as proof the Card’s code failed.
A pull request is missing
Check the Night Summary and the Feature’s per-Repo result. Rehearsals never push or open pull requests. A real Night may have no eligible work to publish, a pending decision holding landing, a verification problem, or a GitHub publication failure. A Partial Landing can publish completed work while carrying unfinished Cards forward. Follow the reported publication exception, inspect the land log, and check the selected credential:Gather diagnostic details
Collect the Project id, configured Night date, linked Linear issues, repository and pull request links, exact error, relevant Act log, and app or engine version. Includeyh status and the relevant filtered doctor findings. Remove credential values and private source text before sharing.