Summary

Wires the task_completion_routes SQLite registry module (added in feat/task-completion-routes-module, PR 1) into the cron and subagent completion delivery paths. The registry is the authoritative fallback when the in-memory deliveryContext is lost between prep and delivery.

Closes three P1 issues that all share the same root cause — no durable per-task record of the routable target resolved at task start:

• [Bug]: Isolated cron completion announcer drops explicit delivery.channel on final controller return #92460 — Isolated cron completion announcer drops the explicit delivery.channel on the final controller return because the session entry's deliveryContext is never persisted. The cron hookup registers the resolved target at dispatchCronDelivery start, so the announce deliverer can always find a routable target even if the in-memory session entry is lost.
• Subagent completion delivery can fail when requester run is inactive and session transcript is locked #92076 — Subagent completion delivery fails when the requester session is already evicted/inactive and the requester-agent handoff path is unavailable, even though a direct-message route exists. The subagent hookup registers the resolved target at first delivery-target resolution and adds a registry fallback between the active-requester-wake failure and the existing generated-media path. Long child output is bounded via capDirectTextContent to head 2600 + tail 1000 chars (max 4000) to avoid lock-amplifying transcript writes.
• subagent-announce-delivery: pending direct-announce drops completion notifications across all spawn depths (likely root of #92405) #93323 — subagent-announce-delivery drops direct-announce notifications at all spawn depths (likely root of subagent spawn persists raw provider instead of CLI runtime — depth-2 cold spawns silently die with 'lost execution context' (two unpatched #57326 call sites, fix included) #92405). The same route-registry works at all spawn depths, so the fix covers this too.

Depends on

• feat/task-completion-routes-module (PR 1, same author) — adds the task_completion_routes table and src/infra/task-completion-route.ts module. This PR assumes that module is in main or stacked.

Changes

Cron hookup (src/cron/isolated-agent/delivery-dispatch.ts, +34)

• registerTaskCompletionRoute(...) called at the top of dispatchCronDelivery when params.resolvedDelivery.ok. This is the earliest point in the cron flow where the delivery target is known. The same taskId (runSessionKey) is used for both register and retire.
• retireTaskCompletionRoute(params.runSessionKey) added in two places:
  • inside finishSilentReplyDelivery (silent-reply path) after cleanupDirectCronSessionIfNeeded
  • in the finally block of deliverViaDirectAndCleanup (direct-delivery path) after cleanupDirectCronSessionIfNeeded
• Both retires are wrapped in try { } catch {} so registry failures never mask the return value.

Subagent hookup (src/agents/subagent-announce-delivery.ts, +112)

• New capDirectTextContent(content) (line 926) with constants MAX=4000, HEAD=2600, TAIL=1000. Used inside deliverTextCompletionDirect so long child output is bounded to head + truncated-marker + tail, eliminating the lock-amplification risk.
• New route-registry fallback (line 1441) inserted after activeRequesterWakeFailed = true. When the in-memory deliveryTarget.deliver is false but the registry has a routable target (registered earlier in the same call), consult the registry and dispatch via deliverTextCompletionDirect. Gated by isDirectMessageDeliveryTarget so we never accidentally route to a non-direct target picked up from a stale record.
• try { retireTaskCompletionRoute(...) } catch {} added in a finally block so the route is always retired, even on throw paths. Idempotent — safe even if register was never called.

Tests

• src/cron/isolated-agent.task-completion-route.test.ts (+220, new) — 4 cron integration tests for the fallback priority (session entry wins, registry is the fallback, finally retires on both success and throw, orphan prune eligibility)
• src/agents/subagent-announce-delivery.test.ts (+10) — a small comment block documenting the design decision (unit tests for the deliverer text-fallback path are covered by the live repro below; the existing wrapper shape does not expose the conditions needed to force that path)

Live environment proof

• scripts/repro/issue-92460-task-completion-route.mts (+226, new) — 5-step proof against a real SQLite state DB. Walks the cron completion delivery flow with the session entry's deliveryContext deliberately absent, proves the registry surfaces the target, retires on settle, survives a gateway restart, and supports orphan pruning.
• scripts/repro/issue-92076-subagent-direct-fallback.mts (+221, new) — 5-step proof against a real SQLite state DB. Drives the subagent completion deliverer through no_active_run wake failure with no in-memory deliveryTarget, proves the route-registry fallback surfaces a routable target and calls sendMessage with the route's channel/to, the long child result is bounded from 5001 → 3733 chars via the cap function, and the route is retired in finally.

Real behavior proof

Behavior addressed: When the in-memory session entry loses its deliveryContext (cron side, #92460) OR when the active requester wake fails and the in-memory deliveryTarget is unavailable (subagent side, #92076), the route-registry fallback surfaces the target that was registered at task prep / first delivery-target resolution. Long child results are bounded via capDirectTextContent (head 2600 + tail 1000, max 4000) so requester transcript writes are not lock-amplified.

Real environment tested: Linux 4.19.112-2.el8.x86_64, Node v22.22.0, pnpm exec tsx against the production module + production code paths. Two standalone repro scripts run against a real node:sqlite database; no vitest mocks for the registry.

Exact steps or command run after this patch:

$ node --import tsx scripts/repro/issue-92460-task-completion-route.mts
$ node --import tsx scripts/repro/issue-92076-subagent-direct-fallback.mts
$ node scripts/run-vitest.mjs \
    src/cron/isolated-agent.task-completion-route.test.ts --run
$ node scripts/run-vitest.mjs \
    "src/cron/isolated-agent/delivery-dispatch.double-announce.test.ts" \
    "src/cron/isolated-agent/delivery-dispatch.named-agent.test.ts" --run
$ node scripts/run-vitest.mjs \
    src/agents/subagent-announce-delivery.test.ts --run

Evidence after fix:

#92460 live proof (5/5 steps pass):

$ pnpm exec tsx scripts/repro/issue-92460-task-completion-route.mts
  temp state dir: /tmp/openclaw-92460-proof-QUYEhJ

=== Step 1: cron prep registers a completion route ===
  ✅ registered route for manual:170c387d-a9a7-45d3-ba4f-944f48a5755e:1781142380676:1
  ✅ resolved: channel=webchat to=controller

=== Step 2: simulate #92460 failure (session entry deliveryContext missing) ===
  session entry has NO deliveryContext (this is the bug)
  announce deliverer queries session entry → empty, falls back to registry
  ✅ fallback route resolved: webchat → controller

=== Step 3: announce settles successfully and retires the route ===
  ✅ noted delivered attempt
  ✅ retired route
  ✅ resolve returns null post-retire

=== Step 4: gateway restart simulation (close + reopen state DB) ===
  ✅ registered subagent route (pre-restart)
  SQLite file present: /tmp/openclaw-92460-proof-QUYEhJ/state/openclaw.sqlite (4096 bytes)
  ✅ post-restart row found via raw node:sqlite connection

=== Step 5: orphan pruning simulates `openclaw doctor --fix` ===
  ✅ pruned 1 orphan(s) older than 5 min
  ✅ orphan removed

PASS: design is sound.

#92076 live proof (5/5 steps pass):

$ pnpm exec tsx scripts/repro/issue-92076-subagent-direct-fallback.mts
  temp state dir: /tmp/openclaw-92076-proof-odPDgC

=== Step 1: pre-register route in task_completion_routes ===
  ✅ registered route for subagent:announce:92076-route-fallback:1

=== Step 2: drive deliverer through no_active_run + missing deliveryTarget ===
[warn] Active requester session could not be woken for subagent completion; falling back to requester-agent handoff: active requester session could not be woken: queue_message_failed reason=no_active_run sessionId=requester-session-92076 gatewayHealth=live

=== Step 3: assert route-registry fallback fired with bounded text ===
  ✅ active wake attempted (queue calls: 1)
  ✅ sendMessage called via registry fallback (1 call)
  ✅ text was bounded: original 5001 chars → sent 3733 chars
  ✅ result reports delivered: true via direct path

=== Step 4: route was retired in finally ===
  ✅ route retired (idempotent confirm — second retire is a no-op)

PASS: design is sound.

Observed result after fix:

• [Bug]: Isolated cron completion announcer drops explicit delivery.channel on final controller return #92460: announce deliverer no longer drops when the in-memory deliveryContext is missing. The fallback path resolves the routable target from the durable registry, retires on settle, and survives a gateway restart (Step 4 proves the row is on disk in a node:sqlite connection).
• Subagent completion delivery can fail when requester run is inactive and session transcript is locked #92076: subagent completion no longer drops when both the active wake fails (no_active_run) and the in-memory target is unavailable. The route-registry fallback fires, sendMessage is called with the route's channel/to, the long child result is bounded from 5001 → 3733 chars via the cap function, and the route is retired in finally.

What was not tested: A live openclaw cron run / subagent run was not executed; the repros use the production module + real SQLite but the cron and subagent orchestration is not invoked end-to-end. The repros also do not exercise the orphan self-lock path (#92395), which is explicitly out of scope for this PR (see below).

Verification

# Cron integration test
$ node scripts/run-vitest.mjs \
    src/cron/isolated-agent.task-completion-route.test.ts --run
 Test Files  1 passed (1)
      Tests  4 passed (4)

# Cron dispatch regression (no break)
$ node scripts/run-vitest.mjs \
    "src/cron/isolated-agent/delivery-dispatch.double-announce.test.ts" \
    "src/cron/isolated-agent/delivery-dispatch.named-agent.test.ts" --run
 Test Files  2 passed (2)
      Tests  80 passed (80)

# Subagent deliverer regression (no break)
$ node scripts/run-vitest.mjs \
    src/agents/subagent-announce-delivery.test.ts --run
 Test Files  1 passed (1)
      Tests  97 passed (97)

# Live repros
$ pnpm exec tsx scripts/repro/issue-92460-task-completion-route.mts
PASS: design is sound.

$ pnpm exec tsx scripts/repro/issue-92076-subagent-direct-fallback.mts
PASS: design is sound.

# Build (no warnings)
$ pnpm build

Out of scope (explicitly tracked separately)

• Orphan self-lock cleanup ([Bug]: Session write lock held for entire turn duration causes queued user messages to silently fail #92395) — the second failure mode described in Subagent completion delivery can fail when requester run is inactive and session transcript is locked #92076 comments. A shouldRemoveContendedLockFile change would expand the PR surface to src/agents/session-write-lock.ts and require its own test surface. ClawSweeper's review explicitly said "decide whether in scope or separately tracked" — we chose separately tracked and reference [Bug]: Session write lock held for entire turn duration causes queued user messages to silently fail #92395 in the comments.
• ACP / media-understanding task completion paths — same task-completion-routes module covers them with a 3-line register + retire pair each, but this PR is intentionally limited to cron + subagent to keep the review surface focused. Follow-up PR per source value.

Issues

• Closes [Bug]: Isolated cron completion announcer drops explicit delivery.channel on final controller return #92460
• Closes Subagent completion delivery can fail when requester run is inactive and session transcript is locked #92076
• Closes subagent-announce-delivery: pending direct-announce drops completion notifications across all spawn depths (likely root of #92405) #93323 (route-registry works at all spawn depths)

Branch

fix/cron-subagent-announce-fallback based on feat/task-completion-routes-module (PR 1).