Provide capability classes from Mus

components/mus/manifest.json

Index: components/mus/manifest.json
diff --git a/components/mus/manifest.json b/components/mus/manifest.json
index ca144d18be5d27c7e79859f6f7f21ae0a5f67fbe..43d206aee0a1ba91efce48f7cce4037f528468d3 100644
--- a/components/mus/manifest.json
+++ b/components/mus/manifest.json
@@ -3,9 +3,23 @@
   "name": "mojo:mus",
   "display_name": "UI Service",
   "capabilities": {
+    "provided": {
+      "mus:core": [
+        "mus::mojom::DisplayManager",
+        "mus::mojom::Gpu",
+        "mus::mojom::UserAccessManager",
+        "mus::mojom::WindowTreeFactory",

[sky, 2016/04/21 20:10:36]

I tend to think WindowTreeFactory and WindowTreeHostFactory should be grouped in
their own capabilities too. We don't want random apps to be able to create top
level things.

+        "mus::mojom::WindowTreeHostFactory"
+      ],
+      "mus:gpu": [
+        "mus::mojom::Gpu"
+      ],
+      "mus:window_manager": [
+        "mus::mojom::WindowManagerFactoryService"

[sky, 2016/04/21 20:10:36]

Is it worth having mus:window_manager contain everything in mus:core as well?
That way consumers don't need to list both.

+      ]
+    },
     "required": {
-      "*": { "interfaces": [ "*" ] },
-      "mojo:shell": { "classes": [ "all_users" ] }
+      "mojo:shell": { "classes": [ "shell:all_users", "shell:explicit_class" ] }
     }
   }
 }