Let's stop trying to optimize that concatenation and just outsource the file entirely. OK, sure, if you're not connected to the Internet then you can't access the CDN. Big deal, that only applies during development. On any production site, you're connected to the Internet. We can still ship a copy of the file and offer a toggle so that people can switch from local version to remote CDN version, maybe even offer a choice of CDNs. But then we can stop worrying about "do we include jQuery or not", "do we compress jQuery or not", "do we aggregate jQuery or not". If something triggers a need for it, include the one from the CDN.
Consider how many sites will be using Drupal. Consider how many millions of people will therefore be using at least one Drupal site per day, and therefore get their jQuery from a CDN, and therefore NOT need to redownload a new copy of jQuery from every Drupal site they visit because they'll all be pointing to the same file on Google's CDN. Consider how many terabytes we save in the Inter-tubes that way, for everyone.
In fact, we could even ship only the uncompressed "Debug" version of jQuery in core, and assume that the production, compressed version comes from a public CDN.
Let's get off the island and let Google be fast for us.