Cancellation terminal events could be persisted with event_data.instance_id = "" and event_data.execution_id = 0, even when the owning duroxide.history row had correct identifiers. This broke payload-only consumers that correlate events without joining back to history keys.

• Runtime payload normalization at history write boundary

  • Added a BGW-installed trigger function (duroxide._normalize_history_event_payload_identifiers) and BEFORE INSERT trigger on duroxide.history.
  • On insert, if event_data is valid JSON object:
    • fills instance_id when missing/empty from NEW.instance_id
    • fills execution_id when missing/non-numeric/zero from NEW.execution_id
  • Leaves non-JSON or non-object payloads unchanged.

• Deterministic guard installation during worker initialization

  • Worker startup now ensures the normalization function/trigger exist before runtime processing continues.
  • Trigger creation is idempotent (DROP TRIGGER IF EXISTS + CREATE TRIGGER).

• Regression coverage for cancellation path

  • Added tests/e2e/sql/23_cancel_history_payload_ids.sql to verify cancelled-instance history payload identifiers match row identifiers for events carrying those fields.

IF COALESCE(v_data->>'instance_id', '') = '' THEN
  v_data := JSONB_SET(v_data, '{instance_id}', TO_JSONB(NEW.instance_id), true);
END IF;

IF v_execution_text IS NULL OR v_execution_text !~ '^[0-9]+$' OR v_execution_text::BIGINT = 0 THEN
  v_data := JSONB_SET(v_data, '{execution_id}', TO_JSONB(NEW.execution_id), true);
END IF;