Core Lightning says that my bitcoind has gone backwards [pruning] \ stacker news ~lightning

TLDR: Issues that arise from running a Core Lightning node on top of a pruned node are ones that as of now do not resolve themselves with just waiting for the sync to finish. You may have to start your lightning node with a full, unpruned node.

Not having run my Core Lightning node for the last two or three weeks (while my pruned to 550mb Bitcoin Knots was running), yesterday I launched lightningd and it did not launch in the background but froze on me. Alarmed, took a look at the log that showed:

2024-04-08T17:46:52.609Z UNUSUAL plugin-bcli: bitcoin-cli getblock 00000000000000000002f502a034a1204911949f0410ed73a43e5f6d891860e8 0 exited with status 1
2024-04-08T17:46:53.615Z UNUSUAL plugin-bcli: bitcoin-cli getblock 00000000000000000002f502a034a1204911949f0410ed73a43e5f6d891860e8 0 exited with status 1
...
2024-04-08T17:57:49.892Z UNUSUAL plugin-bcli: bitcoin-cli getblock 00000000000000000002f502a034a1204911949f0410ed73a43e5f6d891860e8 0 exited with status 1

Nothing that has not been described as possible issues of running a Core Lightning node with a pruned node. Attempting to shutdown the core lightning node resulted in lightning-cli: Connecting to 'lightning-rpc': Connection refused

sudo pkill lightningd did shut it down, and after restarting lightningd I got again:

2024-04-08T18:12:31.589Z UNUSUAL plugin-bcli: bitcoin-cli getblock 000000000000000000019df0eec12c5d09407899b47df45ec8be0b3cb0a46e4d 0 exited with status 1
2024-04-08T18:12:32.596Z UNUSUAL plugin-bcli: bitcoin-cli getblock 000000000000000000019df0eec12c5d09407899b47df45ec8be0b3cb0a46e4d 0 exited with status 1

Again, sudo pkill lightningd, restart and again I got:

UNUSUAL plugin-bcli: bitcoin-cli getblock 00000000000000000000b23638542c4cf10e2b41e8443d13d736632436e86f2a 0 exited with status 1
2024-04-08T18:15:34.028Z UNUSUAL plugin-bcli: bitcoin-cli getblock 00000000000000000000b23638542c4cf10e2b41e8443d13d736632436e86f2a 0 exited with status 1
2024-04-08T18:15:35.035Z UNUSUAL plugin-bcli: bitcoin-cli getblock 00000000000000000000b23638542c4cf10e2b41e8443d13d736632436e86f2a 0 exited with status 1

It seemed to me that I was left with no choice but to delete the chainstate/ and blocks/ directories and start anew, this time without pruning. And so I did and started syncing bitcoind from zero. At about 40% of job done, I launched lightningd and got the following output Bitcoind has gone backwards from 835937 to 518597 blocks!

Question: Would deleting gossip make lightningd start properly? How have y'all dealt with this issue?