I discovered that communitysquad SputnikDAO proposal 86 passed, but that the function wasn’t able to execute. This is because the proposal target was china_charity_dao.sputnik.near rather than china_charity_dao.sputnikdao.near. The good news is that no funds were lost.
I’ve created a new proposal for the communitysquad donation to china_chairty_dao.sputnikdao.near:
https://www.sputnik.fund/#/dao/communitysquad.sputnikdao.near/proposals/95
If you audit original transaction yourself you will see that the SputnikDAO UI shows the proposal as passed (which is accurate), but no money was transferred. This is the function call which was kicked off when the proposal passed:
https://explorer.near.org/transactions/6SwBzvRbRbEHNzGzSVbZ7NEusDQ4sA5dmLyVCBgRnQqb
At Receipt ID 7wUJtkbFN4niRMSVPoZdtMMVnP2csNgWv6XULji7mgUa you can see the failure/error & at Receipt ID 6iGULit8KMacrt1iz4vdRKMVg8rtAsPt9ocTVJ38YWpc you can see the 10,000N being sent back to communitysquad.sputnikdao.near.
I was able to find the relevant transaction using Finear | NEAR Defi dashboard developed by a community member.