推进 INI 面板 launcher link view-model helper

wasm-port/docs/panel-entry.md

@@ -10,8 +10,9 @@ control view:
 ```js
 import {
   INI_PANEL_ENTRIES,
+  createIniPanelLauncherLinkViewModel,
   getIniPanelEntryByHref,
-  getIniPanelEntryManifest,
+  getVisibleIniPanelEntries,
   createMachineSessionControlPageController,
   renderMachineSessionControlView,
 } from "../runtime/ui/ini-panel/ui-shell.js";
@@ -28,15 +29,19 @@ controller, and the control-view renderer. It does not implement CNC behavior.
 | Edit and run | `runtime/ui/ini-panel/index.html` | Editable INI panel and existing run workflow surface. |
 | Read-only control view | `runtime/ui/ini-panel/control-page.html` | Read-only control view backed by the panel API. |
 
-## Entry Manifest
+## Visible Entries
 
-The visible launch entries come from `getIniPanelEntryManifest()`:
+The visible launch entries come from `getVisibleIniPanelEntries()`:
 
 | Entry id | Href | Title |
 | --- | --- | --- |
 | `edit-run` | `./index.html` | Open edit and run panel |
 | `control-view` | `./control-page.html` | Open read-only control view |
 
+Launcher pages can render links from `createIniPanelLauncherLinkViewModel()`
+without reading manifest field names directly. Each item has `entryId`, `href`,
+and `label`.
+
 ## Boundary
 
 The entry shell only links pages and renders already-observed panel state. It