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

The effectiveness of testing deep reorganization behaviors on the mainnet could be significantly enhanced by adopting a strategy where both sides of a blockchain split are actively mined for an extended period. This approach would closely simulate real-world scenarios where miners or pools, in response to being ousted by a potential attack, might employ strategies like using "invalidateblock" to preserve their investments in a particular chain. Such a method would differ substantially from the simpler current practice of invalidating and quickly re-mining blocks to observe outcomes.

Furthermore, incorporating mechanisms to manage replay protection during the fork and adjusting hash power allocation in response to fluctuating transaction fees could offer insights into the dynamics and resilience of blockchain under varied stress conditions. It is also important to consider technical limitations, such as interactions with NODE_NETWORK_LIMITED when the reorganization reaches up to 288 blocks. Going beyond this point could potentially disrupt pruned nodes, as it requires revisiting more than the minimum of 550MB of block data, thereby exceeding standard storage and processing capacities designed for such nodes. These considerations highlight the need for comprehensive planning and robust testing frameworks to ensure blockchain stability and security against complex attack vectors.