Odd. I'm tempted to explore this a bit more to see if we can figure out what happened.
Is there anything else to do? :/
Yes, but I'm trying to decide what's the best next course of action to have the best chance of success without wasting time.
If you're willing to share the transaction ID with me for the transaction that you sent to localbitcoins, I'd dig into that a bit for you. You could share it here or via PM if you prefer. I have a GPG public key if you would prefer to send it encrypted.
If the transaction was confirmed and it was sent from this wallet, then the wallet should have found it in the blockchain after the zapwallettxes.
You could try shutting down the wallet and then re-starting it from the command line with the -rescan command line option. This will force the wallet to scan the entire blockchain again looking for confirmed transactions that it doesn't know about. I'd be really surprised if it finds it during a rescan after failing to find it during the zapwallettxes, but it won't hurt anything (aside from potentially wasting your time).
As jaydipmodhwadia has mentioned, you could try a -reindex as well. This will rebuild all the indexes from the current blk000??.dat files on your hard drive. This is another step that won't hurt, but is likely to waste time since we don't have any indication yet that it would help.
Nevermind about the local bitcoins, that was just a mis-calculation. Just missing my 6bitcoins from my wallet balance.