Sume /v1/videos says cancelled, /v1/jobs says canceled: guard it

Two routes, two vocabularies

Sume exposes the same video job two ways. POST /v1/videos is shaped like the OpenRouter video API, with a polling_url and its own poll statuses. The same job is also visible at GET /v1/jobs/{id}/status with Sume's job vocabulary. Both are correct; they just do not spell things alike.

The trap is a poll loop whose terminal set came from one page and whose input came from the other. A job that ends canceled but is looked up as cancelled would never match and the loop would run to its deadline.

The two vocabularies (read 2026-10-05)

A normalizer

Map every spelling to the jobs vocabulary at the edge and test against that. Run this as is:

const MAP = {
  pending: "queued", in_progress: "processing",
  cancelled: "canceled", canceled: "canceled",
  queued: "queued", processing: "processing",
  completed: "completed", failed: "failed",
};
export const normalize = (s) => {
  const v = MAP[s];
  if (!v) throw new Error("unknown Sume status: " + s);
  return v;
};
export const isTerminal = (s) => ["completed", "failed", "canceled"].includes(normalize(s));
console.log(isTerminal("cancelled"), isTerminal("in_progress"));

Why throw on unknown

An unknown status should stop the loop loudly, not spin. Sume's docs also mention a queue-shaped field (IN_QUEUE, IN_PROGRESS, COMPLETED) on the jobs status envelope; it maps one to one onto sume_status, so pick one field and stay on it.

On a timeout, do not resubmit the paid request. The job keeps running and billing; read it again from the polling URL.