Restarting the game got rid of it for me. So there's both a bug and a workaround. Unfortunately, the workaround means that the bug will likely not be present in any save files uploaded. Can be reproduced by taking a settlement (I don't know if it happens with auto-resolve, manual battle, or both), though.