Deterministic UTXO consolidation under volatile fee regimes

In a recent update to the live JSON API at api.babyblueviper.com/omega-pruner/plan, a significant change has been implemented concerning the handling of UTXOs (Unspent Transaction Outputs). Previously, the build_consolidation_plan() function merged UTXOs from multiple addresses into one PSBT (Partially Signed Bitcoin Transaction) without any user confirmation or warning. This issue was addressed immediately upon discovery; now, when more than one address is inputted, the system requires users to explicitly set confirm_privacy_cluster_merge=true. If this confirmation is not provided, the operation fails with a detailed error message based on the common-input-ownership heuristic, which highlights the irreversible nature of such merges unlike situations involving fee miscalculations.

The update ensures that transactions involving a single address remain unaffected by this change. Extensive verification was conducted to confirm the functionality: using two addresses without confirmation results in an error code 400 displaying the specified reason, whereas confirmed dual-address inputs proceed as expected. The adjustments are solely applicable to the live JSON API, which directly impacts end-users interacting with the system.

Despite these improvements, there are still areas pending refinement. There remains no separately versioned selection policy artifact, nor is there a snapshot of the eligible UTXO set recorded, an aspect critically underscored as "same wallet state," which continues to lack precise definition, particularly outside of fee and change considerations. Additionally, it is essential to note that the reference Gradio UI mentioned in the repository linked has not yet been updated to reflect these changes, indicating a discrepancy between the API’s capabilities and the UI presentation. This misalignment is acknowledged to ensure transparency and manage expectations regarding the current state of the system's interface.