managarten/apps/mana/apps/web
Till JS d37483a0f9 feat(todo): map LLM topic hints to existing workspace tags
The parse-task endpoint already returns free-text label hints from the
LLM ("steuern", "haushalt", …). Now the todo store fuzzy-matches each
hint against the user's existing tags via tagCollection and assigns
the matched IDs to the task's metadata.labelIds.

Match policy is intentionally conservative:
- Normalize via NFD strip + lowercase + collapsed whitespace
- Exact normalized match wins
- Substring fallback only for ≥3 char strings (avoids "ab" hitting
  every tag containing "ab")
- Never auto-creates a tag — even if the LLM is sure, an unknown topic
  silently drops, because auto-creating would clutter the user's tag
  list with one-off duplicates from voice transcripts

Both flows pick this up: voice always (transcripts almost always carry
topic hints) and typed only when there's structured payoff, same
asymmetry as before — typed quick-add now also enriches when the LLM
just finds a tag match without a date or priority.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-08 16:21:32 +02:00
..
e2e feat(events): bring list (wer bringt was?) — Phase 2 2026-04-07 19:31:39 +02:00
src feat(todo): map LLM topic hints to existing workspace tags 2026-04-08 16:21:32 +02:00
static feat: rename ManaCore to Mana across entire codebase 2026-04-05 20:00:13 +02:00
.env.example chore: complete ManaCore → Mana rename (docs, go modules, plists, images) 2026-04-07 12:26:10 +02:00
.gitignore feat: rename ManaCore to Mana across entire codebase 2026-04-05 20:00:13 +02:00
Dockerfile fix(mana/web): commit module-registry + module.config.ts files (build-critical) 2026-04-07 19:49:58 +02:00
eslint.config.js chore: complete ManaCore → Mana rename (docs, go modules, plists, images) 2026-04-07 12:26:10 +02:00
MIDDLEWARE_SECURITY.md feat: rename ManaCore to Mana across entire codebase 2026-04-05 20:00:13 +02:00
package.json fix(events): production wiring + polling resilience (quick wins) 2026-04-07 18:53:29 +02:00
playwright.config.ts test(events): playwright e2e specs + flake-resistant config 2026-04-07 18:36:45 +02:00
README.md chore: complete ManaCore → Mana rename (docs, go modules, plists, images) 2026-04-07 12:26:10 +02:00
SETUP.md chore: complete ManaCore → Mana rename (docs, go modules, plists, images) 2026-04-07 12:26:10 +02:00
svelte.config.js feat: rename ManaCore to Mana across entire codebase 2026-04-05 20:00:13 +02:00
tailwind.config.js feat: rename ManaCore to Mana across entire codebase 2026-04-05 20:00:13 +02:00
tsconfig.json feat: rename ManaCore to Mana across entire codebase 2026-04-05 20:00:13 +02:00
vite.config.ts fix(mana/web): unblock voice capture — permissions policy, notification mount, dev SW 2026-04-08 15:36:03 +02:00
WELCOME_ROUTE_SETUP.md chore: complete ManaCore → Mana rename (docs, go modules, plists, images) 2026-04-07 12:26:10 +02:00

Mana Web

Modern SvelteKit web application for Mana credit/mana management system.

Features

  • 🔐 Authentication with Supabase
  • 🎨 Tailwind CSS for styling
  • 📱 Responsive design
  • 🔄 Real-time updates
  • 🏢 Organization management
  • 👥 Team management
  • 💰 Credit/Mana transfers
  • 🧪 Comprehensive testing

Tech Stack

  • Framework: SvelteKit 2.x with Svelte 5 (Runes)
  • Language: TypeScript
  • Styling: Tailwind CSS 3.x
  • Backend: Supabase (PostgreSQL + Auth)
  • Middleware: Mana Middleware API
  • Testing: Vitest + Playwright
  • Deployment: Vercel/Netlify ready

Getting Started

Prerequisites

  • Node.js 20+ and pnpm
  • Supabase account and project
  • Access to Mana Middleware

Installation

# Install dependencies
pnpm install

# Copy environment variables
cp .env.example .env

# Update .env with your credentials:
# - PUBLIC_SUPABASE_URL
# - PUBLIC_SUPABASE_ANON_KEY
# - PUBLIC_MIDDLEWARE_URL

Development

# Start dev server
pnpm dev

# Run type checking
pnpm check

# Run tests
pnpm test

# Run E2E tests
pnpm test:e2e

Building

# Build for production
pnpm build

# Preview production build
pnpm preview

Project Structure

src/
├── routes/              # File-based routing
│   ├── (auth)/         # Auth routes (login, register)
│   ├── (app)/          # Protected app routes
│   │   ├── dashboard/
│   │   ├── organizations/
│   │   ├── teams/
│   │   └── settings/
│   └── api/            # API endpoints
├── lib/
│   ├── components/     # Reusable components
│   │   ├── ui/        # UI primitives
│   │   └── features/  # Feature components
│   ├── stores/        # Svelte stores
│   ├── utils/         # Utilities
│   ├── types/         # TypeScript types
│   └── server/        # Server-only code
│       ├── db/        # Database utilities
│       ├── auth/      # Auth helpers
│       └── api/       # API integration
├── hooks.server.ts    # Server hooks
└── app.css            # Global styles

Environment Variables

Public Variables (exposed to client)

  • PUBLIC_SUPABASE_URL - Supabase project URL
  • PUBLIC_SUPABASE_ANON_KEY - Supabase anonymous key
  • PUBLIC_MIDDLEWARE_URL - Mana Middleware URL
  • PUBLIC_APP_NAME - Application name

Private Variables (server-only)

Add any private API keys or secrets here.

Deployment

Netlify (Production Setup)

The app is currently deployed to https://app.mana.how using Netlify.

Prerequisites

# Install Netlify CLI globally
npm install -g netlify-cli

# Login to Netlify
netlify login

Initial Setup (One-time)

The project is already configured with @sveltejs/adapter-netlify. If you need to set it up from scratch:

# Install the Netlify adapter
pnpm add -D @sveltejs/adapter-netlify

Update svelte.config.js:

import adapter from '@sveltejs/adapter-netlify';

Environment Variables

Ensure your .env file exists with the following variables:

PUBLIC_SUPABASE_URL=your_supabase_url
PUBLIC_SUPABASE_ANON_KEY=your_supabase_anon_key
MIDDLEWARE_URL=https://mana-middleware-111768794939.europe-west3.run.app

Important: Set these same environment variables in Netlify Dashboard → Site Settings → Environment Variables for production builds.

Deployment

# 1. Install dependencies (if needed)
pnpm install

# 2. Build for production
pnpm build

# 3. Deploy to production (site: mana)
netlify deploy --prod --site mana --dir build

The build process creates:

  • build/ - Static assets and client code
  • .netlify/ - Serverless functions for SSR

Build Output

After running pnpm build, you should see:

  • Client bundle in build/
  • Server functions in .netlify/
  • Netlify configuration (_headers, _redirects)

Vercel (Alternative)

# Install Vercel adapter instead
pnpm add -D @sveltejs/adapter-vercel

# Deploy
vercel

Docker

# Build image
docker build -t mana-web .

# Run container
docker run -p 3000:3000 mana-web

Contributing

  1. Create a feature branch
  2. Make your changes
  3. Run tests and type checking
  4. Submit a pull request

License

Private - All rights reserved