784 commits

Author	SHA1	Message	Date
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	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	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	dd1bab09d5	chore(decommission): remove packages/cards-core/ ... @mana/cards-core wurde nur von apps/cards + services/cards-server + apps/mana/.../modules/cards genutzt — die ersten zwei sind weg, das mana-Modul kommt im nächsten Commit. Rollback: git checkout cards-decommission-base -- packages/cards-core/ Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-08 20:27:33 +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	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	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	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	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	f422fd6779	fix(shared-error-tracking): point main at src/, strip dashes from Glitchtip DSN ... Two real-world fixes from wiring mana-auth to Glitchtip: 1. The compiled dist/ folder was excluded from Docker builds via .dockerignore's '**/dist' rule, so any container that pnpm-installed the package found node_modules/@mana/shared-error-tracking but no loadable entry point ('Cannot find module' at startup). Match the pattern shared-hono uses — point main + types + exports straight at src/*.ts. Bun runs TS natively and the type-only consumers don't care. 2. Glitchtip projects expose UUID-format public keys (`556fbd2e-a720-…`) in their generated DSNs. @sentry/node v9 tightened its DSN regex to alphanumeric-only, so it silently rejects the DSN with "Invalid Sentry Dsn" and never sends events. Strip the dashes from the user/key portion before handing it to Sentry — the Glitchtip ingest endpoint accepts both forms over the wire, so no server change. Plus the missing Dockerfile COPY lines for shared-error-tracking and eslint-config (root package.json devDeps reference the latter, which breaks pnpm-filter installs that don't include it in the build context). Verified end-to-end: 4 issues now in Glitchtip from mana-auth (2 manual probes + 1 captureException + 1 401 from a real /api/v1/me/data request without auth). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 02:34:54 +02:00
Till JS	f94c047daa	chore: silence pre-existing svelte-check a11y warnings ... Pre-push hook runs svelte-check with --fail-on-warnings; nine long-standing warnings in unrelated files (forms / website-blocks) were blocking otherwise-clean pushes. Each <label> here is a visual label whose control follows on the next line — accessible to a screen reader through proximity but not through a `for=`/`id` association. The state_referenced_locally cases capture a prop on first render by design (re-running the hook on prop change would be a different feature). The <nav role=tablist> is the existing tab-strip semantic. All seven sites get scoped svelte-ignore comments rather than functional rewrites — the goal is to unblock CI, not redesign these components. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 01:34:36 +02:00
Till JS	0a544ac410	feat(cards): Phase-1 Spinoff — standalone cards.mana.how + cards-core extraction ... Builds out the Cards spinoff end-to-end so the standalone app at cards.mana.how shares its data layer with the in-mana cards module through a single pure-utility package. Why a spinoff and not just a deeper module: per the GUIDELINES, Cards gets its own brand + URL while reusing mana-auth, mana-sync, and the mana-credits/billing stack. The in-mana module under mana.how/cards stays untouched as the integrated experience. Phase 0 — mana-modul foundation • New tables cardReviews + cardStudyBlocks (Dexie v61) + plaintext classification in the crypto registry. • LocalCard learns a {type, fields} shape; legacy front/back columns kept as a back-compat mirror so older builds keep rendering. • FSRS v6 scheduler + Cloze parser + Markdown render pipeline. • UI in apps/mana/.../routes/(app)/cards/ gets a learn session (learn/[deckId]), 4-type card editor, due-counter, markdown lists. Phase 1 — standalone (apps/cards/apps/web) • SvelteKit 2 + Svelte 5 + Tailwind 4, port 5180. • Own Dexie 'cards' DB with a slim 5-table schema. • Own sync engine: pending-changes hooks, 1 s push / 5 s pull against POST /sync/cards, server-apply with suppression to avoid ping-pong. • Auth-Gate via @mana/shared-auth-ui (LoginPage / RegisterPage). • Encryption hooks at every write/read/apply path, currently no-op stubs — flipping to real vault-backed AES-GCM is a single-file change in src/lib/data/crypto.ts. Shared package — @mana/cards-core • Pulls types, cloze, card-reviews, FSRS wrapper, and Markdown renderer out of the mana module so both frontends import from one source. mana-modul keeps thin re-export shims so consumers don't need to change imports. • 19 vitest tests carried over from the mana module. Server-side wiring • cards.mana.how added to mana-auth PRODUCTION_TRUSTED_ORIGINS and its CORS_ORIGINS env (sso-config.spec.ts stays green). • New cards-web container in docker-compose.macmini.yml (mirrors manavoxel-web pattern, 128m, depends on mana-auth healthy). • cloudflared-config.yml repoints cards.mana.how from :5000 (the unified mana-web container) to :5180. mana.how/cards is unchanged. Cleanup • Removed an unrelated 2026-03/04 NestJS+Supabase+Expo experiment that was lingering under apps/cards/ (apps/landing, supabase/, .github/workflows, MANA_CORE_*.md, etc.). It predated this plan and would have confused future readers. Validation • svelte-check on mana-web: 0 errors over 7697 files • svelte-check on cards-web: 0 errors over 3481 files • vitest on cards-core: 19/19 pass • pnpm check:crypto: 214 tables classified • bun test sso-config.spec.ts: 8/8 pass • vite build on cards-web: green Not done in this commit (deliberate) • Real encryption (vault roundtrip) — Phase 2. • WebSocket-driven pull (5 s polling for now). • Mobile/landing standalone surfaces — Phase 2/3. • The actual production cutover on the Mac mini (build, deploy, cloudflared sync) — config is staged, deploy is a user action. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-07 01:20:43 +02:00
Till JS	795b39e065	feat(forms): M10d headless wave-cron — server-worker + private internal_meta ... Echter Server-Cron für recurring forms — wave-send läuft jetzt unabhängig von Owner-Tab-State. Bisheriger M10c webapp-side scheduler bleibt als Belt-and-suspenders aktiv (idempotent). Architektur: 1. **Owner-private internal_meta auf unlisted snapshots** - Drizzle: neue jsonb-column `internal_meta` (Drizzle migration 0001_internal_meta.sql). - public-routes.ts strippt sie strukturell — die explicit select()- projection enthält sie nicht (recipients + sender würden sonst via share-link leaken). - publish-route akzeptiert sie im Body, persistiert auf insert + update. - ALLOWED_COLLECTIONS um 'lasts' und 'forms' erweitert (war ein latenter Bug — formsStore.setVisibility('unlisted') hätte ohne diese Ergänzung 400 zurückbekommen; M4b lief vermutlich nie end-to-end durch). 2. **shared-privacy publishUnlistedSnapshot** - PublishUnlistedOptions erweitert um optionales `internalMeta`. Forwarded an /api/v1/unlisted/:collection/:recordId body. 3. **Webapp formsStore** - lib/wave-mail.ts: buildFormInternalMeta(form, broadcastSettings) baut den Owner-Private-Blob: { kind, recurrence: {frequency, recipientEmails, lastSentAt}, sender: {fromEmail, fromName, replyTo, legalAddress}, formMeta: {title, description} }. Returns null wenn Voraussetzungen fehlen (kein recurrence, keine recipients, fehlende broadcast-settings). - stores/forms.svelte.ts: setVisibility / regenerateUnlistedToken / setUnlistedExpiry laden broadcastSettings via Dexie + decrypt, bauen internalMeta, übergeben an publishUnlistedSnapshot. Form wird vor dem buildFormInternalMeta-Call dekrypted. 4. **mana-mail internal bulk-send route** - createInternalRoutes(accountService, broadcastOrchestrator, maxRecipients) — Signature erweitert. - Neue POST /api/v1/internal/mail/bulk-send: gleicher Payload-shape wie user-facing /v1/mail/bulk-send aber userId aus Body statt JWT. X-Service-Key-gate sitzt bei /api/v1/internal/* prefix. Audit-trail trägt principalId aus Body. Cap = 5000 (gleicher Wert wie user-facing). 5. **apps/api forms wave-worker** - 5-min setInterval, advisory-lock-gated (key 0x464f5257 'FORW'). - Tick: select snapshots WHERE collection='forms' AND internal_meta IS NOT NULL AND revoked_at IS NULL. Filter auf kind='forms-recurrence' + isWaveDue (lastSentAt + period <= now, never-sent fires sofort). Pro fälligem snapshot: build HTML/text mailbody (mirror webapp wave-mail-render), POST an mana-mail internal-bulk-send mit X-Service-Key + userId, dann jsonb_set auf internal_meta.recurrence.lastSentAt. Per-snapshot errors werden als console.warn geloggt, Tick läuft weiter. - Disable via FORMS_WAVE_WORKER_DISABLED=true (tests / multi- replica deployments). - Wired in apps/api/src/index.ts neben startArticleImportWorker(). Trade-offs: - internal_meta wird beim setVisibility/regenerate/setExpiry frisch aus broadcast-settings gebaut — wenn der User später broadcast- settings ändert (zB neuer fromEmail) muss er das Form re-publishen damit die snapshot-internal_meta aktualisiert wird. Doc-it: zukünftiger Patch könnte ein "settings drift"-Warning ins UI surfacen. - Worker-Update von lastSentAt geht NICHT zurück in den webapp-form (settings.recurrence.lastSentAt ist verschlüsselt, server kann nicht schreiben). Owner-UI zeigt ältere lastSentAt von manuellen Sends; auto-cron-sends sind in den Server-Logs sichtbar. Future patch: GET /api/v1/forms/:id/recurrence-status (auth) gibt das snapshot.internal_meta zurück, UI rendert Auto-Cron-State. - Webapp-side wave-scheduler (M10c) läuft parallel weiter — wenn Owner-Tab offen ist, kann beides feuern. Idempotent durch lastSentAt-check (weekly/monthly buckets), aber theoretisch könnte double-fire passieren wenn die Calls innerhalb 1ms versetzt sind. Real-world ignorierbar; future patch: scheduler liest jetzt internal_meta.lastSentAt vom server-side state. apps/api buildet (1776 modules). mana-mail buildet (523 modules). svelte-check 0 errors in forms/. Forms-Tests 70/70 unverändert. DB-Migration 0001_internal_meta.sql muss manuell appliziert werden (siehe feedback memory: hand-authored SQL migrations sind nicht in pnpm setup:db). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-06 17:18:05 +02:00
Till JS	ace1b706e6	feat(forms): M8 website-block — formEmbed bindet Mana-Formulare ein ... Neuer Block-Type `formEmbed` im Website-Builder (docs/plans/forms-module.md M8): - @mana/website-blocks/src/formEmbed/: - schema.ts: FormEmbedSchema mit token (32-char base64url) + titleOverride + optional resolved-Block (formTitle, fields, branching, settings.{submitButtonLabel, successMessage}). FormFieldEmbedSchema duplicated leichtgewichtig statt cross- package import — website-blocks bleibt self-contained. - FormEmbed.svelte: edit/preview rendert Placeholder-Card mit Token-Snippet und resolved-Status; public rendert die kompletten 11 Field-Types inkl. Live-Branching-aware-Render. Submitter- Block (Name+Email optional). Submit POSTet an /api/v1/forms/public/:token/submit. Lazy-Fallback fetcht /api/v1/unlisted/public/:token wenn die publish-resolver-blob fehlt. Bot-Honeypot bleibt M8-Polish. - FormEmbedInspector.svelte: Token-Input mit base64url-Validierung bei blur, optional titleOverride, resolved-Card mit Field-Count + Logik-Regel-Count. - BLOCK_SPECS + BLOCK_SCHEMAS + BLOCK_DEFAULTS um formEmbed erweitert. schemas.test.ts erwartet jetzt 12 Block-Types. - apps/mana/apps/web/src/lib/modules/website/forms-embeds.ts: resolveFormEmbed scant formTable nach unlistedToken (linear scan ist günstig bei <100 forms pro user, kein Index nötig), dekrypted, validiert published-status, gibt resolved-Block zurück. - publish.ts.resolveEmbedsInTree erweitert um formEmbed-Branch — ruft resolveFormEmbed parallel zu resolveEmbed (moduleEmbed) im selben Walk. Trade-offs: - Token statt formId: bei Token-Rotation (M4b) muss der User den Block neu konfigurieren. Der formEmbed-Block-Resolver erkennt das + setzt resolved.error; public-Renderer fällt auf lazy-fetch zurück. - Plaintext stored: das resolved-Blob landet als plaintext im public-snapshot, gleiches Trust-Modell wie moduleEmbed (öffentliche Website per Definition). Tests: website-blocks 50/50 grün (12 schema-block-types + per-type defaults validation). svelte-check 0 errors. forms 26/26 unverändert. Use-Case: Vereins-Sommerfest. User legt /forms/anmeldung an, publisht, setzt unlisted, kopiert Token. Im Website-Builder fügt er einen formEmbed-Block auf der Event-Seite ein, paste Token → bei Publish wird der Form-Schema inlined → Besucher submitten direkt auf der Vereins-Website. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-29 02:38:28 +02:00
Till JS	59373c0d57	chore(articles): hygiene pass — shared-ai actor + lib/sync-db + metrics (#5,#7,#11) ... #5 — SYSTEM_ARTICLES_IMPORT_WORKER hoisted into @mana/shared-ai The worker built its actor inline, bypassing the SystemSource union that's the blessed list for system-write principals. Now uses makeSystemActor(SYSTEM_ARTICLES_IMPORT_WORKER) like every other server-side system writer (mission-runner, projection, …). #7 — sync-db helper hoisted out of mcp/ into lib/ Implementation moved to apps/api/src/lib/sync-db.ts; mcp/sync-db.ts is a re-export shim so existing MCP imports keep working. Articles bulk-import + future modules import from lib/ directly — no more "articles depending on mcp" layering smell. #11 — Prometheus metrics for the worker New counters + histogram in lib/metrics.ts under mana_api_articles_import_*: - ticks_total{result=processed|skipped|error} - items_total{result=extracted|error|consent_wall|cancelled} - extract_duration_seconds (histogram, 0.25–30s buckets) - jobs_completed_total{result=done} - pickup_gc_rows_total Worker tick + extractor instrumented at the right transition points. Steady-state pickup_gc_rows_total > 0 over time signals a stuck consumer somewhere — useful operator alert. Plan: docs/plans/articles-bulk-import.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-29 01:06:15 +02:00
Till JS	93545f8516	chore: drop who + kontext MANA_APPS entries to match earlier extractions ... Two cleanup follow-ups that the parallel sessions which extracted these modules left behind, surfaced by the route-drift test added in 6d193a9fa: who — `chore: extract who module into standalone repo` (a3eedfc87) + follow-up cleanup (f076d9345) removed `lib/modules/who/` and the workbench `registerApp({ id: 'who' })` block, but the broken `/who/+page` and `/who/play/[gameId]/+page` routes still imported the deleted module and the MANA_APPS entry, APP_ICONS icon, categories.ts mapping and help-content block were still in place. Drop all five. kontext — `feat(notes): isSpaceContext flag replaces kontext module (Option B)` (8fbdc6db7) replaced the kontext module with a per-note `isSpaceContext` flag in the notes module. The MANA_APPS entry I added in 6d193a9fa and the matching APP_ICONS entry are now both stale — there is no `kontext` route, no module, no registerApp. Drop them. Verification: `registry.spec.ts` 4/4 green, `svelte-check src/lib` 0 errors / 5 warnings (pre-existing in other files). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-29 01:04:34 +02:00
Till JS	0d85d7c36b	feat(forms): M5 AI tools — 7 tools im AI_TOOL_CATALOG ... AI-Zugriff aufs Forms-Modul (docs/plans/forms-module.md M5): Propose (User-Approval erforderlich): - forms_create — neues Formular im Draft-Status, optional mit Feldern. Field-Shape im params-Array: { type, label, required?, helpText?, options?: [{label}] }. Type-Enum aus dem 11-Typ-Katalog. Planner kann z.B. "Vereins-Anmeldung" mit Name+Email+Position+Trikotgröße in einem Aufruf bauen. - forms_add_field — Feld ans Ende anhängen, Reorder bleibt User vorbehalten (Drag im Builder). - forms_publish — draft → published. Wirft, wenn Form keine Antwort- felder hat (nur section/consent würde Public-Submit sinnlos machen). - forms_close — published → closed, Antworten + Share-Link bleiben. Auto (silent execution während Planner-Reasoning): - forms_list — Metadaten (id, title, status, fieldCount, responseCount, visibility), Status-Filter optional, Default-Limit 50. VaultLocked- aware → klare Fehlermeldung statt Crash. - forms_get_responses — Aggregat-Stats: per Form ein ResponseAggregate {totalCount, statusCounts, choiceHistograms, textSamples, numericStats}. Choice-Felder mit Option-Label-Mapping (nicht Option-IDs), Text-Felder als Sample-Array (cap 50, default). - forms_summarize_responses — gleicher Aggregator mit window-filter (sinceDays) und höherem Sample-Cap (200), als Daten-Vorlage für LLM-Clustering im nächsten Planner-Schritt. Augur-style: keine eigene LLM-Roundtrip, der Planner formuliert Themes selbst. Verdrahtung: - AI_TOOL_CATALOG in @mana/shared-ai mit 7 ToolSchema-Einträgen + defaultPolicy. - ModuleTool-Implementierungen in modules/forms/tools.ts mit scopedForModule für Space-Awareness, decryptRecords für encrypted- table-Reads, VaultLocked-Handling. - Registriert in data/tools/init.ts. Validierung: - mana-ai planner-drift test: 4/4 grün — alle 4 propose-Tools (forms_create/add_field/publish/close) im SERVER_TOOLS-Subset. - svelte-check 0 errors in forms/. - Forms unit tests: 16/16 (csv + branching) unverändert grün. Tools-executor.test.ts ist pre-existing rot wegen $lib/modules/context-Drift in module-registry.ts (Parallel-Session- WIP, nicht durch mich). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-29 00:33:55 +02:00
Till JS	a295894ca6	chore: drop legacy context module files (companion to acb737e25) ... Companion deletion sweep — acb737e25 removed all the *registry refs* to the legacy `context` module, but its source files were still on disk on main (because the original deletion in d3e2e73ca on the articles-bulk-import branch was bundled with unrelated photon / broadcast-rename work and never landed on main). Dropping them now so the consolidation is self-contained: - apps/mana/apps/web/src/lib/modules/context/ — entire module dir - apps/mana/apps/web/src/routes/(app)/context/ — page routes - apps/mana/apps/web/src/lib/components/dashboard/widgets/ContextDocsWidget.svelte - apps/mana/apps/web/src/lib/i18n/locales/context/{de,en,es,fr,it}.json - packages/shared-branding/src/logos/ContextLogo.svelte Verified: svelte-check + tsc --noEmit both clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-29 00:23:10 +02:00
Till JS	1815139dc1	chore: drop context module — registry refs, schema, AI route, AppId ... The context module's UI + Dexie tables + i18n bundle were already removed in d3e2e73ca. This follow-up cleans up everything else that still referenced it: - API: rename POST /api/v1/context/import-url → /api/v1/kontext/import-url (the kontext singleton was the only consumer); drop the unused /ai/generate + /ai/estimate endpoints; rename the credit-op label AI_CONTEXT_IMPORT_URL → KONTEXT_IMPORT_URL; drop AI_CONTEXT_GENERATION from packages/credits. - Web: drop registerApp + File icon import from app-registry/apps.ts; drop contextModuleConfig from data/module-registry.ts (+ snapshot test); drop useRecentDocuments + useSpaces from cross-app-queries.ts; drop ContextDocsWidget from widget-registry + dashboard.svelte.ts + types/dashboard{,.test}.ts; drop dashboard.widgets.context from all 5 dashboard locales; drop context entries from hooks.server allowlist, splitscreen registry, observatory mockData, spiral collect, crypto registry + plaintext-allowlist. - Dexie: remove documents/contextSpaces/documentTags from v1, v31, v53 stores blocks; add v57 dropping the three tables on local dev DBs that already ran an earlier schema. - Shared-branding: drop 'context' from AppId union, APP_BRANDING, MANA_APPS, APP_ICONS (+ contextSvg), ContextLogo.svelte (+ logos barrel re-export). - Spiral-DB: drop context: 10 from MANA_APP_INDEX (slot now free). - i18n hardcoded-string baseline: drop 5 context routes/files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-29 00:20:04 +02:00
Till JS	8fbdc6db77	feat(notes): isSpaceContext flag replaces kontext module (Option B) ... Retire the kontext module entirely; the per-Space standing-context document is now a regular Note flagged with `isSpaceContext: true`. Daily use ("URL → Notiz") moves to the notes module as a first-class action; the same primitive is reused by the (planned) Brand/Firma-Space onboarding wizard to seed a Space-context Note from a URL. Why: kontext was inconsistent — its UI was a URL-crawler that wrote to userContext.freeform (profile module), while its kontextDoc table + AI-Mission-Runner auto-injection was a write-only shell with no real editor. One concept (Notes) now carries both ad-hoc noting and Space-context, with mutex (max 1 flagged Note per Space). Notes module: - types: add `isSpaceContext?: boolean` to LocalNote + Note - queries: add `useSpaceContextNote()` (the active Space's flagged note) - store: `markAsSpaceContext(id | null)` with mutex sweep across Space - ListView: "Aus URL importieren" inline form (URL + crawl-mode + KI-Zusammenfassung toggle); "Als Space-Kontext markieren" / "Space-Kontext lösen" context-menu item; ★-Badge on flagged notes - new api.ts: `crawlUrl()` client for POST /api/v1/notes/import-url Notes API (apps/api): - new modules/notes/routes.ts with /import-url (ported from kontext; same crawler + LLM summary pipeline, NOTES_IMPORT_URL credit op) - mount at /api/v1/notes; add 'notes' to RESOURCE_MODULES (beta+ tier) - delete modules/context (UI-less /ai/generate + /ai/estimate had no consumers; /import-url moved to notes) - packages/credits: rename AI_CONTEXT_GENERATION → NOTES_IMPORT_URL AI Mission Runner: - default-resolvers: drop kontextResolver + kontextIndexer; the notesIndexer flags `isSpaceContext` notes with "★ " prefix and bubbles them to the top of the picker - writing reference-resolver: `kind: 'kontext'` now reads the flagged Note via scope-scan instead of the kontextDoc table; tests updated - writing ReferencePicker: useSpaceContextNote replaces useKontextDoc - AiDebugBlock + MissionGrantDialog + ai-missions ListView: drop 'kontextDoc' from ENCRYPTED_SERVER_TABLES set - ai-agents ListView: drop 'kontext' from POLICY_MODULES Profile module: - ContextFreeform.svelte: switch import from kontext/api to notes/api (the URL-crawl is the same primitive; it still writes to userContext.freeform — only the import path changed) Dexie: - v58: notes index gains `isSpaceContext`; kontextDoc table dropped Kontext module deletion: - delete apps/mana/apps/web/src/lib/modules/kontext/ entirely - delete (app)/kontext/ route - drop registerApp + Scroll icon from app-registry/apps.ts - drop kontext entry from help-content - drop kontextModuleConfig from data/module-registry.ts - drop kontextDoc from crypto registry mana-auth: - bootstrap-singletons: drop bootstrapSpaceSingletons function entirely (kontextDoc was the only per-Space singleton); userContext bootstrap unchanged - better-auth.config: drop kontextDoc bootstrap call from personal-space hook + organizationHooks.afterCreateOrganization - me-bootstrap: drop per-space bootstrap loop; response shape kept (always-empty `spaces: {}`) for backwards-compat with older clients Note: the still-existing legacy `context` module (CMS-style docs/spaces, unrelated to kontext) is left in place; its cleanup landed on the articles-bulk-import branch and is out of scope for this PR. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-29 00:14:32 +02:00
Till JS	6d193a9fa7	chore(app-registry): polish 4 small wins — TOC + AppId-derive + route-drift test + 3 MANA_APPS ... §1 AppId derivation (shared-branding): - `AppId` is now `keyof typeof APP_BRANDING` (config.ts) instead of a hand-maintained union in types.ts. Adding/removing an entry in `APP_BRANDING` automatically updates the union — eliminates the drift class that produced the ContextLogo type-error. - `AppBranding.id` relaxed to `string` to break the circular type reference (key in `APP_BRANDING` is the authoritative id). §2 Route-drift smoke test (registry.spec.ts): - New 4th test: parses every `routes/(app)/*+page.svelte`, extracts the `<RoutePage appId="…">` literal, asserts the id is registered in the workbench app-registry. Catches drift like the earlier `appId="broadcasts"` vs id `'broadcast'` bug structurally. - ROUTE_ONLY_APP_IDS allowlist for routes that intentionally don't back a workbench module (gifts, llm-test, milestones, organizations, teams, tags). - Caught two real drifts in the process and fixed them: /agents/+page.svelte → appId="ai-agents" → "agents" /agents/templates/+page.svelte → same §3 MANA_APPS hochgezogen (kontext, wishes): - kontext (Web-Context URL crawler) + wishes (Wunschliste) had module + workbench card but no MANA_APPS branding entry. Both got proper description, longDescription and a fresh APP_ICONS entry (globe- with-text-lines for kontext, shooting-star for wishes). - Removed both from WORKBENCH_ONLY in spec — they're full apps now. - Note: `myday` was already in MANA_APPS, the WORKBENCH_ONLY entry was redundant and had been silently double-counting. §4 apps.ts — top-level INDEX comment: - 80 registerApp() calls were chronological-by-when-added — basically unsearchable. Added an §1–§4 navigation comment near the top grouping apps by role (entity / module surface / AI Workbench / System) so devs can jump to a section. Physical reordering of the 80 blocks deferred to avoid disturbing the active multi- terminal session — the TOC delivers ~80% of the navigation win. Bonus: register `forms` module that the parallel session added but hadn't wired into the workbench yet — the new route-drift test caught this immediately on first run. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-28 22:59:26 +02:00
Till JS	230dfd5dad	chore: extract arcade into standalone repo ... Arcade lives as its own pnpm workspace at ~/Documents/Code/arcade now, with no @mana/* coupling. This drops every reference and the games/ directory from the monorepo. Removes: - games/ directory (89 files: web + server + 22 HTML games + screenshots) - @arcade/web, @arcade/server pnpm workspace entries (games/* globs) - arcade scripts in root package.json (4 scripts) - arcade.mana.how from mana-auth trusted origins + CORS_ORIGINS - arcade entries in mana-apps registry, app-icons, URL overrides - arcade.mana.how from cloudflared tunnel + prometheus blackbox probes - arcade-web service block in docker-compose.macmini.yml - generate-env.mjs entries for arcade server + web - BRANDING_ONLY 'arcade' entry in registry consistency spec - dead arcade translation keys in GuestWelcomeModal (DE+EN) - arcade mention in CLAUDE.md, authentication guideline, MODULE_REGISTRY Verified: - services/mana-auth/src/auth/sso-config.spec.ts: 8/8 pass - pnpm install regenerates lockfile cleanly (-536 lines) - no remaining 'arcade' refs outside historical snapshot docs Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-28 22:40:01 +02:00
Till JS	0fc16d1bfd	feat(articles): bulk-import AI tool wiring (Phase 6) ... Adds import_articles_from_urls tool to the articles module so the AI Workbench can kick off a bulk-import job in one call. Auto-policy: the job itself is the unit of approval, no per-article propose card. - shared-ai schemas: declare the tool name + propose/auto policy - articles/tools.ts: implement parseUrls + articleImportsStore.createJob - consume-pickup.ts: handle the new event type - events/catalog.ts: register article-import lifecycle events - imports.svelte.ts: minor polish Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-28 22:33:31 +02:00
Till JS	fa299e3bf9	feat(app-registry): wire up 4 modules + 7 routes + tier-patch validator ... Resolves the cross-cutting drift that the app-registry sanity-test was silently catching but BRANDING_ONLY exceptions papered over. App-registry wiring: - Register augur, broadcasts, invoices, timeline as workbench cards. - Resolve agents↔ai-agents naming drift: workbench id is now `agents` (matches MANA_APPS + the /agents route URL); folder stays `ai-agents` for grouping with other ai-* modules. Broadcast→broadcasts unification: - module.config appId, MANA_APPS id, APP_ICONS key, all route appIds, and the redundant APP_URL_OVERRIDES entry — all aligned with the earlier folder rename so nothing diverges anymore. Top-level routes for workbench-only modules: - /goals, /myday, /kontext, /rituals, /automations, /activity — thin RoutePage wrappers around the existing module ListViews. - /timeline becomes a real module (ListView extracted from the route), route shrinks to a 12-line wrapper. Food unarchive: - packages/shared-branding/src/mana-apps.ts: remove `archived: true` from food entry. The module is fully wired (registered, synced, routed, with AI tools); the flag was outdated. i18n cleanup: - Rename ai-agents → agents key in all 5 apps locales. - Drop dead "observatory" key from all 5 nav locales (route folder was removed in 7bca16dfa). New CI guard — scripts/validate-tier-patches.mjs: - Scans for `LOCAL TIER PATCH — revert before release` markers. - Default: informational list (does not fail). - Strict mode (MANA_TIER_PATCH_STRICT=1) for release/RC pipeline. - Wired into validate:all. Spec update: - registry.spec.ts WORKBENCH_ONLY/BRANDING_ONLY: documented Settings family + AI Studio surfaces + intentionally-internal modules so the drift guard fires only on real drift. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-28 22:21:41 +02:00
Till JS	c7094207da	fix(feedback): ReactionBar stoppt Click-Bubbling ... Wer in Feed/Workbench eine Reaction setzt, landete bisher direkt im Detail-View — der Button-Click ist zur Card-onclick durchgesickert. Fix in der Quelle: ReactionBar.handleClick ruft jetzt e.stopPropagation() bevor onToggle feuert. Damit funktioniert es überall, wo Reactions in einer klickbaren Hülle sitzen (Feed-Cards, MyReactedView, Detail-Page, zukünftige Surfaces). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-28 17:25:22 +02:00
Till JS	15ab24bda8	feat(feedback): heart-half als globales Feedback-Icon + inline-Form in der Workbench ... Drei Probleme adressiert: 1. **Icon-Vereinheitlichung**: alle Feedback-Affordances tragen jetzt das phosphor `heart-half`-Icon (statt vorher Lightbulb/Mix). Geändert in PillNav-Usermenü, ModuleShell-Header (FeedbackHook), Phosphor-Icon- Map. Eine Stelle, ein Icon — Wiedererkennung steigt. 2. **Inline statt Modal in Workbench-Cards**: AppPage.svelte rendert das Feedback-Formular jetzt im selben Slot wie die Hilfe-Seite — Klick auf das Heart-Half-Icon togglet den Inline-Panel statt einen Modal-Backdrop über die ganze Workbench zu legen. Hilfe und Feedback sind mutually-exclusive (eines geht zu, sobald das andere aufgeht). 3. **Form-Body extrahiert**: FeedbackForm.svelte enthält jetzt das Formular ohne jegliches Chrome. FeedbackQuickModal nutzt es im Modal- Mode (Standalone-Routen, PillNav), AppPage im Inline-Mode. Eine Quelle, beide Surfaces bleiben in sync. ModuleShell schluckt zusätzlich `onFeedback`/`feedbackOpen`-Props: wenn gesetzt, ruft die FeedbackHook-Komponente onClick statt das eigene Modal zu öffnen — der Host (AppPage) übernimmt das Rendering. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-28 15:36:52 +02:00
Till JS	ff823bff60	fix(feedback): POST /api/v1/feedback liest appId aus X-App-Id-Header ... Der Submit-Handler hat den Body 1:1 an feedbackService.createFeedback weitergereicht. Da CreateFeedbackInput appId nicht enthält (Client schickt es als X-App-Id-Header), schlug jeder INSERT mit "null value in column app_id violates not-null constraint" fehl. Außerdem: lightbulb-Icon im phosphor-icon-map nachgezogen, sonst zeigt der "Idee teilen"-Eintrag in der barMode-Variante des Usermenüs kein Icon (nur Label). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-28 15:16:11 +02:00
Till JS	94d3277e2e	feat(feedback): "Idee teilen" lebt jetzt im PillNav-Usermenü ... Ersetzt den schwebenden "Idee?"-Pill durch einen Eintrag im rechten Usermenü (Profil / Credits / Idee teilen / Logout). Ein Affordance an einer Stelle statt zwei nebeneinander. - PillNavigation: neuer onFeedback-Prop + Lightbulb-Icon. Wenn gesetzt, ersetzt der Eintrag den Legacy-/feedback-Link in accountLinks und taucht zusätzlich oben in den userMenuBarItems (barMode) auf. - UserMenuPanel: AccountLink kennt jetzt onClick? als Alternative zu href? — Action-Chips schließen das Panel direkt nach dem Klick. - (app)/+layout: GlobalFeedbackPill-Mount entfernt, FeedbackQuickModal wird state-gebunden gerendert (moduleContext aus Pfad/?app= abgeleitet wie bisher in der alten Pill). - GlobalFeedbackPill.svelte gelöscht — niemand referenziert sie mehr. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-28 15:12:27 +02:00
Till JS	0c30a16eb5	fix: 4 boot-time noise + correctness bugs surfaced by post-deploy smoke ... All four were pre-existing; the audit smoke-test made them visible. Fixed together because they share a "boot console-warn cleanup" theme. 1. streaks ensureSeeded race (DexieError2 ×2) - Two boot-time liveQuery callers passed the `count > 0` check before either had written, then the second's `.add()` hit a ConstraintError. - Fix: cache the seed promise per module, run the existence check + bulkAdd inside one Dexie RW transaction, and only insert MISSING defs (preserves existing currentStreak/longestStreak counts). 2. encryptRecord('agents', …) "wrong table name?" warning - The DEV-only check fired whenever a record carried none of the registered encrypted fields, regardless of whether anything could actually leak. `ensureDefaultAgent` writes a fresh agent row before `systemPrompt` / `memory` exist — pure noise. - Fix: drop the "no fields at all" branch. Keep the case-mismatch branch (the branch that actually catches silent plaintext leaks). 3. Passkey signInWithPasskey "Cannot read properties of undefined (reading 'allowCredentials')" - Client destructured `{ options, challengeId }` from the server's options response, but Better-Auth's `@better-auth/passkey` plugin returns the raw PublicKeyCredentialRequestOptionsJSON (no envelope) and tracks the challenge in a signed cookie. Both `options` and `challengeId` came back undefined; SimpleWebAuthn blew up the moment it tried to read the request shape. Verify body `{ challengeId, credential }` was likewise wrong — Better-Auth wants `{ response }`. - Fix: align both register and authenticate flows with Better-Auth's native shape on options + verify, and add `credentials: 'include'` on every fetch so the challenge cookie actually round-trips. Server's verify proxy now reads `parsed?.response?.id` for credentialID rate-limiting. 4. /api/v1/me/onboarding/ → 404 - Hono's nested router (`app.route(prefix, sub)` + inner `app.get('/')`) matches the prefix-without-slash form only. The onboarding-status store sent the request with a trailing slash, so every login produced a 404 + a console warn. - Fix: client sends the path without trailing slash; mana-auth picks up `hono/trailing-slash` middleware as defense-in-depth so a future accidental trailing slash on any /me/* route 301-redirects instead of 404-ing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-28 14:56:24 +02:00
Till JS	246c94374f	test(feedback): pixel-avatar + redact privacy-boundary; mark plan SHIPPED ... Tests: - packages/feedback/src/avatar.test.ts — 10 unit tests (determinism, mirror-symmetry, color contrast, padding-resilience, pseudonym- integration, density-sanity). - services/mana-analytics/src/services/feedback-redact.test.ts — 9 privacy-boundary tests verifying: * anonymous path NEVER includes realName, even when author opted in * auth path NEVER includes realName when author opted OUT * realName only when (opted-in AND auth-path) — both gates required * userId / deviceInfo / voteCount stripped from output Plan-Doc: - docs/plans/feedback-rewards-and-identity.md status → shipped (3.A, 3.B, 3.C, 3.F live; 3.D, 3.E open) mit Commit-Hashes. Service-Layer minor: REWARD-const + redact als __TEST__-Export publik gemacht (nur fürs Testen, kein Verhaltensänderung). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-27 18:11:17 +02:00
Till JS	ee5bb2871c	feat(community): Phase 3.C — Identität (Avatar + Klarname-Toggle + Karma + Eulen-Profil) ... Macht aus den Pseudonymen echte Charaktere ohne Klarnamen-Zwang. Pixel-Identicon-Avatar (3.C.2): - generateAvatarSvg(displayHash) — pure-function, deterministisch. 5×5 left-mirrored Identicon mit HSL-Foreground/Background aus dem Hash. Inline-SVG, kein Storage, kein img-load-Flicker. - <EulenAvatar> Component im Package, in ItemCard neben dem Pseudonym. Klarname-Toggle (3.C.1): - auth.users + community_show_real_name boolean (default off, opt-in). - PATCH /api/v1/me/profile akzeptiert communityShowRealName. - mana-analytics LEFT JOINs auth.users → bei opt-in liefert auth- required /public + /me/reacted Endpoints zusätzlich realName. - Anonymous /api/v1/public/feedback/* zeigt realName NIE — auch nicht wenn opted-in. Public-Mirror bleibt für SEO + Privacy safe. - Migration 008_community_identity.sql lokal + prod eingespielt. Karma-System (3.C.3): - auth.users + community_karma int. toggleReaction increment/decrement am Author-User (Self-Reactions zählen nicht — kein Self-Farming). - KARMA_THRESHOLDS + tierFromKarma() im Package: Bronze (0-9) / Silver (10-49) / Gold (50-199) / Platin (200+). - ItemCard zeigt Tier-Dot neben dem Pseudonym, Title-Tooltip mit Karma-Zahl. Floor-clamped at 0. Eulen-Profil (3.C.4): - GET /api/v1/public/feedback/eule/{hash} — alle public-Posts dieser Eule + aggregiertes Karma. SHA256-Format-Validation. - /community/eule/[hash] Public-SSR-Route mit Avatar-Hero, Tier-Badge, Karma-Counter, Post-Liste. Author-Klick im ItemCard navigiert hin. - publicFeedbackService.getEulenProfile() im Package. PublicFeedbackItem erweitert um displayHash (public Pseudonym-ID, SHA256 ist one-way → safe to expose) + karma + optional realName. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-27 15:15:16 +02:00
Till JS	3a18a5e50d	feat(community): Phase 3.B — loop closure (notifications + my-wishes page) ... Schließt den Loop zwischen Submit und Ship. User kriegt jetzt: - Toast beim nächsten App-Start, wenn ein eigener oder unterstützter Wisch ›planned/in_progress/completed/declined‹ wurde - /profile/my-wishes als persönliche Roadmap mit drei Tabs: Eigene · Unterstützt · Inbox Server (mana-analytics): - Neue Tabelle feedback_notifications mit ON DELETE CASCADE auf user_feedback. Migration 0004 lokal + prod eingespielt. - adminUpdate enqueued bei jeder Status-Transition Author- Notifications. AdminResponse-Edits feuern eine eigene 'admin_response'-Notify. tryGrantShipBonus hängt zusätzlich Reactioner-Notifications dran (›Dein Like ist gelandet, +25 Mana‹). - Endpoints: GET /api/v1/feedback/me/notifications?unread_only=true&limit=N POST /api/v1/feedback/me/notifications/:id/read POST /api/v1/feedback/me/notifications/read-all GET /api/v1/feedback/me/reacted (für die My-Wishes-Page) Package (@mana/feedback): - FeedbackNotification + NotificationKind types exportiert - service.getNotifications/markNotificationRead/markAllNotificationsRead - service.getMyReactedItems Web: - lib/notifications/feedback-toaster.svelte.ts: Boot-Pull + 60s-Poll, rendert unread-notifications via toast-store, markiert sofort read. In (app)/+layout.svelte's authReady-Hook gestartet/gestoppt. - /profile/my-wishes: Tab-View über getMyFeedback + getMyReactedItems + getNotifications. Tabs zeigen Counter-Badges, unread-Badge in der Inbox-Sektion. ›Alle als gelesen markieren‹-Action vorhanden. Pre-launch saubere Lösung — kein Polling-Spam (60s), Mark-Read direkt nach Toast-Display, fail-soft an mehreren Stellen. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-27 14:55:01 +02:00
Till JS	eecf64c1c6	feat(community,feedback): +5 reward chip + Phase 3.F legacy-cleanup ... UI: - FeedbackQuickModal Success-State + Onboarding-Wish Confirm zeigen +5-Mana-Reward-Chip mit reward-in-Animation. Sofortiger Sichtbarer Reziprozitäts-Loop. Legacy-Cleanup (Phase 3.F): - @mana/feedback dropped: - FeedbackPage.svelte, FeedbackCard.svelte, FeedbackList.svelte, FeedbackForm.svelte, VoteButton.svelte, StatusBadge.svelte (alles Pre-Reactions-Markup, durch Community-Modul ersetzt) - vote/unvote/toggleVote/getPublicFeedback service-shims - VoteResponse, voteCount, userHasVoted Types - mana-web dropped: - lib/modules/feedback/ListView.svelte - routes/(app)/feedback/+page.svelte - app-registry-Eintrag 'feedback' (nur Bug-Reports — Community macht das ohnehin besser via /community) Pre-launch saubere Lösung: keine Backward-Compat-Shims, keine alten Markup-Reste. ReactionBar bleibt der einzige Voting-Surface, /community ist die einzige Feedback-Surface. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-27 14:14:08 +02:00
Till JS	ae6a14fb76	feat(shared-ai): SYSTEM_BOOTSTRAP system source — fallback inserts now stamp origin='system' ... The race-window `getOrCreateLocalDoc()` fallback in userContextStore + kontextStore stays (without it, a write that lands between "endpoint provisioned the singleton in mana_sync" and "first pull landed it in IndexedDB" would hit `update(missing-id, diff)` — a Dexie no-op that silently swallows the user's edit). But it was semantically lying: the insert stamped `origin='user'` even though the row is logically a client-side replica of the server-side bootstrap. This commit adds `SYSTEM_BOOTSTRAP = 'system:bootstrap'` to `@mana/shared-ai` and wraps the two fallback inserts in `runAsAsync(makeSystemActor(SYSTEM_BOOTSTRAP), ...)`. The Dexie hook now stamps `origin: 'system'` on the empty-row insert — structurally identical to the row mana-auth's bootstrap-singletons.ts writes. When the server's pull arrives later both sides carry the same origin and the conflict-gate stays quiet. The user's subsequent writes still stamp `origin: 'user'` on the changed fields. Plan: docs/plans/sync-field-meta-overhaul.md (F4-fu Fallback-Origin row). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-27 01:44:30 +02:00
Till JS	c9b122076a	feat(feedback): public feed types + ReactionBar + service split ... @mana/feedback wird zur Pflege-SSOT für Public-Community-Hub. - PublicFeedbackItem-Typ: anonymisiertes Item, das nur display_name + reactions + status führt — kein userId, displayHash, deviceInfo. - ReactionEmoji ('👍' '❤️' '🚀' '🤔' '🎉') + REACTION_LABELS mit DE-Labels. - CreateFeedbackInput erweitert um moduleContext + parentId. Reactions + score auf Feedback-Type optional gemacht. - Service-Split: createFeedbackService — auth-required Submit/React/Manage, getPublicFeed (auth-enriched mit myReactions) createPublicFeedbackService — anonymous, SSR-only, getFeed/getItem. toggleReaction(emoji) statt vote/unvote (legacy-Shims bleiben für back-compat zu vote → '👍'-Toggle). - ReactionBar.svelte: Slack-Style emoji-row mit Active-Highlighting für myReactions, ReadOnly-Mode für Public-SSR. Auto-disabled-Tooltip. - index.ts re-exportiert die neuen Typen + ReactionBar; FeedbackVote rausgeschmissen (durch FeedbackReactions im Server-Schema ersetzt). FeedbackCard + FeedbackPage minimal angepasst, damit svelte-check clean bleibt — die Legacy-Komponenten bleiben funktional, werden aber in Phase 3 zu @mana/feedback's neuen Modul-Views ausgemistet. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-27 00:01:06 +02:00
Till JS	6bb9d77be9	feat(sync): F3 — drop updatedAt as a synced data field ... Removes `updatedAt` from the wire protocol and from every Local-prefixed record type. Replaced by two orthogonal mechanisms — deriveUpdatedAt() for read-side public-facing values, _updatedAtIndex shadow for indexed sorts. Local-side: - New `_updatedAtIndex` shadow column. Stamped by the Dexie creating / updating hook on every write. Stripped from the pending-change payload so it never travels to mana-sync. Indexed in Dexie v53 on the 22 tables that previously indexed `updatedAt`. - `deriveUpdatedAt(record)` in sync.ts returns max(__fieldMeta[*].at) so the public-facing Task / Note / etc. shape keeps an `updatedAt: string` property without holding it as data. - Type-converters across ~60 module/queries.ts and types.ts files now call `deriveUpdatedAt(local)` instead of reading `local.updatedAt`. Module-store sweep: - Regex codemod removed `updatedAt: new Date().toISOString()` / `: now` / `: now()` / `: nowIso()` stamping from 121 store files (~382 call sites total). Single-property update calls (`{ updatedAt: now }`) collapsed to `{}`; touch-only patterns (writing/drafts, writing/generations) kept the call as a no-op because the hook now stamps `_updatedAtIndex` automatically on any Dexie modification. - Local* interfaces stripped of `updatedAt: string` (43 types.ts files). Public-facing types (Task, Note, Mission, Agent, …) keep `updatedAt: string` as a computed read-side property. - Companion's chat conversation now sorts on a real `lastMessageAt` data field instead of touching `updatedAt`. - Session-only stores (times/session-alarms, session-countdown-timers) stamp `updatedAt: now` directly because they're not in Dexie and have no field-meta layer to derive from. Sync engine: - applyServerChanges sets `_updatedAtIndex` itself when applying server changes (max of server-field times for updates, recordTime for inserts) so server-replays land orderable. - Dropped the legacy `localUpdatedAt` fallback — every record now has `__fieldMeta`, the per-field at is the canonical source. - Soft-delete tombstone path stops stamping `updatedAt: serverTime`, uses `_updatedAtIndex` instead. Server-side: - mana-ai iteration-writer no longer emits `updatedAt` in sync_changes.data; receivers derive it from the field-meta map. - mana-sync types: no change (the wire format already uses `field_meta` / `at` from F1). Out of scope: backend Drizzle schemas (mana-credits, mana-events, …) keep their `updated_at` columns. Those are pure server-internal — not part of the sync_changes / __fieldMeta mechanism F3 cleans up. Tests + checks: - 0 svelte-check errors over 7652 files. - 29/29 sync.test.ts (vitest). - 61 mana-ai bun tests. - mana-sync go test ./... cached green. Plan: docs/plans/sync-field-meta-overhaul.md F3. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-26 23:12:22 +02:00
Till JS	1398d76b41	refactor(lasts,firsts): German display names — "Letzte Male" / "Erste Male" ... "Lasts" auf Deutsch ist ein Homophon zu "die Last" (Bürde/Belastung). Ein deutscher Muttersprachler las "Last nicht gefunden" als "Bürde nicht gefunden". Falsches Gefühl für ein kontemplatives Modul. Renames: - mana-apps.ts: name "Lasts" → "Letzte Male", "Firsts" → "Erste Male" - lasts/de.json: app.title + Singular-Bezüge weg von "Last" auf "Letztes Mal" (detail.routeTitle, banner.recognition) bzw. "Eintrag" (detail.notFound, settings.testSampleTitle, …) - milestones/de.json: tabs.first/last + recap.topFirstsLabel/topLastsLabel switchen auf "Erste Male" / "Letzte Male" - store error: "Aufgehobene Lasts ..." → "Aufgehobene Einträge ..." Andere Locales (en/es/fr/it) bleiben unangetastet — dort ist "Lasts" und "Firsts" linguistisch unproblematisch. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-26 21:58:31 +02:00
Till JS	ba6274edbe	refactor(feedback): align package + DB enums, plan central hub ... Macht @mana/feedback zur SSOT für alle Nutzer-Feedback-Categories und -Status — Voraussetzung dafür, dass Onboarding-Wishes, NPS, Churn-Feedback etc. künftig dort landen. - Status-Enum: DB-Werte umbenannt new/reviewed/done/rejected → submitted/under_review/completed/declined (Package gewinnt). PG≥10 ALTER TYPE … RENAME VALUE ist non-destructive. - Category 'praise' ins Package aufgenommen (war nur in DB). - Category 'onboarding-wish' neu in Package + DB für den Wish-Step. - Default status in DB: 'new' → 'submitted'. - CreateFeedbackInput.isPublic optional → Service reicht durch, default bleibt true; private Categories wie onboarding-wish setzen false. - Schema-Datei mit SSOT-Kommentar versehen, der Drift in Zukunft verhindert. Hand-authored Migration unter services/mana-analytics/drizzle/0001_*.sql weil drizzle-kit push Enum-Werte nicht zuverlässig umbenennt. Manuell einspielen vor nächstem db:push: psql "\$DATABASE_URL" -f services/mana-analytics/drizzle/0001_align-feedback-enums.sql Plan in docs/plans/feedback-hub.md (Phase 0–4); Phase 0 + 1 jetzt, 2-4 deferred. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-26 21:52:25 +02:00
Till JS	bf3bca268a	feat(lasts): M1-M7 — module ship + Meilensteine-Aggregator ... Mirror sibling to firsts: das *letzte* Mal, das du etwas getan hast — markiert oder rückwirkend erkannt. Plan: docs/plans/lasts-module.md. M1 Skelett — Dexie v51 lasts-Tabelle, Encryption-Registry, Per-Space- Welcome-Seed, Empty-State ListView. Kategorien aus firsts/types.ts nach \$lib/data/milestones/categories.ts extrahiert (Re-Exports halten firsts-API stabil). M2 CRUD + DetailView — StatusTabs (Vermutet/Bestätigt/Aufgehoben), Quick-Add mit Mode-Toggle, always-editable DetailView mit Lifecycle- Buttons (Bestätigen, Aufheben mit Inline-Note), 44 i18n-Keys × 5 Locales. M3 Inbox + Inferenz — Dexie v52 lastsCooldown (12-Monate-Cooldown, deterministische ID), Source-Registry-Pattern in inference/, places- Source mit Heuristik visitCount>=5 Span>=180d Silence>=365d. InboxView mit Akzeptieren/Verwerfen + manueller Scan. contacts/habits → M3.b sobald jeweilige Frequenz-Felder existieren. M4 AI-Tools — 5 Tools im AI_TOOL_CATALOG (create_last, confirm_last, reclaim_last, list_lasts, suggest_lasts), Webapp-Executor mit Vault- Locked-Handling. Server-Drift-Test 4/4, Schema-Test 6/6. M5 Reminders + Settings — Pivot zu In-App-DueBanner statt OS-Push (kein PWA-Push-System im Repo). Pure date-math (12 Vitest cases), Settings- Store mit 4 Toggles, DueBanner mit max-N rendering, Test-Banner-Knopf. M6 Visibility + Unlisted-Sharing — VisibilityPicker + SharedLinkControls in DetailView, buildLastBlob mit reflective-core whitelist (reclaimed Lasts gehärtet ausgeblockt), SharedLastView public-render, Share- Dispatcher kennt 'lasts'. M7 Meilensteine-Aggregator — Cross-modul firsts vereinigt mit lasts Timeline + Year-Recap. Pure aggregator (mergeMilestones, buildMilestonesRecap), 12 Vitest cases. /milestones und /milestones/recap/[year] Routes, Cross-Link in lasts/ListView. Validation: 0 errors / 0 warnings (svelte-check 7645 files), 24/24 tests, i18n-parity 39x5 aligned (+2 namespaces), i18n-keys baseline- equal, crypto 211 tables. LOCAL TIER PATCH: lasts ist 'guest' für Testing — vor Release auf 'beta' setzen (packages/shared-branding/src/mana-apps.ts). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-26 21:40:29 +02:00
Till JS	ad5e04a554	feat(sync): F2 — origin-gated conflict-detection ... Closes the false-positive conflict-toast loop on history-replay. Conflict notifications now fire only when the local field meta records origin='user' AND the pull is not an initial hydration round. Origin source-of-truth: - shared-ai/field-meta.ts → originFromActor(actor) maps actor.kind onto the FieldOrigin enum: user→'user', ai→'agent', system+SYSTEM_MIGRATION →'migration', any other system source→'system'. - Dexie creating/updating hooks call it once per write so every persisted field carries the right pipeline tag. - repair-silent-twin + legacy-avatar wrap their writes in runAsAsync(makeSystemActor(SYSTEM_MIGRATION, ...)) so the hook stamps origin='migration'. Future replays of those rows from another device will not surface as conflicts. applyServerChanges options: - New ApplyServerChangesOptions { isInitialHydration?: boolean }. - Push-response and pull-paged-loop callers compute it from the cursor state (`!oldestCursor` / `!cursor`). Pagination resets the flag after the first page. - Conflict-trigger gates on `!options.isInitialHydration && localMeta[k] ?.origin === 'user'` in addition to the prior tests. Tests (sync.test.ts): - New: replay-burst (10 sequential server updates → 0 conflicts) - New: agent-origin local write + server overwrite → 0 conflicts - New: isInitialHydration suppresses everything → 0 conflicts - New: real user edit + server overwrite → 1 conflict - All 25 prior tests still pass. 29/29 vitest sync.test.ts cases green; svelte-check 0 errors over 7647 files. Plan: docs/plans/sync-field-meta-overhaul.md F2 done-criteria met. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-26 21:38:56 +02:00