cctally 1.101.0 → 1.103.0

package/bin/_cctally_dashboard_conversation.py

@@ -764,6 +764,18 @@ def _run_conversation_events_stream(
         pass
     seen = cached_sigs(files)
 
+    # #630 S2: `ready` above means "this connection is live-tailing"; it fires
+    # BEFORE resolve() and ingest(), so it does not mean a baseline exists,
+    # which is why six tests used to sleep a second here. This frame means the
+    # baseline IS established, so any subsequent growth will be caught. The
+    # client listens only for `ready`, `tail` and `error`
+    # (dashboard/web/src/hooks/useConversationLiveTail.ts), and EventSource
+    # dispatches only event types something listens for, so this is inert for
+    # the browser by construction. It exists for tests; do not delete it as
+    # unread. Contract: docs/dashboard-gotchas.md.
+    handler.wfile.write(b"event: baselined\ndata: {}\n\n")
+    handler.wfile.flush()
+
     idle = 0.0
     cycles = 0
     while True:

package/bin/_cctally_dashboard_envelope.py

@@ -995,6 +995,30 @@ def _sync_failure_envelope(
             "action": None,
         }
 
+    text = error.casefold()
+    # Maintenance ownership supplies a more specific recovery action than a
+    # secondary busy attribution from another leg in the same failed tick.
+    # Classify those markers before the typed busy fallback so a blocked stale
+    # owner is never told merely to checkpoint the WAL.
+    if (
+        "stale maintenance marker" in text
+        or "stale repair marker" in text
+        or "recovery could not claim maintenance" in text
+    ):
+        return {
+            "kind": "maintenance_stale",
+            "label": "⚠ cache repair blocked",
+            "detail": "A stale cache repair owner is blocking server sync.",
+            "action": "cctally cache-sync --rebuild",
+        }
+    if "maintenance is in progress" in text:
+        return {
+            "kind": "maintenance_active",
+            "label": "cache repair in progress",
+            "detail": "Another cctally process is repairing the server cache.",
+            "action": None,
+        }
+
     # #583 S2 §7. A locked cache.db is named rather than left in the generic
     # bucket. Typed attribution only — a blanket uncorrupted-cache branch
     # would be too broad, because ANY exception raised while reading cache.db
@@ -1007,9 +1031,7 @@ def _sync_failure_envelope(
     # without it a tick carrying a corruption-shaped cache attribution AND a
     # separate busy one rendered "cache database busy" and dropped the
     # corruption message — the more urgent of the two, whose remedy is not
-    # interchangeable with a checkpoint. The gate names the TYPED corruption
-    # attribution only: a busy attribution still outranks the legacy raw-text
-    # corruption legs below, which is what Preserve 10 asks for.
+    # interchangeable with a checkpoint.
     if attributed("cache", sqlite_busy=True) and not attributed(
         "cache", corruption=True
     ):
@@ -1023,26 +1045,6 @@ def _sync_failure_envelope(
             "action": "cctally db checkpoint",
         }
 
-    text = error.casefold()
-    if (
-        "stale maintenance marker" in text
-        or "stale repair marker" in text
-        or "recovery could not claim maintenance" in text
-    ):
-        return {
-            "kind": "maintenance_stale",
-            "label": "⚠ cache repair blocked",
-            "detail": "A stale cache repair owner is blocking server sync.",
-            "action": "cctally cache-sync --rebuild",
-        }
-    if "maintenance is in progress" in text:
-        return {
-            "kind": "maintenance_active",
-            "label": "cache repair in progress",
-            "detail": "Another cctally process is repairing the server cache.",
-            "action": None,
-        }
-
     c = sys.modules["cctally"]
     if (
         attributed("cache", corruption=True)