---

This section details on the original issue you should resolve

<issue_title>commands/db: Remove obsolete check-refcount command from runtime pruning system</issue_title>
<issue_description>## Summary

The check-refcount command under db is a diagnostic tool for the old runtime pruning system that has been archived and replaced by offline GC. This command serves no purpose in the current architecture and should be removed to reduce codebase complexity.

Problem Description

The check-refcount command is a remnant of the runtime pruning architecture that was designed to:

1. Compare state_node, node_refcount, and smt_stale column families
2. Identify inconsistencies in node reference counts
3. Detect stale nodes that aren't properly tracked

However, the runtime pruning system has been completely archived in favor of offline GC, making this command obsolete.

Why This Command Should Be Removed

1. Runtime Pruner is Archived

• The pruning system now uses offline GC with "stop-the-world" Mark-Sweep approach
• According to pruner_guide.md: "Runtime pruner: archived. The code path is disabled by default and kept only for historical reference"
• Runtime pruning caused safety issues with refcount races

2. Refcount System is Not Functional

• Functions like inc_node_refcount, dec_node_refcount are never called in the current codebase
• The node_refcount column family is maintained but serves no purpose
• Offline GC doesn't rely on refcount consistency checks

3. No Current Integration

• Command accesses column families that are relics of the old architecture
• No integration with current offline GC system
• Not documented or tested anywhere

4. Architectural Incompatibility

• New offline GC explicitly avoids complex refcount tracking for safety reasons
• Documentation states: "Refcounts cannot be trusted under races"
• System moved to offline GC for safety and simplicity

Files to Remove

Primary Command File:

• crates/rooch/src/commands/db/commands/check_refcount.rs

Registration Points:

• crates/rooch/src/commands/db/commands/mod.rs (remove module import)
• crates/rooch/src/commands/db/mod.rs (remove command registration)

Impact Assessment

✅ ZERO IMPACT - Removal will have no negative effects because:

• Command is not used by any current functionality
• Offline GC operations don't depend on refcount consistency
• Refcount system is already non-functional
• No tests or documentation reference this command

Benefits of Removal

1. Reduced Maintenance - One less command to maintain and explain
2. Reduced Confusion - Operators won't accidentally use diagnostics for an obsolete system
3. Cleaner Codebase - Remove dead code with no functional purpose
4. Architectural Alignment - Codebase reflects the move to offline GC

Alternative Considered

Keep for Historical Reference: Rejected because:

• The command is already non-functional
• Keeping it creates confusion about current architecture
• Historical reference can be preserved in git history
• No value in keeping non-working diagnostics

Migration Steps

1. Remove the command implementation file
2. Remove module imports and command registration
3. Update any documentation that might reference it (unlikely to exist)
4. Run tests to ensure no regression

Risk Assessment

LOW RISK - This is pure removal of dead code:

• No functional dependencies
• No API changes affecting users
• No database schema changes
• Safe to remove in any release

Expected Outcome

• Cleaner codebase that reflects current architecture
• Reduced maintenance burden
• No confusion about diagnostic tools for obsolete systems
• Better alignment with offline GC-based pruning strategy</issue_description>

Comments on the Issue (you are @copilot in this section)