every plugin route renders a workspace, and it is not a rule you can forget

an exclusionary rule, made structural. a plugin does not render a screen: it
contributes panels and says how they are arranged, and the shell renders
WorkspaceView around them.

    web/panels.ts   appRegistryMetas — at least one panel
    web/layout.ts   defaultLayout — how they are arranged

both required the moment web/ exists, and missing either is refused at discovery
by name and with the reason. tested:

    probeplug: has a web/ directory but is missing web/layout.ts.
    Every plugin route renders a Workspace: contribute panels and a layout,
    not a screen.

there is deliberately no way to export a component. one that could would be free
to render a bare div, a full-page form, or its own navigation, and the platform
would become a shell hosting strangers' layouts rather than one application.
non-compliance is not so much refused as unrepresentable — there is nowhere to
put a screen.

the shell registers <prefix> and <prefix>/:section, exactly as the core screens
do, so a plugin's sections stay addressable and cmd-clickable, and panels read
useParams independently rather than passing state between themselves.
appTypes.allowed is pinned to that plugin's own keys, so a persisted layout
naming something else falls back instead of rendering another plugin's panel
inside this screen.

the example plugin is rebuilt to model it — two panels, a layout, one of them
calling its own /api/example/ping through useClient — because the reference
implementation is what everyone copies.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/apps/officer-web/Screens/Dashboard/Settings/ProfileSettings/AIModels.tsx

@@ -87,19 +87,25 @@ export const AIModels = () => {
     <div className="grid gap-5">
       <Label className="grid gap-2">
         <span className="text-duck-dark/70 dark:text-foreground/70">Default Chat Model</span>
-        <p className="text-xs text-duck-dark/40 dark:text-foreground/40">Used when starting a new chat from the home screen</p>
+        <p className="text-xs text-duck-dark/40 dark:text-foreground/40">
+          Used when starting a new chat from the home screen
+        </p>
         {renderModelSelect(chatModel, setChatModel, 'System default')}
       </Label>
 
       <Label className="grid gap-2">
         <span className="text-duck-dark/70 dark:text-foreground/70">Default Project Model</span>
-        <p className="text-xs text-duck-dark/40 dark:text-foreground/40">Used when starting a new chat inside a project dashboard</p>
+        <p className="text-xs text-duck-dark/40 dark:text-foreground/40">
+          Used when starting a new chat inside a project dashboard
+        </p>
         {renderModelSelect(projectModel, setProjectModel, 'Same as chat default')}
       </Label>
 
       <Label className="grid gap-2">
         <span className="text-duck-dark/70 dark:text-foreground/70">Default Task Model</span>
-        <p className="text-xs text-duck-dark/40 dark:text-foreground/40">Used when running tasks from the file browser</p>
+        <p className="text-xs text-duck-dark/40 dark:text-foreground/40">
+          Used when running tasks from the file browser
+        </p>
         {renderModelSelect(taskModel, setTaskModel, 'Same as chat default')}
       </Label>