yes

no

no, no reason to do that

I keep small amounts in my pc wallet for casual spending. I applied the 0.9.0->0.9.1 update and once done syncing, the client told me that my database was corrupt and wanted to reindex it. I allowed it to, and sometime during the sync, 1.3 BTC went from confirmed to unconfirmed and hasn't moved since (24 hours or so I'd guess). Any ideas/suggestions?

It appears to me that you have a few unconfirmed transactions that hold up inputs.
Have you perhaps set "spend unconfirmed change" in options to false (or passed -spendzeroconfchange=0)?

If you look in the transaction list do you see any tx which are unconfirmed?  If so check another source (blockr.io or blockchain.info) to determine if the tx is indeed unconfirmed.

No, but i just noticed that it reverted me to 0.8.6.... How is this possible? All tx before 7/30/2013 are gone, and those coins are still unconfirmed. I was at version 0.9.0 prior to updating..

I got the message "Corrupted block database detected.

Do you want to rebuild the block database now?" then when it was almost entirely rebuilt I got the message again and it is rebuilding again now-I updated to 0.9.1 between the rebuilt and it  didn't change anytging; can someone help me explain?

Why isn't 0.9.1 on SourceForge, and what is its checksum?

Yes I think separate the core and wallet should be a good thing, but this might require some effort and time, modularization usually take years to achieve

"@MultiBitOrg Does the OpenSSL bug affect Multibit?"

"-@QuadraQ As MultiBit is installed on your machine you interact with it directly so no."
https://twitter.com/MultiBitOrg