Observe merging through a durable job

Context

Long merges need a monitored outcome even when workflow execution is lost.

Decision

A durable job publishes its step definitions, runs one merge task and records failure; watched steps are settled from the transaction outcome and reconciliation handles lost executions.

Alternatives Considered

Use only a queue worker. The former pattern lacked the durable step reporting and lost-execution settlement required here.

Commit progress between merge stages. Separate business commits would violate atomic merging.

Consequences

A new execution after a failed attempt creates another merge and job. Cross-workspace monitoring reads job roots without workspace row policies; each workspace job also carries its customer.