@@ -3,18 +3,17 @@
 '@objectstack/plugin-audit': patch
 ---
 
-fix(platform-objects,plugin-audit): Setup and Studio navigation entries for the console's Audit Log, AI Approvals and Integrations & APIs pages (#20142)
+fix(platform-objects,plugin-audit): Setup and Studio navigation entries for the console's Audit Log and Integrations & APIs pages (#20142)
 
-The console retired its System Hub card wall and its Developer Hub, which had been the only in-app links to three pages, and registered each page under a component-registry key instead. Framework navigation reaches a console page only through a `type: 'component'` item that names such a key, and no item named these three, so each page was reachable only by a typed URL. Three entries now name them:
+The console retired its System Hub card wall and its Developer Hub, which had been the only in-app links to several pages, and registered each page under a component-registry key instead. Framework navigation reaches a console page only through a `type: 'component'` item that names such a key, and no item named them, so each page was reachable only by a typed URL. Two entries now name the pages whose capability ships in the open framework:
 
 | Entry | App / group | `componentRef` | Contributed by | Gate |
 | --- | --- | --- | --- | --- |
 | `nav_audit_log_browser` ("Audit Log Browser") | Setup / Diagnostics, directly under Audit Logs | `audit:log` | `@objectstack/plugin-audit` | none: it lives and dies with the plugin that owns `sys_audit_log` |
-| `nav_ai_approvals` ("AI Approvals") | Setup / Approvals, after the approvals engine's entries | `ai:approvals` | `@objectstack/platform-objects` | `requiresService: 'ai'` |
 | `nav_integrations` ("Integrations & APIs") | Studio / Developer, after Public Forms | `developer:integrations` | `@objectstack/platform-objects` | none beyond Studio's own `studio.access` |
 
 **Two audit entries, on purpose.** The existing Audit Logs entry (the `sys_audit_log` object view) stays. It carries the named list views, search, and the actor and tenant rendered as resolved lookups. The new page adds one filterable table whose detail drawer pretty-prints a change's before and after JSON, where the record page shows `old_value` / `new_value` as raw text. Neither surface replaces the other.
 
-**The `ai` gate.** The `ai` service has no implementation in the open framework (it is provided by `@objectstack/service-ai` in Cloud/Enterprise), and the AI Approvals page reads only that service. So on a Community Edition runtime the entry is removed server-side, before the app metadata reaches the browser, and it appears once an `ai` service is registered.
+**No entry for the console's AI Approvals page (`ai:approvals`) here.** Under ADR-0029 D7, each capability plugin contributes its own navigation entries into a Setup slot, and the Setup shell does not enumerate capability objects. The AI pending-action queue belongs to the AI capability, whose provider (`@objectstack/service-ai`) ships in Cloud/Enterprise, not in the open framework. Its entry is therefore that capability's to contribute.
 
 The keys are the ones the console registers at the objectui commit this release's console is built from. Labels ship in all four locales (en, zh-CN, ja-JP, es-ES), with their source hashes recorded. Nothing is removed or renamed, and there is nothing to migrate.
@@ -252,15 +252,10 @@ describe('#17647 — Connect-an-Agent visibility: BOTH halves, over the wire', (
         expect(allowedIds).toContain('nav_connect_agent');
         expect(groupChildren(setupAllowed.body?.item, 'group_integrations'))
             .toContain('nav_connect_agent');
-        // The Setup tree the platform admin is served: 9 authored groups, plus
-        // 26 contributed entries plus the MCP one. One of the 26 is
-        // `nav_ai_approvals` (#20142), the only entry this composition folds
-        // into `group_approvals` (plugin-approvals is not part of it). It is
-        // gated on the `ai` service, and it rides through HERE only because
-        // this harness has no service probe, so ADR-0057 D10 fails open (see
-        // the header); its absence without that service is pinned where a
-        // probe is wired, in `console-page-nav-entries.pin.test.ts`.
-        expect(allowedIds).toHaveLength(36);
+        // The Setup tree the platform admin is served: 9 authored groups less
+        // `group_approvals`, which nothing contributes into and the filter
+        // collapses, plus 25 contributed entries plus the MCP one.
+        expect(allowedIds).toHaveLength(34);
     });
 
     it('the Account half widened NOTHING on Setup — the admin tree is unchanged', async () => {
@@ -278,7 +273,7 @@ describe('#17647 — Connect-an-Agent visibility: BOTH halves, over the wire', (
         expect(withAccountHalf.statusCode).toBe(200);
         expect(withoutAccountHalf.statusCode).toBe(200);
         expect(navIds(withAccountHalf.body?.item)).toEqual(navIds(withoutAccountHalf.body?.item));
-        expect(navIds(withAccountHalf.body?.item)).toHaveLength(36);
+        expect(navIds(withAccountHalf.body?.item)).toHaveLength(34);
 
         // The mechanism behind the invariance, asserted rather than assumed:
         // the bundle aims exactly one contribution at `setup` and one at
 
@@ -1,84 +1,62 @@
 // Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.
 //
-// #20142 — the three console pages that lost their only in-app link when
-// objectui#10520 retired the System Hub card wall and the Developer Hub, read
-// back OVER THE WIRE from the composed Setup and Studio apps.
+// #20142 — the Integrations & APIs page, one of the console pages that lost
+// their only in-app link when objectui#10520 retired the Developer Hub, read
+// back OVER THE WIRE from the composed Studio app.
 //
 // ---------------------------------------------------------------------------
 // What this pins
 // ---------------------------------------------------------------------------
-// The card's acceptance, in its own words: "each entry resolves to its
-// registered page (a `componentRef` that is registered), and the
-// `ai:approvals` entry is absent when the `ai` service is not." For the two
-// entries `@objectstack/platform-objects` declares:
+// The card's acceptance: "each entry resolves to its registered page (a
+// `componentRef` that is registered)". For the entry
+// `@objectstack/platform-objects` declares — `nav_integrations` →
+// `developer:integrations`, last in Studio's `group_developer` — this file
+// reads it from the served body of `GET /api/v1/meta/:type/:name`, after the
+// real `SchemaRegistry` registration and the real per-request filter, so a
+// regression anywhere between the declaration and the wire turns it red.
 //
-//   1. `nav_ai_approvals` → `ai:approvals`, in `group_approvals` — ABSENT from
-//      the served body on a Community Edition composition, PRESENT once an
-//      `ai` service is registered. Both readings sit in one `it()`: a gated-off
-//      entry with no lit counterpart proves the gate held exactly as much as
-//      it proves the fold never reached the entry.
-//   2. `nav_integrations` → `developer:integrations`, in Studio's
-//      `group_developer`.
-//
-// The third entry, `nav_audit_log_browser` → `audit:log`, carries no gate and
-// is contributed by `@objectstack/plugin-audit`; its ref is pinned beside it in
-// `packages/plugins/plugin-audit/src/audit-nav-contribution.test.ts`. It is not
-// folded in here because importing that plugin (or plugin-approvals) from this
-// package's tests resolves to its `dist/`, which `check:test-source-alias`
-// refuses for a new import — and nothing about an ungated entry needs the
-// probe this file exists to wire.
+// The other two pages are pinned where they belong:
+//  - `nav_audit_log_browser` → `audit:log` is contributed by
+//    `@objectstack/plugin-audit`; its ref is pinned beside it in
+//    `packages/plugins/plugin-audit/src/audit-nav-contribution.test.ts`.
+//    Importing that plugin from this package's tests would resolve to its
+//    `dist/`, which `check:test-source-alias` refuses for a new import.
+//  - `ai:approvals` is not this repository's entry: ADR-0029 D7 has each
+//    capability plugin contribute its own navigation, and the `ai`
+//    capability's owner is `@objectstack/service-ai` in Cloud/Enterprise.
 //
 // "Registered" is judged against the keys MEASURED at the commit
 // objectstack's `.objectui-sha` pins (dd3f7e1be3561d63267d7162f3fc0ac52e72834d):
-// `registerSystemComponents.tsx` registers `audit:log` and `ai:approvals`,
-// `registerDeveloperComponents.tsx` registers `developer:integrations`.
-// objectui pins its registration half in
+// `registerDeveloperComponents.tsx` registers `developer:integrations` and
+// `registerSystemComponents.tsx` registers `audit:log`. objectui pins its
+// registration half in
 // `apps/console/src/__tests__/orphanedPageComponentRefs-10520.test.tsx`.
 //
-// ---------------------------------------------------------------------------
-// The Community Edition composition, and why the service gate is WIRED here
-// ---------------------------------------------------------------------------
-// The sibling `connect-agent-both-halves-wire.pin.test.ts` deliberately leaves
-// the ADR-0057 D10 capability probe unwired, so every `requiresService` gate
-// there fails OPEN. This file is the opposite case: the probe is the subject.
-// `serviceExistsProvider` answers the way the most generous Community Edition
-// boot would — every service slot some open-framework package can fill is
-// registered — derived from `CORE_SERVICE_PROVIDER`, the discovery table that
-// names each core slot's installable provider. It records none for `ai`
-// (`@objectstack/service-ai` is Cloud/Enterprise only), so `ai` is the one name
-// this composition cannot answer for. The probe also records what it was
-// asked, so a gate that never ran cannot pass as a gate that held.
-//
-// It lives in `packages/cli/test/` for the reason its sibling states: `cli` is
-// the one workspace package that depends on every piece at once — the shells
-// and contributions (`@objectstack/platform-objects`), the fold
-// (`@objectstack/objectql`) and the per-request filter (`@objectstack/rest`).
+// It lives in `packages/cli/test/` for the reason its sibling
+// `connect-agent-both-halves-wire.pin.test.ts` states: `cli` is the one
+// workspace package that depends on every piece at once — the app shells
+// (`@objectstack/platform-objects`), the registry (`@objectstack/objectql`) and
+// the per-request filter (`@objectstack/rest`).
 
 import { describe, expect, it, vi } from 'vitest';
 import { SchemaRegistry } from '@objectstack/objectql';
-import { SETUP_APP, SETUP_NAV_CONTRIBUTIONS, STUDIO_APP } from '@objectstack/platform-objects/apps';
+import { STUDIO_APP } from '@objectstack/platform-objects/apps';
 import { RestServer } from '@objectstack/rest';
-import { CORE_SERVICE_PROVIDER } from '@objectstack/spec/system';
 
 type AnyRec = Record<string, any>;
 
-/** The registry keys the pinned console registers for the three pages. */
-const MEASURED_CONSOLE_KEYS = ['audit:log', 'ai:approvals', 'developer:integrations'];
+/** The registry keys the pinned console registers for the pages this repo links. */
+const MEASURED_CONSOLE_KEYS = ['audit:log', 'developer:integrations'];
 
 /**
- * The real composition: the Setup and Studio shells and the Setup
- * contributions `@objectstack/platform-objects` ships. `structuredClone`
- * because `registerItem` writes the `_lock` envelope onto what it is handed
+ * The real registration of the Studio shell. `structuredClone` because
+ * `registerItem` writes the `_lock` envelope onto what it is handed
  * (ADR-0010 §3.7).
  */
 function composedRegistry(): SchemaRegistry {
     const registry = new SchemaRegistry({ multiTenant: false, collisionPolicy: 'error' });
     (registry as AnyRec).logLevel = 'silent';
-    registry.registerApp(structuredClone(SETUP_APP), '@objectstack/platform-objects');
     registry.registerApp(structuredClone(STUDIO_APP), '@objectstack/platform-objects');
-    for (const c of SETUP_NAV_CONTRIBUTIONS) {
-        registry.registerAppNavContribution(c as any, '@objectstack/platform-objects');
-    }
     return registry;
 }
 
@@ -97,14 +75,9 @@ function makeRes() {
     return res;
 }
 
-/**
- * A `RestServer` serving the composed apps to a platform admin, with the
- * capability probe answering from `serviceExists` and recording every name
- * it was asked about.
- */
-function serve(serviceExists: (name: string) => boolean) {
+/** A `RestServer` serving the composed Studio app to a caller holding `studio.access`. */
+function serve() {
     const registry = composedRegistry();
-    const probed: string[] = [];
     const protocol: AnyRec = {
         getDiscovery: vi.fn().mockResolvedValue({
             version: 'v0', routes: { data: '', metadata: '', ui: '', auth: '/auth' },
@@ -123,13 +96,9 @@ function serve(serviceExists: (name: string) => boolean) {
     const rest: AnyRec = new RestServer(
         createMockServer() as any, protocol as any, { api: { requireAuth: false } } as any,
     );
-    rest.resolveExecCtx = async () => ({
-        userId: 'u1',
-        systemPermissions: ['setup.access', 'studio.access', 'manage_platform_settings'],
-    });
-    rest.serviceExistsProvider = (name: string) => { probed.push(name); return serviceExists(name); };
+    rest.resolveExecCtx = async () => ({ userId: 'u1', systemPermissions: ['studio.access'] });
     rest.registerRoutes();
-    return { rest, probed };
+    return rest;
 }
 
 /** `GET /api/v1/meta/apps/:name`, answered as `{ statusCode, body }`. */
@@ -153,45 +122,9 @@ function group(app: AnyRec | undefined, groupId: string): AnyRec[] | undefined {
 
 const ids = (items: AnyRec[] | undefined) => (items ?? []).map((i) => String(i?.id));
 
-/** The most generous Community Edition: every slot an open package can fill is filled. */
-const communityEdition = (name: string) => CORE_SERVICE_PROVIDER[name] !== null;
-
-describe('#20142 — the console pages\' nav entries, served from the composed apps', () => {
-    it('ai:approvals is absent on a Community Edition composition and present once `ai` is registered', async () => {
-        // The premise the CE probe is built on, asserted rather than assumed.
-        expect(CORE_SERVICE_PROVIDER.ai).toBeNull();
-
-        // ── Community Edition: no `ai` service ─────────────────────────────
-        const ce = serve(communityEdition);
-        const ceSetup = await getApp(ce.rest, 'setup');
-        expect(ceSetup.statusCode).toBe(200);
-        // The gate RAN: the probe was asked about `ai`. Without this, an
-        // unwired probe (fail-open) and a held gate read the same way below.
-        expect(ce.probed).toContain('ai');
-        // Absent from the served tree AND from the wire bytes. `nav_ai_approvals`
-        // is the only entry this composition folds into `group_approvals`
-        // (plugin-approvals is not part of it), so stripping it leaves the group
-        // with nothing to serve.
-        expect(ids(group(ceSetup.body?.item, 'group_approvals'))).toEqual([]);
-        expect(JSON.stringify(ceSetup.body)).not.toContain('nav_ai_approvals');
-        expect(JSON.stringify(ceSetup.body)).not.toContain('ai:approvals');
-        // The rest of the served Setup tree is untouched by the gate: a
-        // neighbouring component entry from the same contributor still arrives.
-        expect(ids(group(ceSetup.body?.item, 'group_apps'))).toContain('nav_packaged_automation');
-
-        // ── Cloud / Enterprise: `ai` registered — the lit counterpart ──────
-        const cloud = serve(() => true);
-        const cloudSetup = await getApp(cloud.rest, 'setup');
-        expect(cloudSetup.statusCode).toBe(200);
-        expect(cloud.probed).toContain('ai');
-        const approvals = group(cloudSetup.body?.item, 'group_approvals');
-        expect(ids(approvals)).toEqual(['nav_ai_approvals']);
-        expect(approvals?.[0]).toMatchObject({ type: 'component', componentRef: 'ai:approvals' });
-    });
-
+describe('#20142 — the Integrations & APIs nav entry, served from the composed Studio app', () => {
     it('developer:integrations is served last in Studio\'s Developer group', async () => {
-        const { rest } = serve(communityEdition);
-        const studio = await getApp(rest, 'studio');
+        const studio = await getApp(serve(), 'studio');
         expect(studio.statusCode).toBe(200);
         const developer = group(studio.body?.item, 'group_developer');
         expect(ids(developer)).toEqual([
@@ -200,16 +133,12 @@ describe('#20142 — the console pages\' nav entries, served from the composed a
         expect(developer?.at(-1)).toMatchObject({ type: 'component', componentRef: 'developer:integrations' });
     });
 
-    it('every served ref of the two entries is a key the pinned console registers', async () => {
-        const { rest } = serve(() => true);
-        const served = [
-            ...((await getApp(rest, 'setup')).body?.item?.navigation ?? []),
-            ...((await getApp(rest, 'studio')).body?.item?.navigation ?? []),
-        ].flatMap((g: AnyRec) => (g?.children ?? []) as AnyRec[]);
-        const refs = served
-            .filter((i) => ['nav_ai_approvals', 'nav_integrations'].includes(i?.id))
-            .map((i) => i.componentRef);
-        expect(refs).toHaveLength(2);
-        for (const ref of refs) expect(MEASURED_CONSOLE_KEYS).toContain(ref);
+    it('the served ref is a key the pinned console registers', async () => {
+        const studio = await getApp(serve(), 'studio');
+        const served = ((studio.body?.item?.navigation ?? []) as AnyRec[])
+            .flatMap((g) => (g?.children ?? []) as AnyRec[])
+            .filter((i) => i?.id === 'nav_integrations');
+        expect(served).toHaveLength(1);
+        expect(MEASURED_CONSOLE_KEYS).toContain(served[0].componentRef);
     });
 });