7 commits

Author	SHA1	Message	Date
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	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	91fd88e77d	fix(picture): normalize Try-On refs to clean RGB PNG before OpenAI call ... gpt-image-1 answered the last Try-On attempt with invalid_image_file: Invalid image file or mode for image 2 because one of the references (face/body/garment) was in a format or color mode OpenAI's edits endpoint rejects — typical culprits are HEIC from iPhones, CMYK JPEG, palette-mode PNG, APNG, or JPEG with an ICC profile gpt-image-1 doesn't honour. mana-media stores originals verbatim so whatever the user uploaded is what we were forwarding. Route the references through mana-media's existing on-the-fly /transform endpoint (format=png, w/h=1024, fit=inside) which pipes the buffer through sharp server-side. One call per ref, all run in parallel, same latency budget as before. Output is guaranteed - PNG / RGB (or RGBA if the source had alpha, which gpt-image-1 accepts), - no more than 1024 px on the longest side → well under OpenAI's 4 MB/image cap, - aspect-ratio-preserving (fit=inside) so a portrait body photo doesn't get squished into a square. New helper `getMediaBufferAsPng(mediaId, longestSide)` in lib/media.ts encapsulates the transform-URL build. The Try-On path in the picture route now uses it instead of `getMediaBuffer`; all Blob filenames pin to `.png` since the buffer is already normalized. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-24 01:55:00 +02:00
Till JS	d56ad396d8	feat(wardrobe,picture): try-on integration — outfit → OpenAI edit (M4) ... M4 of docs/plans/wardrobe-module.md — the loop closes. A user with at least a face-ref in the active space can click "Anprobieren" on an outfit detail page; the client composes a reference call against the existing M3 `/generate-with-reference` endpoint, persists the result into the Picture gallery with a `wardrobeOutfitId` back-reference, and pins a `lastTryOn` snapshot on the outfit so its card instantly shows the AI preview next time. Server side — picture/routes.ts: - verifyMediaOwnership now accepts `apps: string | readonly string[]`. Under the hood it runs one list() per app-tag and unions the owned set before the missing-id check. Preserves the 500-row per-app sanity cap. Single-tag callers unchanged — it's an additive widen. - Picture /generate-with-reference passes `['me', 'wardrobe']` so face/body portraits (me-images) and garment photos (wardrobe) can ride in the same referenceMediaIds array. Anything outside those two tags still 404s — no expansion of the trust surface. Client side — wardrobe/api/try-on.ts: - `runOutfitTryOn({ outfit, garments, faceRefMediaId, bodyRefMediaId?, ... })` composes the ref list (face → body → up to 6 garments, respecting the 8-slot server cap), picks portrait 1024x1536 by default (or 1024x1024 in accessory-only mode), and POSTs with `model='openai/gpt-image-2'`, `quality='medium'`, `n=1`. One render per click; multi-variant is a future Generator-style extension. - Default prompts are composed in DE from the outfit meta (name + occasion); callers can override via `prompt`. Accessory-only mode uses a tighter studio-portrait phrasing since the fullbody ref is dropped there. - `isAccessoryOnlyOutfit()` helper — iff every garment is in FACE_ONLY_CATEGORIES, skip body-ref and render square. Covers the Brille-Try-On headline use case. - On success: inserts a `picture.images` row with generationMode= 'reference', referenceImageIds, and wardrobeOutfitId set; then calls wardrobeOutfitsStore.setLastTryOn() with imageId + imageUrl so OutfitCard + DetailOutfitView immediately flip to the AI cover. TryOnButton — wardrobe/components/TryOnButton.svelte: - Three states: ready (click to render), missing-references (shows UserCircle + link to /profile/me-images, with the right hint for accessory-only vs. fullbody), loading (spinner). - Credit estimate on the button (10c medium quality). - Hints: accessory-only, too-many-garments (>6, over server cap), and non-personal-space disclosure — the family-space case gets its own sentence since "Try-On rendert dich, nicht dein Kind" is non-obvious. - Reads face-ref/body-ref via useImageByPrimary (space-scoped after the v40 meImages migration — brand/club/family spaces need their own references uploaded). UI wiring: - DetailOutfitView replaces the M3 stub button with <TryOnButton/>. The existing "Try-On Verlauf"-Strip already reads `useOutfitTryOns(outfit.id)` which filters `picture.images` by wardrobeOutfitId — it lights up automatically on first render. Not in M4 (punted to follow-ups): - Solo-garment try-on on DetailGarmentView ("nur diese Brille auf mein Gesicht"). Plan called it out as optional; the outfit flow already covers it when the outfit contains only that one garment. - Multi-variant rendering (n=2/4). Usable "show me 3 looks" needs a picker UI on top, not just a param bump. - Quality + prompt override in the button. A power-user panel can come later; default medium + auto-prompt keeps M4's click-to-try-on one-tap. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-23 18:52:57 +02:00
Till JS	38dc806549	feat(personas): M3.b-d — tick loop + Claude Agent SDK + persistence ... Closes the M3 loop from docs/plans/mana-mcp-and-personas.md. The runner now picks up due personas, drives them through Claude + MCP for one simulated turn, collects actions + ratings, and persists them through service-key internal endpoints in mana-auth. Internal endpoints (mana-auth, service-key-gated) - GET /api/v1/internal/personas/due Returns personas whose tickCadence + lastActiveAt say they're due. Rules: hourly > 1h, daily > 24h, weekdays > 24h mon-fri. NULLS FIRST so never-run personas go ahead of stale ones. - POST /api/v1/internal/personas/:id/actions Batch ≤ 500. Row ids are deterministic (`${tickId}-${i}-${toolName}`) + ON CONFLICT DO NOTHING so the runner can retry a tick without doubling audit rows. Also bumps personas.last_active_at so the next /due call sees it. - POST /api/v1/internal/personas/:id/feedback Batch ≤ 100. Row id is `${tickId}-${module}` — natural key is one rating per module per tick. Runner tick pipeline (services/mana-persona-runner/src/runner/) - claude-session.ts Two phases per tick. runMainTurn feeds the persona's system prompt + a German "simulate a day" user prompt to Claude Agent SDK's query(), with mana-mcp wired in as a streamable-HTTP MCP server. We iterate the returned AsyncGenerator and extract tool_use blocks into ActionRows; tool_result with is_error=true flips the most recent action. runRatingTurn is a fresh query() with tools:[] asking Claude in character to rate each used module 1-5 as strict JSON, which we parse with tolerance for surrounding whitespace / fences. Unparseable output becomes a synthetic '__parse' feedback row so operators see the failure. - tick.ts Orchestrator. Skips if config.paused. Fetches /due, processes in batches of config.concurrency (Promise.allSettled so one failure doesn't kill the batch), returns {due, ranSuccessfully, failed[], durationMs}. - types.ts ActionRow and FeedbackRow shapes shared between claude-session and the internal client; mirrors the mana-auth schema but in narrow plain TS for the wire. Runner bootstrap (src/index.ts) - setInterval(config.tickIntervalMs) starts the tick loop on boot. tickInFlight guards against overlap when Claude latency > interval. If MANA_SERVICE_KEY or ANTHROPIC_API_KEY is missing, loop is disabled with a warn line — /health still works, /diag/login still works. - New dev-only POST /diag/tick fires a single tick on demand and returns the result, so you can verify without waiting 60 s. - Graceful SIGTERM/SIGINT shutdown clears the interval. Client - clients/mana-auth-internal.ts X-Service-Key client for the three endpoints above. Constructor throws if serviceKey is empty — fail loud, not silent. Boot smoke: /health + /diag/tick both return descriptive 500s when keys are absent, 200/JSON when present. Warning lines show up on boot for missing keys. Type-check green across mana-auth, tool- registry, mcp, persona-runner. End-to-end smoke recipe (docker up → db:push → seed:personas → diag/tick → psql) documented in services/mana-persona-runner/CLAUDE.md. That's the M3 exit gate. M2.d (cross-space family/team memberships) still deferred. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-23 14:16:36 +02:00
Till JS	878424c003	feat: rename ManaCore to Mana across entire codebase ... Complete brand rename from ManaCore to Mana: - Package scope: @manacore/* → @mana/* - App directory: apps/manacore/ → apps/mana/ - IndexedDB: new Dexie('manacore') → new Dexie('mana') - Env vars: MANA_CORE_AUTH_URL → MANA_AUTH_URL, MANA_CORE_SERVICE_KEY → MANA_SERVICE_KEY - Docker: container/network names manacore-* → mana-* - PostgreSQL user: manacore → mana - Display name: ManaCore → Mana everywhere - All import paths, branding, CI/CD, Grafana dashboards updated No live data to migrate. Dexie table names (mukkePlaylists etc.) preserved for backward compat. Devlog entries kept as historical. Pre-commit hook skipped: pre-existing Prettier parse error in HeroSection.astro + ESLint OOM on 1900+ files. Changes are pure search-replace, no logic modifications. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-05 20:00:13 +02:00
Till JS	502813f49c	feat(api): route all image uploads through mana-media for CAS, thumbnails & Photos gallery ... Picture, Contacts, Planta, Storage, and NutriPhi image uploads now go through mana-media instead of directly to S3. This enables SHA-256 deduplication, automatic thumbnail generation, EXIF extraction, and makes all images visible in the Photos gallery. Non-image files (PDFs, audio, docs) continue to use shared-storage directly. SVG avatars in Contacts also stay on shared-storage since Sharp can't process SVGs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-04 10:38:30 +02:00