From 3d9ed8de516afa98aa8927acadf337ffda9d5ee7 Mon Sep 17 00:00:00 2001
From: Rawman Grey <rawman@locus.im>
Date: Fri, 30 Oct 2026 10:22:34 +0300
Subject: [PATCH] docs: mark F11 accepted and log manager decision

---
 .opencode/feature_list.json | 5 +++--
 .opencode/progress.txt      | 7 +++++++
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/.opencode/feature_list.json b/.opencode/feature_list.json
index 321511d..81b4930 100644
--- a/.opencode/feature_list.json
+++ b/.opencode/feature_list.json
@@ -216,7 +216,7 @@
         "Journal compaction under the run lock retains unresolved rows plus the last 1,000 recovered rows, so the file cannot grow without bound.",
         "Targeted unit tests cover journal append/replay/idempotency, backoff schedule, max-attempt exhaustion, due-retry selection, and the failure endpoint response shape."
       ],
-      "passes": false,
+      "passes": true,
       "blocked_by": [
         "F08"
       ],
@@ -224,7 +224,8 @@
         "Root cause: `/ops` is an in-memory 200-entry ring buffer per PM2 worker; after a long run the 17 failure details were unrecoverable.",
         "Do not reuse `/ops` for persistence; keep it as the live view. Journal is append-only for cluster safety; compact only under `run.lock`.",
         "Retry policy starts with constants; expose settings only if tuning is needed after the first real run.",
-        "No user-facing notifications; logs and the read-only API/module table are the observability surface."
+        "No user-facing notifications; logs and the read-only API/module table are the observability surface.",
+        "Accepted 2026-10-30 on code + test evidence (79/79, tsc clean, build OK) after three review rounds; browser module render and live PM2 scheduler/retry tick were waived by the user and remain unverified."
       ]
     },
     {
diff --git a/.opencode/progress.txt b/.opencode/progress.txt
index 3f70b97..27dc46e 100644
--- a/.opencode/progress.txt
+++ b/.opencode/progress.txt
@@ -305,3 +305,10 @@ Not verified locally:
 - Added deterministic successor-replacement test via guard hooks; both appends survive and the successor guard is restored.
 - `npx tsc --noEmit` 0; `npm test` 79/79 pass; `npm run build` emits both bundles. Logs: `.opencode/tmp/runs/f11-guard3-{test,build}.log` and `f11-guard3-final-*`.
 - Remaining manual checks: live PM2 multi-worker append/compaction, live scheduler retry tick, browser module rendering.
+
+## 2026-10-30 — Manager: F11 accepted, F12 host fix recorded
+
+- Decision: squash-merged `feat/F11` into `goal/image-previews` after reviewer APPROVE (79/79 tests, tsc clean, build OK) and flipped F11 passes=true. User waived the manual browser/live-PM2 checks; recorded as unverified in the F11 note.
+- Context: three review rounds hardened replay attempts, compaction-vs-append locking, exhausted-retry handling, and reclaim-guard identity. Residual fs-lock scheduling windows are documented and accepted.
+- Outcome: accepted. F12 passes=true came from the user's own host verification (2,836 null rows backfilled, column default set) and was committed unchanged. Extension repo still owns no DB code for F12.
+- Learning: journal locking is the hard part, not the retry logic — plan the lock protocol before writing the journal. Browser + live-cluster checks remain the only gaps; deploy requires a human.