Add the "options_ui" extension manifest field.

extensions/common/api/_manifest_features.json

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // This features file defines manifest keys implemented under src/extensions.
 // See extensions/common/features/* to understand this file, in particular
 // feature.h, simple_feature.h, and base_feature_provider.h.
 
 // To add a new whitelisted ID, SHA-1 it and force it to uppercase. In Bash:
 //
@@ skipping 77 matching lines @@
     "extension_types": [
       "platform_app"
     ]
   },
   "offline_enabled": {
     "channel": "stable",
     "extension_types": [
       "extension", "legacy_packaged_app", "hosted_app", "platform_app"
     ]
   },
+  "options_ui": {
+    "channel": "trunk",
+    "extension_types": ["extension"]

[Yoyo Zhou, 2014/08/29 23:06:27]

Do we want legacy_packaged_app too? Those also show up in chrome://extensions.

[not at google - send to devlin, 2014/08/29 23:26:42]

I was thinking no, since we don't want to give legacy packaged apps any new
features. However now that I think about it... perhaps this should be an
exception. It's a bit mean to potentially break legacy packaged apps without the
ability for them to opt out. The deprecation process can happen elsewhere.

[ericzeng, 2014/09/02 18:23:37]

Adding legacy packaged apps to the list.

+  },
   "sandbox": {
     "channel": "stable",
     "extension_types": [
       "extension", "platform_app", "legacy_packaged_app"
     ],
     "min_manifest_version": 2
   },
   "sockets": {
     "channel": "stable",
     "extension_types": ["platform_app"]
@@ skipping 10 matching lines @@
       "extension_types": ["platform_app"],
       "location": "component"
     }
   ],
   "webview": {
     "channel": "stable",
     "extension_types": ["platform_app"],
     "min_manifest_version": 2
   }
 }