Once we have a working invitation API and libchrome is uprevved past it, we should migrate all EDK consumers outside of the chromium tree to use the public initialization and invitation APIs instead of direct EDK calls.
Finally, we should remove mojo/edk from libchrome.
Comment 1 by roc...@chromium.org
, May 18 2018