job_get

When to use

• Use when a previously started BeatBandit job needs progress or result inspection.
• Use this to follow backend-owned workflows such as `story_bootstrap`, `screenplay_import_run`, and `screenplay_writer` instead of switching to low-level mutation tools mid-flight.
• Completed Novel parents with canonical results set `finalize_required=false` and `job.result.finalized=true`, then return the saved-artifact or author-review action. Voice jobs expose the complete proposal resource and apply actions only while their source Voice revisions remain current.
• Running Novel Blueprint, Chapter Outline, Voice, Writer, and Audit parents are long-running backend-owned jobs with a minimum 20-second poll cadence. Poll at the cadence in `job.progress`; the parent persists its result at completion and no client finalize call is required.
• Terminal progress uses a terminal label and caps `elapsed_seconds` at `completed_at`; repeated reads do not make a completed job appear to keep running.
• Trust `job.progress` and `job.client_guidance` for long-running work. Beat, scene, and screenplay jobs on feature and TV templates can legitimately take several minutes (short-format templates such as advertisement and one_scene usually finish in about a minute); keep polling `job_get` rather than restarting the workflow.
• Set `include_result=true` when the job is completed and you want the final generated data rather than only progress metadata.
• Terminal quoted jobs expose `job.billing` from the caller-owned ledger. Report charged/released credits only when `settlement_status=settled`; pending or absent billing is unknown, including when provider usage is null. Parent-owned children do not present their parent's receipt as a separate charge.