That was a nice and comprehensive answer.
I would like to suggest again, that you put info like this, especially that is aspirational in nature and shows that some things are going on behind the scenes and in which direction we are heading in some place more visible. Like the blog or maybe even the knowledge base for the “supported features” parts. At least for me, this kind of info moves the needle. I use info like this to decide whether I would recommend newer Framework products to others or would want to upgrade to newer boards.
And I think you are shooting yourself in the foot by publishing for example the 13th gen update just using the same quote you have been using on 12th gen and earlier, stating that LVFS update is not available:
I presume the reason is more, you already had the beta EFI updater and Windows updater from 12th gen that use the separate ME updater executable and it was just easier to reuse that. And the answer “unified ME updates and LVFS updates are possible for future updates of 13th gen and newer, but we are not ready for it yet” would have been much more accurate and informative.
Understandable. I always overestimate the capacity of other users to use a commandline successfully.
But on the other hand, your current EFI update procedure, as published for 13th gen includes a quick-time event to interrupt the default script and includes running a command on the EFI shell without extremely explicit instructions. So you are already doing similar things with firmware updates.
Also you are saying things like
without stating any reason for why anybody would ever want to run this update.
That sort of thing makes me question what is going on with your firmware updates, if Framework cannot even state the pros/cons of doing sth. optional. I would assume it either fixes bugs or improves the power consumption for some combination of expansion cards. Because if it adds nothing, why are you even offering it, especially in this way.