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

package/dist/renderer/entries/main/index.html

@@ -26,7 +26,7 @@
       overflow: hidden;
     }
   </style>
-  <script type="module" crossorigin src="../../assets/index-BJlFbXHb.js"></script>
+  <script type="module" crossorigin src="../../assets/index-BBg3YI5b.js"></script>
   <link rel="modulepreload" crossorigin href="../../assets/ipc-transport-B3EpmfNS.js">
   <link rel="modulepreload" crossorigin href="../../assets/input-xdmfv-eH.js">
   <link rel="modulepreload" crossorigin href="../../assets/select-CD9CJyhI.js">

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

package/dist/shared/bridge-channels.js

@@ -1,90 +1,2 @@
-export const 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',
-};
-export const SIMULATOR_EVENTS = {
-    DOM_READY: 'simulator:dom-ready',
-    NAV_BAR: 'simulator:navigation-bar',
-    NAV_ACTION: 'simulator:nav-action',
-    TAB_ACTION: 'simulator:tab-action',
-    /** main → simulator: invoke a wx.* API on the simulator-resident MiniApp. */
-    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.
-     */
-    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.
-     */
-    RELAUNCH: 'simulator:relaunch',
-};
-export const CHANNELS = BRIDGE_CHANNELS;
-/**
- * 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 function deviceInfoToHostEnv(d) {
-    return {
-        brand: d.brand,
-        model: d.model,
-        system: d.system,
-        platform: d.platform,
-        pixelRatio: d.pixelRatio,
-        screenWidth: d.screenWidth,
-        screenHeight: d.screenHeight,
-        windowWidth: d.screenWidth,
-        windowHeight: Math.max(0, d.screenHeight - d.statusBarHeight),
-        statusBarHeight: d.statusBarHeight,
-    };
-}
+export * from '@dimina-kit/electron-runtime/shared/bridge-channels';
 //# sourceMappingURL=bridge-channels.js.map

package/dist/shared/dmb-resource-url.d.ts

@@ -0,0 +1,2 @@
+export * from '@dimina-kit/electron-runtime/shared/dmb-resource-url';
+//# sourceMappingURL=dmb-resource-url.d.ts.map

package/dist/shared/dmb-resource-url.js

@@ -0,0 +1,2 @@
+export * from '@dimina-kit/electron-runtime/shared/dmb-resource-url';
+//# sourceMappingURL=dmb-resource-url.js.map

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

@@ -14,34 +14,7 @@ export declare const SimulatorChannel: {
     readonly CurrentPage: "simulator:current-page";
 };
 /** iPhone bezel cutout family driving the device-shell notch visual. */
-export type NotchType = 'none' | 'notch' | 'dynamic-island';
-/** Per-device safe-area insets in CSS px (portrait). */
-export interface SafeAreaInsets {
-    top: number;
-    right: number;
-    bottom: number;
-    left: number;
-}
-/**
- * Logical device metrics pushed by the renderer device dropdown under
- * native-host (`SimulatorChannel.SetDeviceInfo`). Mirrors a row of the renderer
- * `DEVICES` table; main maps it onto a `HostEnvSnapshot` for the service-host
- * window so `wx.getSystemInfoSync()` reflects the selected device, relays it to
- * the simulator WCV (DeviceShell: bezel size + status bar + notch), and drives
- * the CSS `env(safe-area-inset-*)` override on render-host guests.
- */
-export interface NativeDeviceInfo {
-    brand: string;
-    model: string;
-    system: string;
-    platform: string;
-    pixelRatio: number;
-    screenWidth: number;
-    screenHeight: number;
-    statusBarHeight: number;
-    notchType: NotchType;
-    safeAreaInsets: SafeAreaInsets;
-}
+export type { NativeDeviceInfo, NotchType, SafeAreaInsets, } from '@dimina-kit/electron-runtime';
 export declare const ServiceHostChannel: {
     /**
      * NATIVE-HOST ONLY. Live-update the service-host window's host-env snapshot
@@ -62,10 +35,7 @@ export declare const ServiceHostChannel: {
 export declare const SimulatorCustomApiChannel: {
     readonly Invoke: "simulator:custom-apis:invoke";
 };
-export declare const SimulatorCustomApiBridgeChannel: {
-    readonly Request: "simulator:custom-apis:bridge-request";
-    readonly Response: "simulator:custom-apis:bridge-response";
-};
+export { SimulatorCustomApiBridgeChannel, } from '@dimina-kit/electron-runtime/shared/bridge-channels';
 export declare const SimulatorStorageChannel: {
     readonly GetSnapshot: "simulator:storage:snapshot";
     readonly GetActivePrefix: "simulator:storage:activePrefix";

package/dist/shared/ipc-channels.js

@@ -68,11 +68,8 @@ export const SimulatorCustomApiChannel = {
 // `<webview>.send`, no longer exists — native-host is the sole runtime.)
 //
 // Request/response are correlated by `id` so multiple concurrent invokes can
-// be in flight at once.
-export const SimulatorCustomApiBridgeChannel = {
-    Request: 'simulator:custom-apis:bridge-request',
-    Response: 'simulator:custom-apis:bridge-response',
-};
+// be in flight at once. The standalone runtime owns the wire contract.
+export { SimulatorCustomApiBridgeChannel, } from '@dimina-kit/electron-runtime/shared/bridge-channels';
 // ── Storage (CDP-backed; main process attaches the debugger to the
 // simulator guest and forwards DOMStorage events to the renderer) ──
 export const SimulatorStorageChannel = {

package/dist/shared/request-core.d.ts

@@ -1,84 +1,2 @@
-/**
- * Single authoritative implementation of wx.request network semantics, shared
- * by every request surface (simulator `directRequest`, preload api-compat
- * `wx.request` shim). Keeping the semantics in one module is what prevents the
- * surfaces from drifting apart on the core contract.
- *
- * The contract (official wx.request semantics):
- *  - success vs fail is decided ONLY by whether a server response was
- *    received. Any HTTP response — 200, 401, 500 — resolves via `success`
- *    with `{ data, statusCode, header, errMsg: 'request:ok' }`; callers
- *    branch on `statusCode` (e.g. 401 → re-login).
- *  - `fail` fires only for network-layer failures and always carries a
- *    non-empty errMsg: 'request:fail timeout' (deadline hit),
- *    'request:fail abort' (caller aborted), 'request:fail <reason>' (DNS/
- *    connection/protocol errors).
- *  - `timeout` defaults to 60000ms (the wx default) when omitted or
- *    non-positive — a request never hangs indefinitely.
- *  - `dataType` (default 'json') controls body decoding: 'json' attempts
- *    JSON.parse with raw-text fallback; anything else keeps raw text.
- *    `responseType: 'arraybuffer'` (or the legacy `dataType: 'arraybuffer'`
- *    spelling) yields an ArrayBuffer instead.
- *  - Outgoing headers merge case-insensitively via `Headers` so a caller's
- *    `content-type` in any casing wins exactly once; the `application/json`
- *    default applies only when the caller supplied none. Plain-object merges
- *    would keep both casings as distinct keys and comma-join them on the wire.
- *  - GET/HEAD serialize object `data` into URL query params (no body);
- *    other methods send string data verbatim, form-encode objects under
- *    application/x-www-form-urlencoded, and JSON-encode otherwise.
- *  - `complete` fires exactly once, after success or fail, with that same
- *    result object.
- *
- * Not provided: `cookies` on the success result — fetch() cannot read
- * Set-Cookie response headers, so surfacing a fabricated list would lie.
- */
-export interface RequestSuccessResult {
-    data: unknown;
-    statusCode: number;
-    header: Record<string, string>;
-    errMsg: 'request:ok';
-}
-export interface RequestFailResult {
-    errMsg: string;
-    errno?: number;
-}
-export interface RequestHandle {
-    abort(): void;
-}
-export interface RequestCoreOptions {
-    url: string;
-    data?: unknown;
-    header?: Record<string, string>;
-    timeout?: number;
-    method?: string;
-    dataType?: string;
-    responseType?: string;
-}
-export interface RequestCoreCallbacks {
-    success?: (res: RequestSuccessResult) => void;
-    fail?: (err: RequestFailResult) => void;
-    complete?: (res: RequestSuccessResult | RequestFailResult) => void;
-}
-/**
- * The wx.request default timeout budget. Exported as the single source of
- * truth for every layer that reasons about a request's time budget — the
- * bridge-router watchdog (apiCallWatchdogMs in simulator-api-metadata.ts)
- * derives its window from this so the two cannot drift apart.
- */
-export declare const DEFAULT_REQUEST_TIMEOUT_MS = 60000;
-/**
- * Largest delay setTimeout honours (2^31-1 ms). Anything above overflows the
- * signed-32-bit timer register and fires ~immediately (~1ms) instead of late —
- * so an oversized caller timeout must be rejected, never passed through.
- */
-export declare const MAX_TIMEOUT_MS = 2147483647;
-/**
- * Resolve a caller-supplied wx timeout into a usable budget: a finite positive
- * number within setTimeout's range is honoured; anything else (absent, 0,
- * negative, NaN, Infinity, overflowing) falls back to the wx default. Shared
- * by performRequest and the bridge-router watchdog (apiCallWatchdogMs) so the
- * two layers can never disagree on what a valid timeout is.
- */
-export declare function resolveTimeoutBudgetMs(timeout: unknown): number;
-export declare function performRequest(opts: RequestCoreOptions, callbacks: RequestCoreCallbacks): RequestHandle;
+export * from '@dimina-kit/electron-runtime/shared/request-core';
 //# sourceMappingURL=request-core.d.ts.map