2580 commits

Author	SHA1	Message	Date
Till JS	98207eb1fc	chore(mana-web): /offline-Kommentar updated nach Layout-Bypass-Fix ... Folge-Commit zu a0a463a4f. Der FIXME-Block in +page.ts war noch der alte „prerender = false weil 500-Crash" — jetzt ersetzt durch die Erklärung warum @-Notation + prerender = true die saubere Lösung sind. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-20 14:42:14 +02:00
Till JS	a0a463a4f1	fix(mana-web): /offline prerendert wieder + ohne Workbox-Bug ... Seit 2026-04-07 stand `prerender = false` mit FIXME im Repo, weil der SvelteKit-Build-SSR der Offline-Page in „Error: 500 /offline" lief — ohne Stack. Daraus folgten zwei latente Probleme: - /offline lag NICHT in `prerendered/`, die @mana/shared-pwa-Workbox matched aber nur `**/*.html`. Pageta hat 2026-05-20 denselben Effekt unter `non-precached-url: /offline` aufgedeckt. - SSR-at-request-time war kaschiert, weil mana.how heute kaum Worker-Caching greift. Root-Cause: `apps/mana/apps/web/src/routes/+layout.svelte` lädt Dexie / encryption-vault / data-layer-listeners / auth-store auf Modul-Ebene — Browser-only Code (window/document/IndexedDB) explodiert im SSR-Worker. Fix: `/offline` aus der Layout-Chain rauswerfen. Datei umbenannt von `+page.svelte` zu `+page@.svelte` (SvelteKit-Konvention: @-Suffix bricht alle Eltern-Layouts). OfflinePage-Komponente aus @mana/shared-ui kommt ohne Stores aus, also unproblematisch. Verifiziert: - pnpm run build → keine Crashes mehr - `.svelte-kit/output/prerendered/pages/offline.html` (9.2 KB) generiert - `sw.js` Precache enthält `/offline` + `offline/__data.json` - Workbox `createHandlerBoundToURL("/offline")` hat jetzt ein Target Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-20 14:41:34 +02:00
Till JS	8b7b56f823	docs(lasts): scan.ts Header an leere SOURCES anpassen, auf Followup-Playbook verweisen ... Nach places-Lift hat scan.ts SOURCES=[]. Der alte Header behauptete "M3 ships only places source" — das war historisch korrekt, ist aber seit dem places-Decommission irreführend. Jetzt klar dokumentiert: Inbox bleibt leer bis habits/contacts-Source kommt; manuelles create_last via UI/Tool funktioniert weiter. Plan-Doc: mana/docs/playbooks/MANAGARTEN_LIFTS_FOLLOWUPS.md @ 9e7046f. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-19 19:49:57 +02:00
Till JS	7b842cabaf	chore(mana): places + locationLogs aus unified-App entfernen ... viadocu ist als Standalone-App live (viadocu-api.mana.how) und deckt GPS-Tracking + Cities-Aggregation ab. Till bestätigt: keine User-Daten, 5 places-exklusive Features (Kategorien home/work/shopping/transit/ leisure, Heart-Favoriten, Tags, Visit-Counter pro Place, Place-Sharing via Unlisted-Snapshot) werden bewusst aufgegeben. Entfernt: - apps/mana/apps/web/src/routes/(app)/places/ (1 Route) - apps/mana/apps/web/src/lib/modules/places/ (Stores, Queries, Collections, Types, Tools, Views, SharedPlaceView, tracking-store mit Geolocation-Permission-Flow) - apps/mana/apps/web/src/lib/i18n/locales/places/ (DE/EN/ES/FR/IT) - apps/mana/apps/web/src/lib/modules/lasts/inference/sources/places.ts (places war einzige aktive Inference-Source; SOURCES-Array jetzt leer, habits/contacts-Sources sind M3.b geplant) Cross-Module-Konsumenten aufgeräumt: - modules/website/embeds.ts: resolvePlaces + 'places.places' embed-Case - modules/myday/tools.ts: allPlaces-Read + visitedToday-Aggregat raus - data/projections/day-snapshot.ts: places-Section + trackingStore- Import raus - data/projections/types.ts: DaySnapshot.places-Feld raus - data/projections/context-document.ts: "X Orte besucht" + "Standort- Tracking aktiv" Zeilen raus - data/unlisted/resolvers.ts: buildPlaceBlob + 'places'-Case raus - data/privacy/exposed-records.ts: places-Eintrag raus - data/ai/revert/inverse-operations.ts: PlaceCreated-Inverse raus - routes/share/[token]/+page.svelte: SharedPlaceView-Mount raus Cross-Refs raus: - module-registry.ts (placesModuleConfig) - module-registry.test.ts (places-Tabellen) - data/tools/init.ts (placesTools) - data/crypto/registry.ts (places + locationLogs entry) - data/crypto/plaintext-allowlist.ts (placeTags) - app-registry/apps.ts (registerApp 'places' + MapPin-Icon-Import) - packages/shared-branding/src/mana-apps.ts (places-Eintrag) NICHT angefasst (mit Absicht): - data/database.ts db.version()-Stores — Schema-Snapshots sind frozen. Tabellen places, locationLogs, placeTags bleiben im IndexedDB-Schema, werden aber nicht mehr beschrieben. - packages/shared-branding/src/app-icons.ts APP_ICONS.places. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-19 17:22:38 +02:00
Till JS	0112161e78	chore(mana+api): articles + Backend-Worker raus, pageta trägt allein ... Pageta ist seit 2026-05-17 standalone live (pageta.mana.how + pageta.com, voll-featured laut STATUS.md) und deckt alle Articles-Module-Features ab + mehr (research, reactions, feed, share, snapshot, preferences). Keine User-Daten im managarten/articles-Modul (Till bestätigt). Frontend entfernt: - apps/mana/apps/web/src/routes/(app)/articles/ (9 Routes inkl. (tabs), [id], add, import, import/[jobId], settings) - apps/mana/apps/web/src/lib/modules/articles/ (5 Stores, Queries, Collections, Types, Tools, Components, Widgets, ArticlesTabShell, consume-pickup, tab-context, parse-urls) - apps/mana/apps/web/src/lib/i18n/locales/articles/ (DE/EN/ES/FR/IT) Backend entfernt: - apps/api/src/modules/articles/ (routes, import-worker, import-projection, import-extractor, consent-wall, field-meta, plus Tests) - apps/api/src/index.ts: articlesRoutes + startArticleImportWorker raus - apps/api/src/lib/metrics.ts: 5 articles-Metrics raus (articlesImportTicks/Items/Extract/JobsCompleted/PickupGc) "Save-to-Articles"-Features in anderen Modulen entfernt (User kann später direkt in pageta speichern via Share-Sheet): - news-research/ListView + routes/(app)/news-research/+page.svelte: "Speichern"-Button raus - writing/tools.ts: save_draft_as_article-Tool raus - writing/components/ExportMenu.svelte: "Als Artikel speichern"-Option raus - writing/components/ReferencePicker.svelte: 'article'-Mode raus - writing/components/ReferenceChip.svelte: KIND_ICON/LABEL ohne 'article' - writing/utils/reference-resolver.ts: resolveArticle + 'article'-case raus - writing/utils/reference-resolver.test.ts: kind: 'article' → 'note' in Aggregate-Budget-Tests - writing/utils/prompt-builder.test.ts: 'article'-Resolved-Reference raus - writing/views/DetailView.svelte: 'articles'-published-Chip raus - writing/types.ts: DraftReferenceKind ohne 'article', DraftPublishModule ohne 'articles' Aktualisiert (Cross-Refs raus): - module-registry.ts (articlesModuleConfig) - module-registry.test.ts (articles-Tabellen + sync-name-Mappings) - data-layer-listeners.ts (startArticlePickupConsumer) - app-registry/apps.ts (registerApp 'articles') - packages/shared-branding/src/mana-apps.ts (articles-Eintrag) - components/dashboard/widget-registry.ts (ArticlesUnreadWidget) - types/dashboard.ts (WidgetType 'articles-unread') - data/crypto/registry.ts (LocalArticle/LocalHighlight) - data/crypto/plaintext-allowlist.ts (articleTags/articleImportJobs/ articleImportItems/articleExtractPickup) - data/tools/init.ts (articlesTools) NICHT angefasst (mit Absicht): - data/database.ts db.version()-Stores — Schema-Snapshots sind frozen. Tabellen articles, articleHighlights, articleTags, articleImportJobs, articleImportItems, articleExtractPickup bleiben im IndexedDB-Schema, werden aber nicht mehr beschrieben. - packages/shared-branding/src/app-icons.ts APP_ICONS.articles (für Native-PNG-Generator, harmlos). - apps/api/src/lib/sync-db.ts Z6 Kommentar (historisches Beispiel). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-19 16:44:20 +02:00
Till JS	001548c74d	chore(mana): quotes + apps/quotes aus unified-App entfernen ... Zitare ist als Standalone-App live (zitare.mana.how) und im Wesentlichen feature-complete für das Public-Korpus + Curator-Workflow. Keine Daten im managarten/quotes-Modul vorhanden (Till bestätigt), kein Migrations-Aufwand. Lücken in zitare (Favoriten/Lists/Custom-private-Quotes) bewusst nicht jetzt geschlossen — DB-Schema in zitare für User-Collections ist da (collections.curatorId + visibility='private'), API/UI können später nachgezogen werden wenn gebraucht. Entfernt: - apps/mana/apps/web/src/routes/(app)/quotes/ (6 Routes inkl. category, lists, favorites, categories) - apps/mana/apps/web/src/lib/modules/quotes/ (6 Stores, Queries, Collections, Tools, Types, SpiralCanvas-Component) - apps/mana/apps/web/src/lib/i18n/locales/quotes/ (DE/EN/ES/FR/IT) - apps/mana/apps/web/src/lib/search/providers/quotes.ts - apps/mana/apps/web/src/lib/components/dashboard/widgets/QuoteWidget.svelte - apps/mana/apps/web/src/lib/modules/core/widgets/QuoteOfTheDayWidget.svelte - apps/quotes/ (komplettes Top-Level inkl. @quotes/content Workspace- Package mit 87 Zitaten in 13 Kategorien) Aktualisiert (Quotes-Refs raus): - module-registry.ts (quotesModuleConfig) - module-registry.test.ts (quotes-Tabellen + sync-name-Mappings) - cross-app-queries.ts (useRandomFavorite + LocalFavorite-Import) - search/providers/index.ts (registerLazy 'quotes') - app-registry/apps.ts (registerApp 'quotes' + Quotes-Icon-Import) - packages/shared-branding/src/mana-apps.ts (quotes-Eintrag) - hooks.server.ts (Allowlist) - types/dashboard.ts (WidgetType 'quotes-quote' + 'quotes') - types/dashboard.test.ts - stores/dashboard.svelte.ts (Widget-Default-Liste) - splitscreen/registry.ts - components/dashboard/widget-registry.ts - modules/core/widgets/{WidgetGrid.svelte,index.ts} - modules/spiral/collect.ts (Quotes/Music/Cards-Snapshots raus — collect dient den Spiral-DB-Engagement-Snapshot, alle 3 Apps sind dekommissioniert) - crypto/plaintext-allowlist.ts (quotesFavorites/Lists/ListTags + customQuotes raus; bei der Gelegenheit auch music-Reste: mukkeProjects/playlistSongs/songTags) - apps/mana/apps/web/package.json ('@quotes/content' Workspace-Dep) - package.json (6 Quotes-Scripts: quotes:dev, dev:quotes:*, deploy:landing:quotes, cf:projects:create-Eintrag, dev:quotes:local) NICHT angefasst (mit Absicht): - data/database.ts db.version(1).stores — Schema-Snapshot ist frozen (gleiche Konvention wie für cards/music). Tabellen quotesFavorites, quotesLists, quotesListTags, customQuotes bleiben im IndexedDB- Schema, werden aber nicht mehr beschrieben. - packages/spiral-db — bleibt, wird vom verbleibenden modules/spiral noch konsumiert (Mana-Activity-Spiral). - packages/shared-branding/src/app-icons.ts APP_ICONS.quotes (für Native-PNG-Generator, harmlos). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-19 16:15:22 +02:00
Till JS	1b637b9aa7	chore(repo): fix pre-existing svelte-check errors blocking pre-push ... Drei Root-Causes für die 8 pre-existing svelte-check errors auf main (blockierten den pre-push-Hook seit längerem): 1. `dexie` fehlte als devDep in packages/shared-stores — 4 Files importieren `type { Table } from 'dexie'`. Type-only-Import, daher devDep reicht. 2. `vite-plugin-pwa` fehlte als devDep in apps/mana/apps/web. Wird nur transitiv via `@vite-pwa/sveltekit` gezogen, aber die `/// <reference types="vite-plugin-pwa/info" />`-Direktiven in src/app.d.ts brauchen das Package direkt im Tree. 3. packages/shared-auth/tsconfig.json baut `src/**/*` inklusive `*.spec.ts` — Spec-Files sollen aber nicht in den prepare-Build. exclude erweitert um `*.spec.ts` + `*.test.ts`. Verifikation: `pnpm check` von apps/mana/apps/web läuft jetzt mit 0 ERRORS / 0 WARNINGS / 0 FILES_WITH_PROBLEMS (vorher 8 Errors). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-19 15:34:21 +02:00
Till JS	f9159741a0	chore(mana): music + apps/mukke aus unified-App entfernen ... Mukke ist seit 2026-05-19 als Standalone-App live (mukke.mana.how + mukke-api.mana.how, Repo git.mana.how/till/mukke) mit umfassenderem Feature-Set (Studio, Wavesurfer, Lyrics-Sync, Beats, LRC/SRT/JSON- Export, ID3-Extract, S3-Streaming). Modul + alte Landing können raus. Entfernt: - apps/mana/apps/web/src/routes/(app)/music/ (alle 6 Routes) - apps/mana/apps/web/src/lib/modules/music/ (Stores, Queries, Collections, Tools, Types, Views, Components) - apps/mana/apps/web/src/lib/i18n/locales/music/ (DE/EN/ES/FR/IT) - apps/mana/apps/web/src/lib/search/providers/music.ts - apps/mana/apps/web/src/lib/components/dashboard/widgets/MusicLibraryWidget.svelte - apps/mukke/ (alte Landing + shared types-Package — Standalone hat beides selbst; VISUALIZER_CONCEPT.md + ALTERNATIVES.md vorab nach mukke/docs/ ins Standalone-Repo migriert) Aktualisiert (Music-Refs raus): - module-registry.ts (musicModuleConfig) - module-registry.test.ts (music-Tabellen-Expectation) - cross-app-queries.ts (useMusicStats + MusicStats-Interface) - tools/init.ts (musicTools-Init) - search/providers/index.ts (registerLazy 'music') - app-registry/apps.ts (registerApp 'music' + MusicNotes-Icon-Import) - packages/shared-branding/src/mana-apps.ts (music-Eintrag) - hooks.server.ts (Allowlist) - types/dashboard.ts (WidgetType 'music-library' + RequiredBackend) - types/dashboard.test.ts (Erwartung 'music-library') - stores/dashboard.svelte.ts (Widget-Default-Liste) - splitscreen/registry.ts - components/dashboard/widget-registry.ts NICHT angefasst (mit Absicht): - data/database.ts db.version(1).stores — Schema-Snapshot ist frozen (gleiche Konvention wie für cards/quotes). Tabellen (songs, mukkePlaylists, playlistSongs, mukkeProjects, markers, songTags) bleiben im IndexedDB-Schema, werden aber nicht mehr beschrieben. Bei Bedarf später ein db.version(N) mit `songs: null` etc. nachschieben. - modules/events/discovery/types.ts 'music' (Event-Kategorie, generisch) - data/time-blocks/types.ts 'music' (TimeBlock-Kategorie, generisch) - shared-ai/tools/schemas.ts 'music' (Event-Discovery-Enum) - packages/shared-branding/src/app-icons.ts APP_ICONS.music (für Native-PNG-Generator, harmlos) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-19 15:20:13 +02:00
Till JS	e9e43abaa0	shared-uload: HTTP-federation (Option B) — schreibt jetzt gegen uload-api ... Nach dem uLoad-Cutover 2026-05-18 (Code/uload/ als Standalone) war @mana/shared-uload structurell broken: ShareModal-Calls aus presi+ music landeten in mana_sync.sync_changes, aber der alte Konsument (mana-app-uload-server) ist abgeschaltet → 404 auf ulo.ad/r/<code>. Fix: shared-uload schreibt jetzt direkt via HTTP gegen die föderierte uload-API. - create-link.ts: createShortLink() → POST {apiUrl}/api/v1/links mit Authorization: Bearer <token>. Init-Signatur ist neu initSharedUload({ apiUrl, getAuthToken, shortUrlOrigin? }). - types.ts: UloadLink (Dexie-internal-Type) entfernt — Caller arbeiten nur noch mit CreateShortLinkOptions + CreatedLink (Wire-Shapes). - package.json: @mana/local-store-Dep entfernt. Version 0.2.0. - index.ts: getBaseUrl-Export ergänzt, UloadLink raus. Caller-Site (apps/mana/apps/web/src/routes/(app)/+layout.svelte): initSharedUload({ apiUrl: PUBLIC_ULOAD_API_URL ?? 'https://uload-api.mana.how', getAuthToken: () => authStore.getValidToken(), shortUrlOrigin: PUBLIC_ULOAD_SHORT_ORIGIN ?? 'https://ulo.ad', }); Bonus-Cleanup: - plaintext-allowlist.ts: uloadFolders + uloadTags raus (Tables sind via Dexie v67 gedroppt, Allowlist-Entries waren orphaned). mana-Web-App: pnpm check grün (0/0 auf 7396 Files).	2026-05-18 16:39:44 +02:00
Till JS	0b44acdde1	chore(mana): uload aus unified-App entfernen ... uLoad ist nach Code/uload/ als eigenständiger Hono+Bun-Server migriert (siehe mana/docs/playbooks/ULOAD_GREENFIELD.md, υ-0..υ-7 durch). Live auf: - uload.mana.how → :3108 (SvelteKit-Web, Standalone) - uload-api.mana.how → :3107 (Hono-API, eigene Postgres-DB im `uload`-Schema) - ulo.ad → :3107 (Short-Redirect-Domain) Gelöscht / abgebaut: - Module: apps/mana/.../modules/uload + Routen + Locales - Top-Level: apps/uload/ (alter SvelteKit-Web + Hono-Server-Code) - docker-compose.macmini.yml uload-server Service-Block (alter Container :3070 wurde durch Standalone-Stack auf :3107 ersetzt) - mana-web env: PUBLIC_ULOAD_SERVER_URL / _CLIENT in compose + hooks.server.ts (env-Injection, window.__-Export, CSP-connectSrc), status/+page.server.ts Service-List - prometheus uload-server scrape job + mana.how/uload probe - shared-branding APP_BRANDING.uload + APP_ICONS.uload + MANA_APPS uload-Entry + UloadLogo - spiral-db MANA_APP_INDEX.uload (=21) - shared-types/spaces 5× 'uload' Modul-Einträge in den Space-Listen - Registries: app-registry/apps.ts (Uload registerApp + DownloadSimple icon + Header), categories, help-content, module-registry, splitscreen, hooks.server APP_SUBDOMAINS, data/tools/init - package.json dev:uload:* + deploy:landing:uload Scripts - i18n: uload in apps/{de,en,es,fr,it}.json Was BLEIBT: - cloudflared `uload.mana.how` → :3108, `uload-api.mana.how` → :3107, `ulo.ad` → :3107 — Standalone-Routes - docker-compose mana-auth CORS_ORIGINS uload.mana.how + ulo.ad — SSO für Standalone Dexie v67: - droppt links + uloadTags + uloadFolders + linkTags mana-web svelte-check 0/0 (7256 files), snapshot test 10/10. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-18 16:14:40 +02:00
Till JS	2b08e2f3a2	chore(mana): comic aus unified-App entfernen ... Comic-Surface ist nach Comicello (comicello.mana.how + comicello.com) umgezogen. Comicello hat seit Phase ω-2 (2026-05-18) Feature-Parität + Cross-Module-Hooks via mana-share: - Character-Variant-Render mit pinned-Variant-Anker - Panel-Render via mana-image-edits - Panel-Edit/Delete/Reorder - POST /api/v1/share/receive für externe Apps (Journal/Notes/Calendar/ Library/Writing können Text-Snippet rüberschicken, Story wird als Draft angelegt) - /comics/new?text=…&sourceModule=… URL-Prefill als Alternative zum Server-Roundtrip Gelöscht / abgebaut: - Module: apps/mana/.../modules/comic + Routen + Locales - Backend: apps/api/src/modules/comic, picture/routes verifyMediaOwnership-Allowlist auf nur `['me']` reduziert (comic- Tag war hier Identity-Anchor-Quelle für panel renders, jetzt Comicello-intern) - shared-branding: APP_ICONS.comic + MANA_APPS comic-Entry - shared-ai/tools/schemas: ganzer Comic-Block (list_comic_stories, create_comic_story, generate_comic_panel, list_comic_characters, create_comic_character, generate_character_variant, pin_character_variant) - shared-ai/agents/templates: comic-author.ts + index.ts Eintrag - mana-tool-registry: modules/comic.ts + types ModuleId 'comic' raus - Cross-Module: website/embeds resolveComicStories + LocalComicStory-Import + 'comic.stories' EmbedSource + Inspector- Option; crypto-registry comicStories+comicCharacters; exposed-records comic-Eintrag - picture/types: comicStoryId, comicPanelIndex, comicCharacterId Back-Ref-Felder (sowohl LocalImage als auch Image-Public-DTO); picture/queries to-Public-Mapping - Registries: app-registry/apps.ts (Comic registerApp + FilmStrip- Icon + Header), categories, help-content, module-registry, data/tools/init - i18n: comic in apps/{de,en,es,fr,it}.json Was BLEIBT: - cloudflared `comicello.mana.how` + `comicello-api.mana.how` — Standalone-Routes - docker-compose mana-auth CORS_ORIGINS comicello.com + .mana.how — SSO für Standalone Dexie v66: - droppt comicStories + comicCharacters - Upgrade-Callback strippt comicStoryId/comicPanelIndex/comicCharacterId aus existierenden Image-Rows (waren nie indiziert, nur Properties) mana-web svelte-check 0/0 (7281 files), snapshot test 10/10. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-18 15:54:11 +02:00
Till JS	609f662538	chore(mana): news aus unified-App entfernen ... Reader-Surface ist nach Pageta (pageta.mana.how + pageta-api.mana.how) umgezogen, das seit 2026-05-16 live ist und mehr Features bietet als das alte managarten-news-Modul: - Highlights (4 Farben, plain-text-offsets, Kontext) - Reading-Progress + User-Note pro Artikel - Bulk-Import (200 URLs/Job mit Worker) - 5 MCP-Tools (save/list/archive/tag/highlight) - Reading-Status-Enum (unread/reading/finished/archived) statt Boolean Was Pageta NICHT hat: Categories mit Color+Icon — Pageta verwendet freie String-Tags statt visuelle Folders. Bewusste Design-Entscheidung in Pageta. Daten-Migration: KEIN automatisches Skript. User mit gespeicherten Artikeln im managarten-newsArticles müssen ihre Liste in Pageta neu aufbauen (oder Bulk-Import via /api/v1/imports verwenden). Gelöscht / abgebaut: - Module: apps/mana/.../modules/news + Routen + Locales - apps/articles/migrations/from-news.ts (one-off-Migration nach articles-Modul, Sentinel-gated, abgeschlossen) + Call in (app)/+layout.svelte - apps/api/src/modules/news + MCP-Executor save_news_article - shared-branding: APP_ICONS.news + MANA_APPS news-Entry - shared-ai/tools/schemas save_news_article - shared-types/spaces: 3 'news'-Einträge in Space-Modul-Listen - Cross-Module: news-research/ListView + (app)/news-research/+page.svelte hatten den preferencesStore + usePreferences vom news-Modul für Custom-Feed-Pinning — Pin-UI entfernt (Custom-Feeds sind jetzt Pageta-Verantwortung) - Dashboard: 'news-unread' Widget + NewsUnreadWidget-Import - Registries: app-registry/apps.ts (News registerApp + Newspaper icon + Header), categories, help-content, module-registry, data/tools/init - i18n: news in apps/{de,en,es,fr,it}.json Was BLEIBT: - `news-research` Modul + `apps/api/src/modules/news-research/` — RSS-Discovery + Search-Funktion bleibt im managarten als Recherche-Tool für andere Module - `mana-news-pool` Plattform-Service (Code/mana/services/) — wird von news-research + Pageta-Standalone konsumiert - shared-ai `research_news` Tool Dexie v65 Migration: - droppt newsArticles, newsCategories, newsPreferences, newsReactions, newsCachedFeed mana-web svelte-check 0/0, snapshot test 10/10. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-18 15:05:25 +02:00
Till JS	fc616688e3	chore(mana): memoro aus unified-App entfernen ... Memoro lebt als eigenständiger Stack: - `memoro.mana.how` (Astro landing :3120) - `memoro-app.mana.how` (SvelteKit Web SPA) - `memoro-api.mana.how` (Bun/Hono server) - `memoro-audio.mana.how` (audio-server) Quelle: `Code/memoro/`, deployt nach `~/projects/memoro-deploy/` auf Mac Mini. Phasenstand: Phase 2.5 (Cutover-Endphase), 2.5a/b durch. Gelöscht / abgebaut: - Module: apps/mana/.../modules/memoro + Routen + Locales - Top-Level: apps/memoro/ (Server, Audio-Server, Landing, Mobile) - docker-compose.macmini.yml memoro-server + memoro-audio-server Service-Blocks (alter Container im managarten-Compose, der echte Memoro läuft aus ~/projects/memoro-deploy/) - .github/workflows/cd-macmini.yml memoro-server + memoro-audio-server Build-Jobs + Service-Liste + Health-Check-Mapping - prometheus memoro-server scrape job + mana.how/memoro probe - shared-branding APP_BRANDING.memoro + APP_ICONS.memoro + MANA_APPS Memoro-Entry + MemoroLogo + onboarding-template - shared-utils analytics: memoro tracker + MemoroEvents-Block - website-blocks EmbedSourceSchema 'memoro.memos' + Inspector-Option - Cross-Module: website/embeds.ts resolveMemos + LocalMemo-Import, crypto-registry memos+memories + LocalMemo-Import, plaintext- allowlist memoSpaces+memoTags+memoroSpaces+spaceMembers, exposed-records memoro-Eintrag - Registries: app-registry/apps.ts (Memoro registerApp + Microphone icon + Header), categories, help-content, module-registry, splitscreen, hooks.server, data/tools/init - (app)/+layout.svelte startMemoroLlmWatcher/stopMemoroLlmWatcher imports + Calls - package.json memoro:dev / dev:memoro:* Scripts - cloudflared: irreführender Comment-Block in unified-app-Sektion bereinigt; Standalone-Memoro-Routes (memoro.mana.how, memoro-app.mana.how, memoro-api.mana.how, memoro-audio.mana.how) bleiben — sie zeigen auf den live Standalone-Stack - i18n locales apps/{de,en,es,fr,it}.json memoro raus Dexie v64 Migration: - droppt memos, memories, memoTags, memoroSpaces, spaceMembers, memoSpaces shared-theme/store.svelte.ts APP_THEME_CONFIGS.memoro bleibt erhalten — das Package wird auch vom externen Memoro-Web-Repo konsumiert. Test/Doku: - module-registry.test.ts: memoro-Eintrag aus SYNC_APP_MAP + memoroSpaces aus TABLE_TO_SYNC_NAME entfernt mana-web svelte-check 0/0, snapshot test 10/10. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-18 14:50:47 +02:00
Till JS	9a6e51b7a3	chore(mana): plants + who aus unified-App entfernen ... Plants → Herbatrium (herbatrium.mana.how, LIVE seit 2026-05-17), Who → eigenständiger Bun-Stack auf who.mana.how (außerhalb des managarten-Repos, deployt nativ unter PM2 auf dem Mac Mini). Gelöscht / abgebaut: - Module: apps/mana/.../modules/{plants,who} + Routen + Locales + routes/api/v1/who Proxy - Top-Level: apps/plants/ - Backend: apps/api/src/modules/{plants,who} + scripts/generate-who- dossiers.ts + RESOURCE_MODULES + app.route()-Mounts - shared-branding: APP_BRANDING, APP_ICONS, MANA_APPS, PlantsLogo - credits AI_PLANT_ANALYSIS, shared-utils analytics PlantsEvents, spiral-db MANA_APP_INDEX plants - Cross-Module: PlantWateringWidget, time-blocks/types, seed-registry PLANTS_GUEST_SEED, crypto-registry plants + plaintext-allowlist plantPhotos/plantTags/wateringLogs/wateringSchedules - Dashboard: 'plant-watering' Widget, requiredBackend 'plants', WIDGET_REGISTRY-Eintrag - Registries: app-registry/apps.ts + categories + help-content + module-registry + splitscreen + hooks.server APP_SUBDOMAINS + quick-input registry + data/tools/init - Infrastruktur: cloudflared plants.mana.how, docker-compose CORS_ORIGINS + MinIO plants-storage Bucket, prometheus probe, package.json plants:dev Scripts, i18n locales plants+who Strings - who.mana.how / who-api.mana.how Standalone-Routes BLEIBEN (PM2-Container auf Mac Mini, eigenständige Auth/SQLite/LLM-Keys) Dexie v62 (Nachholung) + v63 Migrations: - v62: dropped meals, goals, foodFavorites, mealTags, wardrobeGarments, wardrobeOutfits + images-Schema-Index ohne wardrobe-FKs + Upgrade- Callback strippt wardrobeOutfitId/wardrobeGarmentId aus Image-Rows. (Migration war im vorherigen Commit nicht im File gelandet, jetzt nachgeholt.) - v63: dropped plants, plantPhotos, wateringSchedules, wateringLogs, plantTags, whoGames, whoMessages. Test/Doku: - module-registry.test.ts Snapshot: plants-Eintrag entfernt, whoGames/whoMessages aus LEGACY_TABLES (werden jetzt gedroppt) mana-web svelte-check 0/0, snapshot test 10/10, streaks 5/5. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-18 14:25:45 +02:00
Till JS	0c15f73b58	backup-cron: lesen-postgres → pageta-postgres mapping ... Brand-Rebrand 2026-05-18 nachgezogen. lesen-postgres existiert nicht mehr, pageta-postgres läuft mit User pageta in DB pageta. Ohne dieses Mapping fällt der Container in den Default-Branch (User postgres) und backup failt still. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-18 12:49:15 +02:00
Till JS	ae04c9e194	chore(mana): citycorners + food + wardrobe aus unified-App entfernen ... Citycorners-Reste vom vorherigen Sprint mit committet. food → Nutriphi, wardrobe → Werdrobe sind als Standalone-Apps live; die mana.how-unified- App trägt die Modul-Surfaces nicht mehr. Gelöscht / abgebaut: - Module: apps/mana/.../modules/{food,wardrobe} + Routen + Locales - Landing-Apps: apps/{food,citycorners}/ Top-Level - Backend: apps/api/src/modules/{food,wardrobe} + MCP-Tools log_meal / nutrition_summary, picture-routes verifyMediaOwnership-Allowlist - shared-branding: APP_BRANDING, APP_ICONS, MANA_APPS, Logos, Onboarding - shared-ai, mana-tool-registry, credits, shared-types/spaces, shared-utils/analytics, spiral-db/MANA_APP_INDEX, website-blocks - Cross-Module: Body-CalorieWeightChart, Comic-CharacterPicker-Wardrobe, website-Embed wardrobe.outfits, DaySnapshot.nutrition, FoodEventType, MealLogged/Meal*-Streaks/Goals/Companion/Trigger, AI-Agent-Policy, GoalEditor MealLogged, MyDay/RitualRunner/Rules nutrition-Refs, Crypto-Registry meals/wardrobeGarments/wardrobeOutfits - Generic: PlaceCategory 'food' (places + geocoding + Locales), spaces.ts 'food'/'wardrobe' Modul-IDs - Infrastruktur: cloudflared, docker-compose CORS, nginx-Landing, prometheus-Probe, load-tests, package.json dev-Scripts, generate-env, mac-mini/build-landings, dependabot Dexie v62 Migration: - droppt meals, goals, foodFavorites, mealTags, wardrobeGarments, wardrobeOutfits Tabellen - entfernt wardrobeOutfitId / wardrobeGarmentId aus images-Index - Upgrade-Callback strippt die toten FK-Properties aus alten image-Rows Test/Doku: - module-registry.test.ts: Snapshot refresht auf aktuellen Stand mit 56 Modulen (vorher 32, statisch eingefroren pre-refactor). Plus LEGACY_TABLES-Exclusion für nicht-mehr-registrierte Tabellen aus cards/citycorners/moodlit/rituals/wishes/who. - streaks.test.ts: MealLogged-Test in TaskCompleted-Test umgebaut - apps/mana/CLAUDE.md: food-Refs in AI-Tool-Tabelle und AiProposalInbox-Liste entfernt - validate-i18n-keys.mjs + validate-no-recursive-turbo.mjs: existsSync-Guard, damit die Skripte mit gestaged-aber-rm'ten Dateien klarkommen mana-web svelte-check 0 errors / 7436 files, betroffene Tests grün (streaks, dashboard, module-registry), validate:pg-schema, validate:turbo, validate:i18n-parity grün. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-18 12:47:33 +02:00
Till JS	ad97c5362c	managarten cutover: news-Modul liest jetzt aus mana-news-pool ... apps/api/src/modules/news/routes.ts — ehemals Raw-SQL gegen mana_platform.news.curated_articles, jetzt HTTP-Proxy auf MANA_NEWS_POOL_URL/feed mit X-Service-Key. Identischer Query- Param-Vertrag (topics/lang/since/limit/offset), kein Drizzle- Schema-Coupling mehr für News. docker-compose.macmini.yml — MANA_NEWS_POOL_URL=http://mana-news-pool:3079 in mana-api environment. News-Ingester-Kommentar-Section aktualisiert (Container ist seit Lift-B abgeschaltet). Damit ist der vollständige Cutover-Pfad aus mana/services/mana-news-pool/CLAUDE.md durch: 1. Plattform-Service deployed (gestern) 2. managarten konsumiert ihn (jetzt) 3. alter news-ingester:3066-Container schon weg Type-check: news/routes.ts grün (2 pre-existing forms/-Errors unrelated).	2026-05-17 16:34:12 +02:00
Till JS	009a695345	fix(mana-web): add @simplewebauthn/browser as explicit dep ... Vite/Rollup im Docker-Build resolved den Import nicht über transitive shared-auth-Hoisting — anderes pnpm-Layout in der Container-Stage. Lokal funktionierte es nur durch zufällige Hoisting-Reihenfolge. `settings-client.ts` importiert `@simplewebauthn/browser` für Passkey- Register. Daher explizite Dep im managarten-Web-Paket. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-12 17:25:39 +02:00
Till JS	dd2e4b6e9f	fix(mana-auth): read PUBLIC_*_URL from window-injected vars, not $env/dynamic/public ... Pre-deploy-Audit gefunden: meine neue session.svelte.ts + portal-redirect.ts lasen PUBLIC_MANA_AUTH_URL/PUBLIC_AUTH_WEB_URL via $env/dynamic/public. In Production ist das aber die Docker-interne URL `http://mana-auth:3001`, die der Browser nicht erreichen kann — Folge wäre endlose Redirect-Loop bei der ersten User-Session. managarten hat das Pattern schon gelöst: hooks.server.ts injiziert `window.__PUBLIC_*_URL__` aus den `_CLIENT`-suffixed env-Vars (Public- Domain-Werte). `lib/data/scope/auth-fetch.authBaseUrl()` ist der kanonische Helper dafür. - session.svelte.ts: ruft jetzt `authBaseUrl()` aus auth-fetch. - portal-redirect.ts: eigenes window/process-Lookup für PUBLIC_AUTH_WEB_URL, gleiches Pattern. - hooks.server.ts: PUBLIC_AUTH_WEB_URL_CLIENT-Lesen + window-Injection. - docker-compose.macmini.yml (mana-app-web): PUBLIC_AUTH_WEB_URL + PUBLIC_AUTH_WEB_URL_CLIENT env-Vars hinzugefügt. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-12 17:05:28 +02:00
Till JS	5635598a58	feat(mana): migrate to central auth portal — no embedded login UI, clean cut ... managarten redet jetzt nicht mehr direkt mit Better-Auth — Login, Register, Passwort-Reset, 2FA-Verify, Magic-Link, Passkey-Login laufen ALLE über `auth.mana.how` (mana-auth-web portal). managarten ist nur noch Consumer einer existierenden Session. ## Architektur - Unauthenticated: `redirectToPortal({ next })` macht hartes Redirect zu `auth.mana.how/login?app=mana&redirect=<callback>`. AuthGate (`(app)/+layout.svelte`) und `require-auth` triggern das. - Nach Login: Portal setzt SSO-Cookie auf `.mana.how`. Browser landet auf `/auth/callback?next=<deep-link>`. - Callback: `session.tryRefresh()` holt frischen JWT via Cookie, `loadUserFromToken()` setzt User, `goto(next)` renderet (app)-Layout mit unlocked Vault (Root-Layout-$effect feuert auf User-ID-Wechsel). ## Files NEU: - `lib/auth/portal-redirect.ts` — Helper für Portal-URL-Bau + hard redirect. - `lib/auth/session.svelte.ts` — schlanke Session-Klasse: Token-Refresh via SSO-Cookie, ensureFresh, signOut. Storage: `mana.auth.accessToken`, `mana.auth.user`. - `lib/auth/settings-client.ts` — Passkey-CRUD, 2FA-Setup, Sessions, Audit-Events. Pflegt keinen State, ruft direkt mana-auth API. GELÖSCHT: - `routes/(auth)/login|register|forgot-password|reset-password|+layout` - `routes/auth/reset-password` (war Alias-Redirect) - Komplette `(auth)` route group. UMGESCHRIEBEN: - `lib/stores/auth.svelte.ts` — re-exportiert `session` als `authStore` (keine 47-Methoden-Factory aus `@mana/shared-auth-ui` mehr). - `routes/auth/callback/+page.svelte` — Token-Refresh + Deep-Link statt Legacy-Supabase-Stub. - `lib/components/settings/sections/SecuritySection.svelte` — alle `authStore.registerPasskey/enableTwoFactor/...` Calls auf neuen `settings-client` umgelenkt. UI-Komponenten (PasskeyManager, TwoFactorSetup, …) aus `@mana/shared-auth-ui` bleiben — sind reine Render-Components. ANGEPASST (Portal-Redirect statt `goto('/login')`): - `(app)/+layout.svelte`, `RouteTierGate`, `email-verified`, `verification-failed`, `feedback/+layout`, `quotes/lists`, `quotes/favorites`, `citycorners/favorites`, `feedback/DetailView`, `feedback/ListView`, `profile/ListView`, `guest-prompt`, `require-auth.svelte.ts`. ENV: - `.env.development`: `MANA_AUTH_WEB_URL=http://localhost:3002`. - `scripts/generate-env.mjs`: schreibt `PUBLIC_MANA_AUTH_URL` + `PUBLIC_AUTH_WEB_URL` ins `apps/mana/apps/web/.env`. ## Status - `pnpm run check`: 0 errors, 0 warnings, 7672 files. - `pnpm build` (8 GB heap): grün. - E2E lokal + Production-Deploy stehen aus — Plan siehe `mana/docs/playbooks/MANAGARTEN_AUTH_PORTAL_MIGRATION.md`. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-05-12 17:00:03 +02:00
Till JS	67963a4c0f	chore(devlog): Schritte 1+2 der mana/docs/DEVLOG.md-Migration ... 55 Session-Devlogs nach _legacy-sessions/ verschoben (git mv erhält History) und Disclaimer-Header injected. Astro-Routen so angepasst dass alle alten /devlog/<slug>-URLs erhalten bleiben — slug.replace strippt das _legacy-sessions/-Prefix in [slug].astro/index.astro/ activity.astro. Build-Test verifiziert: 55 Posts in dist/devlog/, kein nested _legacy-sessions/-Pfad. Disclaimer-Box pro Datei: > **Legacy-Format.** Dieser Eintrag stammt aus dem Session-basierten > Devlog vor der Umstellung auf das Tages-Modell (Cutover 2026-05-09). > Bestand bleibt erhalten und unverändert; neue Einträge folgen der > Tages-Konvention mit spieler.md + macher.md pro 06–06-Bucket. > Spec: mana/docs/DEVLOG.md. Offene Cutover-Schritte (eigene Session, blocked auf Verdaccio- Token-Setup für @mana/devlog-gen): - Tages-Modell-Collection mit data.json + spieler.md + macher.md (eigenes Schema, parallel zur Legacy-Ansicht) - @mana/devlog-gen via npm.mana.how integrieren (aktuell nur auf pkg.mana.how Lame-Duck publiziert) - CI-Workflow .github/workflows/devlog.yml für pnpm devlog:today	2026-05-09 02:08:51 +02:00
Till JS	0aec1d43c0	fix(docs): astro starlight repo URL → Memo-2023/managarten ... Vorbestehender Bug: zeigte auf nicht-existente Org `mana/`. Korrigiert auf den tatsächlichen GitHub-Pfad. Edit-Link auf docs-Seite + GitHub- Icon im Footer funktionieren jetzt.	2026-05-09 01:28:50 +02:00
Till JS	b1b9bbc269	chore: rename repo mana-monorepo → managarten ... Phase-3-Rename des ehemaligen Multi-App-Monorepos zum eigenständigen Produkt-Repo. Verein heißt mana e.V., Plattform-Domain bleibt mana.how, apps/mana/ bleibt unverändert — nur der Repo-Container kriegt den neuen Namen "managarten" (Garten der mana-Apps). Geändert: - package.json#name + #description - README.md (Titel + erster Absatz) - TROUBLESHOOTING.md - alle Mac-Mini-Skripte (Pfade ~/projects/mana-monorepo → ~/projects/managarten) - COMPOSE_PROJECT_NAME-default in scripts/mac-mini/status.sh - .github/workflows/cd-macmini.yml + mirror-to-forgejo.yml - apps/docs (astro.config.mjs + content) - .claude/settings.local.json (Bash-Permission-Pfade) - alle docs/*.md Pfad-Referenzen - launchd plists, .env.macmini.example, infrastructure/ Forgejo-Repo + GitHub-Repo bereits via API umbenannt. Lokales Verzeichnis-Rename + Mac-Mini-Cutover folgen separat.	2026-05-09 01:16:02 +02:00
Till JS	ac15de280b	chore(decommission): remove cards module from mana web app ... Cards-Modul war im unified mana-Frontend tief verzahnt. Cardecky ist seit 2026-05-08 standalone auf cardecky.mana.how — Dual-Stack ist nicht das Ziel. Entfernt: - apps/mana/apps/web/src/lib/modules/cards/ (UI + stores + queries + collections + module.config + tools + cloze + fsrs + render) - apps/mana/apps/web/src/routes/(app)/cards/ (alle Routes) - apps/mana/apps/web/src/lib/i18n/locales/cards/ (5 Locales) - apps/mana/apps/web/src/lib/search/providers/cards.ts - apps/mana/apps/web/src/lib/components/dashboard/widgets/ CardsProgressWidget.svelte + 'cards-progress' WidgetType-Eintrag Cross-Refs aufgeräumt: - app-registry/apps.ts: Cards-Icon-Import + registerApp-Block raus - shared-branding/mana-apps.ts: 'cards'-App-Eintrag raus - data/cross-app-queries.ts: useCardsProgress + Cards-Queries-Block raus (Konsument war nur das gelöschte Dashboard-Widget) - data/seed-registry.ts: CARDS_GUEST_SEED-Import + register-Aufruf - data/module-registry.ts: cardsModuleConfig-Import + Eintrag - data/privacy/exposed-records.ts: Cards-Block (cardDecks visibility) - data/tools/init.ts: cardsTools-Import + registerTools - modules/website/embeds.ts: 'cards.decks'-Source + resolveCardDecks - apps/mana/apps/web/package.json: @mana/cards-core dependency - pnpm-lock.yaml regeneriert - dashboard.test.ts: cards-progress-Assertion Dexie-Tabellen `cardDecks`/`cardReviews`/`cards` (lokal pro User-IndexedDB) und ggf. mana_platform.cards.* in der prod-DB werden NICHT in diesem Commit gedroppt — bleibt offen als separater Migrations-Schritt, sobald sicher ist dass kein anderer Pfad mehr darauf zugreift. Type-check (svelte-check) 7669 files 0 errors. Rollback: git checkout cards-decommission-base -- apps/mana/apps/web Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-08 20:36:33 +02:00
Till JS	9cd8717494	chore(decommission): remove apps/cards/ ... Cards-App ist seit 2026-05-08 ein eigenständiges Repo git.mana.how/till/cards (Strategie-B-Greenfield, beschlossen 2026-05-08), live auf cardecky.mana.how + cardecky-api.mana.how. Alte cards-web-Container wurden gestoppt + entfernt. Rollback: git checkout cards-decommission-base -- apps/cards/ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-08 20:27:24 +02:00
Till JS	467d8339cc	fix(apps/api): COPY packages/eslint-config in Dockerfile ... Root package.json devDeps reference @mana/eslint-config (workspace:*). Even with `--filter @mana/api...`, pnpm resolves the root workspace manifest and chokes on the missing package. Copy eslint-config into the builder stage so the root resolves cleanly. Same pattern as the platform mana-auth Dockerfile already uses. Discovered while running the 8-Doppel-Cutover smoke test on Mac Mini: mana-api build failed with ERR_PNPM_WORKSPACE_PKG_NOT_FOUND. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-08 18:44:57 +02:00
Till JS	774852ba2d	feat(cutover): platform services build from ../mana, not from this repo ... Part of the 8-Doppel-Cutover (2026-05-08, plan ~/.claude/plans/floating-swinging-flurry.md): - docker-compose.{macmini,dev,test}.yml: build context for mana-{auth,credits,media,llm,notify} switched to ../mana/services/... so the Mac Mini stack pulls platform services from the platform repo (sibling clone), not from services/ in this monorepo. - .npmrc + apps/api/{Dockerfile,package.json}: @mana/media-client now resolved from Verdaccio (npm.mana.how, ^0.1.0) instead of as a workspace COPY from services/mana-media/packages/client. Build-arg NPM_TOKEN flows through .npmrc for pnpm install auth. Required before services/mana-media/ can be deleted. - .github/workflows/{ci,cd-macmini,daily-tests}.yml: removed the detect-/build-/test-jobs that targeted services/mana-{auth,credits, notify,media}/. Those services build out of the platform repo now — CI for them belongs in mana/-repo (open). cd-macmini's workflow_dispatch can still rebuild any of them on demand; auto-detect on path-change is gone for these five. - scripts/{mac-mini/push-schemas.sh,run-integration-tests.sh}: rewritten to look in ../mana/ for the platform services. - package.json dev:{auth,credits,notify,media}: paths point at ../mana/services/... so local dev still works post-cutover. What this commit does NOT do: delete services/mana-{auth,credits,...} from this repo. That waits for Phase 7 once the Mac Mini stack has booted cleanly from the new build paths. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-08 18:40:08 +02:00
Till JS	8acf35eecf	chore(dev): finish --watch → --hot sweep across remaining Bun services ... Catches the service-level package.json files that the previous sweep (4cca25ed0) missed — they don't appear in any dev:*:full orchestrator but get invoked when someone runs `pnpm --filter @mana/<service> dev` directly. Touched: mana-geocoding, mana-mail, mana-subscriptions, mana-mcp, news-ingester, mana-persona-runner, mana-research, mana-user, plus apps/memoro (server + audio-server). mana-ai stays on --watch on purpose: its entry uses an explicit `Bun.serve({...})` call instead of `export default { port, fetch }`, plus a SIGTERM/SIGINT handler that calls `server.stop()`. --hot would replace the module without releasing the old server reference and produce exactly the EADDRINUSE we're trying to avoid. If mana-ai gets refactored to the standard default-export shape, flip its dev script too.	2026-05-08 14:33:27 +02:00
Till JS	4cca25ed03	chore(dev): switch all Bun services from --watch to --hot ... Fans out the cards-server fix from 08f422340 to every other Bun service in the monorepo. --hot keeps the port bound across HMR reloads via globalThis[hmrSymbol]; --watch restarts the process and races old/new Bun.serve for the port. Touched: dev:auth, dev:credits, dev:events, dev:analytics, dev:memoro:server, dev:memoro:audio-server, dev:uload:server in the root package.json plus the matching `dev` script in each service's own package.json. All six services already export the `{ port, fetch }` default that Bun's --hot expects. Smoke-tested: pnpm dev:cardecky:full boots clean, then touching auth/credits/cards-server entry files all hot-reload without dropping their port. (memoro/apps/audio-server doesn't have a `dev: bun --watch ...` script in its own package.json, so only the root entry got the swap there.)	2026-05-08 14:24:24 +02:00
Till JS	61f2772789	chore(brand): rename Cards → Cardecky (display, infra, license-IDs) ... - App display name → Cardecky in mana-apps.ts, MODULE_REGISTRY, alle Docs - Domains: cardecky.mana.how (App), cardecky-api.mana.how (Marketplace API), cardecky.com (Marketing-Landing — cloudflared-route + nginx-Block vorbereitet, DNS muss noch gesetzt werden) - 301-Redirect cards.mana.how → cardecky.mana.how (nginx + cloudflared) für alte Bookmarks; kann nach 6–12 Monaten wieder raus - SPDX license IDs Cards-Personal-Use/Pro-Only-1.0 → Cardecky-* via Drizzle 0001-Migration (DROP CHECK → UPDATE rows → SET DEFAULT → ADD CHECK), inkl. _journal- und 0001_snapshot-Update - In-mana cards-Modul: dezenter Banner zur Standalone-App (GUIDELINES §12), einmal schließbar via localStorage - Docker-CORS-Listen, sso-origins.ts, Prometheus-Target aktualisiert Technische IDs bleiben bewusst: appId 'cards', schema mana_platform.cards.*, Verzeichnis apps/cards/, Package @cards/web, services/cards-server, Env-Vars CARDS_*, UMAMI_WEBSITE_ID_CARDS*, Class CardsEvents — Mana-Konvention (Brand ≠ technischer Identifier). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-08 13:49:47 +02:00
Till JS	39e508075a	feat(cards): CardFace v2 — 3D-Flip + tap-anywhere reveal ... - CardFace now renders one card surface that flips on Y-axis when the user taps it. Both faces share a CSS-grid cell so the parent height is the max of front/back, no jumpy reflow on flip. - Tap-anywhere on the surface reveals (only while showBack is false). The /learn page keeps the keyboard space/enter shortcut via the existing handler; the standalone "Aufdecken" button is now type-in-only (where the input field on the front breaks the flip-mental-model). - prefers-reduced-motion: reduce collapses the rotateY into an instant cross-fade — same affordance, no vestibular trigger. - Added a subtle "Tippe auf die Karte oder drücke Leertaste" hint on the front face so the new affordance is discoverable. - Fixed the last Phase-A leftover: focus:border-indigo-400 in the type-in input → focus:border-app-accent.	2026-05-08 02:48:40 +02:00
Till JS	ad3b99fe6d	refactor(cards): Phase A + C — adopt @mana/shared-theme + per-app accent ... Phase A — Cards joins the unified theme system: - Drop placeholder --color-cards-* palette; app.css imports @mana/shared-tailwind/themes.css + sources.css. - Remove hardcoded class="dark" from app.html; body uses bg-background text-foreground. - New $lib/stores/theme.ts: createThemeStore({ appId: 'cards' }). ThemeToggle from @mana/shared-theme-ui in the header next to the streak chip. - Sweep all neutral / red / emerald / amber / indigo utilities in apps/cards/apps/web/src to semantic tokens (560 substitutions across 19 files): bg-neutral-900 → bg-card, text-neutral-400 → text-muted-foreground, bg-red-500 → bg-error, etc. Domain literals kept (FSRS grade colors red/orange/green/blue, GitHub- violet PR-merged badge, marketplace-amber Buy button, admin- inbox category palette). - Cards added to validate-theme-utilities scope so future drift fails CI. Phase C — per-app accent token: - New --color-app-accent in shared-tailwind/themes.css. Theme- agnostic (registered in validate-theme-parity's THEME_AGNOSTIC regex), so it stays the same across light/dark/lume/etc. Defaults to Mana indigo at :root. - Cards layout writes 258 90% 66% (= #8b5cf6 violet, from MANA_APPS.cards.color) onto documentElement at boot via applyCardsAccent(). All Cards CTAs (Lernen, Abonnieren, Senden, links inside cloze cards) flow through bg-app-accent / text-app-accent now. Net effect: Cards gets light/dark + 4 palette variants + a11y toggles for free, and any future app can drop in by setting its own --color-app-accent without touching shared-tailwind.	2026-05-08 01:54:16 +02:00
Till JS	863311eefa	docs(cards): Phasen-Statusupdate nach η.1 — Stand 2026-05-07 ... Marketplace-Plan auf den realen Code-Stand gebracht: - §11 Phasen-Liste: pro Phase ✅ shipped / 🟡 partial / ⏳ pending Marker mit Kurzbegründung. β/γ/δ/ε sind ✅, ζ und η sind 🟡 mit ζ.2 / η.2 als nächste Sub-Phasen. - §13a „Bekannte Limitierungen": neue Einträge für ζ (Refunds, Reconciler, CSV) und η (Community-Verify-Cron, Mod-Permissions, Public-Changelog, Rate-Limit). PR-Merge-Stale-Blindness und Card-Preview-Heuristik bleiben dokumentiert. - §15 ersetzt: Status-Tabelle pro Phase + Empfehlung für die nächsten 4 Schritte (ζ.2 Reconciler → η.2 Verify-Cron → Update-Mail δ.4 → Phase θ Auto-Tags/Summary).	2026-05-07 23:38:42 +02:00
Till JS	c05022611e	feat(cards): Phase η.1 — Reports + admin moderation actions ... Server (cards-server): - ModerationService: createReport, listOpen, resolveReport, takedownDeck, banAuthor, setVerifiedMana, restoreDeck. Takedown also auto-closes any sibling open reports against the deck and closes any open PRs (so contributors see clean state). Ban cascades to all of the author's decks. - routes/moderation.ts: POST /v1/reports (any authed user), GET /v1/admin/reports (admin only), POST /v1/admin/reports/:id/ resolve, POST /v1/admin/decks/:slug/{takedown,restore}, POST /v1/admin/authors/:slug/verify. Admin gate is `role === 'admin'` for now — verified-mana-only mods land later. - Notify hooks: takedown emails the deck owner, mana-verify status change emails the author. Frontend (cards-web): - <ReportButton> (icon or inline variant) with category picker + optional explanation. On /d/<slug> as a discreet 🚩 next to the published-date stamp; in <CardDiscussions> per non-own comment. - /d/<slug> shows a red "wurde von der Moderation entfernt" banner when isTakedown is true. - /admin/reports inbox: lists open reports with category badges, Abweisen / Deck entfernen / Author bannen actions. Renders a forbidden state if the current user isn't admin.	2026-05-07 23:24:23 +02:00
Till JS	5dbc9ace2d	feat(cards): Phase ζ.1 — Paid decks via mana-credits ... Server (cards-server): - lib/credits.ts: thin internal-API client for mana-credits (reserve / commit / refund-reservation / grant). Service-to- service via X-Service-Key. Throws InsufficientCreditsError separately so the buy flow can branch on UX. - services/purchases.ts: 4-step purchase pipeline: reserve → insert deck_purchases row → commit reservation → grant author share + insert author_payouts. Idempotent on (buyer, deck) so a refresh-spam-click can't double-charge. Verified-mana authors get the 90/10 split, others 80/20 (already in config). Refunds intentionally out of scope — see MARKETPLACE_PLAN §13a. - routes/purchases.ts: POST /v1/decks/:slug/purchase, GET /v1/me/purchases, GET /v1/authors/me/payouts. - decks.bySlug now returns hasPurchased (null when anonymous, bool when authed) so the deck-detail page can pick the right CTA. - subscriptions.subscribe now blocks paid decks unless the caller has a non-refunded purchase row (owner exempt for testing). - Notify: author gets a "Verkauf"-Email at grant time, with a deterministic externalId for dedup. Frontend (cards-web): - /d/<slug> shows "Kaufen für N 💎" instead of "Abonnieren" when paid + not yet bought; flips to subscribe path once purchased. - /me/purchases page listing buyer history + (when present) author-payout history. Linked from the top nav.	2026-05-07 23:10:18 +02:00
Till JS	46fefd5cc4	feat(cards): Phase ε.4 — Card list + discussions on /d/<slug> ... - DiscussionService.countsForDeck: bulk count (visible) comments per card-content-hash for one deck. Mounted at GET /v1/decks/:slug/discussion-counts so the public deck page can render comment badges without N+1 fetches. - <DeckCardList> on /d/<slug>: lists the latest version's cards, renders a one-line preview + "💬 N" badge, and expands the inline <CardDiscussions> on click. Anonymous visitors see counts; posting requires auth (CardDiscussions already gates that).	2026-05-07 22:46:47 +02:00
Till JS	a8ddb6dea4	feat(cards): Phase ε.3 — PR notifications + Card-Discussions UI ... - mana-notify integration in cards-server: PR-create notifies the deck owner, merge/reject notifies the PR author. Fire-and-forget via lib/notify.ts so a notify-service outage never rolls back a domain action. ExternalIDs are deterministic (cards.pr.{event}.{id}) so retries dedupe. - <CardDiscussions> on the learn page: collapsed by default, opens via "💬 Diskussion" alongside the "✏️ Verbessern" trigger. Resets whenever the current card changes so the panel doesn't bleed between flashcards. - MARKETPLACE_PLAN.md §13a — known limitations: PR-merge is stale-blind (no rebase yet), diff-preview flat, threading 1-level.	2026-05-07 22:24:45 +02:00
Till JS	61fc16e8e9	feat(cards): Phase ε — Pull-Requests + Card-Discussions ... Server (cards-server): - PullRequestService: create / list / get / merge / close / reject. Merge applies the PR's {add, modify, remove} diff to the latest version's cards in a single transaction, writes a new deck_version + deck_cards, bumps latest_version_id, and stamps the PR with mergedIntoVersionId. - DiscussionService: post / listForCard / hide. Threads are keyed by card_content_hash so they survive version bumps. - Routes mounted under /v1: POST/GET /decks/:slug/pull-requests, GET /pull-requests/:id, POST /pull-requests/:id/{merge,close,reject}, GET/POST /cards/:contentHash/discussions, POST /discussions/:id/hide. Frontend (cards-web): - cardsApi.pullRequests + cardsApi.discussions client surface. - <PullRequestsSection> on /d/:slug — lists PRs with diff preview; owner sees Merge/Reject/Close buttons. - <SuggestEditModal> + "✏️ Verbessern" button on /learn/:deckId for cards from a subscribed deck — submits a one-card modify (or remove) PR using the card's serverContentHash as the previous hash. - Deck/Card DTOs gain subscribedFromSlug + serverContentHash so the learn page can decide whether to show the suggest-edit affordance.	2026-05-07 21:56:20 +02:00
Till JS	521ae52a62	feat(cards-web): Phase δ.3 — Smart-merge updates + read-only subscribed decks ... Closes the marketplace subscribe loop. When the author publishes a new version of a subscribed deck, the user sees a compact banner with a per-card breakdown and one-click "Update anwenden" — FSRS learning state survives across the merge. - lib/services/subscribe.ts: - previewUpdate(slug): server diff /v1/decks/:slug/diff?from=… with a small UpdatePreview shape ({added, changed, removed, unchanged} as counts). - applyUpdate(slug): - removed → soft-delete by [deckId+serverContentHash], cascade reviewStore.softDeleteForCard. - changed → update local card in place; ensureReviewsForCard re-runs to pick up cloze-cluster changes. FSRS reviews stay attached because the card-id never changes. - added → fresh local card + fresh FSRS reviews. - unchanged → only re-stamp ord if the diff moved it. Bumps subscribedAtVersion locally + re-stamps server-side. - lib/data/database.ts: Dexie v3 adds compound index [deckId+serverContentHash] for the smart-merge lookup. - routes/decks/[id]/+page.svelte: - subscribed decks get a green "📥 Abonniert"-banner with the version stamp + a deep-link to the public marketplace page. - if previewUpdate returns a non-null diff, the banner inlines the counts and an "Update anwenden" button. - "Veröffentlichen", "Neue Karte", "Aus Text generieren" and the per-card delete buttons are hidden when the deck is subscribed — read-only mirror of the author's content. Validated: svelte-check 0/0, vite build green. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 20:21:32 +02:00
Till JS	58c057f6c5	feat(cards-web): Phase δ.2 — Subscribe + initial pull ... End-to-end subscribe flow on cards.mana.how. From a public deck page the user can now pull the deck into their own Cards instance with one click; subscribed decks live alongside own decks but carry a `subscribedFromSlug` marker so the editor knows to hide mutate controls (UI gating in δ.3). - cards-core types: LocalDeck gains subscribedFromSlug + subscribedAtVersion. LocalCard gains serverContentHash. Both optional — own decks/cards are unaffected. - data/database.ts: Dexie v2 adds index on cardDecks.subscribedFromSlug so the lookup-by-slug path is O(1). - lib/api/cards-api.ts: subscriptions.{list,subscribe,unsubscribe, version,diff} + the SubscriptionInfo / ServerCard / DeckVersionPayload / DiffPayload types. - lib/services/subscribe.ts: subscribeAndPull() sequences server POST /subscribe → GET /decks/:slug → GET /versions/:semver → create LocalDeck + LocalCards + ensure FSRS reviews. Re-pull refreshes in place (Phase δ.3 will swap to real diff-apply that keeps FSRS state). unsubscribe() soft-deletes the local mirror. isSubscribedLocally() backs the deck-page state check. - routes/d/[slug]/+page.svelte: full subscribe UI — Abonnieren → Abonniert + Lernen-Button (deep-links into the existing learn session route). Validated: svelte-check 0/0, vite build green. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 19:56:48 +02:00
Till JS	86a01426e8	feat(cards-server): Phase δ.1 — subscriptions + version reads + smart-merge diff ... Server-side plumbing for Phase δ. Frontend hookup follows in δ.2. - services/subscriptions.ts: subscribe/unsubscribe (idempotent upsert on (user, deck), stamps the latest_version_id at subscribe-time so the client knows what it pulled). listForUser returns each sub with `updateAvailable: currentVersion !== latest` so the client can render an update indicator without a second round-trip. Refuses paid decks with 403 — that path comes back in Phase ζ once the credits Marketplace lands. - versionWithCards: deterministic ord-ordered card payload for a specific version. Read-public so anonymous browsers can preview a deck's content. - diffSince: smart-merge payload between any two versions. Splits the latest cards into added/changed/unchanged + lists removed by content_hash. The 'changed' bucket is heuristic (ord-position pair where one was removed and one was added) — solid enough until Phase ε's pull-request pipeline gives us real card lineage. - routes/subscriptions.ts mounts: GET /v1/me/subscriptions, POST/DELETE /v1/decks/:slug/subscribe (auth required), GET /v1/decks/:slug/versions/:semver (public), GET /v1/decks/:slug/diff?from=<semver> (public). cards-web layout fix: - Marketplace surface (/explore, /u/, /d/) was previously gated behind the AuthGate — anonymous browsers got pushed to /login via client-side navigate. PUBLIC_PATHS extended so those routes SSR + render unauthed. Validated: tsc clean on cards-server, svelte-check 0/0 on cards-web. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 19:33:58 +02:00
Till JS	e77134bd8b	docs(infra): Phase 2f added to PLAN_OPTION_C + hostname table updated to v28 ... - PLAN_OPTION_C.md: new row covers verdaccio + news-ingester + mana-ai with the cross-arch + workspace-deps gotchas - infrastructure/README.md: hostname table catches up to npm.mana.how (Phase 2f-1) and mana-ai.mana.how (Phase 2f-3); config v26 → v28 - infrastructure/.env.gpu-box.example: MANA_SERVICE_KEY + MANA_AI_PRIVATE_KEY_PEM block added with note that the values mirror Mini's .env.macmini (the latter's matching public-half stays on mana-auth, that's what makes Mission-Grant decryption work) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 17:09:28 +02:00
Till JS	ec8abfe6b8	feat(cards-web): Phase β.2 — author onboarding + publish flow ... End-to-end "publish my local deck to the marketplace" surface in the Cards standalone app. Hooks into cards-server (Phase β) so a user can take a deck they've been editing locally and put it under cards.mana.how/d/<slug> with one modal. Pipeline: • lib/api/cards-api.ts — typed fetch wrapper around the cards-server /v1 surface. Reads the JWT from authStore, never from storage directly. CardsApiError carries `{status, message, details}` so UI can branch on 401/409/etc. • lib/stores/author.svelte.ts — lazy-loaded author state. Caches `cardsApi.authors.me()` on first access; resets cleanly on logout. • lib/util/slug.ts — best-effort slugify mirror of the server-side validator (server still has final say). • lib/components/PublishDeckModal.svelte — three-stage flow: become-author (slug + displayName + pseudonym), deck-meta (title, description, language, license picker, semver, changelog), then publishing → done with moderation-flag surface if AI mod returned 'flag'. Keys off authorStore.isAuthor to skip stage 1 for returning authors. • routes/decks/[id]/+page.svelte gets a "🌍 Veröffentlichen" button next to "Lernen". Disabled until the deck has cards. Wiring: • hooks.server.ts injects __PUBLIC_CARDS_API_URL__ on every SSR'd page so the client knows where cards-server lives. • compose adds PUBLIC_CARDS_API_URL_CLIENT=https://cards-api.mana.how to the cards-web container. Validated: svelte-check 0/0, vite build green. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 16:53:17 +02:00
Till JS	0686300243	docs(cards): Marktplatz Plan — Vollvision mit mana-credits + dual verification ... Vollvision-Plan für den Cards-Decks-Marktplatz, basierend auf der Konkurrenz-Analyse vom selben Tag. Bewusst nicht MVP-getrieben — unbegrenzte Ressourcen-Annahme, optimale Lösung als Ziel. Kern-Entscheidungen aus dem User-Briefing: - Versionierte Decks + Live-Updates + Pull-Requests = volle Vision - mana-credits zentral: User kaufen, Authoren verdienen (80/20 Cut, 90/10 für verified-mana) - Verifizierung zweigleisig: Mana-Verein-Kuration UND Community- Schwelle, mit unterschiedlichen Badges (🛡️ und ⭐) - Co-Learn-Sessions explizit auf Phase λ verschoben - Mobile-Apps explizit auf Phase μ verschoben Inhalt: - 17 Tabellen-Schema (Authoren, Decks, Versionen, Karten, Subscriptions, Forks, Stars, PRs, Discussions, Reports, Tags, Käufe, Auszahlungen, AI-Mod-Log) - mana-credits Integration end-to-end (2-phase Reservation, Author-Payout, Refund-Workflow, Buyer-Protection) - Service-Architektur: cards-server (neu), cards-search (neu, später), Erweiterungen an mana-llm/mana-credits/mana-notify/ mana-media - 7 API-Endpoint-Bereiche mit konkreten Routes - 9 Phasen (α–ι) plus 4 explizit-später-Phasen - Cold-Start: Verein-Seed + Anki-Top-100 + Influencer-Outreach - Risiko-Matrix mit Mitigationen - "Was wir NICHT tun"-Sektion (Sterne-Bewertung, Reddit-Voting, Anki-Bashing, Klarname-Pflicht, > 30% Cut) - 7 konkrete Differenzierungs-Hebel gegen die 17 Konkurrenten Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 15:48:45 +02:00
Till JS	8a90cd296c	docs(cards): competitor analysis Mai 2026 ... Recherche zu 17 Spaced-Repetition-Konkurrenten (Anki, Quizlet, RemNote, Mochi, Brainscape, Memrise, SuperMemo, AnkiPro/Noji, AnkiApp/AlgoApp, Quizgecko, Knowt, Wisdolia, Mnemosyne, Traverse, Cerego, NeuraCache, AnkiHub) inkl. USP, Lizenz, Kosten, User- Stimmen, Firma + Bedrohungs-Ranking. Wichtigste Erkenntnisse für die Cards-Strategie: - Free Markdown+FSRS+Cloud-Sync ist eine objektive Marktlücke (Mochi: $5/mo Sync, RemNote: $8/mo, Brainscape: ~$20/mo). - AI-Karten-Generierung ist Tischeinsatz, kein USP mehr — Quizlet, Quizgecko, Knowt, RemNote, Wisdolia haben es alle. - Quizlet ist mit Trustpilot 1.4/5 verwundbar (Paywall-Walls); Quizlet-Refugee-Markt ist offen. - AnkiPro (Noji) und AnkiApp (AlgoApp) haben mit "Anki"-Brand- Sniping ihre Reputation verbrannt — Lehre für unsere Brand- Hygiene. Empfohlene Hebel: (1) Free Sync explizit ausspielen, (2) Anki- Migration als First-Class-Feature (eigene from-anki-Landing), (3) Local-First PWA als Tech-Identität. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 15:28:02 +02:00
Till JS	c1423d2f72	fix(cards-web): missing static assets — sql-wasm-browser.wasm + PWA icons ... Two 404s reported from prod: 1) sql.js's production-bundled loader requested /sql-wasm-browser.wasm but only sql-wasm.wasm was in static/. The browser bundle is its own file; copy both so the loader hits whichever variant the runtime picks. Without this the .apkg import dies before reading SQLite. 2) shared-pwa's manifest references pwa-192x192.png, pwa-512x512.png and apple-touch-icon.png. None existed → Chrome's manifest-icon validator failed and there was no usable icon for A2HS. Generated minimal indigo-stacked-cards PNGs at the three required sizes. Note: the sync 402 reports in the same console output are a separate, intentional behaviour — mana-sync's billing middleware blocks pull/ push when the user has no active sync subscription. No code change needed; handled at the mana-credits layer. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 14:42:47 +02:00
Till JS	82db4eb794	feat(cards-web): Anki import carries images + audio along ... Closes the gap from the first Anki-import pass: media files are now uploaded alongside the cards instead of stripped. Pipeline: • parse.ts: read the .apkg's `media` JSON manifest, build a filename → ZIP-entry map (Anki names files numerically; the manifest is the original-name lookup table). Returned alongside decks/cards as parsed.mediaByFilename. • import.ts: collectMediaRefs() walks every card field, gathers distinct <img src=…> and [sound:…] references — orphan media bundled in the .apkg are ignored. Referenced files upload to mana-media in 4 parallel workers, returning a filename → URL map. • parse.sanitizeAnkiHtml() now takes that map: <img src="X"> → <img src="<url>" alt="" />, [sound:Y] → <audio controls preload="metadata" src="<url>"/>. The remaining-tag stripper has a negative lookahead for img/audio/video/source so the new tags survive. • CardFace already renders <img>/<audio> via @mana/cards-core's DOMPurify config (the image/audio attachments commit added the allowlist), so the freshly-imported cards just work in the learn session. UI: • AnkiImport gains an "uploading-media" stage with X / N progress bar between preview and card creation. • Preview now shows the media count, copy promise updated from "Bilder/Audio bleiben raus" to "Bilder + Audio werden mit übernommen". • Result block reports `N Medien übernommen · M fehlgeschlagen`. Phase-2 ideas: per-user media scoping in mana-media; verify-then- upload via /media/hash/:sha256 to skip duplicates from re-imports. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 14:25:43 +02:00
Till JS	daa1ef0513	feat(cards): image / audio attachments on cards via mana-media ... Cards can now carry image, audio, and video attachments uploaded to mana-media (the existing CAS service that already powers picture, photos, wardrobe, etc.). Pipeline: • lib/media/upload.ts wraps POST /api/v1/media/upload (multipart, app=cards). Returns { id, url, kind } with the right variant URL per kind (medium for images, full file for audio/video). 25 MB cap matches the website-upload pattern. • mediaToFieldSnippet(): drops Markdown ![]() for images; raw <audio>/<video controls> for the others — the user can later tweak attributes by hand. • Deck-detail card editor gains a "📎 Anhang" button next to every text field (front/back/cloze). Pick → upload → snippet appended to the field's content. Loading + error states surfaced inline. Render: • @mana/cards-core/render.ts whitelists `audio`, `source`, `video` plus the `controls`/`preload`/`src`/`type` attrs in DOMPurify so inline media survives sanitization. Markdown's <img> already passed through the default policy. Wiring: • hooks.server.ts injects __PUBLIC_MANA_MEDIA_URL__. • compose adds PUBLIC_MANA_MEDIA_URL_CLIENT=https://media.mana.how to cards-web. Phase 2 ideas: drag-drop directly into the textarea, paste-from- clipboard for screenshots, mana-media auth scoping per user, Anki import bringing media files along. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 13:52:53 +02:00
Till JS	1f2206f10b	feat(cards-web): PDF input for AI generator + study activity heatmap ... PDF input: • lib/ai/pdf.ts wraps pdfjs-dist (Apache-2.0). Worker is bound via Vite's `?worker` suffix so the heavy parsing runs off-main-thread. • AiCardGen gains a "📄 PDF laden" button that pipes extracted text into the same textarea — the user can review/trim before generation. Reading state shows file name + page count + chars. Heatmap: • queries.useStudyHeatmap(weeks=12) fills gaps with count=0 so the grid renders without holes. • StudyHeatmap.svelte: 7 rows × N columns (Monday-anchored), 5 intensity buckets (neutral → emerald-300), tooltip per cell with date + count, legend strip. • Mounted on the dashboard between the deck list and the Anki import so the user lands on a quick visual progress receipt every visit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 13:37:01 +02:00
Till JS	e3cca9e271	feat(cards-web): PWA installability + AI card generation from text ... PWA: • SvelteKitPWA in vite.config via @mana/shared-pwa preset (name + theme color). Layout injects pwaInfo.webManifest.linkTag so Chrome's manifest pickup works → install icon + A2HS. • Service worker registers automatically (workbox auto-update); the cards-already-cached path now keeps working offline as long as the user has visited a deck once. AI generation: • lib/ai/generate.ts — direct fetch to mana-llm /v1/chat/completions (OpenAI-compatible, mirrors playground module). System prompt constrains the model to a JSON array of {front, back}. Code-fence stripping handles models that wrap JSON in ```json blocks despite the prompt. • AiCardGen.svelte — text in, list of generated cards out, per-card checkbox preview, "X übernehmen" creates them via cardStore. Phase-1 lands them as basic cards. • Mounted on the deck-detail page next to "Neue Karte". Wiring: • hooks.server.ts injects __PUBLIC_MANA_LLM_URL__. • compose adds PUBLIC_MANA_LLM_URL_CLIENT=https://llm.mana.how to the cards-web service. • app.d.ts gets vite-plugin-pwa virtual-module references so svelte-check can resolve `virtual:pwa-info`. Phase 2: PDF/image input, mana-credits gating, model selector, streaming preview as cards arrive. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 13:24:42 +02:00