fix

src/components/shell/assistantContext.ts

@@ -34,66 +34,10 @@ export const CONTEXT: Record<
     agent?: string;
   }
 > = {
-  /* ── Nearle Admin ─────────────────────────────────────────────────────────
-   *
-   * The `platform` agent, which holds ONE tool: `help`.
-   *
-   * Not a reduced version of the merchant agents — the only one a platform
-   * account can use. `issuperadmin` reads across every merchant and belongs to
-   * none, so it carries no tenant, and all eight tools that read a shop's data
-   * declare `RequiresTenant` or `RequiresBranch` and refuse it. Giving this
-   * workspace those tools would produce a composer that accepts every question
-   * and answers "pick a shop first" to all of them.
-   *
-   * The chips changed with it, and had to. They used to ask "Which tenants have
-   * no branches?" and "Summarise platform growth" — questions no tool here can
-   * answer. The rule above holds: a chip that comes back "I cannot look that
-   * up" reads as a broken assistant rather than an unbuilt feature.
-   *
-   * The corpus now carries platform passages as well as the merchant ones —
-   * what creating a branch produces, what assigning a delivery partner does,
-   * what a district is, and why a shop's own figures are not reachable from
-   * here. The chips ask those.
-   */
-
-  '/nearle/stores': {
-    agent: 'platform',
-    page: 'Stores',
-    title: 'Nearle Buddy',
-    greeting: 'Answers about how Nearle works — not about any one shop’s numbers.',
-    reading: 'Reads the help material. A shop’s own data is reachable only from inside its console.',
-    prompts: [
-      'What does creating a branch actually create?',
-      'Why can I not see a shop’s orders from here?',
-      'How does a shop get riders?',
-      'What is the difference between a till account and a console login?',
-    ],
-  },
-  '/nearle/onboard/tenant': {
-    agent: 'platform',
-    page: 'Onboard tenant',
-    title: 'Provisioning a tenant',
-    greeting: 'A branch is never created alone — it arrives with somebody who can run it.',
-    reading: 'Reads the help material on onboarding, accounts and delivery regions.',
-    prompts: [
-      'What does creating a branch actually create?',
-      'New outlet cannot sign in',
-      'What is a district?',
-      'How does a shop get riders?',
-    ],
-  },
-  '/nearle/catalogue': {
-    agent: 'platform',
-    page: 'Global catalogue',
-    title: 'Stocking a store',
-    greeting: 'The catalogue carries a price range, not a price — the store sets the real one.',
-    reading: 'Reads the help material on how the catalogue reaches a shop’s shelf.',
-    prompts: [
-      'What does re-importing a product do?',
-      'Why is a product in my catalogue but not on the shelf?',
-      'Why can I not see a shop’s stock from here?',
-    ],
-  },
+  /* The platform workspace was here — three routes pointing at a `platform`
+     agent. It moved out with the rest of Nearle Admin: those paths are not
+     routes in this application any more, so the entries could never match and
+     only shipped platform copy to merchants. They live in `nearle-platform`. */
 
   /* ── Store Admin ──────────────────────────────────────────────────────── */