The admin app shell is already designed

Four edges, four scopes

Top, left, right, and bottom panels have explicit geometry and responsive presentation. App, tenant, focus, and system scopes make ownership legible instead of accumulating one giant sidebar.

Navigation comes from the manifest

tenantNavFromManifest groups resources by package and filters them by permitted resources. Build it in +layout.server.ts and the first render arrives with the correct navigation—no client fetch required.

• Collections, internal and test classes, and anything without a REST list route are dropped.
• A subtype that shares its parent collection is dropped, because the shared endpoint is already polymorphic.
• permittedResources filters by role, expanding through inheritance so a permitted subtype keeps the link it routes through.
• Sections and items are sorted, so reordering the manifest never reshuffles the sidebar.

import { tenantNavFromManifest } from '@happyvertical/smrt-svelte/workspace';
import { manifest } from '$lib/manifest';

export const load = async ({ locals }) => ({
  nav: tenantNavFromManifest(manifest, {
    permittedResources: locals.permittedResources,
    sectionHints: { '@happyvertical/smrt-content': 'Content' },
    basePath: ''
  })
});

Activities accept any transport

Jobs, polling, SSE, WebSockets, and application events all adapt into one activity registry. The shell itself stays transport-agnostic and SSR-safe.

AdminShell is the surface to build on

Earlier releases shipped a sidebar-and-inspector WorkspaceShell and a role-driven RoleShell. The four-edge AdminShell replaced both, and those primitives are no longer exported. Focus tools now live on the shell. The previous dock stays available on a separate legacy subpath. An existing application can migrate one screen at a time.