Till JS f10439e369 fix(mana-analytics): point migration at public.feedback_status, not feedback.* ... Drizzle's pgEnum() ohne pgSchema-Wrap landet immer in public — der schemaFilter versteckt das nur im Diff (siehe Repo-Memory: "Drizzle enums with schemaFilter must use pgSchema().enum()"). Die Tabelle feedback.user_feedback referenziert die Enums quer aus public, das funktioniert; aber die ALTER-TYPE-Statements in der ursprünglichen Migration zielten auf feedback.feedback_status / feedback.feedback_category und hätten damit nichts gefunden. Lokal verifiziert (mana_platform.public.feedback_status, mana_platform.public.feedback_category): - 6 Status-Werte umbenannt → submitted/under_review/planned/in_progress/completed/declined - Default-Status auf 'submitted' - Category 'onboarding-wish' hinzugefügt - Re-Run idempotent (DO-Blöcke + ADD VALUE IF NOT EXISTS) Mittelfristig sollte feedbackSchema.enum(...) verwendet werden, damit Enums tatsächlich im feedback-Namespace landen — eigener Refactor. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-26 21:55:45 +02:00
..
drizzle	fix(mana-analytics): point migration at public.feedback_status, not feedback.*	2026-04-26 21:55:45 +02:00
src	refactor(feedback): align package + DB enums, plan central hub	2026-04-26 21:52:25 +02:00
CLAUDE.md	chore: complete ManaCore → Mana rename (docs, go modules, plists, images)	2026-04-07 12:26:10 +02:00
Dockerfile	chore: misc fixes, new services, lockfile cleanup	2026-03-28 10:27:35 +01:00
drizzle.config.ts	feat: rename ManaCore to Mana across entire codebase	2026-04-05 20:00:13 +02:00
package.json	refactor(shared-tailwind): rewrite themes.css to single-layer shadcn convention	2026-04-09 01:13:06 +02:00
tsconfig.json	feat(services): create mana-analytics, remove feedback/analytics/ai from auth	2026-03-28 02:29:24 +01:00