When a block reward is spent together with other outputs in the wallet and that block reward is later orphaned, the wallet does not show the other funds as available anymore.  Even a `-rescan` is not enough - only `-zapwallettxes` or an explicit `abandontransaction` "recovers" the funds.  I prepared a [test case](https://github.com/domob1812/bitcoin/blob/wallet-bug-invalidated-block-rewards/test/functional/wallet_bug.py) that shows this behaviour.

Is this a known issue or the expected behaviour?  While this situation is something that will presumably not occur in practice (as it requires a long reorg), I wonder if that transaction should be automatically abandoned as it seems clear it won't be able to be confirmed anymore.
}
        context.chain->initMessage(_("Loading …").translated);
        stdshared_ptr<CWallet>  = CWalletCreate(context, name, stdmove(database), options.create_flags, error, warnings);
        if (!) {
            error = Untranslated("Wallet loading failed.") + Untranslated(" ") + error;
            status = DatabaseStatusFAILED_LOAD;
            return nullptr;
        }
        NotifyWalletLoaded(context, );
        AddWallet(context, );
        ->postInitProcess();
        
        UpdateWalletSetting(*context.chain, name, load_on_start, warnings);
        return ;
    } catch (const stdruntime_error& e) {
        error = Untranslated(e.what());
        status = DatabaseStatusFAILED_LOAD;
        return nullptr;
    }
}
class FastWalletRescanFilter
{
public
    FastWalletRescanFilter(const CWallet& )  m_()
    {
        // 
        assert(!m_.IsLegacy());
        // 
        for (auto spkm  m_.GetAllScriptPubKeyMans()) {
            auto desc_spkm{dynamic_cast<DescriptorScriptPubKeyMan*>(spkm)};