收口 INI 面板 persistence summary 发布门禁

wasm-port/docs/panel-entry.md

@@ -76,6 +76,9 @@ import {
   createIniPanelShellViewModel,
   getIniPanelEntryByHref,
   getVisibleIniPanelEntries,
+  createMachineSessionPersistenceDisplayViewModel,
+  createMachineSessionPersistenceRenderState,
+  createMachineSessionPersistenceSummary,
   createMachineSessionControlPageController,
   createMachineSessionReadonlyStatus,
   createMachineSessionReadonlyStatusApiManifest,
@@ -138,6 +141,17 @@ needs a read-only `ready`/`blocked` readiness report before loading a machine
 session into WASM. `createMachineSessionReadinessFieldState()` and
 `machineSessionReadinessLogLines()` turn that report into stable fields and
 status text without parsing G-code or executing LinuxCNC behavior.
+Use `createMachineSessionPersistenceSummary()` or
+`linuxCncIniPanelApi.getMachineSessionPersistenceSummary()` when a browser
+panel or outer shell needs one read-only OPFS/session persistence summary with
+machine-file, session snapshot, session readiness, session load, readonly
+status, and handoff readiness rows. The launch page exposes the same helper as
+`linuxCncIniPanelLaunchApi.getMachineSessionPersistenceSummary()`, and the
+workflow overview page exposes it as
+`linuxCncIniPanelWorkflowOverviewApi.getWorkflowOverviewPersistenceSummary()`.
+Use `createMachineSessionPersistenceDisplayViewModel()` and
+`createMachineSessionPersistenceRenderState()` when that summary needs stable
+display text, rows, status line, and dataset fields for caller-owned DOM.
 Use `createIniPanelShellControlPageContract()` or `controlPage.contract` when
 an outer shell needs a fast contract check for `createController`,
 `loadSessionState`, `readStatus`, `refresh`, `renderView`, the readonly status
@@ -306,9 +320,16 @@ the same report through
 Use `createIniPanelShellApiSurfaceInventory()` or
 `linuxCncIniPanelLaunchApi.getShellApiSurfaceInventory()` when an outer shell
 needs a machine-readable inventory of launch, control-page, workflow overview,
-persistence, and session readiness report API counts. The workflow overview
-page exposes the same inventory through
+persistence capabilities, session readiness report rows, and persistence
+summary rows. The workflow overview page exposes the same inventory through
 `linuxCncIniPanelWorkflowOverviewApi.getWorkflowOverviewApiSurfaceInventory()`.
+When provided to `createIniPanelShellSessionHandoffWorkflowSummary()`, the
+inventory is also rendered as the read-only `api-surface-inventory` workflow
+summary row for browser overview pages and external shells. The same workflow
+summary accepts `persistenceSummary` from
+`createMachineSessionPersistenceSummary()` and renders it as the
+`persistence-summary` row, so a shell overview can show API coverage and
+OPFS/session persistence state together.
 Use
 `createIniPanelShellSessionHandoffWorkflowDisplayViewModel()` or
 `linuxCncIniPanelLaunchApi.getShellSessionHandoffWorkflowDisplayViewModel()`

wasm-port/docs/project-release-handoff.md

@@ -32,7 +32,16 @@ continuation records are in `../text14.txt`.
 - SDK callers should import stable helpers from `runtime/sdk/src/index.js`,
   including `createIniPanelShellApiSurfaceInventory()` for API discovery and
   `createIniPanelShellSessionReadinessWorkflowReport()` when they need
-  machine-readable session readiness phase and missing reasons.
+  machine-readable session readiness phase and missing reasons. The workflow
+  overview exposes the API surface inventory as a read-only summary row.
+- OPFS/session callers can use `createMachineSessionPersistenceSummary()` or
+  `linuxCncIniPanelApi.getMachineSessionPersistenceSummary()` to inspect
+  machine files, session snapshot, session readiness, session load, readonly
+  status, and shell handoff readiness as stable rows. Shell handoff workflow
+  summaries can include that report as the `persistence-summary` row beside the
+  API surface inventory row, and launch/workflow-overview APIs expose the same
+  helper for external shells. The summary also has display and render-state
+  helpers for caller-owned DOM.
 - OPFS/session persistence is host-side storage glue. Parameter and tool-table
   behavior still comes from the LinuxCNC-backed interpreter SDK calls.
 - Sim-config inventory promotion remains evidence-driven and must keep