diff --git a/.claude/agents/component-builder.md b/.claude/agents/component-builder.md
new file mode 100644
index 000000000..69d4b28ff
--- /dev/null
+++ b/.claude/agents/component-builder.md
@@ -0,0 +1,211 @@
+---
+name: component-builder
+description: Use this agent when building any Vue UI in the insights repo. It knows every uikit component available, PrimeVue patterns, and Tailwind config. Ask it to build a form, table, modal, card layout, or any other UI — it will assemble it using existing uikit components instead of writing raw HTML. When building uikit components, it also writes the Storybook story file.
+---
+
+You are a frontend UI expert for the LFX Insights repo. Your job is to build Vue 3 components using the project's existing uikit and conventions.
+
+## Core Rules
+
+1. **Always use uikit components** — never use raw `<button>`, `<input>`, `<select>`, `<textarea>`, `<table>`, `<dialog>` when a uikit equivalent exists
+2. **Use `<script setup lang="ts">`** — always, no Options API
+3. **Tailwind for layout/spacing** — check `frontend/tailwind.config.ts` for custom tokens before using arbitrary values
+4. **PrimeVue** — available for complex patterns not in the uikit
+5. **License header** — every `.vue` file must start with the MIT header
+
+## Available Uikit Components
+
+Located in `frontend/app/components/uikit/`. Auto-imported by Nuxt as `<lfx-*>`. Always scan this directory before writing a component — new components may have been added since this list was written.
+
+| Component | Tag | Use for |
+|---|---|---|
+| accordion | `<lfx-accordion>` | Collapsible sections |
+| avatar | `<lfx-avatar>` | User/org avatars |
+| avatar-group | `<lfx-avatar-group>` | Stacked avatar list |
+| back | `<lfx-back>` | Back navigation link |
+| benchmarks | `<lfx-benchmarks>` | Benchmark comparisons |
+| button | `<lfx-button>` | All clickable actions |
+| card | `<lfx-card>` | Content containers |
+| carousel | `<lfx-carousel>` | Sliding content |
+| chart | `<lfx-chart>` | ECharts wrapper |
+| checkbox | `<lfx-checkbox>` | Boolean inputs |
+| chip | `<lfx-chip>` | Inline labels/tags |
+| datepicker | `<lfx-datepicker>` | Date selection |
+| delta-display | `<lfx-delta-display>` | Numeric change indicators |
+| drawer | `<lfx-drawer>` | Side panel overlays |
+| dropdown | `<lfx-dropdown>` | Dropdown menus |
+| field | `<lfx-field>` | Form field wrapper with label |
+| icon | `<lfx-icon>` | Icons |
+| icon-button | `<lfx-icon-button>` | Icon-only buttons |
+| input | `<lfx-input>` | Text inputs |
+| maintain-height | `<lfx-maintain-height>` | Prevent layout shift during loading |
+| menu-button | `<lfx-menu-button>` | Button with dropdown menu |
+| modal | `<lfx-modal>` | Dialog/modal overlays |
+| organization-logo | `<lfx-organization-logo>` | Org logo display |
+| popover | `<lfx-popover>` | Hover/click popovers |
+| progress-bar | `<lfx-progress-bar>` | Progress indicators |
+| radio | `<lfx-radio>` | Radio inputs |
+| scroll-view | `<lfx-scroll-view>` | Scrollable containers |
+| scrollable-shadow | `<lfx-scrollable-shadow>` | Scroll shadow effect |
+| select | `<lfx-select>` | Select dropdowns |
+| share | `<lfx-share>` | Share actions |
+| side-nav | `<lfx-side-nav>` | Sidebar navigation |
+| skeleton | `<lfx-skeleton>` | Loading placeholders |
+| spinner | `<lfx-spinner>` | Loading spinners |
+| table | `<lfx-table>` | Data tables |
+| tabs | `<lfx-tabs>` | Tab navigation |
+| tag | `<lfx-tag>` | Status/category tags |
+| textarea | `<lfx-textarea>` | Multi-line text input |
+| toast | `<lfx-toast>` | Notification toasts |
+| toggle | `<lfx-toggle>` | Boolean toggles |
+| tooltip | `<lfx-tooltip>` | Hover tooltips |
+
+## File Header
+
+Always start `.vue` files with:
+```
+<!--
+Copyright (c) 2025 The Linux Foundation and each contributor.
+SPDX-License-Identifier: MIT
+-->
+```
+
+## Before Writing Any Component
+
+1. Read the relevant uikit component file(s) in `frontend/app/components/uikit/` to understand accepted props/slots
+2. Check `frontend/tailwind.config.ts` for color tokens, spacing scale, breakpoints
+3. If using data, check what composables exist in `frontend/composables/` before writing new ones
+
+## Storybook Stories
+
+Storybook scans `frontend/app/components/**/*.stories.@(js|jsx|ts|tsx|mdx)`. Stories are only written for **uikit components** — not for feature/module components.
+
+When creating or modifying a uikit component, always produce a co-located `<component-name>.stories.ts` file alongside the `.vue` file.
+
+### Story File Conventions
+
+**Title:** `'LinuxFoundation/ComponentName'` — match the PascalCase component name.
+
+**Always include** `tags: ['autodocs']` on the default export.
+
+**`argTypes` block** — document every prop and slot:
+```ts
+argTypes: {
+  // Props
+  size: {
+    description: 'Size of the component',
+    control: 'select',
+    options: sizeOptions,       // import from types file if available
+  },
+  disabled: {
+    description: 'Disables the component',
+    control: 'boolean',
+  },
+  label: {
+    description: 'Text label',
+    control: 'text',
+  },
+  // Slots — always set control to null
+  default: {
+    description: 'Default slot content',
+    control: { type: null },
+  },
+  // Events — always set control to null
+  'update:modelValue': {
+    description: 'Emitted when value changes',
+    control: { type: null },
+  },
+},
+```
+
+**Simple story** (no custom template needed):
+```ts
+export const Default = {
+  args: {
+    label: 'Example',
+    size: 'medium',
+  },
+};
+```
+
+**Story with a custom template** (needed when using slots, composing multiple components, or interactive state):
+```ts
+const tmpl = `<lfx-my-component v-bind="propsObj">Slot content</lfx-my-component>`;
+
+export const WithSlot = {
+  args: { size: 'default' },
+  render: (args, { argTypes }) => ({
+    components: { LfxMyComponent },
+    props: Object.keys(argTypes),
+    template: tmpl,
+    computed: {
+      propsObj() { return args; },
+    },
+  }),
+  parameters: {
+    docs: {
+      source: {
+        code: `<template>\n  ${tmpl}\n</template>`,
+      },
+    },
+  },
+};
+```
+
+**Interactive state** (modals, drawers, toggles — use `setup()` with `ref`):
+```ts
+export const Default = {
+  args: { modelValue: true },
+  render: (args) => ({
+    components: { LfxMyComponent, LfxButton },
+    setup() {
+      const isOpen = ref(true);
+      return { args, isOpen };
+    },
+    template: `<div>
+      <lfx-button @click="isOpen = true">Open</lfx-button>
+      <lfx-my-component v-model="isOpen" />
+    </div>`,
+  }),
+};
+```
+
+**Background hint** (use when the component needs a specific background to look correct):
+```ts
+parameters: {
+  backgrounds: {
+    default: 'Light',
+    values: [
+      { name: 'Light', value: '#F1F5F9' },
+      { name: 'Dark', value: '#333' },
+    ],
+  },
+},
+```
+
+### Story Variants to Include
+
+Cover the main use cases in separate named exports:
+- `Default` — always required, shows the most common usage
+- One export per meaningful variant (e.g. `Secondary`, `WithIcon`, `Disabled`, `Loading`)
+- For components with slots: at least one story that demonstrates slot usage via `render`
+
+### Story File Header
+
+Same MIT license header as `.vue` files:
+```ts
+// Copyright (c) 2025 The Linux Foundation and each contributor.
+// SPDX-License-Identifier: MIT
+```
+
+## Your Output
+
+For **uikit components**: produce both the `.vue` file and a co-located `.stories.ts` file.
+
+For **feature/module components**: produce only the `.vue` file — no story needed.
+
+Always:
+- Use uikit components for every UI primitive
+- Apply Tailwind classes for layout
+- Type all props and emits
+- Include the license header
diff --git a/.claude/commands/db-migrate.md b/.claude/commands/db-migrate.md
new file mode 100644
index 000000000..e7cd874f1
--- /dev/null
+++ b/.claude/commands/db-migrate.md
@@ -0,0 +1,79 @@
+# DB Migrate
+
+Apply pending Flyway migrations to the local Insights PostgreSQL database.
+
+## Usage
+
+`/db-migrate`
+
+Optional — create a new migration file:
+`/db-migrate new <migration_name>`
+
+## How It Works
+
+Migrations live in `database/migrations/` and are managed by [Flyway](https://flywaydb.org/) running inside Docker. The `database/migrate.sh` script wraps the Docker invocation.
+
+File naming convention: `V<unix_timestamp>__<description>.sql`
+
+## Apply Pending Migrations
+
+Run from the repo root:
+```sh
+cd database && \
+  PGHOST=host.docker.internal \
+  PGPORT=5450 \
+  PGDATABASE=insights \
+  PGUSER=postgres \
+  PGPASSWORD=example \
+  bash migrate.sh
+```
+
+> Flyway runs inside Docker, so use `host.docker.internal` (not `localhost`). Port `5450` is the host port mapped to the container's 5432. Adjust if you used a different port when creating the container.
+
+This runs `flyway migrate` with `-outOfOrder=true` and `-baselineOnMigrate=true`.
+
+## Create a New Migration File
+
+Run from the `database/` directory:
+```sh
+cd database && bash create_migration.sh <migration_name>
+```
+
+Example:
+```sh
+cd database && bash create_migration.sh add_index_to_project_costs
+```
+
+This creates `database/migrations/V<timestamp>__<migration_name>.sql`. Open the file and write the SQL, then apply it with `/db-migrate`.
+
+## Check Migration Status
+
+To see which migrations have been applied:
+```sh
+cd database && \
+  PGHOST=host.docker.internal \
+  PGPORT=5450 \
+  PGDATABASE=insights \
+  PGUSER=postgres \
+  PGPASSWORD=example \
+  bash migrate.sh info
+```
+
+## Validate Migrations
+
+```sh
+cd database && \
+  PGHOST=host.docker.internal \
+  PGPORT=5450 \
+  PGDATABASE=insights \
+  PGUSER=postgres \
+  PGPASSWORD=example \
+  bash migrate.sh validate
+```
+
+## Troubleshooting
+
+- **Docker not running**: start Docker Desktop first
+- **Connection refused**: make sure the `insights-postgres` container is running (`docker start insights-postgres`)
+- **Checksum mismatch**: never edit an already-applied migration — create a new one instead
+- **Out of order**: the `-outOfOrder=true` flag is already set, so migrations with older timestamps applied after newer ones are allowed
diff --git a/.claude/commands/db-setup.md b/.claude/commands/db-setup.md
new file mode 100644
index 000000000..fa50fcf5c
--- /dev/null
+++ b/.claude/commands/db-setup.md
@@ -0,0 +1,118 @@
+# DB Setup
+
+Start a local PostgreSQL instance for Insights development using Docker.
+
+## Usage
+
+`/db-setup`
+
+## What This Does
+
+Starts a PostgreSQL container with the default local credentials matching the Nuxt runtime config defaults, then runs Flyway migrations to bring the schema up to date.
+
+## Steps
+
+### 1. Check prerequisites
+
+Verify Docker is running:
+```sh
+docker info > /dev/null 2>&1 || echo "Docker is not running — start Docker Desktop first"
+```
+
+### 2. Check for port conflicts
+
+Port 5432 may already be in use (e.g. by another Postgres instance or Docker Desktop). Check first:
+```sh
+lsof -i :5432 | grep LISTEN
+```
+
+- If free → use `-p 5432:5432` and `PGPORT=5432` throughout
+- If occupied → use `-p 5450:5432` and `PGPORT=5450` (default below)
+
+### 3. Start the PostgreSQL container
+
+```sh
+docker run -d \
+  --name insights-postgres \
+  -e POSTGRES_USER=postgres \
+  -e POSTGRES_PASSWORD=example \
+  -e POSTGRES_DB=insights \
+  -p 5450:5432 \
+  postgres:15-alpine \
+  postgres -c wal_level=logical
+```
+
+> **`wal_level=logical` is required** — migration `V1749196362__createSequinReplicationSlot.sql` creates a logical replication slot for Sequin. Without it, migrations fail.
+
+If the container already exists and was created with the correct settings, just start it:
+```sh
+docker start insights-postgres
+```
+
+Wait for Postgres to be ready:
+```sh
+until docker exec insights-postgres pg_isready -U postgres; do sleep 1; done
+```
+
+### 4. Apply migrations
+
+Flyway runs inside Docker so use `host.docker.internal` (not `localhost`) to reach the host:
+```sh
+cd database && \
+  PGHOST=host.docker.internal \
+  PGPORT=5450 \
+  PGDATABASE=insights \
+  PGUSER=postgres \
+  PGPASSWORD=example \
+  bash migrate.sh
+```
+
+> **Linux users:** `host.docker.internal` may not resolve by default on Linux. Use `--host-network` instead, which makes the container share the host's network stack so `localhost` works:
+> ```sh
+> cd database && \
+>   PGHOST=localhost \
+>   PGPORT=5450 \
+>   PGDATABASE=insights \
+>   PGUSER=postgres \
+>   PGPASSWORD=example \
+>   bash migrate.sh --host-network
+> ```
+
+### 5. Verify
+
+```sh
+docker exec insights-postgres psql -U postgres -d insights -c "\dt"
+```
+
+Expected: 11 tables including `chat_responses`, `project_costs`, `vulnerabilities`, etc.
+
+## Default Credentials
+
+These match the runtime config defaults in `frontend/setup/runtime-config.ts`:
+
+| Variable | Value |
+|---|---|
+| Host | `localhost` |
+| Port | `5450` (host port mapped to container's 5432) |
+| Database | `insights` |
+| Username | `postgres` |
+| Password | `example` |
+
+## .env Configuration
+
+These map to the following Nuxt env vars in `frontend/.env`:
+```
+NUXT_INSIGHTS_DB_WRITE_HOST=localhost
+NUXT_INSIGHTS_DB_READ_HOST=localhost
+NUXT_INSIGHTS_DB_PORT=5450
+NUXT_INSIGHTS_DB_USERNAME=postgres
+NUXT_INSIGHTS_DB_PASSWORD=example
+NUXT_INSIGHTS_DB_DATABASE=insights
+```
+
+## Teardown
+
+To stop and remove the container:
+```sh
+docker stop insights-postgres && docker rm insights-postgres
+```
diff --git a/.claude/rules/always-use-uikit.md b/.claude/rules/always-use-uikit.md
new file mode 100644
index 000000000..a65219ae7
--- /dev/null
+++ b/.claude/rules/always-use-uikit.md
@@ -0,0 +1,33 @@
+# Always Use Uikit Components
+
+When generating any Vue template in this repo, you MUST use components from `frontend/app/components/uikit/` instead of raw HTML equivalents.
+
+## Rule
+
+**Before writing any HTML element, check if a uikit component exists for it.**
+
+Never use these raw elements when a uikit equivalent is available:
+
+| Raw HTML | Use instead |
+|---|---|
+| `<button>` | `<lfx-button>` or `<lfx-icon-button>` |
+| `<input>` | `<lfx-input>` |
+| `<select>` | `<lfx-select>` |
+| `<textarea>` | `<lfx-textarea>` |
+| `<table>`, `<tr>`, `<td>` | `<lfx-table>` |
+| `<dialog>` / modal div | `<lfx-modal>` |
+| `<aside>` / side panel | `<lfx-drawer>` |
+| Loading spinner div | `<lfx-spinner>` |
+| Placeholder shimmer | `<lfx-skeleton>` |
+| Tab bar | `<lfx-tabs>` |
+| Tooltip wrapper | `<lfx-tooltip>` |
+| Checkbox input | `<lfx-checkbox>` |
+| Radio input | `<lfx-radio>` |
+| Toggle/switch | `<lfx-toggle>` |
+
+## How to Apply
+
+1. Before writing a component template, scan `frontend/app/components/uikit/` to see what's available
+2. Read the uikit component's `.vue` file to understand its props and slots before using it
+3. If no uikit component exists for the element, use Tailwind + raw HTML and note that a uikit component may be needed
+4. Never invent a custom button, input, or modal — always use the uikit versions
diff --git a/.claude/rules/pnpm-workspace-commands.md b/.claude/rules/pnpm-workspace-commands.md
new file mode 100644
index 000000000..3741ae858
--- /dev/null
+++ b/.claude/rules/pnpm-workspace-commands.md
@@ -0,0 +1,41 @@
+# pnpm Workspace Commands
+
+This is a pnpm monorepo. All package management and script execution must follow workspace conventions.
+
+## Rules
+
+1. **Always use `pnpm`** — never `npm`, `npx`, or `yarn`
+
+2. **Run installs from the repo root with a workspace filter:**
+   ```sh
+   pnpm install --filter frontend
+   ```
+   Never `cd frontend && pnpm install`
+
+3. **Run scripts from the `frontend/` directory** (dev server, build, lint, test):
+   ```sh
+   cd frontend && pnpm dev
+   cd frontend && pnpm build
+   cd frontend && pnpm lint
+   cd frontend && pnpm test
+   cd frontend && pnpm tsc-check
+   ```
+
+4. **Never use `npm run *`** — `.claude/settings.json` only allows `Bash(pnpm *)` and git commands, and pnpm is the required tool for this repo
+
+## Common Commands Reference
+
+| Task | Command (from `frontend/`) |
+|---|---|
+| Dev server | `pnpm dev` |
+| Production build | `pnpm build` |
+| Type check | `pnpm tsc-check` |
+| Lint | `pnpm lint` |
+| Lint + fix | `pnpm lint:fix` |
+| Format | `pnpm format` |
+| Tests | `pnpm test` |
+| Storybook | `pnpm storybook` |
+
+## Why
+
+pnpm workspaces manage shared dependencies and hoisting. Using npm or yarn will bypass lockfile integrity and may install incorrect dependency versions.
diff --git a/.claude/settings.json b/.claude/settings.json
new file mode 100644
index 000000000..a0626743c
--- /dev/null
+++ b/.claude/settings.json
@@ -0,0 +1,24 @@
+{
+    "$schema": "https://json.schemastore.org/claude-code-settings.json",
+    "permissions": {
+      "allow": [
+        "Bash(pnpm *)",
+        "Bash(git status)",
+        "Bash(git diff *)",
+        "Bash(git log *)",
+        "Bash(git checkout *)",
+        "Bash(git commit *)",
+        "Read",
+        "Write",
+        "Edit"
+      ],
+      "deny": [
+        "Bash(rm -rf *)",
+        "Bash(curl *)",
+        "Bash(git push *)",
+        "Bash(git reset --hard)",
+        "Read(./.env)",
+        "Read(./.env.*)"
+      ]
+    }
+  }
\ No newline at end of file
diff --git a/.claude/skills/tech-writer/Skill.md b/.claude/skills/tech-writer/Skill.md
new file mode 100644
index 000000000..fb28b9249
--- /dev/null
+++ b/.claude/skills/tech-writer/Skill.md
@@ -0,0 +1,176 @@
+# Tech Writer
+
+Write public-facing documentation for new features, improvements, or changes in LFX Insights.
+
+## When to Use
+
+Invoke `/tech-writer` when:
+- A new feature has been built and needs a doc page
+- An existing feature has changed and its doc needs updating
+- A new metric, concept, or configuration option needs to be explained publicly
+- The user says "write docs for X", "document this feature", "update the docs"
+
+## Docs Site Overview
+
+- **Location:** `frontend/docs/`
+- **Framework:** VitePress (Markdown → static site)
+- **Live URL:** `https://insights.linuxfoundation.org/docs/`
+- **Local preview:** `cd frontend && pnpm docs:dev` → `http://localhost:5173`
+- **Sidebar config:** `frontend/docs/.vitepress/config.ts` — every new page must be added here
+
+### Sidebar Sections
+
+| Section | Folder | Purpose |
+|---|---|---|
+| Introduction | `docs/introduction/` | What Insights is, data sources, contributions, maintainers |
+| Metrics | `docs/metrics/` | Health score, contributors, popularity, development, security |
+| Features | `docs/features/` | User-facing product features (Copilot, repo groups, collections) |
+| More | `docs/more/` | FAQ, glossary |
+
+**Rule:** New feature docs go in `docs/features/`. New metric docs go in `docs/metrics/`. Clarifications or concept docs go in `docs/introduction/`.
+
+## File Structure
+
+Each doc lives in its own folder as `index.md`:
+
+```
+frontend/docs/features/my-new-feature/index.md
+```
+
+Images go in:
+```
+frontend/docs/images/my-new-feature-screenshot.png
+```
+
+Reference images with relative paths:
+```markdown
+![Alt text](../../images/my-new-feature-screenshot.png)
+```
+
+## Markdown Conventions
+
+**No frontmatter for standard doc pages** — regular docs in `docs/features/`, `docs/metrics/`, and `docs/introduction/` start directly with the `#` heading (unlike blog posts which use YAML frontmatter). Special VitePress pages (such as `frontend/docs/index.md` with `layout: home`) may use YAML frontmatter when required by the framework.
+
+**Heading hierarchy:**
+```markdown
+# Feature Name          ← page title, used in sidebar if not overridden
+## Overview             ← first section, always present
+## How It Works         ← or "Using X", "Key Concepts", etc.
+## Example              ← include screenshots when possible
+## Configuration        ← if applicable
+## FAQ                  ← if applicable
+```
+
+**VitePress callout blocks:**
+```markdown
+::: warning ⚠️ Heads up
+Something the user should be aware of.
+:::
+
+::: info
+Neutral informational note.
+:::
+
+::: tip
+Helpful suggestion or shortcut.
+:::
+```
+
+**Links — always use relative paths within docs:**
+```markdown
+[Health Score](../../metrics/health-score/index.md)
+[Data Sources](../../introduction/data-sources/index.md)
+```
+
+**Tables:**
+```markdown
+| Column A | Column B |
+|---|---|
+| Value    | Value    |
+```
+
+**Images:**
+```markdown
+![Descriptive alt text](../../images/feature-name.png)
+```
+
+## Writing Style
+
+- **Audience:** open source maintainers, contributors, and project leads — technically literate but not necessarily engineers
+- **Tone:** clear, direct, informative — not marketing-heavy
+- **Perspective:** second person ("you can", "your project") for instructions; third person for concept explanations
+- **Length:** as long as needed, no padding — each section should earn its place
+- **No jargon** without a definition or link to the glossary
+
+**Avoid:**
+- "Simply", "easily", "just" — don't minimize complexity
+- Passive voice where active is clearer
+- Repeating the page title verbatim in the first sentence
+
+## Workflow
+
+When `/tech-writer` is invoked, follow these steps:
+
+### Step 1 — Understand the feature
+
+Before writing anything:
+1. Ask the user: *"What is the feature? What does it do for the end user?"* if not already described
+2. Read relevant source files to understand the implementation — check `frontend/app/pages/`, `frontend/app/components/modules/`, and `frontend/server/api/`
+3. Check if a doc already exists in `frontend/docs/` for this topic — if so, update rather than create
+
+### Step 2 — Decide placement
+
+Based on what the feature is:
+- **New product feature** (UI, workflow, user action) → `docs/features/<slug>/index.md`
+- **New metric or data point** → `docs/metrics/<slug>/index.md`
+- **Concept, term, or data explanation** → `docs/introduction/<slug>/index.md` or add to `docs/more/glossary/index.md`
+- **Update to existing page** → edit the existing file
+
+### Step 3 — Draft the doc
+
+Use the structure:
+```markdown
+# <Feature Name>
+
+## Overview
+
+<2–4 sentence description of what this feature is and why it matters to the user.>
+
+## <Core Section>
+
+<Explain how it works, what the user sees, what actions they can take.>
+
+## Example
+
+<Screenshot or walkthrough. If no screenshot is available yet, add a placeholder note.>
+
+## <Additional Sections as needed>
+```
+
+### Step 4 — Update the sidebar
+
+After creating a new file, add it to the sidebar in `frontend/docs/.vitepress/config.ts`:
+
+```ts
+// In the correct section:
+{ text: 'My New Feature', link: '/features/my-new-feature/index.md' },
+```
+
+Match the casing and style of surrounding entries.
+
+### Step 5 — Confirm with user
+
+Present the draft and ask:
+- Does the description match how you'd explain this to a user?
+- Are there screenshots you want to include?
+- Should this link to or from any other doc page?
+
+## Example Invocations
+
+```
+/tech-writer The team just shipped "Saved Filters" — users can now bookmark their current filter state and share it via URL. Write the docs.
+
+/tech-writer Update the Repository Groups doc to mention the new self-service request form we added.
+
+/tech-writer We added a new "Community Voice" tab to project pages that shows sentiment from GitHub Discussions. Document it.
+```
diff --git a/.gitignore b/.gitignore
index 4232c49f9..40d7b8488 100644
--- a/.gitignore
+++ b/.gitignore
@@ -14,4 +14,6 @@ node_modules
 database/Dockerfile.flyway
 database/flyway_migrate.sh
 
-**/AGENTS.md
\ No newline at end of file
+**/AGENTS.md
+
+CLAUDE.local.md
\ No newline at end of file
diff --git a/frontend/CLAUDE.md b/CLAUDE.md
similarity index 67%
rename from frontend/CLAUDE.md
rename to CLAUDE.md
index 17a74ee41..98eeef0e6 100644
--- a/frontend/CLAUDE.md
+++ b/CLAUDE.md
@@ -6,7 +6,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ### Package Management
 - Use `pnpm` for package management (not npm/yarn)
-- `pnpm install --filter lfx-insights...` - Install dependencies from project root
+- `pnpm install --filter frontend` - Install dependencies from project root
 - `pnpm dev` - Start development server on localhost:3000 (run from frontend directory)
 - Always run install commands from project root using workspace filter
 
@@ -31,7 +31,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 ## Architecture Overview
 
 ### Framework & Technology Stack
-- **Nuxt 3** (Vue 3) framework with TypeScript
+- **Nuxt 4** (Vue 3) framework with TypeScript
 - **Tailwind CSS** for styling with **PrimeVue** component library
 - **Pinia** for state management
 - **TanStack Vue Query** for data fetching and caching
@@ -41,28 +41,33 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 - **Vitest** for testing, **Storybook** for component development
 
 ### Project Structure
+All paths below are relative to the `frontend/` directory.
+
 ```
-app/                    # Main application code
-├── assets/            # Static assets and styles
-├── components/        # Vue components (UI kit and feature components)
-├── config/           # Configuration files
-├── layouts/          # Nuxt layout components
-├── pages/            # File-based routing pages
-└── plugins/          # Nuxt plugins
-
-server/                # Server-side code
-├── api/              # API routes and endpoints
-├── constants/        # Server constants
-├── data/            # Data layer and queries
-├── helpers/         # Utility functions
-├── middleware/      # Server middleware
-├── mocks/           # Mock data for development
-├── repo/            # Repository pattern implementations
-└── utils/           # Server utilities
-
-types/                # TypeScript type definitions
-composables/          # Vue composables
-setup/               # Nuxt configuration modules
+frontend/
+├── app/                    # Main application code
+│   ├── assets/            # Static assets and styles
+│   ├── components/        # Vue components (UI kit and feature components)
+│   ├── config/           # Configuration files
+│   ├── layouts/          # Nuxt layout components
+│   ├── pages/            # File-based routing pages
+│   ├── middleware/       # Client-side middleware
+│   └── plugins/          # Nuxt plugins
+│
+├── server/                # Server-side code
+│   ├── api/              # API routes and endpoints
+│   ├── constants/        # Server constants
+│   ├── data/            # Data layer and queries
+│   ├── helpers/         # Utility functions
+│   ├── middleware/      # Server middleware
+│   ├── mocks/           # Mock data for development
+│   ├── repo/            # Repository pattern implementations
+│   ├── types/           # Server-side type definitions
+│   └── utils/           # Server utilities
+│
+├── types/                # TypeScript type definitions
+├── composables/          # Vue composables
+└── setup/               # Nuxt configuration modules
 ```
 
 ### Key Architectural Patterns
@@ -93,6 +98,18 @@ setup/               # Nuxt configuration modules
   - `primevue.ts` - PrimeVue theming
   - `caching.ts` - Route caching rules
   - `sitemap.ts` - Sitemap generation
+  - `analytics.ts` - Analytics (Google Analytics, Plausible)
+  - `echarts.ts` - ECharts configuration
+  - `hooks.ts` - Nuxt lifecycle hooks
+  - `image.ts` - Image optimization
+  - `modules.ts` - Nuxt modules registration
+  - `og-image.ts` - Open Graph image generation
+  - `robots.ts` - Robots.txt configuration
+  - `runtime-config.ts` - Runtime environment config
+  - `site.ts` - Site metadata
+  - `vite.ts` - Vite bundler config
+  - `vue.ts` - Vue compiler options
+  - `rate-limiter.ts` - API rate limiting
 
 #### Environment & Deployment
 - Environment-specific configuration via runtime config
@@ -136,5 +153,5 @@ setup/               # Nuxt configuration modules
 - Prettier for code formatting
 - Husky git hooks for pre-commit checks
 - License headers automatically added via lint-staged
-- whenever you generate html/vue code make sure to use ui components from the ui kit in the project src/components/uikit
+- whenever you generate html/vue code make sure to use ui components from the ui kit in the project `frontend/app/components/uikit/`
 - make sure to always consider tailwind config file to see correct classes names