@dimina-kit/devtools 0.4.0-dev.20260729062524 → 0.4.0-dev.20260731100034

package/dist/preload/windows/simulator.js

@@ -341,6 +341,49 @@ function installSimulatorBridge() {
 // src/preload/runtime/custom-apis.ts
 var import_electron2 = require("electron");
 
+// ../dimina-electron-runtime/dist/shared/bridge-channels.js
+var BRIDGE_CHANNELS = {
+  SPAWN: "dmb:spawn",
+  DISPOSE: "dmb:dispose",
+  PAGE_OPEN: "dmb:page:open",
+  PAGE_CLOSE: "dmb:page:close",
+  PAGE_LIFECYCLE: "dmb:page:lifecycle",
+  NAV_CALLBACK: "dmb:nav:callback",
+  SERVICE_INVOKE: "dmb:service:invoke",
+  SERVICE_PUBLISH: "dmb:service:publish",
+  RENDER_INVOKE: "dmb:render:invoke",
+  RENDER_PUBLISH: "dmb:render:publish",
+  TO_SERVICE: "dmb:to-service",
+  TO_RENDER: "dmb:to-render",
+  SIMULATOR_API: "dmb:simulator-api",
+  /** simulator → main: ack of an API_CALL request (carries success/fail args). */
+  API_RESPONSE: "dmb:api:response",
+  /**
+   * simulator webview preload → main (sendSync): "is native-host mode on?".
+   * The guest preload can't read the launch `process.env`, so it asks main
+   * (which can) at install time. Reply is `e.returnValue = boolean`.
+   */
+  NATIVE_HOST_ENABLED: "dmb:native-host-enabled",
+  /**
+   * simulator (DeviceShell) → main: the visible top-of-stack page bridgeId.
+   * Main has no z-order concept — the active page lives only in DeviceShell's
+   * ShellState — so devtools panels / automation that must target "the current
+   * page's render webContents" resolve it through this signal. Fire-and-forget.
+   */
+  ACTIVE_PAGE: "dmb:active-page",
+  /**
+   * simulator (DeviceShell) → main: the FULL ordered page stack (bottom→top)
+   * whenever it changes. Main has no stack of its own (it only learns the
+   * active bridgeId via ACTIVE_PAGE), so automation's `App.getPageStack` needs
+   * this to report multi-page stacks. Fire-and-forget.
+   */
+  PAGE_STACK: "dmb:page-stack"
+};
+var SimulatorCustomApiBridgeChannel = {
+  Request: "simulator:custom-apis:bridge-request",
+  Response: "simulator:custom-apis:bridge-response"
+};
+
 // src/shared/ipc-channels.ts
 var SimulatorChannel = {
   // Ask main to create the simulator as a top-level WebContentsView (so nested
@@ -365,10 +408,6 @@ var SimulatorChannel = {
   // string (same bare format as `getCurrentPagePath`), or '' when unknown.
   CurrentPage: "simulator:current-page"
 };
-var SimulatorCustomApiBridgeChannel = {
-  Request: "simulator:custom-apis:bridge-request",
-  Response: "simulator:custom-apis:bridge-response"
-};
 
 // src/preload/runtime/custom-apis.ts
 var LIST_RETRY_INTERVAL_MS = 150;
@@ -654,7 +693,7 @@ function createAppDataSource() {
   };
 }
 
-// src/shared/request-core.ts
+// ../dimina-electron-runtime/dist/shared/request-core.js
 var DEFAULT_REQUEST_TIMEOUT_MS = 6e4;
 var MAX_TIMEOUT_MS = 2147483647;
 function resolveTimeoutBudgetMs(timeout) {
@@ -664,9 +703,11 @@ function resolveTimeoutBudgetMs(timeout) {
 function buildHeaders(header) {
   const headers = new Headers();
   for (const [key, value] of Object.entries(header ?? {})) {
-    if (value != null) headers.set(key, String(value));
+    if (value != null)
+      headers.set(key, String(value));
   }
-  if (!headers.has("content-type")) headers.set("content-type", "application/json");
+  if (!headers.has("content-type"))
+    headers.set("content-type", "application/json");
   return headers;
 }
 function appendQueryParams(url, data) {
@@ -678,7 +719,8 @@ function appendQueryParams(url, data) {
   return resolved.toString();
 }
 function encodeBody(data, contentType) {
-  if (typeof data === "string") return data;
+  if (typeof data === "string")
+    return data;
   if (contentType.includes("application/x-www-form-urlencoded")) {
     const form = new URLSearchParams();
     for (const [key, value] of Object.entries(data)) {
@@ -693,7 +735,8 @@ async function decodeResponseData(response, dataType, responseType) {
     return response.arrayBuffer();
   }
   const text = await response.text();
-  if (dataType !== "json") return text;
+  if (dataType !== "json")
+    return text;
   try {
     return JSON.parse(text);
   } catch {
@@ -717,14 +760,16 @@ function performRequest(opts, callbacks) {
   init.signal = controller.signal;
   let settled = false;
   function settleSuccess(res) {
-    if (settled) return;
+    if (settled)
+      return;
     settled = true;
     clearTimeout(timer);
     callbacks.success?.(res);
     callbacks.complete?.(res);
   }
   function settleFail(err) {
-    if (settled) return;
+    if (settled)
+      return;
     settled = true;
     clearTimeout(timer);
     callbacks.fail?.(err);
@@ -909,44 +954,19 @@ function setupApiCompatHook() {
 // src/preload/runtime/native-host.ts
 var import_electron5 = require("electron");
 
-// src/shared/bridge-channels.ts
-var BRIDGE_CHANNELS = {
-  SPAWN: "dmb:spawn",
-  DISPOSE: "dmb:dispose",
-  PAGE_OPEN: "dmb:page:open",
-  PAGE_CLOSE: "dmb:page:close",
-  PAGE_LIFECYCLE: "dmb:page:lifecycle",
-  NAV_CALLBACK: "dmb:nav:callback",
-  SERVICE_INVOKE: "dmb:service:invoke",
-  SERVICE_PUBLISH: "dmb:service:publish",
-  RENDER_INVOKE: "dmb:render:invoke",
-  RENDER_PUBLISH: "dmb:render:publish",
-  TO_SERVICE: "dmb:to-service",
-  TO_RENDER: "dmb:to-render",
-  SIMULATOR_API: "dmb:simulator-api",
-  /** simulator → main: ack of an API_CALL request (carries success/fail args). */
-  API_RESPONSE: "dmb:api:response",
-  /**
-   * simulator webview preload → main (sendSync): "is native-host mode on?".
-   * The guest preload can't read the launch `process.env`, so it asks main
-   * (which can) at install time. Reply is `e.returnValue = boolean`.
-   */
-  NATIVE_HOST_ENABLED: "dmb:native-host-enabled",
-  /**
-   * simulator (DeviceShell) → main: the visible top-of-stack page bridgeId.
-   * Main has no z-order concept — the active page lives only in DeviceShell's
-   * ShellState — so devtools panels / automation that must target "the current
-   * page's render webContents" resolve it through this signal. Fire-and-forget.
-   */
-  ACTIVE_PAGE: "dmb:active-page",
-  /**
-   * simulator (DeviceShell) → main: the FULL ordered page stack (bottom→top)
-   * whenever it changes. Main has no stack of its own (it only learns the
-   * active bridgeId via ACTIVE_PAGE), so automation's `App.getPageStack` needs
-   * this to report multi-page stacks. Fire-and-forget.
-   */
-  PAGE_STACK: "dmb:page-stack"
-};
+// ../dimina-electron-runtime/dist/shared/dmb-resource-url.js
+var DMB_SDK_PREFIX = "/__sdk__/";
+function buildRenderHostDocumentUrl(opts) {
+  const url = new URL(`dmb-resource://${opts.bridgeId}${DMB_SDK_PREFIX}render-host/pageFrame.html`);
+  url.searchParams.set("bridgeId", opts.bridgeId);
+  url.searchParams.set("appId", opts.appId);
+  url.searchParams.set("pagePath", opts.pagePath);
+  if (opts.isTab)
+    url.searchParams.set("isTab", "1");
+  if (opts.backgroundColor)
+    url.searchParams.set("bgColor", opts.backgroundColor);
+  return url.toString();
+}
 
 // src/preload/runtime/native-host.ts
 function queryNativeHostConfig() {
@@ -990,13 +1010,7 @@ function buildBridge2(cfg) {
       import_electron5.ipcRenderer.send(BRIDGE_CHANNELS.PAGE_STACK, payload);
     },
     createRenderHostUrl(opts) {
-      const url = new URL(cfg.renderHostHtmlUrl);
-      url.searchParams.set("bridgeId", opts.bridgeId);
-      url.searchParams.set("appId", opts.appId);
-      url.searchParams.set("pagePath", opts.pagePath);
-      if (opts.isTab) url.searchParams.set("isTab", "1");
-      if (opts.backgroundColor) url.searchParams.set("bgColor", opts.backgroundColor);
-      return url.toString();
+      return buildRenderHostDocumentUrl(opts);
     },
     renderPreloadUrl: cfg.renderPreloadUrl,
     device: cfg.device,
@@ -1017,12 +1031,25 @@ function installNativeHostBridge() {
   return exposeOnMainWorld("__diminaNativeHost", buildBridge2(cfg));
 }
 
+// src/preload/runtime/clipboard.ts
+var import_electron6 = require("electron");
+function buildBridge3() {
+  return {
+    readText: () => import_electron6.clipboard.readText(),
+    writeText: (text) => import_electron6.clipboard.writeText(text)
+  };
+}
+function installClipboardBridge() {
+  return exposeOnMainWorld("__diminaClipboard", buildBridge3());
+}
+
 // src/preload/windows/simulator.ts
 setupApiCompatHook();
 installSimulatorBridge();
 installCustomApisBridge();
 installTempFileBridge();
 installConsoleInstrumentation();
+installClipboardBridge();
 installNativeHostBridge();
 createAppDataSource().start(() => {
 });

package/dist/shared/bridge-channels.d.ts

@@ -1,420 +1,2 @@
-import type { NativeDeviceInfo } from './ipc-channels.js';
-export declare const BRIDGE_CHANNELS: {
-    readonly SPAWN: "dmb:spawn";
-    readonly DISPOSE: "dmb:dispose";
-    readonly PAGE_OPEN: "dmb:page:open";
-    readonly PAGE_CLOSE: "dmb:page:close";
-    readonly PAGE_LIFECYCLE: "dmb:page:lifecycle";
-    readonly NAV_CALLBACK: "dmb:nav:callback";
-    readonly SERVICE_INVOKE: "dmb:service:invoke";
-    readonly SERVICE_PUBLISH: "dmb:service:publish";
-    readonly RENDER_INVOKE: "dmb:render:invoke";
-    readonly RENDER_PUBLISH: "dmb:render:publish";
-    readonly TO_SERVICE: "dmb:to-service";
-    readonly TO_RENDER: "dmb:to-render";
-    readonly SIMULATOR_API: "dmb:simulator-api";
-    /** simulator → main: ack of an API_CALL request (carries success/fail args). */
-    readonly API_RESPONSE: "dmb:api:response";
-    /**
-     * simulator webview preload → main (sendSync): "is native-host mode on?".
-     * The guest preload can't read the launch `process.env`, so it asks main
-     * (which can) at install time. Reply is `e.returnValue = boolean`.
-     */
-    readonly NATIVE_HOST_ENABLED: "dmb:native-host-enabled";
-    /**
-     * simulator (DeviceShell) → main: the visible top-of-stack page bridgeId.
-     * Main has no z-order concept — the active page lives only in DeviceShell's
-     * ShellState — so devtools panels / automation that must target "the current
-     * page's render webContents" resolve it through this signal. Fire-and-forget.
-     */
-    readonly ACTIVE_PAGE: "dmb:active-page";
-    /**
-     * simulator (DeviceShell) → main: the FULL ordered page stack (bottom→top)
-     * whenever it changes. Main has no stack of its own (it only learns the
-     * active bridgeId via ACTIVE_PAGE), so automation's `App.getPageStack` needs
-     * this to report multi-page stacks. Fire-and-forget.
-     */
-    readonly PAGE_STACK: "dmb:page-stack";
-};
-export declare const SIMULATOR_EVENTS: {
-    readonly DOM_READY: "simulator:dom-ready";
-    readonly NAV_BAR: "simulator:navigation-bar";
-    readonly NAV_ACTION: "simulator:nav-action";
-    readonly TAB_ACTION: "simulator:tab-action";
-    /** main → simulator: invoke a wx.* API on the simulator-resident MiniApp. */
-    readonly API_CALL: "simulator:api-call";
-    /**
-     * main → simulator: the renderer toolbar picked a different device. Carries a
-     * NativeDeviceInfo; DeviceShell resizes the bezel + re-renders status bar /
-     * notch. The race-free INITIAL device rides NativeHostConfig.device (read
-     * synchronously at preload bridge-install); this event covers live changes.
-     */
-    readonly DEVICE_CHANGE: "simulator:device-change";
-    /**
-     * main → simulator: a watcher rebuild finished; boot a NEW app session for
-     * the carried url ({@link RelaunchPayload}) IN PLACE, keeping the live
-     * DeviceShell painted, and swap once the new session's root page reports
-     * DOM_READY (ready-then-swap soft reload). Main sends this only when the
-     * shell is live+ready; otherwise the renderer falls back to the hard
-     * attachNativeSimulator rebuild.
-     */
-    readonly RELAUNCH: "simulator:relaunch";
-};
-/**
- * `simulator:relaunch` payload. `url` is a full simulator URL (same format as
- * the simulator page's own location / AttachNative), carrying the appId and
- * the page route the new session must boot at.
- */
-export interface RelaunchPayload {
-    url: string;
-}
-export declare const CHANNELS: {
-    readonly SPAWN: "dmb:spawn";
-    readonly DISPOSE: "dmb:dispose";
-    readonly PAGE_OPEN: "dmb:page:open";
-    readonly PAGE_CLOSE: "dmb:page:close";
-    readonly PAGE_LIFECYCLE: "dmb:page:lifecycle";
-    readonly NAV_CALLBACK: "dmb:nav:callback";
-    readonly SERVICE_INVOKE: "dmb:service:invoke";
-    readonly SERVICE_PUBLISH: "dmb:service:publish";
-    readonly RENDER_INVOKE: "dmb:render:invoke";
-    readonly RENDER_PUBLISH: "dmb:render:publish";
-    readonly TO_SERVICE: "dmb:to-service";
-    readonly TO_RENDER: "dmb:to-render";
-    readonly SIMULATOR_API: "dmb:simulator-api";
-    /** simulator → main: ack of an API_CALL request (carries success/fail args). */
-    readonly API_RESPONSE: "dmb:api:response";
-    /**
-     * simulator webview preload → main (sendSync): "is native-host mode on?".
-     * The guest preload can't read the launch `process.env`, so it asks main
-     * (which can) at install time. Reply is `e.returnValue = boolean`.
-     */
-    readonly NATIVE_HOST_ENABLED: "dmb:native-host-enabled";
-    /**
-     * simulator (DeviceShell) → main: the visible top-of-stack page bridgeId.
-     * Main has no z-order concept — the active page lives only in DeviceShell's
-     * ShellState — so devtools panels / automation that must target "the current
-     * page's render webContents" resolve it through this signal. Fire-and-forget.
-     */
-    readonly ACTIVE_PAGE: "dmb:active-page";
-    /**
-     * simulator (DeviceShell) → main: the FULL ordered page stack (bottom→top)
-     * whenever it changes. Main has no stack of its own (it only learns the
-     * active bridgeId via ACTIVE_PAGE), so automation's `App.getPageStack` needs
-     * this to report multi-page stacks. Fire-and-forget.
-     */
-    readonly PAGE_STACK: "dmb:page-stack";
-};
-/**
- * Reply to a `NATIVE_HOST_ENABLED` sendSync. Main supplies the render-host
- * file:// URLs (computed with node:path/url, which the simulator webview's
- * preload lacks) so the preload can build the native-host bridge.
- */
-export interface NativeHostConfig {
-    enabled: boolean;
-    renderHostHtmlUrl: string;
-    renderPreloadUrl: string;
-    /**
-     * The currently-selected device, if the renderer already pushed it before the
-     * simulator WCV's preload installed (it does — SetDeviceInfo precedes
-     * AttachNative). DeviceShell reads this as its initial device so it never
-     * mounts with the wrong bezel size while waiting for the first DEVICE_CHANGE.
-     * Absent only on the pre-spawn default path.
-     */
-    device?: NativeDeviceInfo;
-}
-export type BridgeChannel = typeof BRIDGE_CHANNELS[keyof typeof BRIDGE_CHANNELS];
-export type BridgeTarget = 'service' | 'render' | 'container';
-export type BridgeMessageType = 'loadResource' | 'serviceResourceLoaded' | 'renderResourceLoaded' | 'resourceLoaded' | 'firstRender' | 'appShow' | 'appHide' | 'stackShow' | 'stackHide' | 'pageShow' | 'pageHide' | 'pageReady' | 'pageUnload' | 'pageScroll' | 'pageResize' | 'pageRouteDone' | 'mC' | 'mR' | 'mU' | 't' | 'u' | 'ub' | 'triggerCallback' | 'invokeAPI' | 'h5SdkAction' | 'componentError' | 'domReady' | 'print' | 'renderHostReady' | 'serviceHostError' | string;
-export interface MessageEnvelope<TBody extends Record<string, unknown> = Record<string, unknown>> {
-    type: BridgeMessageType;
-    target: BridgeTarget;
-    body: TBody;
-}
-export interface HostEnvSnapshot {
-    brand: string;
-    model: string;
-    platform: string;
-    system: string;
-    version: string;
-    SDKVersion: string;
-    pixelRatio: number;
-    screenWidth: number;
-    screenHeight: number;
-    windowWidth: number;
-    windowHeight: number;
-    statusBarHeight: number;
-    language: string;
-    theme: string;
-    [key: string]: unknown;
-}
-/**
- * Map the renderer's logical device metrics onto the subset of a
- * HostEnvSnapshot the service-host window's `getSystemInfoSync` consumes.
- * `windowHeight` excludes the status bar (the page area); `windowWidth` has no
- * horizontal chrome. Zoom is intentionally absent — it is a display scale, not
- * a logical-size change.
- *
- * Single source of truth for the device→host-env mapping, shared by the live
- * `SetDeviceInfo` IPC path (main/ipc/simulator.ts) and the per-spawn host-env
- * seeding (main/ipc/bridge-router.ts). Keeping them identical guarantees a
- * service-host RESPAWN after a device change reports the same dims the live
- * update pushed — otherwise a respawn would silently revert to the boot device.
- */
-export declare function deviceInfoToHostEnv(d: NativeDeviceInfo): Partial<HostEnvSnapshot>;
-/**
- * Subset of WeChat page `window` config plus tabBar list, parsed from
- * `app-config.json` (`{app:{window,tabBar,pages,entryPagePath}, modules:{[pagePath]:{...flat page.json fields,root?}}}`).
- * `modules[pagePath]` is FLAT — the compiler assigns the page's own `.json` file
- * content as-is (see `dimina/fe/packages/compiler/src/env.js` `collectionPageJson()`),
- * not wrapped under a `.window` key. Mirrors mergePageConfig in dimina-fe:
- * page-level keys override app-level.
- */
-export interface PageWindowConfig {
-    navigationBarTitleText?: string;
-    navigationBarBackgroundColor?: string;
-    navigationBarTextStyle?: 'black' | 'white';
-    navigationStyle?: 'default' | 'custom';
-    homeButton?: boolean;
-    backgroundColor?: string;
-    backgroundTextStyle?: 'dark' | 'light';
-    enablePullDownRefresh?: boolean;
-    disableScroll?: boolean;
-    [key: string]: unknown;
-}
-export interface TabBarItem {
-    pagePath: string;
-    text?: string;
-    iconPath?: string;
-    selectedIconPath?: string;
-}
-export interface TabBarConfig {
-    color?: string;
-    selectedColor?: string;
-    backgroundColor?: string;
-    borderStyle?: 'black' | 'white';
-    position?: 'bottom' | 'top';
-    custom?: boolean;
-    list: TabBarItem[];
-}
-export interface AppManifest {
-    entryPagePath: string;
-    pages: string[];
-    tabBar?: TabBarConfig;
-    /**
-     * Provenance of this manifest: `'app-config'` when built from a real
-     * compiled `app-config.json` (its `pages` list is authoritative, so mount
-     * gates can validate membership against it); `'fallback'` when
-     * app-config.json was unreachable and the manifest is a single-page stand-in
-     * built from the spawn request. Mount gates only enforce against
-     * `'app-config'` — a `'fallback'` manifest has no compiled truth to check
-     * membership against, so it must let every page/nav target through.
-     */
-    source: 'app-config' | 'fallback';
-}
-export interface SpawnRequest {
-    simulatorWcId?: number;
-    appId: string;
-    bridgeId?: string;
-    pagePath?: string;
-    scene?: number;
-    query?: Record<string, unknown>;
-    apiNamespaces?: string[];
-    hostEnvSnapshot?: Partial<HostEnvSnapshot>;
-    pkgRoot?: string;
-    root?: string;
-    /**
-     * Base URL of the dev server that serves the compiled mini-app, i.e. the
-     * SAME origin the simulator page was loaded from (`http://localhost:<port>/`).
-     * The dev server statically serves `<appId>/<root>/…` (app-config.json,
-     * logic.js, page bundles, styles) — exactly what the default dimina-fe
-     * `<webview>` fetches. The native-host render + service hosts source every
-     * resource from here, so we don't need a second resource server or a local
-     * compiled-output path. Trailing slash expected.
-     */
-    resourceBaseUrl?: string;
-}
-export interface SpawnResult {
-    appSessionId: string;
-    bridgeId: string;
-    /** The pagePath originally requested (unchanged even when a fallback applied — see `resolvedPagePath`). */
-    pagePath: string;
-    /**
-     * The pagePath the root PageSession was ACTUALLY spawned with. Equal to
-     * `pagePath` unless `pageFallbackApplied` is true, in which case the request
-     * was absent from `manifest.pages` and this is `manifest.entryPagePath`
-     * (or `manifest.pages[0]` when even that isn't a member). Callers that cache
-     * "the current page" (e.g. `SimulatorMiniApp`) must reconcile against this,
-     * not the original request.
-     */
-    resolvedPagePath: string;
-    /** Whether `resolvedPagePath` differs from the request because it was absent from the compiled manifest. Always false for a `'fallback'` manifest (nothing to validate against). */
-    pageFallbackApplied: boolean;
-    serviceWcId: number;
-    resourceBaseUrl: string;
-    manifest: AppManifest;
-    rootWindowConfig: PageWindowConfig;
-}
-export interface PageOpenRequest {
-    appSessionId: string;
-    pagePath: string;
-    query?: Record<string, unknown>;
-    bridgeId?: string;
-}
-export interface PageOpenResult {
-    bridgeId: string;
-    pagePath: string;
-    windowConfig: PageWindowConfig;
-    isTab: boolean;
-}
-export interface PageClosePayload {
-    bridgeId: string;
-}
-export interface DisposePayload {
-    /** AppSession root bridgeId (legacy) or any page bridgeId. */
-    bridgeId: string;
-}
-export type PageLifecycleEvent = 'pageShow' | 'pageHide' | 'pageUnload' | 'stackShow' | 'stackHide' | 'appShow' | 'appHide';
-export interface PageLifecyclePayload {
-    appSessionId: string;
-    bridgeId: string;
-    event: PageLifecycleEvent;
-}
-/**
- * Sent by simulator after a routing action (navigateTo etc.) completes so the
- * main process can call sendCallback() against the original service-issued
- * success/fail/complete ids.
- */
-export interface NavCallbackPayload {
-    appSessionId: string;
-    ok: boolean;
-    errMsg: string;
-    callbacks: {
-        success?: unknown;
-        fail?: unknown;
-        complete?: unknown;
-    };
-}
-export interface ServiceInvokePayload {
-    bridgeId: string;
-    msg: MessageEnvelope;
-}
-export interface ServicePublishPayload {
-    bridgeId: string;
-    targetBridgeId?: string;
-    msg: MessageEnvelope;
-}
-/**
- * `dmb:active-page` — simulator (DeviceShell) → main. Records which page is the
- * visible top-of-stack so main-side services (WXML/element-inspect, automation)
- * can resolve "the active page's render webContents" by bridgeId.
- */
-export interface ActivePagePayload {
-    appSessionId: string;
-    bridgeId: string;
-}
-/**
- * `dmb:page-stack` — simulator (DeviceShell) → main. The full ordered page
- * stack (bottom→top) so `App.getPageStack` can report multi-page stacks.
- */
-export interface PageStackEntry {
-    pagePath: string;
-    query: Record<string, unknown>;
-}
-export interface PageStackPayload {
-    appSessionId: string;
-    stack: PageStackEntry[];
-}
-export interface RenderInvokePayload {
-    bridgeId: string;
-    msg: MessageEnvelope;
-}
-export interface RenderPublishPayload {
-    bridgeId: string;
-    msg: MessageEnvelope;
-}
-export interface ToServicePayload {
-    msg: MessageEnvelope;
-}
-export interface ToRenderPayload {
-    msg: MessageEnvelope;
-}
-export interface SimulatorApiInvokePayload {
-    bridgeId: string;
-    name: string;
-    params: unknown;
-}
-/**
- * `simulator:nav-action` — main → simulator window, carries router/tabBar
- * intentions. Simulator owns the visual stack state and decides whether to
- * push/pop webviews; it then calls back PAGE_LIFECYCLE + NAV_CALLBACK.
- */
-export interface NavActionPayload {
-    appSessionId: string;
-    bridgeId: string;
-    name: 'navigateTo' | 'navigateBack' | 'redirectTo' | 'reLaunch' | 'switchTab';
-    params: Record<string, unknown>;
-    callbacks: {
-        success?: unknown;
-        fail?: unknown;
-        complete?: unknown;
-    };
-}
-/**
- * `simulator:api-call` — main → simulator. Fallback path used when an
- * invokeAPI name is not registered in the main-process `ctx.simulatorApis`
- * registry: the simulator-resident MiniApp owns the wx.* handler (it can
- * read DOM, open file pickers, etc.), so we forward the call there and wait
- * for an `API_RESPONSE` ack.
- */
-export interface ApiCallPayload {
-    appSessionId: string;
-    bridgeId: string;
-    requestId: string;
-    name: string;
-    params: Record<string, unknown>;
-    callbacks: {
-        success?: unknown;
-        fail?: unknown;
-        complete?: unknown;
-    };
-}
-/**
- * `dmb:api:response` — simulator → main. Ack for an `API_CALL`. Main looks
- * up `requestId` in its pending map and fires the original service-side
- * success/fail/complete callbacks accordingly.
- */
-export interface ApiResponsePayload {
-    appSessionId: string;
-    requestId: string;
-    ok: boolean;
-    /** Argument the simulator-side success/fail callback was invoked with. */
-    result?: unknown;
-    errMsg?: string;
-    /**
-     * Persistent-subscription marker (`keep: true` APIs, e.g.
-     * `audioListen`). When set, this response is one of potentially many
-     * fires of the same subscription: main re-fires the service-side success
-     * callback but keeps the pendingApiCall alive (does not delete it or fire
-     * `complete`) so subsequent fires of the same `requestId` are delivered.
-     * Cleanup happens on page/app teardown instead.
-     */
-    keep?: boolean;
-}
-/**
- * `simulator:tab-action` — main → simulator window, carries dynamic TabBar
- * API calls. Simulator updates TabBar React state and acknowledges via
- * NAV_CALLBACK so the service-side wx.* callback fires.
- */
-export interface TabActionPayload {
-    appSessionId: string;
-    bridgeId: string;
-    name: 'setTabBarStyle' | 'setTabBarItem' | 'showTabBar' | 'hideTabBar' | 'setTabBarBadge' | 'removeTabBarBadge' | 'showTabBarRedDot' | 'hideTabBarRedDot';
-    params: Record<string, unknown>;
-    callbacks: {
-        success?: unknown;
-        fail?: unknown;
-        complete?: unknown;
-    };
-}
+export * from '@dimina-kit/electron-runtime/shared/bridge-channels';
 //# sourceMappingURL=bridge-channels.d.ts.map