From 4aef48f3bab0b797516f8d503a94fac1590be134 Mon Sep 17 00:00:00 2001
From: Eyejoker <phj1081@gmail.com>
Date: Tue, 31 Mar 2026 07:45:50 +0900
Subject: [PATCH] fix: fallback to default arbiter_service_id in explicit
 channel leases

Explicit leases created by failover didn't include arbiter_service_id,
causing arbiter verdict to never be saved (pairedExecutionContext was
undefined). Now falls back to ARBITER_SERVICE_ID from config when the
stored lease has null arbiter_service_id.
---
 src/service-routing.ts | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/service-routing.ts b/src/service-routing.ts
index 2bac9fe..9231b33 100644
--- a/src/service-routing.ts
+++ b/src/service-routing.ts
@@ -45,7 +45,9 @@ function normalizeLeaseRow(
       : null,
     arbiter_service_id: row.arbiter_service_id
       ? normalizeServiceId(row.arbiter_service_id)
-      : null,
+      : isArbiterEnabled()
+        ? ARBITER_SERVICE_ID
+        : null,
     activated_at: row.activated_at,
     reason: row.reason,
     explicit,