remove audit label in comments

Author: nekomoto911

crates/pipe-exec-layer-ext-v2/execute/src/lib.rs

@@ -301,7 +301,7 @@ enum SystemTxnExecutionOutcome {
     EpochChanged(ExecuteOrderedBlockResult),
 }
 
-// DESIGN(GRETH-021, GRETH-028): This validation is intentionally debug-only.
+// DESIGN: This validation is intentionally debug-only.
 // These checks (gas overflow, gas accounting consistency, timestamp-unit sanity)
 // detect logic bugs during development and testing. They are not needed in
 // production and use `panic!` which is inappropriate for release builds.
@@ -815,7 +815,7 @@ impl<Storage: GravityStorage> Core<Storage> {
             precompile_state.merge_transitions(BundleRetention::Reverts);
             let precompile_bundle = precompile_state.take_bundle();
 
-            // DESIGN(GRETH-026): Using `insert` (shallow merge) is intentional here.
+            // DESIGN: Using `insert` (shallow merge) is intentional here.
             // The mint precompile only modifies regular user accounts (mint recipients),
             // which are disjoint from accounts touched by system transactions
             // (SYSTEM_CALLER, on-chain config contracts). The two state domains are

crates/pipe-exec-layer-ext-v2/execute/src/onchain_config/metadata_txn.rs

@@ -197,7 +197,7 @@ pub fn transact_system_txn(
     let tx_env = Recovered::new_unchecked(txn.clone(), SYSTEM_CALLER).into_tx_env();
     let result = evm.transact_raw(tx_env).unwrap();
 
-    // DESIGN(GRETH-025): System transaction failures are intentionally logged, not asserted.
+    // DESIGN: System transaction failures are intentionally logged, not asserted.
     // DKG and JWK system transactions can legitimately fail or revert, so a hard
     // assert would crash the node on valid failure scenarios. Graceful handling
     // (logging + continuing) is the correct behavior here.

crates/pipe-exec-layer-ext-v2/relayer/src/blockchain_source.rs

@@ -88,7 +88,7 @@ impl LastProcessedEvent {
 /// This is the primary data source for cross-chain message bridging.
 /// Tracks `last_processed` to ensure exactly-once consumption semantics.
 ///
-/// DESIGN(GRETH-027): All RPC calls (`eth_getLogs`, `eth_getBlockReceipts`) use the
+/// DESIGN: All RPC calls (`eth_getLogs`, `eth_getBlockReceipts`) use the
 /// same `rpc_client` endpoint. This is an acknowledged architectural limitation — a
 /// fully compromised RPC could forge mutually consistent responses. The current threat
 /// model assumes the RPC endpoint is trusted. Multi-endpoint or Merkle-proof

crates/storage/db/src/implementation/rocksdb/cursor.rs

@@ -270,7 +270,7 @@ impl<K: TransactionKind, T: Table> DbCursorRO<T> for Cursor<K, T> {
 impl<T: Table> DbCursorRW<T> for Cursor<RW, T> {
     /// Insert or update a key-value pair in the database.
     ///
-    /// # Read-Your-Writes Limitation (GRETH-014)
+    /// # Read-Your-Writes Limitation
     ///
     /// Writes are buffered in a `WriteBatch` and are **not visible to subsequent
     /// read operations** (`seek`, `current`, `get`) on the same cursor within the