From 0c7681a25cf89d335dfba7a680becf054cee6637 Mon Sep 17 00:00:00 2001
From: Elrond
 <28d6302a099e5225b02c4155ac4236e4912603df2ab08dbfc2f4fef08ce598c8@buzz.block.builderlab.xyz>
Date: Fri, 16 Oct 2026 10:21:23 -0400
Subject: [PATCH] buzz-db: name deletion-lock admission in the isolation
 refusal

Signed-off-by: Elrond <28d6302a099e5225b02c4155ac4236e4912603df2ab08dbfc2f4fef08ce598c8@buzz.block.builderlab.xyz>
---
 crates/buzz-db/src/store/deletion.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/crates/buzz-db/src/store/deletion.rs b/crates/buzz-db/src/store/deletion.rs
index a81a58ceef..387015cea7 100644
--- a/crates/buzz-db/src/store/deletion.rs
+++ b/crates/buzz-db/src/store/deletion.rs
@@ -3362,10 +3362,10 @@ pub(crate) async fn lock_community_deletion_shared(
     )
     .await?;
     if isolation != "read committed" {
-        tracing::error!(%isolation, %community, "community write admission requires read committed isolation");
+        tracing::error!(%isolation, %community, "deletion-lock admission requires read committed isolation");
         // AccessDenied deliberately refuses writes; the log distinguishes config errors from fences.
         return Err(DbError::AccessDenied(format!(
-            "community write admission requires read committed isolation, got {isolation}"
+            "deletion-lock admission requires read committed isolation, got {isolation}"
         )));
     }
     Ok(())