fix(heal): cleanup consumed MRF replay journals

Do not retain Accepted or Merged replay intents as startup anchors after they have been handed to the heal manager. Only refused or still-pending replay records keep the journal on disk until a successor snapshot can persist them.

This keeps successor snapshots limited to the pending queue, which lets successful replay remove both authoritative and legacy journal paths and restores the crash-boundary tests around successor flush.

Co-Authored-By: heihutu <heihutu@gmail.com>

Co-Authored-By: zhi22915 <qiuzgang@gmail.com>
(cherry picked from commit d5b8f49c9d)

.config/e2e-repl-nightly-selection.txt

@@ -1 +1 @@
-sha256=95c8adc016bbc0df9fb2afa24a108bcdf6567ec4d0518725a6cae301593ab556
+sha256=0fe8408874ccec3620262a9812d67920ddd72dc9edf0e36e0d0aed3f8bad026e

crates/log-analyzer/src/rules/seed/disk.rs

@@ -68,17 +68,14 @@ pub(super) fn rules() -> Vec<Rule> {
             )
         },
         Rule {
-            anchors: strings(["Storage inventory probe failed; current drive health is unknown"]),
+            anchors: strings(["reporting peer disks offline after consecutive storage_info failures"]),
             ..base(
                 "peer-disks-offline",
                 P2Degraded,
                 "disk",
-                "peer 存储清单探测失败",
-                any([
-                    contains("Storage inventory probe failed; current drive health is unknown"),
-                    contains("reporting peer disks offline after consecutive storage_info failures"),
-                ]),
-                "某 peer 的 storage_info 探测失败,当前磁盘健康状态未知。",
+                "peer 磁盘被整体判定离线",
+                contains("reporting peer disks offline after consecutive storage_info failures"),
+                "对某 peer 连续 storage_info 失败,判定其磁盘整体离线。",
                 "检查该 peer 节点存活与 RPC 端口可达。",
             )
         },

crates/log-analyzer/src/rules/seed/tests.rs

@@ -110,7 +110,7 @@ fn every_rule_has_a_positive_sample() {
         ("remote-peer-faulty", msg("Remote peer health check failed for node2: marking as faulty")),
         (
             "peer-disks-offline",
-            msg("Storage inventory probe failed; current drive health is unknown"),
+            msg("reporting peer disks offline after consecutive storage_info failures"),
         ),
         ("drive-faulty-error", msg("remote drive is faulty")),
         (
@@ -318,10 +318,6 @@ fn smoke_samples_hit_exact_rule_sets() {
         &["disk-marked-faulty"],
     );
     exact(&msg("erasure write quorum (required=8, achieved=5)"), &["ec-write-quorum"]);
-    exact(
-        &msg("reporting peer disks offline after consecutive storage_info failures"),
-        &["peer-disks-offline"],
-    );
     exact(
         &Sample {
             message: "Metacache listing quorum failed",