feat(settings): open Assistenten on Kunskap with the konteringskarta first (#1044)

The Assistenten settings hub used to open on Minne, with the
konteringskarta buried two clicks away (Kunskap tab, below a second
nested tab row). Now /settings/assistant opens on Kunskap and the
LedgerGraph hero is the first thing on screen.

- Kunskap is the default view and first tab; Minne moves to ?view=memory
  (old ?view=knowledge links still resolve to the default)
- Drop the nested Kompetens/Minne/Regler & profil tab row inside the
  Kunskap view: Kompetens and Minne duplicated the top-level tabs one
  row above; Regler & profil now renders inline under the graph with a
  section header (KnowledgeTabs.tsx deleted)
- Restore vertical rhythm (space-y-8) between the hero, detail section
  and footer, lost when the view moved into the settings tabs
- Update redirects and memory deep links (/settings/agent-memory,
  AgentChat memory chips, FactsCard manage link) to ?view=memory
- Match the loading skeleton to the new layout

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

components/settings/sections/AssistantSettingsContent.tsx

@@ -6,48 +6,49 @@ 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), 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'
+// "Assistenten": the ledger profile the agent reads before booking (Kunskap =
+// "Vad din agent vet", opens on the konteringskarta and is the default view),
+// what the assistant remembers about this company (Minne, editable), and the
+// domain knowledge it ships with (Kompetens, read-only). Tabs keep all three
+// one click away instead of stacked.
+type View = 'knowledge' | 'memory' | 'skills'
 
 const VIEW_ROUTE: Record<View, string> = {
-  memory: '/settings/assistant',
+  knowledge: '/settings/assistant',
+  memory: '/settings/assistant?view=memory',
   skills: '/settings/assistant?view=skills',
-  knowledge: '/settings/assistant?view=knowledge',
 }
 
 export function AssistantSettingsContent() {
   const searchParams = useSearchParams()
   const router = useRouter()
   const raw = searchParams.get('view')
-  const view: View = raw === 'skills' ? 'skills' : raw === 'knowledge' ? 'knowledge' : 'memory'
+  const view: View = raw === 'skills' ? 'skills' : raw === 'memory' ? 'memory' : 'knowledge'
 
   function setView(next: string) {
-    // 'memory' is the default: keep its URL clean (no query string).
-    router.replace(VIEW_ROUTE[next as View] ?? VIEW_ROUTE.memory, { scroll: false })
+    // 'knowledge' is the default: keep its URL clean (no query string).
+    router.replace(VIEW_ROUTE[next as View] ?? VIEW_ROUTE.knowledge, { scroll: false })
   }
 
   return (
     <Tabs value={view} onValueChange={setView} className="space-y-6">
       <TabsList>
+        <TabsTrigger value="knowledge">Kunskap</TabsTrigger>
         <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
           lazily the first time its tab is opened. */}
+      <TabsContent value="knowledge">
+        <AgentKnowledgePanel />
+      </TabsContent>
       <TabsContent value="memory">
         <AgentMemoryPanel />
       </TabsContent>
       <TabsContent value="skills">
         <AgentSkillsPanel />
       </TabsContent>
-      <TabsContent value="knowledge">
-        <AgentKnowledgePanel />
-      </TabsContent>
     </Tabs>
   )
 }