Never mind. I tested this using a new return and found that the bug has not been corrected as if 2025.47.5 (Nov 13, 2025).
And it appears that I'll have to leave the override in place all the way through to filing as there is no way to retrigger a transfer from last year without starting over (as far as I can tell).
