推进 INI 面板 shell integration manifest

wasm-port/docs/panel-entry.md

@@ -17,6 +17,8 @@ import {
   createIniPanelLaunchApiSchema,
   createIniPanelLauncherLinkViewModel,
   createIniPanelShellControlPageContract,
+  createIniPanelShellIntegrationManifest,
+  createIniPanelShellIntegrationSchema,
   createIniPanelShellViewModel,
   getIniPanelEntryByHref,
   getVisibleIniPanelEntries,
@@ -31,6 +33,7 @@ import {
   renderMachineSessionControlView,
   isSupportedIniPanelControlPageApiManifest,
   isSupportedIniPanelLaunchApiManifest,
+  isSupportedIniPanelShellIntegrationManifest,
 } from "../runtime/ui/ini-panel/ui-shell.js";
 ```
 
@@ -107,6 +110,14 @@ fields.
 Use `isSupportedIniPanelLaunchApiManifest()` or
 `linuxCncIniPanelLaunchApi.isSupportedLaunchApiManifest()` for a read-only
 compatibility predicate before using a launch manifest.
+Use `createIniPanelShellIntegrationSchema()`,
+`createIniPanelShellIntegrationManifest()`,
+`linuxCncIniPanelLaunchApi.getShellIntegrationSchema()`, or
+`linuxCncIniPanelLaunchApi.getShellIntegrationManifest()` when an outer shell
+needs one versioned read of pages, launcher links, launch API metadata,
+control-page API metadata, OPFS/session persistence capabilities, and current
+compatibility status. Use `isSupportedIniPanelShellIntegrationManifest()` when
+the outer shell needs to check that integration manifest before consuming it.
 
 The control-page refresh workflow lives in
 `runtime/ui/ini-panel/control-page-refresh-workflow.js`. Use