Whether a form_runs status is terminal (the run will not progress further).
form_runs statuses only; other run-status domains (job_executions, rpa_runs,
audit_status) have different terminal sets — do not reuse this for them.
Accepts raw strings so it can classify legacy v1 statuses too: v1's terminal statuses
(completed, failed) coincide with v2's; every v1 in-flight status (in_progress,
checking_namespaces, answering, chunking, chunking_skipped, searching,
running) is non-terminal, as is any unknown status.
Note: the legacy v2 UI (PatientGeneratedFormsList) still uses status !== 'running'
semantics; it will be aligned to this helper in PR12.
Whether a
form_runsstatus is terminal (the run will not progress further).form_runsstatuses only; other run-status domains (job_executions,rpa_runs,audit_status) have different terminal sets — do not reuse this for them.Accepts raw strings so it can classify legacy v1 statuses too: v1's terminal statuses (
completed,failed) coincide with v2's; every v1 in-flight status (in_progress,checking_namespaces,answering,chunking,chunking_skipped,searching,running) is non-terminal, as is any unknown status.Note: the legacy v2 UI (PatientGeneratedFormsList) still uses
status !== 'running'semantics; it will be aligned to this helper in PR12.