Record cancelled workflows as Canceled in duroxide.executions

[Copilot]

Cancelled workflows could end as Failed in duroxide.executions.status, while df.status()/df.instances reported cancelled. This mismatch made cancellations indistinguishable from true failures in execution-level queries.

• Status normalization in runtime-managed durable schema

  • Added worker-installed normalization functions/triggers to map cancellation outcomes to durable-store terminal status Canceled in duroxide.executions.
  • Added backfill normalization for pre-existing mismatched rows (Failed execution rows tied to df.instances.status = 'cancelled').

• Race-safe cancellation convergence

  • Added normalization on both sides of the race:
    • when df.instances.status transitions to cancelled;
    • when duroxide.executions.status is inserted/updated.
  • This closes timing windows where cancellation and execution-finalization were previously recorded out of sync.

• Worker schema versioning

  • Bumped WORKER_SCHEMA_VERSION so the worker readiness/version marker reflects installation of the new normalization behavior.

• Targeted regression coverage

  • Extended cancellation consistency E2E coverage to assert duroxide.executions.status resolves to cancellation (canceled/cancelled) rather than Failed.

UPDATE duroxide.executions e
SET status = 'Canceled'
FROM df.instances i
WHERE i.id = e.instance_id
  AND i.status = 'cancelled'
  AND e.status = 'Failed';