Distillation

Date: Sep 17, 2026

• 🟡 (00:19) Production artifact rebuild completed and emitted the frontend bundle under dist/assets/; notable large assets included dist/assets/sprite-Fb-TFjRY.svg at 943.96 kB (243.53 kB gzip) and dist/assets/shiki-JaaGU9RH.js at 9,575.87 kB (1,664.38 kB gzip; 12,683.64 kB source map).
• 🟡 (00:19) Recovery smoke script was updated at /tmp/opencode/session-recovery-v18-smoke.mjs.
• 🟡 (00:20) Exact rebuilt server artifact packages/opencode/dist/server/opencode-server had SHA-256 c5730f7d6017ebd8dde2a2e91365e574469ef10494ec632632b91d7e2318885c.
• 🟡 (00:20) Isolated v18 recovery smoke succeeded against healthy server version 1.18.30 across four starts: initial port 28830, first recovery start 21735, second start 27580, and third idempotence-check start 23449; every start had empty stderr.
• 🟡 (00:20) Smoke schema verification found session.wake_attempts default 0, session_input.wake_pending default false, and session_recovery.wake_pending default true plus session_recovery.wake_attempts default 0.
• 🟡 (00:20) Smoke index verification found session_execution_recovery_scan_idx, defined as CREATE INDEX \session_execution_recovery_scan_idx` ON `session_execution` (`recovery_error`,`expires_at`,`time_created`,`id`)`.
• 🟡 (00:20) Before recovery, smoke database counts were execution_count: 1, recovery_count: 0, input_count: 0, message_count: 0, and event_count: 0.
• 🟡 (00:20) After the second server start, execution recovery-final-v18 had been recovered exactly once: counts became execution_count: 0, recovery_count: 1, input_count: 1, message_count: 2, and event_count: 2; recovery state was phase: "ready", wake_pending: 0, wake_attempts: 2, and recovery_error: null.
• 🟡 (00:20) Recovery smoke created input msg_recovery_continue_recovery-final-v18 with prompt {"text":"continue"}, delivery queue, promoted_seq: 1, and wake_pending: 0; emitted events were sequence 0 type session.next.step.recovered.1 and sequence 1 type session.next.prompted.1.
• 🟡 (00:20) Third-start idempotence check left counts unchanged at execution_count: 0, recovery_count: 1, input_count: 1, message_count: 2, and event_count: 2, confirming no duplicate recovery input, messages, or events.