Harden worker polling and dashboard writes

apps/worker/src/index.ts

@@ -102,9 +102,9 @@ async function main(): Promise<void> {
   );
   providerRegistry = await buildProviderRegistry(systemMessages);
   console.log(`VoidBot worker polling every ${config.workerPollIntervalMs}ms.`);
-  await processPendingJobs();
+  await pollPendingJobs();
   setInterval(() => {
-    void processPendingJobs();
+    void pollPendingJobs();
   }, config.workerPollIntervalMs);
 }
 
@@ -131,6 +131,16 @@ async function processPendingJobs(): Promise<void> {
   }
 }
 
+async function pollPendingJobs(): Promise<void> {
+  try {
+    await processPendingJobs();
+  } catch (error) {
+    const message =
+      error instanceof Error ? `${error.name}: ${error.message}` : "Unexpected worker poll failure.";
+    console.error(`Worker poll failed: ${message}`);
+  }
+}
+
 async function buildProviderRegistry(systemMessagesCatalog: SystemMessageCatalog): Promise<ProviderRegistry> {
   return new ProviderRegistry([
     new OwnerCodexProvider({

scripts/voidbot-operations-dashboard-lib.ps1

@@ -112,6 +112,24 @@ function ConvertTo-VoidBotDashboardFileUri {
   return ([System.Uri]::new($Path)).AbsoluteUri
 }
 
+function Write-VoidBotDashboardUtf8File {
+  param(
+    [Parameter(Mandatory = $true)]
+    [string] $Path,
+    [Parameter(Mandatory = $true)]
+    [AllowEmptyString()]
+    [string] $Content
+  )
+
+  $directory = Split-Path -Parent $Path
+  if (-not [string]::IsNullOrWhiteSpace($directory)) {
+    New-Item -ItemType Directory -Force -Path $directory | Out-Null
+  }
+
+  $encoding = [System.Text.UTF8Encoding]::new($false)
+  [System.IO.File]::WriteAllText($Path, $Content, $encoding)
+}
+
 function New-VoidBotDashboardFileLink {
   param(
     [Parameter(Mandatory = $true)]
@@ -1452,7 +1470,8 @@ $($checkRows -join [Environment]::NewLine)
       importState = $importStatePath
     }
   }
-  $snapshot | ConvertTo-Json -Depth 10 | Set-Content -LiteralPath $snapshotPath -Encoding utf8
+  $snapshotJson = $snapshot | ConvertTo-Json -Depth 10
+  Write-VoidBotDashboardUtf8File -Path $snapshotPath -Content $snapshotJson
 
   $html = @"
 <!doctype html>
@@ -1769,7 +1788,7 @@ $checksSection
 </html>
 "@
 
-  Set-Content -LiteralPath $dashboardPath -Value $html -Encoding utf8
+  Write-VoidBotDashboardUtf8File -Path $dashboardPath -Content $html
 
   return [PSCustomObject]@{
     DashboardPath = $dashboardPath

state/evidence.jsonl

@@ -69,3 +69,4 @@
 {"ts":"2026-05-10T15:36:28Z","type":"implementation","status":"ok","note":"Heartbeat repo weather was re-injecting the same four-day commit window on every run because the repo-activity helper had no per-repo cursor. The helper now uses moderation state as an incremental cursor store, persists repo commit cutoffs through the canonical MessagePack-backed state seam, and suppresses already-injected commits by default so repeated sweeps return only genuinely new motion."}
 {"ts":"2026-05-11T01:27:37Z","type":"implementation","status":"ok","note":"Heartbeat Portuguese mojibake had two sources: the unattended send path was letting human text pass through Windows shell encoding, and PowerShell Get-Content stdout was still mangling UTF-8 moderation surfaces even when the underlying files were fine. Fixed by adding scripts/send-discord-message.ps1 plus BOM-aware content-file reads in scripts/send-discord-message.mjs, and steering the moderation loop through node scripts/export-moderation-context.mjs instead of raw Get-Content for doctrine/state bundles."}
 {"ts":"2026-05-12T11:47:57Z","type":"implementation","status":"ok","note":"Logon startup failures were dying without a durable transcript and likely firing before Docker finished waking up after reboot. The stack startup script now appends .voidbot/logs/start-voidbot-stack.log, stops the transcript on failure, waits up to 90 seconds for docker version before giving up, and the logon task now runs with an explicit working directory plus a two-minute delay after logon."}
+{"ts":"2026-05-13T18:46:07Z","type":"implementation","status":"ok","note":"Worker polling now catches transient claim-loop failures instead of letting a Postgres timeout kill the process, and the operations dashboard writes snapshot/html via explicit UTF-8 file writes so status/dashboard generation stops tripping stack start and watchdog runs with Set-Content stream errors."}