mirror of
https://github.com/Memo-2023/mana-monorepo.git
synced 2026-05-15 01:21:09 +02:00
Comic nutzte bisher 'openai/gpt-image-2' hartcodiert auf drei Ebenen (generate-panel.ts, comic.generatePanel MCP-Tool, generate_comic_panel AI-Tool). Wardrobe hat seit dem Nano-Banana-Commit einen TryOnModelPicker mit drei Optionen — Comic spiegelt das jetzt 1:1. Wählbar in allen drei Editoren (PanelEditor, BatchPanelEditor, StoryboardSuggester): - openai/gpt-image-2 (Default) — OpenAI GPT-image Standard - google/gemini-3-pro-image-preview — Nano Banana Pro, hohe Konsistenz, teurer - google/gemini-3.1-flash-image-preview — Nano Banana 2, neuestes, schnell, günstig Implementierung: - api/generate-panel.ts: PanelModel Union + DEFAULT_PANEL_MODEL + model? Param auf RunPanelGenerateParams + im HTTP-Body weitergereicht (vorher hart 'openai/gpt-image-2'). - components/PanelModelPicker.svelte: neue Komponente, Stil/Markup identisch zu TryOnModelPicker für Muskel-Memory über beide Flows. - components/PanelEditor.svelte: `let model = $state(DEFAULT_PANEL_MODEL)` + Picker oberhalb der Qualität-/Format-Leiste + model im runPanelGenerate-Call. - components/BatchPanelEditor.svelte: gleiche Änderung — ein Model pro Batch (nicht pro Row) damit der Batch konsistent rendert. - components/StoryboardSuggester.svelte: gleiches Pattern; der Picker landet zwischen "Panel manuell"-Button und dem Qualität/Format-Block. - packages/mana-tool-registry/src/modules/comic.ts: generatePanel Input-Schema bekommt model mit zod.enum() + default; im Body wird input.model durchgereicht. - packages/shared-ai/src/tools/schemas.ts: generate_comic_panel bekommt Parameter 'model' optional mit gleicher Enum-Liste. - apps/mana/apps/web/src/lib/modules/comic/tools.ts: isValidModel Guard + Parameter-Validierung; model an runPanelGenerate. Keine Story-Level-Persistierung — model bleibt lokaler State pro Editor-Mount. Eine model-Spalte auf comicStories würde Migration brauchen und die Wahl ist eh ad-hoc pro Panel/Batch. Plan-Doc (§2.1) dokumentiert die Entscheidung + die drei Optionen. 107 shared-ai tests weiter grün. check + validate:all clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| agent-loop-improvements-m1.md | ||
| ai-mission-key-grant.md | ||
| articles-homepage.md | ||
| articles-module.md | ||
| broadcast-module.md | ||
| comic-module.md | ||
| data-export-v2.md | ||
| destructive-tools-opt-in.md | ||
| event-discovery.md | ||
| invoices-module.md | ||
| library-module.md | ||
| mail-module-plan.md | ||
| mana-mcp-and-personas.md | ||
| mana-research-service.md | ||
| me-images-and-reference-generation.md | ||
| me-images-space-scope-migration.md | ||
| multi-agent-workbench.md | ||
| news-research-module.md | ||
| onboarding-flow.md | ||
| per-space-vs-user-global-tags.md | ||
| planner-function-calling.md | ||
| README.md | ||
| scene-scope-empty-state.md | ||
| shared-space-smoketest.md | ||
| social-relay-module.md | ||
| space-scoped-data-model.md | ||
| spaces-foundation.md | ||
| team-workbench.md | ||
| tipps-module.md | ||
| unlisted-sharing.md | ||
| visibility-system.md | ||
| wardrobe-module.md | ||
| website-builder-smoketest.md | ||
| website-builder.md | ||
| workbench-cards-migration.md | ||
| workbench-templates.md | ||
| writing-module.md | ||
Plans
Design + rollout plans, grouped by topic. Plans are long-form docs with baked-in decisions, phasing, open questions, and (when shipped) a history section with commit refs.
AI / Workbench roadmap
The Mana AI Workbench has evolved in three successive planned waves — each one laying foundations the next one relies on:
User hat einen Companion (v0 — shipped before these docs)
│
▼
AI Missions + Proposals + Policy + Revert
│
▼
Mission Key-Grants ← ai-mission-key-grant.md ✅
(encrypted inputs decryptable by the server runner)
│
▼
Multi-Agent Workbench ← multi-agent-workbench.md ✅
(named agents, per-agent policy/memory/budget,
identity-aware Actor, scene→agent lens)
│
▼
Team Workbench ← team-workbench.md 📝 (not started)
(multi-user + shared AI context,
admin lens on team members)
| Plan | Status | Scope |
|---|---|---|
ai-mission-key-grant.md |
✅ Shipped | Per-mission RSA-wrapped key grant so mana-ai can decrypt allowlisted encrypted records when user opts in. |
multi-agent-workbench.md |
✅ Shipped | Identity-aware Actor + named AI agents owning missions + per-agent policy + scene lens. 28 tools across 11 modules including server-side web-research. |
workbench-templates.md |
✅ T1 Shipped | Generalised templates: 3 agent-templates + 3 non-AI workbench starter-kits. Seed-handler registry for per-module data seeding. |
team-workbench.md |
📝 Forward-looking | TeamSpace with membership, team-encrypted records, admin lens on team members. Reuses Actor.principalId + key-wrapping patterns from the two above. |
Cross-references:
- Architecture narrative:
docs/architecture/COMPANION_BRAIN_ARCHITECTURE.md§20 (AI Workbench base), §21 (Mission Grants), §22 (Multi-Agent), §23 (Reasoning Loop + Research + Debug) - Non-plan ideas backlog:
docs/future/AI_AGENTS_IDEAS.md - Service-internal notes:
services/mana-ai/CLAUDE.md - Webapp-internal notes:
apps/mana/CLAUDE.md→ "AI Workbench" section
Other plans
| Plan | Topic |
|---|---|
mail-module-plan.md |
Mail module — IMAP/SMTP integration |
news-research-module.md |
News + research pipeline |