Cassiel - I agree with what you're saying... there probably will not even be options to 'search by your version' like we currently have (except on the search page itself).
flapjack - I was actually thinking of that myself... the problem is, is that I don't want some newb coming along, having a hard time installing it, and giving it a thumbs down because of their own issues... as far as SMF is concerned, it either works on a version out of the box, or it doesn't... there isn't any middle ground. For determining what versions of SMF a package works with, the new site will use the package-info.xml files (and theme-info.xml for themes). So if an author puts 1.1.0-1.1.99, the mod site will show it as working for all 1.1.x versions, so as new versions of SMF become available, the author doesn't need to update the page. *most* mods would fall into this category for a 'Gold' release of SMF... it's very rare that a minor update to SMF causes a mod not to work (unless the mod isn't coded properly (more on that below). I think the new way of determining what version of SMF a mod works with will be much better than we currently have with the checkboxes.
As for coding standards, we plan on implementing a 'Editor's Choice' award that any customization is eligible to receive as long as it meets a strict set of coding guidelines that will be published around the time that feature is implemented. We will have our normal 'Community Customizer' program which will allow the community to help in analyzing mods before approval, with the customize team giving final approval, and once a mod is approved, the author can request an 'Editor's Review', in which the customize team will check the mod against the coding guidelines. If the customization passes, it will be given the award. This is aimed at getting more mods on the mod site (or older ones updated) that will make everyone's lives easier when coding and installing. The customize team typically knows the SMF code inside and out, and we are able to make recommendations (which would be in the coding guidelines) that will allow mod authors to make 'fool proof' modifications and modifications hopefully requiring less support requests due to their robustness (or something like that).
*Note: the actual name of the award and process haven't been hammered out yet... I've merely used the above so that it makes it more obvious as to what we have planned*