From a49e9562bd029c3c59c5fd604ae690a9e5113b56 Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 10 May 2026 13:42:03 +0000 Subject: [PATCH] Workers: cover logging gaps so each one is visible at the default level Three workers were silent at the default Logs-drawer level: **attachment-expiry-worker** had no `createLogger` at all - the only log path was the legacy `post({type:'log'})` channel inside the worker entry, which only fires on setup-session failure and lease loss. The cycle itself had zero logging, so an attachment-expiry problem in production left no breadcrumb. Now the loop logs at .info on lease acquisition, on each non-zero expire batch ("expired N attachment row(s) older than D days"), and on errors; .debug on polling and empty-queue ticks so an idle worker isn't noisy. **samskara-worker** logged at .debug for events the other agent workers log at .info ("picked up thread X" / "finished thread X"), and used .trace for some routine state. With the drawer at the default level, samskara was invisible - you saw every other worker fire but not this one. Bumped four lifecycle lines to .info: - assimilate: claimed substrate (thread ) - assimilate: saved substrate - pair-relate: selected pair <> (cosine X.XXX) - pair-relate: associated <> (: