fix(spec): resolve doc review findings in adoption specs and core spec

- Make layout, registration.path, manifest.required_fields optional in
  extensionModelBundle schema (match prose OPTIONAL declarations)
- Remove phantom filePaths/configEntry wrapper keys from component_paths
  prose and examples in assistant-adoption.md
- Fix Gemini CLI transport: http-streaming -> streamable-http
- Add missing configuration/capabilities to copilot-cli.json
- Add missing configuration to gemini-cli.json
- Update core spec version 2026-02-14 -> 2026-02-22
- Replace stale plugin_model/adapter_interface refs with extension_model

Author: zircote

spec/assistant-adoption.md

@@ -137,12 +137,18 @@ The following example shows `component_paths` version-gated so that the skill in
 {
   "component_paths": {
     ">=1.0.0": {
-      "skills": { "filePaths": { "user": "~/.assistant/skills/{name}.md", "project": ".assistant/skills/{name}.md" } },
-      "hooks": { "configEntry": { "file": ".assistant/hooks.json", "format": "json" } }
+      "skills": { "user": "~/.assistant/skills/{name}.md", "project": ".assistant/skills/{name}.md" },
+      "hooks": {
+        "user": { "file": ".assistant/hooks.json", "format": "json" },
+        "project": { "file": ".assistant/config.json", "format": "json", "key": "hooks" }
+      }
     },
     "<1.0.0": {
-      "skills": { "filePaths": { "user": "~/.assistant/legacy/{name}.md", "project": ".assistant/legacy/{name}.md" } },
-      "hooks": { "configEntry": { "file": ".assistant/config.json", "format": "json", "key": "hooks" } }
+      "skills": { "user": "~/.assistant/legacy/{name}.md", "project": ".assistant/legacy/{name}.md" },
+      "hooks": {
+        "user": { "file": ".assistant/config.json", "format": "json", "key": "hooks" },
+        "project": { "file": ".assistant/config.json", "format": "json", "key": "hooks" }
+      }
     }
   }
 }
@@ -210,13 +216,7 @@ Component path entries fall into two categories based on how the host consumes t
 
 #### File-Based Components
 
-Components that are installed as individual files on disk. The component types `skills`, `agents`, `commands`, and `instructions` use this pattern.
-
-| Property | Type | Required | Description |
-|---|---|---|---|
-| `filePaths` | `object` | REQUIRED | An object with optional `user` and `project` keys, each mapping to a filesystem path string. |
-
-The `filePaths` object:
+Components that are installed as individual files on disk. The component types `skills`, `agents`, `commands`, and `instructions` use this pattern. The component path entry is an object with optional `user` and `project` keys, each a string filesystem path.
 
 | Key | Type | Description |
 |---|---|---|
@@ -225,13 +225,9 @@ The `filePaths` object:
 
 #### Config-Entry Components
 
-Components that are registered as entries within a configuration file rather than placed as standalone files. The component types `hooks`, `mcp_servers`, and `lsp_servers` use this pattern.
-
-| Property | Type | Required | Description |
-|---|---|---|---|
-| `configEntry` | `object` | REQUIRED | Describes the configuration file where the component is registered. |
+Components that are registered as entries within a configuration file rather than placed as standalone files. The component types `hooks`, `mcp_servers`, and `lsp_servers` use this pattern. The component path entry is an object with optional `user` and `project` keys, each an object describing the configuration file for that scope.
 
-The `configEntry` object:
+Each scope object has the following properties:
 
 | Key | Type | Required | Description |
 |---|---|---|---|
@@ -256,47 +252,31 @@ The `component_paths` object as a whole MAY be version-gated at the top level.
 {
   "component_paths": {
     "skills": {
-      "filePaths": {
-        "user": "~/.claude/skills/{name}.md",
-        "project": ".claude/skills/{name}.md"
-      }
+      "user": "~/.claude/skills/{name}.md",
+      "project": ".claude/skills/{name}.md"
     },
     "agents": {
-      "filePaths": {
-        "user": "~/.claude/agents/{name}.md",
-        "project": ".claude/agents/{name}.md"
-      }
+      "user": "~/.claude/agents/{name}.md",
+      "project": ".claude/agents/{name}.md"
     },
     "commands": {
-      "filePaths": {
-        "user": "~/.claude/commands/{name}.md",
-        "project": ".claude/commands/{name}.md"
-      }
+      "user": "~/.claude/commands/{name}.md",
+      "project": ".claude/commands/{name}.md"
     },
     "instructions": {
-      "filePaths": {
-        "project": "CLAUDE.md"
-      }
+      "project": "CLAUDE.md"
     },
     "hooks": {
-      "configEntry": {
-        "file": ".claude/settings.json",
-        "format": "jsonc",
-        "key": "hooks"
-      }
+      "user": { "file": "~/.claude/settings.json", "format": "jsonc", "key": "hooks" },
+      "project": { "file": ".claude/settings.json", "format": "jsonc", "key": "hooks" }
     },
     "mcp_servers": {
-      "configEntry": {
-        "file": ".claude/mcp.json",
-        "format": "json"
-      }
+      "user": { "file": "~/.claude.json", "format": "json", "key": "mcpServers" },
+      "project": { "file": ".mcp.json", "format": "json", "key": "mcpServers" }
     },
     "lsp_servers": {
-      "configEntry": {
-        "file": ".claude/settings.json",
-        "format": "jsonc",
-        "key": "lspServers"
-      }
+      "user": { "file": "~/.claude/settings.json", "format": "jsonc", "key": "lspServers" },
+      "project": { "file": ".claude/settings.json", "format": "jsonc", "key": "lspServers" }
     }
   }
 }

spec/assistants/copilot-cli.json

@@ -104,5 +104,16 @@
       "mcp_servers": ".mcp.json",
       "lsp_servers": ".lsp.json"
     }
+  },
+  "configuration": {
+    "settings_paths": {
+      "user": "~/.copilot/settings.json",
+      "project": ".github/copilot-settings.json"
+    }
+  },
+  "capabilities": {
+    "lazy_loading": false,
+    "hot_reload": false,
+    "managed_settings": false
   }
 }

spec/assistants/gemini-cli.json

@@ -111,7 +111,7 @@
   },
   "mcp": {
     "supported": true,
-    "transports": ["stdio", "sse", "http-streaming"],
+    "transports": ["stdio", "sse", "streamable-http"],
     "env_prefix": null
   },
   "extension_model": {
@@ -133,6 +133,12 @@
       "mcp_servers": ".mcp.json"
     }
   },
+  "configuration": {
+    "settings_paths": {
+      "user": "~/.gemini/settings.json",
+      "project": ".gemini/settings.json"
+    }
+  },
   "capabilities": {
     "lazy_loading": false,
     "hot_reload": false,

spec/schemas/assistant-adoption.schema.json

@@ -222,7 +222,7 @@
 
     "extensionModelBundle": {
       "type": "object",
-      "required": ["type", "install_dir", "manifest", "registration", "layout"],
+      "required": ["type", "install_dir", "manifest", "registration"],
       "additionalProperties": false,
       "properties": {
         "type": {
@@ -236,7 +236,7 @@
         },
         "manifest": {
           "type": "object",
-          "required": ["filename", "required_fields"],
+          "required": ["filename"],
           "additionalProperties": false,
           "properties": {
             "filename": {
@@ -252,7 +252,7 @@
         },
         "registration": {
           "type": "object",
-          "required": ["mechanism", "path"],
+          "required": ["mechanism"],
           "additionalProperties": false,
           "properties": {
             "mechanism": {

spec/specification.md

@@ -6,7 +6,7 @@ nav_order: 2
 
 # ccpkg Specification
 
-**Specification Version: 2026-02-14 (Draft)**
+**Specification Version: 2026-02-22 (Draft)**
 
 ## Status
 
@@ -1092,15 +1092,15 @@ ccpkg integrates with each host's extension or plugin system, leveraging the hos
 
 ### Bootstrap
 
-On first use, ccpkg registers itself with the host's extension discovery system. The bootstrap process varies by host — some use marketplace registration, others use directory scanning or plugin manifests. The exact mechanism is defined in the host's adoption specification under `plugin_model`.
+On first use, ccpkg registers itself with the host's extension discovery system. The bootstrap process varies by host — some use marketplace registration, others use directory scanning or plugin manifests. The exact mechanism is defined in the host's adoption specification under `extension_model`.
 
 ### Plugin Registration
 
 During installation, the installer performs two host-facing steps as defined by the host's adoption specification:
 
-1. **Generate host plugin manifest.** The installer creates the host's expected plugin manifest inside the install directory, mapping ccpkg manifest fields (name, version, description, author) to the host's manifest format. The manifest path and format are defined in the host's `plugin_model.manifest_path` field. Package authors SHOULD NOT include host-specific plugin manifests in their archives. If a host-specific manifest is present, the installer MUST use the generated version and MAY warn the author.
+1. **Generate host plugin manifest.** The installer creates the host's expected plugin manifest inside the install directory, mapping ccpkg manifest fields (name, version, description, author) to the host's manifest format. The manifest path and format are defined in the host's `extension_model.manifest.filename` field. Package authors SHOULD NOT include host-specific plugin manifests in their archives. If a host-specific manifest is present, the installer MUST use the generated version and MAY warn the author.
 
-2. **Register with host.** The installer registers the package with the host's extension system as described in the host's `adapter_interface` operations. This ensures the host recognizes the package on the next session start.
+2. **Register with host.** The installer registers the package with the host's extension system as described in the host's `extension_model.registration` mechanism. This ensures the host recognizes the package on the next session start.
 
 These two steps — generating a plugin manifest and registering with the host — are the complete integration surface. The specific files and settings keys are defined in each host's [adoption specification](assistant-adoption.md).