fix: orphaned channel recovery pre-startup

[jvsena42]

Fixes #819

Port of synonymdev/bitkit-ios#480

This PR:
Fixes channel manager override by passing null for orphaned recovery — only monitors are needed for sweeping force-closed channels

Description

When recovering orphaned channel monitors from an RN remote backup, the stale RN channel manager was being passed to LDK alongside the monitors. This overwrites the native app's current channel manager, which can force-close any existing channels the user has opened.

Preview

recover-channel-monitor.webm

counterparty-close.webm

QA Notes

Implement this code to simulate a failure:

    suspend fun retrieveChannelMonitor(channelId: String): ByteArray? = withContext(ioDispatcher) {
        runCatching {
            throw RuntimeException() //dont commit

1. Fresh install from RN migration
   • Install RN app, open a channel, backup seed
   • Implement android code to simulate a channel recovery failure
   • Install Android app, restore from seed
   • Verify the channel is force closed
   • Open a new channel
   • Re-runt the android app without the mock code
   • ✅ Verify channel monitor is imported and the new channel is not closed
   • Mine 146 blocks
   • Verify that the swiping transaction is displayed and the balance is updated

OBS: The not can't trigger the ChanelClosed event for the RN closed channel because the old channelManager isn't set anymore, but still can detect the confirmed force-close transaction because it imports the channel monitor. Same behavior on iOS

OBS2: I realized there is not much value on implementing #819 for android because the node is frequently already running from the Foreground Service logic and would have to be restarted anyway

2. Normal counterparty close channel
   • Use the slack command to close the channel
   • Verify the app displays the closed channel sheet and update the balance

[jvsena42]

draft for testing

[jvsena42]

after setting channelManager = null the ChannelClose event is not being triggered. I'm still investigating

[claude]

Code review

Found 3 CLAUDE.md compliance issues.

[ovitrif]

tAck

Tested:

1. Fresh install from RN migration 🟢
2. Normal counterparty close 🟢

Two remarks:

1. Would've been great to create a Closed Channel record in the Lightning Connections screen.
2. Would've been nice to fix #668 for release 2.1.0
   • Since we're working with milestones now, assigned it the 2.2.0 milestone for next release