Log lock-release lifecycle in executor_step_status and distributed_lock

Adds two INFO-level log lines so the next occurrence of the self-race
described in issue #5026 can be triaged from logs alone. StatusFile.write_status
now announces the terminal-status release with path, worker, and reason; and
DistributedLease.release logs at INFO when it actually deletes the lock object
(promoted from the prior DEBUG). Together these disambiguate a self-release
from an external delete or a stale-lease takeover, which the existing
LeaseLostError message at distributed_lock.py:152 cannot distinguish.

Refs #5026

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: yonromai

lib/marin/src/marin/execution/executor_step_status.py

@@ -120,6 +120,12 @@ def write_status(self, status: str) -> None:
             f.write(status)
 
         if status != STATUS_RUNNING:
+            logger.info(
+                "Releasing lock path=%s worker=%s reason=terminal_status:%s",
+                self._lock_path,
+                self.worker_id,
+                status,
+            )
             self.release_lock()
         logger.debug("[%s] Wrote status %s to %s", self.worker_id, status, self.path)
 

lib/rigging/src/rigging/distributed_lock.py

@@ -161,7 +161,7 @@ def release(self) -> None:
             _, lock_data = self._read_with_generation()
             if lock_data and lock_data.worker_id == self.worker_id:
                 self._delete()
-                logger.debug("[%s] Released lock %s", self.worker_id, self.lock_path)
+                logger.info("Released lock path=%s worker=%s", self.lock_path, self.worker_id)
         except FileNotFoundError:
             pass