dave-parachute rewrites Mike's setup guide for lawyers, not engineers

An outside contributor installed Mike as a non-technical user, hit a wall at every step, and wrote down the fixes.

dave-parachute walked through installing Mike as if he were a lawyer rather than an engineer, catalogued every place it snagged, and proposed a full rewrite of the setup instructions. The changes were structural and practical:

A linear, start-to-finish install path a newcomer can actually follow, closing the gap where the old guide assumed you'd already downloaded the code.
An up-front list of the outside services you have to sign up for, with links, so you know what you're committing to before you begin.
A reference table spelling out every configuration value and where to find it.
A note that each user needs their own model provider key to unlock the assistant, not just the shared server key.
A flag that the hosted database service recently moved its settings and still expects its older key format.
The document-conversion tool marked optional, needed only for uploading Word files.
A troubleshooting section for the three real install failures he hit.

The proposal was closed without merging, so none of it landed in Mike itself.