Default signet reorg history — was the fork at height 287766 (depth 19) deliberate?

The email discusses concerns and preferences regarding blockchain network behaviors, specifically focusing on the occurrence of reorganizations (reorgs). The sender appreciates that the reorganizations happening are not part of an intentional deep reorganization strategy. For their specific use case, maintaining shallow reorgs is crucial because the predictability of block production and fork behaviors similar to mainnet are key reasons for choosing Signet over Testnet4. While occasional shallow reorgs are acceptable, deep reorgs in a default setting would undermine their operational needs. Moreover, there is an interest in testing deep-reorg handling; however, they prefer it to be an opt-in feature rather than an unexpected default behavior. This approach allows for better preparedness and control over their system’s response to such events.