mesh-issues: keep every issue in the log changes and the bucket as its fold, so the record outlives the bucket's cap and a week of events (hq ADR 0300, issues 501, 502)

Every write appends one operation at the issue's last sequence before the bucket is written; a refused append writes nothing. The start carries what the bucket holds, refolds what is behind and indexes every issue in memory, so list answers from memory with a ranked search and a before cursor.
2026-10-12 02:41:54 +02:00
parent 8a92a47bf7
commit 983d434623
21 changed files with 2074 additions and 176 deletions
@@ -66,10 +66,13 @@
    "records.records_read",
    "mesh-knowledge.knowledge_highest"
  ],
+  "logs": [
+    "changes"
+  ],
  "state": [
    {
      "name": "issues",
-      "history": 8
+      "history": 1
    },
    "counters",
    "grooming",