feat(agent): move 'Vad din agent vet' into settings (Assistenten -> Kunskap) (#1008)

Relocates the ledger-knowledge surface off the top nav and into the
assistant settings hub as a third tab (Minne / Kompetens / Kunskap), per
the code's own "minne + kunskap under Assistenten" intent and the #935
flag that this was an easy call to change.

Because both settings surfaces (the full-page rail and the intercepting
settings modal) mount each section as a propless component via
SETTINGS_SECTIONS, the knowledge data must be fetched client-side rather
than passed as a server prop:

- New GET /api/agent/knowledge aggregates buildLedgerContext +
  buildDeepEntities + buildAgentCompetence + company name (read-only,
  company-scoped via withRouteContext).
- AgentKnowledgeView + AgentCompetenceSections converted from async
  server components to client components (getTranslations ->
  useTranslations; no other server-only usage).
- New AgentKnowledgePanel client wrapper lazy-fetches the payload when
  the Kunskap tab opens (Radix unmounts inactive tabs), with Skeleton and
  error states matching the memory/skills panels.
- Removed the Brain/agent-knowledge entry (and its now-unused import)
  from the Analys nav group.
- /agent-knowledge kept as a redirect to /settings/assistant?view=knowledge
  so old links/bookmarks resolve.

Tests: new route test (auth 401, no-company 400, happy-path aggregation).
i18n: load_error_* keys added to both locales (parity kept).

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

components/settings/sections/AssistantSettingsContent.tsx

@@ -4,23 +4,29 @@ import { useSearchParams, useRouter } from 'next/navigation'
 import { Tabs, TabsList, TabsTrigger, TabsContent } from '@/components/ui/tabs'
 import { AgentMemoryPanel } from '@/components/settings/AgentMemoryPanel'
 import { AgentSkillsPanel } from '@/components/settings/AgentSkillsPanel'
+import { AgentKnowledgePanel } from '@/components/agent-knowledge/AgentKnowledgePanel'
 
 // "Assistenten": what the assistant remembers about this company (Minne,
-// editable) and the domain knowledge it ships with (Kompetens, read-only).
-// A toggle keeps both one click away instead of stacked, so the competence
-// view isn't buried below the memory list.
-type View = 'memory' | 'skills'
+// editable), the domain knowledge it ships with (Kompetens, read-only), and
+// the ledger profile it reads before booking (Kunskap = "Vad din agent vet",
+// read-only). Tabs keep all three one click away instead of stacked.
+type View = 'memory' | 'skills' | 'knowledge'
+
+const VIEW_ROUTE: Record<View, string> = {
+  memory: '/settings/assistant',
+  skills: '/settings/assistant?view=skills',
+  knowledge: '/settings/assistant?view=knowledge',
+}
 
 export function AssistantSettingsContent() {
   const searchParams = useSearchParams()
   const router = useRouter()
-  const view: View = searchParams.get('view') === 'skills' ? 'skills' : 'memory'
+  const raw = searchParams.get('view')
+  const view: View = raw === 'skills' ? 'skills' : raw === 'knowledge' ? 'knowledge' : 'memory'
 
   function setView(next: string) {
     // 'memory' is the default: keep its URL clean (no query string).
-    router.replace(next === 'skills' ? '/settings/assistant?view=skills' : '/settings/assistant', {
-      scroll: false,
-    })
+    router.replace(VIEW_ROUTE[next as View] ?? VIEW_ROUTE.memory, { scroll: false })
   }
 
   return (
@@ -28,6 +34,7 @@ export function AssistantSettingsContent() {
       <TabsList>
         <TabsTrigger value="memory">Minne</TabsTrigger>
         <TabsTrigger value="skills">Kompetens</TabsTrigger>
+        <TabsTrigger value="knowledge">Kunskap</TabsTrigger>
       </TabsList>
 
       {/* Radix unmounts the inactive panel, so each panel's data is fetched
@@ -38,6 +45,9 @@ export function AssistantSettingsContent() {
       <TabsContent value="skills">
         <AgentSkillsPanel />
       </TabsContent>
+      <TabsContent value="knowledge">
+        <AgentKnowledgePanel />
+      </TabsContent>
     </Tabs>
   )
 }