@objectstack/platform-objects 7.2.1 → 7.4.0

package/dist/apps/index.d.mts

@@ -1,32 +1,58 @@
-import { App } from '@objectstack/spec/ui';
+import { App, NavigationContribution } from '@objectstack/spec/ui';
 import * as _objectstack_spec_data from '@objectstack/spec/data';
 import { TranslationBundle, TranslationData } from '@objectstack/spec/system';
 
 /**
- * Platform Setup App — static definition.
+ * Platform Setup App — navigation **shell** (ADR-0029 D7).
  *
- * Lists every `sys_*` administrative object as a left-hand navigation
- * entry in ObjectUI's "Setup" area. Lives here (alongside the object
- * schemas it references) instead of being assembled at runtime by
- * `@objectstack/plugin-setup` — that plugin existed only because the
- * referenced objects used to live in three different runtime plugins
- * (auth/security/audit). Now that all `sys_*` objects are centralized
- * in `@objectstack/platform-objects`, the Setup App is a fixed metadata
- * artifact too and can be exported as plain data.
+ * The Setup App is now a thin shell: it defines the app envelope plus the
+ * stable left-nav **group anchors** ("slots"), but enumerates **no** objects.
+ * Each capability plugin contributes its own menu entries into a slot via
+ * `navigationContributions` (the UI-layer analog of object `extend`), so the
+ * menu for an object ships with the package that owns the object.
  *
- * The runtime registration happens in `plugin-auth` (which is always
- * loaded alongside security + audit and already calls
- * `manifest.register({...})`).
+ * - Items owned by `@objectstack/platform-objects` are contributed by
+ *   `SETUP_NAV_CONTRIBUTIONS` (see `setup-nav.contributions.ts`), registered
+ *   alongside this app.
+ * - Items owned by a capability plugin are contributed by that plugin — e.g.
+ *   `@objectstack/plugin-webhooks` fills `group_integrations` with its
+ *   `sys_webhook` / `sys_webhook_delivery` entries (ADR-0029 K2.a).
+ *
+ * The runtime merges all contributions into this app's `navigation` tree by
+ * group id + priority on read, so the rendered Setup nav is identical to the
+ * former static artifact — just assembled from its owners. A disabled
+ * capability contributes nothing and its slot stays empty.
  *
  * Menu shape: flat `navigation[]` with `type: 'group'` category nodes,
- * matching the convention used by the HotCRM reference app at
- * https://github.com/objectstack-ai/hotcrm (see `src/apps/crm.app.ts`).
- * The legacy `areas[]` shape was abandoned because it rendered poorly
- * compared to the category style ObjectUI is built around.
+ * matching the convention used by the HotCRM reference app.
  */
 
 declare const SETUP_APP: App;
 
+/**
+ * Setup App navigation contributions owned by `@objectstack/platform-objects`
+ * (ADR-0029 D7).
+ *
+ * The Setup App (`setup.app.ts`) is a shell of empty group anchors; these
+ * contributions fill the groups with the entries for objects that still live
+ * in `@objectstack/platform-objects`. They are registered alongside
+ * `SETUP_APP` (via `plugin-auth`'s `manifest.register`).
+ *
+ * Some entries/groups are intentionally contributed by the capability plugin
+ * that owns the underlying objects rather than living here (ADR-0029 K2):
+ *   - `group_integrations` → `@objectstack/plugin-webhooks` (K2.a)
+ *   - `group_approvals`     → `@objectstack/plugin-approvals` (K2.b)
+ *   - `group_access_control` Roles / Permission Sets → `@objectstack/plugin-security`
+ *   - `group_access_control` Sharing Rules / Record Shares → `@objectstack/plugin-sharing`
+ * As each remaining domain moves to its capability plugin, its entries move out
+ * of this file into that plugin the same way.
+ *
+ * Priority 100 keeps platform-objects base entries ahead of later
+ * contributions in the same group (mirrors object owner priority).
+ */
+
+declare const SETUP_NAV_CONTRIBUTIONS: NavigationContribution[];
+
 /**
  * Platform Studio App — static definition.
  *
@@ -176,7 +202,7 @@ declare const SystemOverviewDashboard: {
                 role?: string | undefined;
             } | undefined;
         } | undefined;
-        colorVariant?: "default" | "danger" | "success" | "warning" | "blue" | "teal" | "orange" | "purple" | undefined;
+        colorVariant?: "default" | "danger" | "warning" | "success" | "blue" | "teal" | "orange" | "purple" | undefined;
         requiresObject?: string | undefined;
         requiresService?: string | undefined;
         actionUrl?: string | undefined;
@@ -339,4 +365,4 @@ declare const jaJP: TranslationData;
  */
 declare const esES: TranslationData;
 
-export { ACCOUNT_APP, SETUP_APP, STUDIO_APP, SetupAppTranslations, SystemOverviewDashboard, en, esES, jaJP, zhCN };
+export { ACCOUNT_APP, SETUP_APP, SETUP_NAV_CONTRIBUTIONS, STUDIO_APP, SetupAppTranslations, SystemOverviewDashboard, en, esES, jaJP, zhCN };

package/dist/apps/index.d.ts

@@ -1,32 +1,58 @@
-import { App } from '@objectstack/spec/ui';
+import { App, NavigationContribution } from '@objectstack/spec/ui';
 import * as _objectstack_spec_data from '@objectstack/spec/data';
 import { TranslationBundle, TranslationData } from '@objectstack/spec/system';
 
 /**
- * Platform Setup App — static definition.
+ * Platform Setup App — navigation **shell** (ADR-0029 D7).
  *
- * Lists every `sys_*` administrative object as a left-hand navigation
- * entry in ObjectUI's "Setup" area. Lives here (alongside the object
- * schemas it references) instead of being assembled at runtime by
- * `@objectstack/plugin-setup` — that plugin existed only because the
- * referenced objects used to live in three different runtime plugins
- * (auth/security/audit). Now that all `sys_*` objects are centralized
- * in `@objectstack/platform-objects`, the Setup App is a fixed metadata
- * artifact too and can be exported as plain data.
+ * The Setup App is now a thin shell: it defines the app envelope plus the
+ * stable left-nav **group anchors** ("slots"), but enumerates **no** objects.
+ * Each capability plugin contributes its own menu entries into a slot via
+ * `navigationContributions` (the UI-layer analog of object `extend`), so the
+ * menu for an object ships with the package that owns the object.
  *
- * The runtime registration happens in `plugin-auth` (which is always
- * loaded alongside security + audit and already calls
- * `manifest.register({...})`).
+ * - Items owned by `@objectstack/platform-objects` are contributed by
+ *   `SETUP_NAV_CONTRIBUTIONS` (see `setup-nav.contributions.ts`), registered
+ *   alongside this app.
+ * - Items owned by a capability plugin are contributed by that plugin — e.g.
+ *   `@objectstack/plugin-webhooks` fills `group_integrations` with its
+ *   `sys_webhook` / `sys_webhook_delivery` entries (ADR-0029 K2.a).
+ *
+ * The runtime merges all contributions into this app's `navigation` tree by
+ * group id + priority on read, so the rendered Setup nav is identical to the
+ * former static artifact — just assembled from its owners. A disabled
+ * capability contributes nothing and its slot stays empty.
  *
  * Menu shape: flat `navigation[]` with `type: 'group'` category nodes,
- * matching the convention used by the HotCRM reference app at
- * https://github.com/objectstack-ai/hotcrm (see `src/apps/crm.app.ts`).
- * The legacy `areas[]` shape was abandoned because it rendered poorly
- * compared to the category style ObjectUI is built around.
+ * matching the convention used by the HotCRM reference app.
  */
 
 declare const SETUP_APP: App;
 
+/**
+ * Setup App navigation contributions owned by `@objectstack/platform-objects`
+ * (ADR-0029 D7).
+ *
+ * The Setup App (`setup.app.ts`) is a shell of empty group anchors; these
+ * contributions fill the groups with the entries for objects that still live
+ * in `@objectstack/platform-objects`. They are registered alongside
+ * `SETUP_APP` (via `plugin-auth`'s `manifest.register`).
+ *
+ * Some entries/groups are intentionally contributed by the capability plugin
+ * that owns the underlying objects rather than living here (ADR-0029 K2):
+ *   - `group_integrations` → `@objectstack/plugin-webhooks` (K2.a)
+ *   - `group_approvals`     → `@objectstack/plugin-approvals` (K2.b)
+ *   - `group_access_control` Roles / Permission Sets → `@objectstack/plugin-security`
+ *   - `group_access_control` Sharing Rules / Record Shares → `@objectstack/plugin-sharing`
+ * As each remaining domain moves to its capability plugin, its entries move out
+ * of this file into that plugin the same way.
+ *
+ * Priority 100 keeps platform-objects base entries ahead of later
+ * contributions in the same group (mirrors object owner priority).
+ */
+
+declare const SETUP_NAV_CONTRIBUTIONS: NavigationContribution[];
+
 /**
  * Platform Studio App — static definition.
  *
@@ -176,7 +202,7 @@ declare const SystemOverviewDashboard: {
                 role?: string | undefined;
             } | undefined;
         } | undefined;
-        colorVariant?: "default" | "danger" | "success" | "warning" | "blue" | "teal" | "orange" | "purple" | undefined;
+        colorVariant?: "default" | "danger" | "warning" | "success" | "blue" | "teal" | "orange" | "purple" | undefined;
         requiresObject?: string | undefined;
         requiresService?: string | undefined;
         actionUrl?: string | undefined;
@@ -339,4 +365,4 @@ declare const jaJP: TranslationData;
  */
 declare const esES: TranslationData;
 
-export { ACCOUNT_APP, SETUP_APP, STUDIO_APP, SetupAppTranslations, SystemOverviewDashboard, en, esES, jaJP, zhCN };
+export { ACCOUNT_APP, SETUP_APP, SETUP_NAV_CONTRIBUTIONS, STUDIO_APP, SetupAppTranslations, SystemOverviewDashboard, en, esES, jaJP, zhCN };