In several scenarios, including two today (the one with the badges and the one with the comment focus), we have had bugs set to status-completed simply because the fix has been checked in. Just because the code portion has been completed does not mean the work is done, and this can be confusing for users who come across the same problem. Until then it really is status-planned or maybe a tag that doesn't yet exist (status-checked-in?).
Particularly in times like this week, where the stability of the system is a priority, I don't think this status should be set merely because the code has been checked in - it should happen when the code is actually deployed and verified. Currently the devs are being very good about telling us that the code is done but they're not sure when it will be deployed, but I think that is because of the stability issue.