What information are you looking for?
Mafia was left open over rollover, which I agree might have been part of the issue. I also noticed that before exiting, it logged back in, and I *think* it tried to run svn update and breakfast before exiting, but I wasn't paying very close attention.
So...
You left mafia running.
Rollover happened.
Your next action/interaction was to type exit in the gCLI
"Unexpected things happened".
If I've got the mafia side of things right, rollover triggered a logout.
When you typed exit the first thing mafia tried to do was login.
As part of logging in mafia (may have) done SVN Update and Breakfast.
At some point mafia realized it had a command to process so it started processing exit.
mafia probably got very confused since it was doing start up and shut down things simultaneously.
If the above is correct I'm inclined to say Bug - Won't Fix.
mafia does use blocking - if X is happening then don't do Y - but I'm not sure exactly how I would prevent this. There are valid gCLI interactions that do not require being logged in, "timing in" after rollover is a feature and the list of things that should be blocked during time in may be larger than just the gCLI exit.
Let's see if any other dev has ideas, opinions or sees something obvious that I am overlooking.