@ethisyscore/vite-plugin 1.32.0 → 1.34.0

package/dist/index.d.cts

@@ -239,6 +239,24 @@ interface PlatformReactPageDeclaration {
     title?: string;
     [key: string]: unknown;
 }
+/**
+ * The singular PlatformReact overlay declaration extracted from
+ * `ui.platformReactOverlay` in the manifest (WI 5160 SP-A).
+ * At most one overlay is permitted per plugin manifest.
+ *
+ * - `id` is the host-side overlay identifier and the basename of the emitted
+ *   bundle (e.g. `id: "ai-overlay"` → `platform-react/ai-overlay.js`).
+ * - `moduleSpecifier` is a host-origin relative path to the overlay module.
+ * - `exportName` is the named export the host loader reads at mount time.
+ * - `title` is an optional display label for the host's surface chrome.
+ */
+interface PlatformReactOverlayDeclaration {
+    id?: string;
+    moduleSpecifier?: string;
+    exportName?: string;
+    title?: string;
+    [key: string]: unknown;
+}
 /**
  * The subset of a manifest this pass consumes. Manifests are tolerated as a
  * superset — extra fields are ignored so newer-schema manifests still load.
@@ -247,6 +265,7 @@ interface PlatformReactManifest {
     type?: string;
     ui?: {
         platformReactPages?: PlatformReactPageDeclaration[];
+        platformReactOverlay?: PlatformReactOverlayDeclaration;
         [key: string]: unknown;
     };
     [key: string]: unknown;
@@ -557,6 +576,22 @@ interface PlatformReactPageEntry {
     /** View name → src-relative module path, read by the page's `useView(<module>, name)`. */
     views: Record<string, string>;
 }
+/**
+ * The singular `ui.platformReactOverlay` entry (feature-manifest form, incl. the build-only `views`).
+ * Mirrors {@link PlatformReactPageEntry} minus `route` — overlays are not routed.
+ * `views` is a build-time wiring artifact consumed by `build-pages` to synthesise the
+ * virtual entry's `definePluginOverlay(Overlay, { ...views })` call, exactly as page `views` are.
+ * It is NOT part of the protocol `PlatformReactOverlayDeclaration` and is stripped at the
+ * wire/admission boundary (parallel to how page `views` are stripped).
+ */
+interface PlatformReactOverlayEntry {
+    id: string;
+    moduleSpecifier: string;
+    exportName: string;
+    title: string;
+    /** View name → src-relative module path (build-time wiring only; stripped from the wire manifest). */
+    views: Record<string, string>;
+}
 /**
  * Per-page override, keyed by page filename (incl. `.tsx`). For plugins whose page
  * ids/titles are NOT derived from the filename (e.g. `Timesheets.tsx` → id
@@ -634,6 +669,13 @@ interface GeneratePlatformReactManifestConfig {
     slug?: string;
     /** Metadata written into `feature.manifest.json`. */
     manifest: PlatformReactManifestMeta;
+    /**
+     * Singular overlay declaration. When present, emits `ui.platformReactOverlay` in
+     * `feature.manifest.json` (with `views` for build-pages virtual-entry synthesis) and
+     * in the `extension.manifest.json` wire overlay (without `views`, mirroring the page
+     * strip). Omit to suppress the key entirely.
+     */
+    overlay?: PlatformReactOverlayEntry;
     /**
      * Per-page id/title/route overrides, keyed by page filename (incl. `.tsx`). Only
      * needed for plugins whose ids/titles aren't the filename-derived defaults; omit

package/dist/index.d.ts

@@ -239,6 +239,24 @@ interface PlatformReactPageDeclaration {
     title?: string;
     [key: string]: unknown;
 }
+/**
+ * The singular PlatformReact overlay declaration extracted from
+ * `ui.platformReactOverlay` in the manifest (WI 5160 SP-A).
+ * At most one overlay is permitted per plugin manifest.
+ *
+ * - `id` is the host-side overlay identifier and the basename of the emitted
+ *   bundle (e.g. `id: "ai-overlay"` → `platform-react/ai-overlay.js`).
+ * - `moduleSpecifier` is a host-origin relative path to the overlay module.
+ * - `exportName` is the named export the host loader reads at mount time.
+ * - `title` is an optional display label for the host's surface chrome.
+ */
+interface PlatformReactOverlayDeclaration {
+    id?: string;
+    moduleSpecifier?: string;
+    exportName?: string;
+    title?: string;
+    [key: string]: unknown;
+}
 /**
  * The subset of a manifest this pass consumes. Manifests are tolerated as a
  * superset — extra fields are ignored so newer-schema manifests still load.
@@ -247,6 +265,7 @@ interface PlatformReactManifest {
     type?: string;
     ui?: {
         platformReactPages?: PlatformReactPageDeclaration[];
+        platformReactOverlay?: PlatformReactOverlayDeclaration;
         [key: string]: unknown;
     };
     [key: string]: unknown;
@@ -557,6 +576,22 @@ interface PlatformReactPageEntry {
     /** View name → src-relative module path, read by the page's `useView(<module>, name)`. */
     views: Record<string, string>;
 }
+/**
+ * The singular `ui.platformReactOverlay` entry (feature-manifest form, incl. the build-only `views`).
+ * Mirrors {@link PlatformReactPageEntry} minus `route` — overlays are not routed.
+ * `views` is a build-time wiring artifact consumed by `build-pages` to synthesise the
+ * virtual entry's `definePluginOverlay(Overlay, { ...views })` call, exactly as page `views` are.
+ * It is NOT part of the protocol `PlatformReactOverlayDeclaration` and is stripped at the
+ * wire/admission boundary (parallel to how page `views` are stripped).
+ */
+interface PlatformReactOverlayEntry {
+    id: string;
+    moduleSpecifier: string;
+    exportName: string;
+    title: string;
+    /** View name → src-relative module path (build-time wiring only; stripped from the wire manifest). */
+    views: Record<string, string>;
+}
 /**
  * Per-page override, keyed by page filename (incl. `.tsx`). For plugins whose page
  * ids/titles are NOT derived from the filename (e.g. `Timesheets.tsx` → id
@@ -634,6 +669,13 @@ interface GeneratePlatformReactManifestConfig {
     slug?: string;
     /** Metadata written into `feature.manifest.json`. */
     manifest: PlatformReactManifestMeta;
+    /**
+     * Singular overlay declaration. When present, emits `ui.platformReactOverlay` in
+     * `feature.manifest.json` (with `views` for build-pages virtual-entry synthesis) and
+     * in the `extension.manifest.json` wire overlay (without `views`, mirroring the page
+     * strip). Omit to suppress the key entirely.
+     */
+    overlay?: PlatformReactOverlayEntry;
     /**
      * Per-page id/title/route overrides, keyed by page filename (incl. `.tsx`). Only
      * needed for plugins whose ids/titles aren't the filename-derived defaults; omit