As @volker01 notes a few posts up, 2 of the stubs are coming from aa4mg (TTS, Maps), and 1 (“Google App”) from other places. I put all 3 togther, and posted them here:
I also added a very basic overview, noting that rooting (Magisk or other) is not needed for iodé because we already have Android Auto stub at the root level (for this very reason). But ROMs without that root level stub (LineageOS 4 microG, etc.) will likely need rooting for AA to work.
For @Guardian24 and wireless AA, it may be I didn’t have everything right, but wireless AA on my “stubs only” device gave the same “intermittent at best buggy results” as on my other device that had the full “google apps” installed. I want to test another car, I am currently blaming Toyota for the poor AA wireless experience (the car owner on an iPhone also has headaches with it forgetting the pairing, needing to restart the car sometimes, etc 
) Anyway, I think “more research needed” but if you have a spare phone to test, could you try with only the stub apps to see if it may work?
When I connected by wire, it did auto-setup a BT connection. I am also confused as to why, possibly for phone calls? Not really sure. My test car just traveled yesterday so I won’t be able to re-test for a bit.
Regarding notification permissions, even with the AA app (and stub apps) set to allow notifications (from their respective “App Info” pages), I still had the error that I needed to grant notification permissions. I then saw a dropdown prompt showing that AA was not yet approved for “Notification read, reply & control”. After approving AA for that, then it worked. I could NOT find this “Notification read, reply & control” permission just under “App info”, I also can’t find where this is set or denied when digging through System Settings. I want to get a bit better understanding of this (why “App Info” notification permissions alone aren’t enough).