@objectstack/platform-objects 11.7.0 → 11.9.0

package/dist/index.js

@@ -5245,9 +5245,19 @@ var SETUP_NAV_CONTRIBUTIONS = [
       { id: "nav_system_overview", type: "dashboard", label: "System Overview", dashboardName: "system_overview", icon: "activity" }
     ]
   },
-  // No group_apps contribution left here — both marketplace entries moved
-  // out (see header note); the group_apps shell anchor in setup.app.ts is
-  // filled entirely by capability plugins now.
+  {
+    // Package ADMINISTRATION is a platform/operator concern (ADR-0084:
+    // packages are Operate, out of the builder) — so its home is Setup, not
+    // the application builder. The console binds `developer:packages` to the
+    // existing package-management page. Building/creating apps is a separate
+    // journey (Home cover → /studio); this entry is for install/inspect/admin.
+    app: "setup",
+    group: "group_apps",
+    priority: BASE_PRIORITY,
+    items: [
+      { id: "nav_packages", type: "component", label: "Packages", componentRef: "developer:packages", icon: "package" }
+    ]
+  },
   {
     app: "setup",
     group: "group_people_org",
@@ -5391,6 +5401,19 @@ var STUDIO_APP = {
       label: "Overview",
       icon: "layout-dashboard",
       children: [
+        {
+          // The application builder's front door (ADR-0080/0084): pick or
+          // create a writable base package, then design in the full-screen
+          // pillar builder (/studio/:packageId/:tab). The console binds
+          // `studio:builder` to the BuilderLanding page — this makes the
+          // builder reachable from login (Home → Studio → App Builder)
+          // instead of being a URL-only surface.
+          id: "nav_app_builder",
+          type: "component",
+          label: "App Builder",
+          componentRef: "studio:builder",
+          icon: "hammer"
+        },
         {
           id: "nav_metadata_directory",
           type: "component",