@aglyn/aglyn 1.0.0-beta.218 → 1.0.0-beta.220

package/src/lib/plugin-manager/feature-plugins.js

@@ -161,7 +161,66 @@ import { _ as _extends } from "@swc/helpers/_/_extends";
    * the test: both are drawn by a console page that is NOT the marketplace —
    * the installation detail page and a site's layouts list — offering a
    * marketplace action in passing.
-   */ /** Bottom of the host dashboard. Props: hostId, org. (AGL-433) */ dashboardFooter: 'dashboardFooter',
+   */ /**
+   * The org Plugins page, above the built-in plugins (AGL-3080): the code a
+   * plugin has INSTALLED into this workspace, one row per installation.
+   * Props: {@link ConsoleOrgPluginInstallsZoneProps}.
+   *
+   * The Plugins page is the workspace's inventory — what it runs, wherever it
+   * came from. The built-in half is the shell's own: the switchboard catalog
+   * says what ships. The installed half is not: where an installation is
+   * pinned, what version it runs, whether a newer one may be installed and
+   * whether its publisher's kill switch is thrown are all facts held by the
+   * plugin that installed it, in collections that are its own. So the page
+   * hands over the sites it can see and the plugin draws its installations.
+   *
+   * Every row links to `/[orgSlug]/plugins/[pluginRef]`, the shell's
+   * installation page, keyed by whatever id the installing plugin pins by —
+   * that page is the one place an installation is managed, whoever drew the
+   * row.
+   */ orgPluginInstalls: 'orgPluginInstalls',
+    /**
+   * The installation page of a plugin some plugin INSTALLED, above where it
+   * runs (AGL-3080): what the installer says about the version this
+   * workspace runs. Props: {@link ConsolePluginInstallStatusZoneProps}.
+   *
+   * Drawn only for an installation that exists — a first-party plugin has no
+   * version to be behind, and a page for code installed nowhere says so
+   * itself. A widget here reports; it never installs. Applying an update is
+   * the installing plugin's own surface, which the widget may link to.
+   */ pluginInstallStatus: 'pluginInstallStatus',
+    /**
+   * The template gallery — "Start from a template" on a site's Screens,
+   * Layouts and Components pages — below the site's own templates and the
+   * starters (AGL-3080): a shelf of templates a plugin offers to INSTALL.
+   * Props: {@link ConsoleTemplateGalleryZoneProps}.
+   *
+   * The gallery is the shell's: what the site holds and what ships with the
+   * platform. Templates offered from elsewhere are the offering plugin's —
+   * what it lists, how it is searched, what it costs and the route that
+   * installs one, with every check that route makes — so the dialog hands
+   * over the kind it picks and the word typed in its search, and the plugin
+   * draws its own shelf. An install lands in the site's library and
+   * publishes nothing; the widget calls `onInstalled` so the gallery closes.
+   *
+   * The dialog's "nothing matches" line covers every shelf, so a widget
+   * reports whether its shelf is loading, empty or showing something through
+   * `reportShelf`. A widget that never reports is a shelf the line ignores;
+   * with no widget at all the gallery is the site's own and the starters.
+   */ templateGallery: 'templateGallery',
+    /**
+   * One row of a site's Templates library whose template a plugin INSTALLED,
+   * beside its Source badge (AGL-3080): what the installer says about the
+   * copy the site holds — that a newer version can be installed, and the
+   * control that installs it. Props: {@link ConsoleTemplateInstallStatusZoneProps}.
+   *
+   * Drawn once per such row, and never for a template saved here or a
+   * starter. A widget draws nothing for a template it did not install, and
+   * nothing when there is nothing to say. Applying an update goes through
+   * the installing plugin's own route, which keeps all its checks; the
+   * library's rows re-read the templates it replaced.
+   */ templateInstallStatus: 'templateInstallStatus',
+    /** Bottom of the host dashboard. Props: hostId, org. (AGL-433) */ dashboardFooter: 'dashboardFooter',
     /** Org settings page, below the tabbed cards. Props: orgId, org. */ orgSettings: 'orgSettings',
     /** Host setup page, below the built-in cards. Props: hostId, org. */ hostSettings: 'hostSettings',
     /**
@@ -211,6 +270,12 @@ import { _ as _extends } from "@swc/helpers/_/_extends";
    * widget.
    */ hostTheme: 'hostTheme',
     /**
+   * The staff overview, among its platform-wide cards (AGL-3080). No props:
+   * the overview is about the platform, not one org, so a widget here reads
+   * what its plugin holds across every workspace through its own staff
+   * route. A staff zone — see {@link CONSOLE_STAFF_WIDGET_SLOTS}.
+   */ staffOverview: 'staffOverview',
+    /**
    * Staff admin org detail (staff-only surfaces). Props: orgId. A staff
    * zone — see {@link CONSOLE_STAFF_WIDGET_SLOTS}.
    */ adminOrgDetail: 'adminOrgDetail',
@@ -280,11 +345,20 @@ import { _ as _extends } from "@swc/helpers/_/_extends";
    * table with `{ hostId, canManage }`.
    */ hostMembers: 'hostMembers',
     /**
-   * The console shell's assistant dock (AGL-2940): the one position above
-   * every route boundary in both the `(app)` and `(editor)` shells, where a
-   * floating helper survives a navigation. Props: none — a widget here
-   * resolves its own scope from the URL, as the shell's own chrome does.
-   */ assistPanel: 'assistPanel',
+   * One visitor account's drawer on a site's Users page (AGL-546), under the
+   * account's password controls and above its saved addresses: what a plugin
+   * holds about the person behind the account — what they bought, what they
+   * subscribe to. Props: {@link ConsoleSiteMemberZoneProps}. Each widget is
+   * one section of the drawer's own column, which spaces it; the drawer
+   * draws the account itself, its suspension and its password help.
+   */ siteMember: 'siteMember',
+    /**
+   * The console dock (AGL-2940): the one position above every route boundary
+   * in both the `(app)` and `(editor)` shells, where a floating panel — an
+   * assistant, a helper — survives a navigation. Props:
+   * {@link ConsoleDockZoneProps}. Named for the position, not for what a
+   * plugin puts there (AGL-3080: it was `assistPanel`).
+   */ consoleDock: 'consoleDock',
     /**
    * A section at the bottom of the besigner's Attributes panel (AGL-2940),
    * under the selected element's own fields. Props: `hostId` (`null` on an
@@ -292,6 +366,19 @@ import { _ as _extends } from "@swc/helpers/_/_extends";
    * — present wherever the designer draws the panel for a selection.
    */ besignerInspector: 'besignerInspector',
     /**
+   * The besigner's Interactions section, on every editor that offers one
+   * (AGL-3080): the section experiments a plugin runs on a page's elements.
+   * Props: {@link ConsoleBesignerInteractionsZoneProps}.
+   *
+   * The section is the designer's, and so are an element's own interactions:
+   * they live on its node and ride the document's save. A section experiment
+   * is not a node's: it is a record of whichever plugin runs experiments,
+   * stored where that plugin keeps them. So a widget here draws nothing. It
+   * reads its own records and REPORTS them, and the section badges an element
+   * and offers to start one from what was reported. With no widget the
+   * section offers none, which is a workspace with no plugin that runs them.
+   */ besignerInteractions: 'besignerInteractions',
+    /**
    * Inside a SEARCH LISTING editor (AGL-2910), under its fields. Props:
    * {@link ConsoleSeoFieldsZoneProps} — what the listing describes, the
    * fields the editor edits and what they hold, and `proposeValues`, which
@@ -305,11 +392,11 @@ import { _ as _extends } from "@swc/helpers/_/_extends";
    * a translation memory and a generator are the same shape of widget.
    */ seoFields: 'seoFields',
     /**
-   * The host setup SEO section, above the site SEO form (AGL-2910). Props:
-   * {@link ConsoleHostSeoZoneProps} — the site, its stored SEO settings, and
-   * `proposeDraft`, which puts values in the form as unsaved edits. The
-   * form's Update stores them; nothing a widget proposes reaches the
-   * published site before that.
+   * The host setup SEO section, under the site's SEO check and above the site
+   * SEO form (AGL-2910). Props: {@link ConsoleHostSeoZoneProps} — the site,
+   * its stored SEO settings, the check's last report, and `proposeDraft`,
+   * which puts values in the form as unsaved edits. The form's Update stores
+   * them; nothing a widget proposes reaches the published site before that.
    */ hostSeo: 'hostSeo',
     /** {@link ConsoleRecordInsightsZoneProps} */ recordInsights: 'recordInsights',
     /** {@link ConsoleRecordEmailZoneProps} */ recordEmail: 'recordEmail',
@@ -341,16 +428,6 @@ import { _ as _extends } from "@swc/helpers/_/_extends";
    * {@link ConsoleHostLayoutsZoneProps}, on the `hostScreens` contract.
    */ hostLayouts: 'hostLayouts',
     /**
-   * The Forms page of a site, beside its Create Form action (AGL-3043):
-   * another way to start a form. Props: {@link ConsoleHostFormsZoneProps}, on
-   * the `hostScreens` contract.
-   *
-   * The Forms page is the forms plugin's own surface, so the plugin HOSTS
-   * this zone: it draws the renderer `useConsoleWidgetSlot` hands down, as
-   * the product editor draws `seoFields`, and every gate a console page's
-   * slot applies applies here too.
-   */ hostForms: 'hostForms',
-    /**
    * A site's Components page, beside its Templates and Create Component
    * actions (AGL-3051): another way to start a reusable component. Props:
    * {@link ConsoleHostComponentsZoneProps}, on the `hostScreens` contract.
@@ -367,38 +444,11 @@ import { _ as _extends } from "@swc/helpers/_/_extends";
    * door proves the reader's permission on each of them again. So the zone
    * carries no gate beyond the slot's own — enablement, entitlement, and the
    * widget's declared permission.
-   */ orgSites: 'orgSites',
-    /**
-   * The Automation page's Actions, beside Add action and Recipes (AGL-2919):
-   * another way to start an automation. Props:
-   * {@link ConsoleHostAutomationsZoneProps}.
-   *
-   * The Automation page is the workflows plugin's own surface, so the plugin
-   * HOSTS this zone through the renderer `useConsoleWidgetSlot` hands down, as
-   * the product editor hosts `seoFields`, and every gate a console page's slot
-   * applies applies here too. A widget here writes nothing through the page:
-   * the Actions list shows what it makes once it exists, and `openAction`
-   * opens a listed action in the Actions editor.
-   */ hostAutomations: 'hostAutomations',
-    /**
-   * The editor of one SAVED automation — an action or a workflow — on the
-   * Automation page (AGL-2919). Props: {@link ConsoleAutomationEditorZoneProps}.
-   * Hosted by the workflows plugin, as `hostAutomations` is. A widget here
-   * reads the automation as it is stored and changes nothing in the editor.
-   */ automationEditor: 'automationEditor',
-    /**
-   * One FAILED run in an automation's run history (AGL-2919), drawn once per
-   * failed row. Props: {@link ConsoleAutomationRunZoneProps}. Hosted by the
-   * workflows plugin. A widget here reads the run as it was recorded and
-   * changes nothing.
-   */ automationRun: 'automationRun',
-    /** The commerce product editor's fields (AGL-2916). Props: {@link ConsoleProductEditorZoneProps}. */ productEditor: 'productEditor',
-    /** Above the commerce products hub's catalog table (AGL-2916). Props: {@link ConsoleProductsHubZoneProps}. */ productsHub: 'productsHub',
-    /** Inside the commerce CSV import dialog (AGL-2916). Props: {@link ConsoleProductImportZoneProps}. */ productImport: 'productImport'
+   */ orgSites: 'orgSites'
 };
 /**
- * The zones on the STAFF pages (AGL-2939): the staff org page, its detail
- * zone, and the staff user page.
+ * The zones on the STAFF pages (AGL-2939): the staff overview, the staff org
+ * page, its detail zone, and the staff user page.
  *
  * No workspace names the plugin set there. A staff page is ABOUT an org or
  * an account, and the reader's own memberships have nothing to do with what
@@ -408,6 +458,7 @@ import { _ as _extends } from "@swc/helpers/_/_extends";
  * answers about a workspace, and the staff area's guard is what admits the
  * reader.
  */ export const CONSOLE_STAFF_WIDGET_SLOTS = [
+    CONSOLE_WIDGET_SLOTS.staffOverview,
     CONSOLE_WIDGET_SLOTS.adminOrgDetail,
     CONSOLE_WIDGET_SLOTS.staffOrg,
     CONSOLE_WIDGET_SLOTS.staffUser,
@@ -678,6 +729,30 @@ function matchNavItemHref(navItem, itemHref, href) {
     }
     return out;
 }
+/**
+ * The load point a plugin contributing search sources declares in its
+ * `console.slots`, and the palette loads before it lists them.
+ */ export const CONSOLE_SEARCH_LOAD_POINT = 'consoleSearch';
+/**
+ * Every search source the enabled plugins contribute, with the extension
+ * each came from so the caller can apply its gates. A second source with an
+ * id already listed is dropped, so two plugins cannot share one group.
+ */ export function listConsoleSearchSources(enabledPluginIds) {
+    const seen = new Set();
+    const out = [];
+    for (const extension of listConsoleExtensions(enabledPluginIds)){
+        var _extension_searchSources;
+        for (const source of (_extension_searchSources = extension.searchSources) != null ? _extension_searchSources : []){
+            if (!(source == null ? void 0 : source.id) || seen.has(source.id)) continue;
+            seen.add(source.id);
+            out.push({
+                extension,
+                source
+            });
+        }
+    }
+    return out;
+}
 /** Providers registered by every extension, in registration order. */ // eslint-disable-next-line @typescript-eslint/no-explicit-any
 export function listConsoleProviders(enabledPluginIds) {
     // eslint-disable-next-line @typescript-eslint/no-explicit-any