@nanobpm/nano-workforce 0.201.1 → 0.201.3

package/resources/processes/convergence-loop.bpmn

@@ -80,6 +80,8 @@
           <nano:extend name="prNumber" type="integer" optional="true" />
           <nano:extend name="prUrl" type="string" optional="true" />
           <nano:extend name="abandonUrl" type="string" optional="true" />
+          <nano:extend name="agentSlaJobType" type="string" optional="true" />
+          <nano:extend name="agentSlaTimeout" type="string" optional="true" />
         </nano:shape>
         <nano:shape id="EscalationOut" name="Record escalation — result">
           <nano:extend name="escalationId" type="integer" optional="true" />
@@ -268,6 +270,7 @@
           <zeebe:input source="=&#34;blocked&#34;" target="status" />
           <zeebe:input source="=false" target="recordRound" />
           <zeebe:input source="=if (noProgressQuestion != null and trim(noProgressQuestion) != &#34;&#34;) then noProgressQuestion else &#34;Round &#34; + string(round) + &#34; reported the review comments were addressed, but the PR head did not advance (no commit was pushed), so another review round would loop on identical code. A human must decide how to proceed (reply to resume the loop).&#34;" target="question" />
+          <zeebe:input source="=null" target="agentSlaJobType" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>f_huskEscalate</bpmn:incoming>
@@ -307,6 +310,7 @@
           <zeebe:input source="=&#34;blocked&#34;" target="status" />
           <zeebe:input source="=false" target="recordRound" />
           <zeebe:input source="=&#34;No review arrived within the review-wait timeout (&#34; + reviewWaitTimeout + &#34;). A human must decide how to proceed (reply to resume the loop).&#34;" target="question" />
+          <zeebe:input source="=null" target="agentSlaJobType" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>f_reviewStalled</bpmn:incoming>
@@ -319,6 +323,9 @@
           <zeebe:property name="io.nanobpm.dataEnvelope.in" value="EscalationIn" />
           <zeebe:property name="io.nanobpm.dataEnvelope.out" value="EscalationOut" />
         </zeebe:properties>
+        <zeebe:ioMapping>
+          <zeebe:input source="=null" target="agentSlaJobType" />
+        </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>f_escalate</bpmn:incoming>
       <bpmn:outgoing>f_escGate</bpmn:outgoing>
@@ -344,6 +351,7 @@
           <zeebe:input source="=&#34;blocked&#34;" target="status" />
           <zeebe:input source="=false" target="recordRound" />
           <zeebe:input source="=&#34;Not converged after &#34; + string(maxRounds) + &#34; rounds. A human must decide how to proceed.&#34;" target="question" />
+          <zeebe:input source="=null" target="agentSlaJobType" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>f_guardMax</bpmn:incoming>
@@ -452,6 +460,7 @@
           <zeebe:input source="=&#34;blocked&#34;" target="status" />
           <zeebe:input source="=false" target="recordRound" />
           <zeebe:input source="=convergeBlockReason" target="question" />
+          <zeebe:input source="=null" target="agentSlaJobType" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>f_ackEscalate</bpmn:incoming>
@@ -491,6 +500,7 @@
           <zeebe:input source="=&#34;blocked&#34;" target="status" />
           <zeebe:input source="=false" target="recordRound" />
           <zeebe:input source="=scopeBlockReason" target="question" />
+          <zeebe:input source="=null" target="agentSlaJobType" />
           <zeebe:output source="=true" target="scopePending" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>

package/resources/processes/implement-cell.bpmn

@@ -11,6 +11,8 @@
           <nano:extend name="transcriptUrl" type="string" optional="true" />
           <nano:extend name="pr" type="string" optional="true" />
           <nano:extend name="deliveryVerified" type="boolean" optional="true" />
+          <nano:extend name="agentSlaJobType" type="string" optional="true" />
+          <nano:extend name="agentSlaTimeout" type="string" optional="true" />
         </nano:shape>
       </nano:shapes>
     </bpmn:extensionElements>
@@ -91,6 +93,7 @@
           <zeebe:property name="io.nanobpm.dataEnvelope.in" value="RecordEscalationIn" />
         </zeebe:properties>
         <zeebe:ioMapping>
+          <zeebe:input source="=null" target="agentSlaJobType" />
           <zeebe:output source="=question" target="question" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>
@@ -104,7 +107,7 @@
           <zeebe:property name="io.nanobpm.dataEnvelope.in" value="RecordEscalationIn" />
         </zeebe:properties>
         <zeebe:ioMapping>
-          <zeebe:input source="=&#34;The implementation agent exceeded its time budget (SLA &#34; + agentSlaTimeout + &#34;) without completing — it is hung or looping. Check its progress or intervene, then answer to resume (the run continues on its deterministic feat/&#60;task.id&#62; branch), or abandon it.&#34;" target="question" />
+          <zeebe:input source="=&#34;senior:feature&#34;" target="agentSlaJobType" />
           <zeebe:output source="=question" target="question" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>

package/resources/processes/merge-cell.bpmn

@@ -36,6 +36,9 @@
         <zeebe:properties>
           <zeebe:property name="io.nanobpm.dataEnvelope.in" value="RecordTrialMergeIn" />
         </zeebe:properties>
+        <zeebe:ioMapping>
+          <zeebe:input source="=null" target="agentSlaJobType" />
+        </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>mc_toRecord</bpmn:incoming>
       <bpmn:outgoing>mc_toGwTrial</bpmn:outgoing>
@@ -48,7 +51,7 @@
         </zeebe:properties>
         <zeebe:ioMapping>
           <zeebe:input source="=&#34;suite-failed&#34;" target="result" />
-          <zeebe:input source="=&#34;The trial-merge agent exceeded its time budget (SLA &#34; + agentSlaTimeout + &#34;) without returning a machine-readable result — it is hung or looping. Acknowledge to record the timeout and decide whether to rerun the trial merge.&#34;" target="summary" />
+          <zeebe:input source="=&#34;senior:trial-merge&#34;" target="agentSlaJobType" />
           <zeebe:input source="=null" target="conflicts" />
           <zeebe:input source="=null" target="failing" />
         </zeebe:ioMapping>

package/resources/processes/merge-loop.bpmn

@@ -110,6 +110,7 @@
         <zeebe:ioMapping>
           <zeebe:output source="=null" target="status" />
           <zeebe:output source="=null" target="ciBlockedReconciled" />
+          <zeebe:output source="=null" target="agentSlaJobType" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>f_m_deps</bpmn:incoming>
@@ -302,6 +303,7 @@
         <zeebe:ioMapping>
           <zeebe:input source="=&#34;blocked&#34;" target="status" />
           <zeebe:input source="=&#34;This PR was reported as added to the merge queue but did not land within the merge-queue landing timeout (&#34; + landedWaitTimeout + &#34;). The repository may not have actually enqueued it — e.g. a Mergify repo where a plain merge does not queue and an explicit `@Mergifyio queue` is required, or a native merge queue that dropped it silently. Add the PR to the merge queue (or merge it) manually, then reply to retry.&#34;" target="question" />
+          <zeebe:input source="=null" target="agentSlaJobType" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>f_m_landedStalled</bpmn:incoming>
@@ -447,6 +449,7 @@
         <bpmn:extensionElements>
           <zeebe:ioMapping>
             <zeebe:output source="=&#34;recheck&#34;" target="ciOutcome" />
+            <zeebe:output source="=null" target="agentSlaJobType" />
           </zeebe:ioMapping>
         </bpmn:extensionElements>
         <bpmn:incoming>f_cib_armed</bpmn:incoming>
@@ -463,6 +466,7 @@
         <bpmn:extensionElements>
           <zeebe:ioMapping>
             <zeebe:output source="=&#34;escalate&#34;" target="ciOutcome" />
+            <zeebe:output source="=null" target="agentSlaJobType" />
           </zeebe:ioMapping>
         </bpmn:extensionElements>
         <bpmn:incoming>f_cib_esc</bpmn:incoming>
@@ -471,6 +475,7 @@
         <bpmn:extensionElements>
           <zeebe:ioMapping>
             <zeebe:output source="=&#34;escalate&#34;" target="ciOutcome" />
+            <zeebe:output source="=&#34;senior:fix-ci&#34;" target="agentSlaJobType" />
           </zeebe:ioMapping>
         </bpmn:extensionElements>
         <bpmn:incoming>f_ci_sla</bpmn:incoming>
@@ -578,6 +583,7 @@
         <bpmn:extensionElements>
           <zeebe:ioMapping>
             <zeebe:output source="=&#34;escalate-attempt&#34;" target="rebaseOutcome" />
+            <zeebe:output source="=null" target="agentSlaJobType" />
           </zeebe:ioMapping>
         </bpmn:extensionElements>
         <bpmn:incoming>f_reb_blocked</bpmn:incoming>
@@ -586,6 +592,7 @@
         <bpmn:extensionElements>
           <zeebe:ioMapping>
             <zeebe:output source="=&#34;escalate-conflict&#34;" target="rebaseOutcome" />
+            <zeebe:output source="=&#34;senior:rebase&#34;" target="agentSlaJobType" />
           </zeebe:ioMapping>
         </bpmn:extensionElements>
         <bpmn:incoming>f_reb_sla</bpmn:incoming>

package/resources/processes/plan-fanout.bpmn

@@ -74,6 +74,8 @@
           <nano:extend name="conflicts" type="string" list="true" optional="true" />
           <nano:extend name="failing" type="string" list="true" optional="true" />
           <nano:extend name="summary" type="string" optional="true" />
+          <nano:extend name="agentSlaJobType" type="string" optional="true" />
+          <nano:extend name="agentSlaTimeout" type="string" optional="true" />
         </nano:shape>
         <nano:shape id="RecordPlanReviewIn" name="Record plan review — input">
           <nano:extend name="planKey" type="string" />
@@ -563,6 +565,9 @@
         <zeebe:properties>
           <zeebe:property name="io.nanobpm.dataEnvelope.in" value="RecordTrialMergeIn" />
         </zeebe:properties>
+        <zeebe:ioMapping>
+          <zeebe:input source="=null" target="agentSlaJobType" />
+        </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>f_toRecordTrialMerge</bpmn:incoming>
       <bpmn:outgoing>f_toGwTrial</bpmn:outgoing>

package/resources/processes/retro.bpmn

@@ -25,6 +25,8 @@
           <nano:extend name="hasDeviations" type="boolean" optional="true" />
           <nano:extend name="agentSlaElapsed" type="boolean" optional="true" />
           <nano:extend name="preserveConformance" type="boolean" optional="true" />
+          <nano:extend name="agentSlaJobType" type="string" optional="true" />
+          <nano:extend name="agentSlaTimeout" type="string" optional="true" />
           <nano:extend name="summary" type="string" optional="true" />
         </nano:shape>
       </nano:shapes>
@@ -71,6 +73,7 @@
         <zeebe:ioMapping>
           <zeebe:input source="=false" target="agentSlaElapsed" />
           <zeebe:input source="=false" target="preserveConformance" />
+          <zeebe:input source="=null" target="agentSlaJobType" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>f_toRecordConformance</bpmn:incoming>
@@ -85,7 +88,7 @@
         <zeebe:ioMapping>
           <zeebe:input source="=true" target="agentSlaElapsed" />
           <zeebe:input source="=false" target="preserveConformance" />
-          <zeebe:input source="=&#34;The spec-conformance agent exceeded its time budget (SLA &#34; + agentSlaTimeout + &#34;) without returning a verdict — it is hung or looping. Acknowledge to record the timeout and continue to the retrospective synthesis.&#34;" target="summary" />
+          <zeebe:input source="=&#34;senior:conformance&#34;" target="agentSlaJobType" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>f_conformanceSla</bpmn:incoming>
@@ -100,7 +103,7 @@
         <zeebe:ioMapping>
           <zeebe:input source="=true" target="agentSlaElapsed" />
           <zeebe:input source="=true" target="preserveConformance" />
-          <zeebe:input source="=&#34;The retrospective-synthesis agent exceeded its time budget (SLA &#34; + agentSlaTimeout + &#34;) without completing — it is hung or looping. Acknowledge to record the timeout and continue.&#34;" target="summary" />
+          <zeebe:input source="=&#34;senior:retro&#34;" target="agentSlaJobType" />
         </zeebe:ioMapping>
       </bpmn:extensionElements>
       <bpmn:incoming>f_synthesizeSla</bpmn:incoming>

package/test/derivation-parity/flows.ts

@@ -137,13 +137,15 @@ export const retroFlow: DeclarativeFlow = defineFlow(
       jobType: "pr.conformance-record",
       // The golden pins both SLA-mode control flags to `=false` on this NORMAL-path recorder
       // (round-7 review, PR #864): the flags share the external conformance agent's result
-      // namespace, so a hoisted agent output must never select the SLA/preserve branch. The port
-      // reproduces those pins so the parity diagnostic's only residual is the class-3 marker +
-      // SLA boundaries.
+      // namespace, so a hoisted agent output must never select the SLA/preserve branch. It also
+      // pins `agentSlaJobType` to `=null` (PR #881 review r4214170285) so a hoisted agent-supplied
+      // marker can never select the SLA escalation builder. The port reproduces those pins so the
+      // parity diagnostic's only residual is the class-3 marker + SLA boundaries.
       io: {
         input: [
           { source: "=false", target: "agentSlaElapsed" },
           { source: "=false", target: "preserveConformance" },
+          { source: "=null", target: "agentSlaJobType" },
         ],
       },
     });

package/workers/conformance-record/worker.ts

@@ -9,6 +9,7 @@
 // reads `status`/`pr`/`summary` through), and exposes the raw transcript under the
 // `io.nanobpm.agentResult` envelope's `.output`.
 import type { AppJobHandler } from "@nanobpm/urban";
+import { agentSlaEscalationQuestion } from "../../app/agentSlaEscalation.ts";
 import { markConformanceSynthesisSla, recordConformance } from "../../app/conformance.ts";
 import type { WorkerInputs } from "../../nano-generated/worker-io.d.ts";
 
@@ -50,7 +51,20 @@ const handler: AppJobHandler<In> = async (job, app) => {
 
   const commentUrl = asStr(job.variables.commentUrl);
   const status = asStatus(job.variables.status, commentUrl !== null);
-  const summary = asStr(job.variables.summary);
+  // Agent-task SLA path (issue #879): the conformance/synthesize agent's interrupting timer boundary
+  // routed here with `agentSlaJobType` set, so there is no agent-produced summary — build the accurate
+  // never-started-vs-hung reason (named job type + wait duration) from the durable activation ledger,
+  // replacing the old blanket "hung or looping" wording. Unset on the normal path, where the agent's
+  // own hoisted `summary` is used.
+  const slaJobType = asStr(job.variables.agentSlaJobType);
+  const summary = slaJobType
+    ? await agentSlaEscalationQuestion(app.data, {
+        processInstanceKey: job.processInstanceKey != null ? String(job.processInstanceKey) : "",
+        jobType: slaJobType,
+        sla: asStr(job.variables.agentSlaTimeout) ?? "PT2H",
+        recovery: "Acknowledge to record the timeout and continue the retrospective.",
+      })
+    : asStr(job.variables.summary);
 
   // biome-ignore lint/plugin: runtime/framework contract boundary for external data shape
   const env = (job.variables as Record<string, unknown>)[AGENT_RESULT_KEY] as { output?: unknown } | undefined;

package/workers/persist-escalation/worker.ts

@@ -18,6 +18,7 @@
 // a token on a durable wait that has no escalation for a human to answer.
 import type { AppJobHandler } from "@nanobpm/urban";
 import { abandonTokenFromUrl } from "../../app/abandon.ts";
+import { agentSlaEscalationQuestion } from "../../app/agentSlaEscalation.ts";
 import { classifyEscalation } from "../../app/escalationTaxonomy.ts";
 import { ensurePr, parsePr } from "../../app/service.ts";
 import type { WorkerInputs } from "../../nano-generated/worker-io.d.ts";
@@ -60,16 +61,34 @@ const handler: AppJobHandler<In> = async (job, app) => {
   const status = rawStatus ?? "needs_input";
   const transcript = transcriptOf(job.variables);
   const worker = workerOf(job.variables);
+  // Agent-task SLA path (issue #879): the merge-loop's fix-ci / rebase interrupting SLA timer boundary
+  // routed here with `agentSlaJobType` set on the SLA end event. Rather than the old blanket "exceeded
+  // its time budget … check its progress" FEEL `else` (which misdiagnoses a never-activated,
+  // queue-starved job as hung), build the accurate never-started-vs-hung question — naming the job type
+  // and how long it waited — from the durable activation ledger. `agentSlaJobType` is set ONLY on the
+  // SLA arm, so it authoritatively selects this path; every other escalation (agent verdict, merge
+  // blocked, rebase conflict) leaves it unset and keeps its FEEL-built `question`. It is CLEARED on
+  // every return below so a later non-SLA escalation in the same looping instance can never inherit a
+  // stale value.
+  const slaJobType = nonBlank(job.variables.agentSlaJobType);
+  const slaQuestion = slaJobType
+    ? await agentSlaEscalationQuestion(app.data, {
+        processInstanceKey: job.processInstanceKey != null ? String(job.processInstanceKey) : "",
+        jobType: slaJobType,
+        sla: nonBlank(job.variables.agentSlaTimeout) ?? "PT2H",
+        recovery: "Reply to retry, or investigate why no capacity was available.",
+      })
+    : undefined;
   // Classify this job through the single canonical taxonomy (ADR 0002 §1). Only a
   // decision-required escalation opens an answerable escalation row. A blank question (or any
   // non-human-blocking status that reached here defensively) is a NON-escalation: open nothing
   // and report `escalated:false` — never FABRICATE a question and never throw. The `gw-status`
   // gateway already routes blank-question rounds back into the durable review wait, so this is
   // defence-in-depth, not the primary guard.
-  const question = nonBlank(job.variables.question);
+  const question = slaQuestion ?? nonBlank(job.variables.question);
   const disposition = classifyEscalation({ kind: "review-round", status: rawStatus, question });
   if (disposition !== "decision-required" || question === undefined) {
-    return { escalationId: null, escalated: false };
+    return { escalationId: null, escalated: false, agentSlaJobType: null };
   }
   const kind = status === "needs_input" ? "question" : "blocker";
   const now = new Date().toISOString();
@@ -142,7 +161,7 @@ const handler: AppJobHandler<In> = async (job, app) => {
     });
   });
 
-  return { escalationId: Number(escalationId), escalated: true, question };
+  return { escalationId: Number(escalationId), escalated: true, question, agentSlaJobType: null };
 };
 
 export default handler;

package/workers/record-feature-escalation/worker.ts

@@ -23,6 +23,7 @@
 // variables through the user-task query, so the process variable must be persisted while it is still in
 // scope on this job.
 import type { AppJobHandler } from "@nanobpm/urban";
+import { agentSlaEscalationQuestion } from "../../app/agentSlaEscalation.ts";
 import { classifyEscalation } from "../../app/escalationTaxonomy.ts";
 import { featureRuns, recordFeatureEscalation } from "../../app/feature.ts";
 import { implementEscalationQuestion, NO_RESULT_QUESTION } from "../../app/implementEscalationReason.ts";
@@ -59,6 +60,13 @@ const handler: AppJobHandler<In, Out> = async (job, app) => {
   // blank-question case.
   const agentEscalated = classifyEscalation({ kind: "task", status: job.variables.status, question: rawQuestion }) ===
     "decision-required";
+  // Agent-task SLA path (issue #879): the interrupting SLA timer boundary (not the agent) routed here,
+  // so there is NO agent result to classify — the job either never started (queue starvation) or ran but
+  // overran its budget. `agentSlaJobType` is set ONLY on the SLA-boundary arm (`record-escalation-sla`),
+  // so its presence authoritatively selects the SLA builder, which reads the durable activation ledger
+  // to distinguish never-started from started-but-hung and names the job type + how long it waited —
+  // never the old blanket "hung or looping" misdiagnosis of a queue-starved job.
+  const slaJobType = str(job.variables.agentSlaJobType);
   // Build the escalation question through the single canonical builder (issue #865), ALWAYS — including
   // when the agent raised its own answerable question. Passing the agent's `question` lets the builder
   // lead with it AND fold in the agent's `summary` + transcript as supporting context (#865 review —
@@ -68,18 +76,26 @@ const handler: AppJobHandler<In, Out> = async (job, app) => {
   // such as `completed`) and from a reported non-completion status — never the false "no status was
   // reported" diagnosis for a reported `escalated`/`failed` (#865 review). The reason can never drift
   // from the reconcile step because both read the same canonical builder.
-  const question = implementEscalationQuestion({
-    status: job.variables.status,
-    question: rawQuestion,
-    summary: job.variables.summary,
-    transcriptUrl: job.variables.transcriptUrl,
-    // Delivery EVIDENCE (#865 review): the preserved PR (an `escalated`/`failed` with a blank question
-    // retains it — never claim "opened no pull request") and whether the reconcile step's GitHub lookup
-    // actually CONFIRMED the delivery state (only then may the reason say "none was found"). Both are
-    // process variables the upstream `reconcile-implement` step emits into scope.
-    pr: job.variables.pr,
-    deliveryVerified: job.variables.deliveryVerified,
-  });
+  const question = slaJobType
+    ? await agentSlaEscalationQuestion(app.data, {
+        processInstanceKey: job.processInstanceKey != null ? String(job.processInstanceKey) : "",
+        jobType: slaJobType,
+        sla: str(job.variables.agentSlaTimeout) ?? "PT2H",
+        recovery:
+          "Answer to resume (the run continues on its deterministic feat/<task.id> branch), or abandon it.",
+      })
+    : implementEscalationQuestion({
+        status: job.variables.status,
+        question: rawQuestion,
+        summary: job.variables.summary,
+        transcriptUrl: job.variables.transcriptUrl,
+        // Delivery EVIDENCE (#865 review): the preserved PR (an `escalated`/`failed` with a blank
+        // question retains it — never claim "opened no pull request") and whether the reconcile step's
+        // GitHub lookup actually CONFIRMED the delivery state (only then may the reason say "none was
+        // found"). Both are process variables the upstream `reconcile-implement` step emits into scope.
+        pr: job.variables.pr,
+        deliveryVerified: job.variables.deliveryVerified,
+      });
 
   // Append to the canonical `feature_escalations` audit log (the surviving table `pollUserTasks` reads),
   // keyed by `subjectKey` — the feature run's `feature_key`, or the epic's `plan_key` for a wave slice.

package/workers/record-trial-merge/worker.ts

@@ -2,6 +2,7 @@
 // Only `suite-failed` escalates. `clean` and textual `merge-conflict` proceed; D2/D6 own textual
 // conflict ordering, while D3 owns clean-merge/combined-suite-red semantic conflicts.
 import type { AppJobHandler } from "@nanobpm/urban";
+import { agentSlaEscalationQuestion } from "../../app/agentSlaEscalation.ts";
 import {
   recordTrialMergeAudit,
   type TrialMergeResult,
@@ -46,7 +47,21 @@ const handler: AppJobHandler<In, Out> = async (job, app) => {
   const planKey = job.variables.planKey;
   const wave = waveNo(job.variables.trialMergeWave ?? job.variables.currentWave);
   const result = parseResult(job.variables.result);
-  const summary = str(job.variables.summary) ??
+  // Agent-task SLA path (issue #879): the interrupting SLA timer boundary routed here with
+  // `agentSlaJobType` set, so there is no agent result — build the accurate never-started-vs-hung
+  // summary (named job type + wait duration) from the durable activation ledger instead of the old
+  // blanket "hung or looping" wording. On every other caller (a real agent result, the plan-fanout D3
+  // gate) `agentSlaJobType` is unset and the summary is derived from the agent's own `summary`/result.
+  const slaJobType = str(job.variables.agentSlaJobType);
+  const slaSummary = slaJobType
+    ? await agentSlaEscalationQuestion(app.data, {
+        processInstanceKey: job.processInstanceKey != null ? String(job.processInstanceKey) : "",
+        jobType: slaJobType,
+        sla: str(job.variables.agentSlaTimeout) ?? "PT2H",
+        recovery: "Acknowledge to record the timeout, then decide whether to rerun the trial merge.",
+      })
+    : undefined;
+  const summary = slaSummary ?? str(job.variables.summary) ??
     (result === "suite-failed" ? "Trial merge suite failed or returned no machine-readable result" : result);
   const legacyJobKey = Reflect.get(job, "key");
   const jobKey = job.jobKey ?? (legacyJobKey == null ? null : String(legacyJobKey));