docs: update generated docs

docs/_instructions/buildpath.md

@@ -36,6 +36,17 @@ An example of the `-buildpath` could be the following, where three dependencies
      osgi.core;version=4.3.1,\
      osgi.cmpn;version=4.3.1
 
+## Eclipse Features
+
+An entry can reference an Eclipse feature from a [p2 repository](/plugins/p2.html) by adding the `type=org.eclipse.update.feature` attribute. The `type` attribute is required because a feature can share its name and version with a bundle; without it the entry is resolved as a bundle.
+
+    -buildpath: \
+     org.eclipse.e4.rcp;version='4.40.0.v20260516-1214';type=org.eclipse.update.feature
+
+A feature is a container of bundles: on the build path it expands to its member bundles, i.e. the `<plugin>` references of its `feature.xml` and, recursively, the members of its `<includes>` referenced features. `<requires>` imports are dependencies, not members, and are not expanded. Members whose `os`/`ws`/`arch` attributes do not match the running platform are skipped. The versions pinned in the feature are resolved exactly; when a pinned version is not present in the repositories, the highest available version is used and a warning is issued.
+
+Feature entries are supported on all container paths, i.e. also on `-testpath`, `-runpath` and `-runbundles`.
+
 ## See Also
 
 * [-testpath] for setting the test path.