Distillation

Date: Sep 15, 2026

• 🔴 [requested-review] (12:35) User asked to continue and finish one same-session frozen correctness-review retry after a server restart, covering ownership, lease, fencing, interruption, recovery, replay, compaction, migration, startup, and test behavior.
• 🔴 [enforced-workflow] (12:35) User required the correctness review to remain strictly read-only and prohibited use of Lore recall.
• 🔴 (12:35) User stated immutable review evidence was present and verified unchanged: /tmp/opencode/session-recovery-full.patch SHA-256 f051a53df476dd924bda0a14c4cd91a63c9e7eafff53bbe71f0460571335fcbd; base ab9408c81cc9916177641ae8e9f08624fc27b5b9; HEAD dc661f30cb2055ad6248fdc59b14998d834497be plus frozen delta; SEA SHA-256 1ecc9afe36c12b31a8892cdbfb8a1560ceec97255c3537c073b795351233be40.
• 🟡 (12:35) Tool output confirmed SHA-256 f051a53df476dd924bda0a14c4cd91a63c9e7eafff53bbe71f0460571335fcbd for /tmp/opencode/session-recovery-full.patch, SHA-256 1ecc9afe36c12b31a8892cdbfb8a1560ceec97255c3537c073b795351233be40 for packages/opencode/dist/server/opencode-server, and HEAD dc661f30cb2055ad6248fdc59b14998d834497be; two object-type checks each returned commit.
• 🔴 (12:35) User required a non-empty final report containing PASS/CONCERN/MUST-FIX findings with exact current file:line evidence and ending exactly MERGE or DO-NOT-MERGE.
• 🔴 (12:35) User required that, if blocked, the report quote the exact command/error and identify the affected scope, then end DO-NOT-MERGE.
• 🔴 [enforced-response-style] (12:35) User stated never to return a context warning, separator, progress note, or empty output.