managarten/packages/website-blocks/src/analytics/AnalyticsInspector.svelte
Till JS 4fc9d6c59c feat(wardrobe): module foundation — garments + outfits space-scoped data layer (M1)
M1 of docs/plans/wardrobe-module.md — pure data layer + backend plumbing,
zero UI (that's M2). A user can now hold a digital wardrobe per space:
brand merch, club Trikots, family Kleiderschrank, team Kostüme, practice
Dresscode, and personal closet all live as separate pools under the same
Dexie tables, space-scoped like tags/scenes/agents after Phase 2c.

Data model — two tables, no join:

- wardrobeGarments (Dexie v41): single clothing items / accessories.
  Indexed on `category` + `createdAt` + `isArchived`. Encrypted:
  name/brand/color/size/material/tags/notes. Plaintext: category,
  mediaIds, counters, timestamps — all indexed or structural.
  `mediaIds[0]` is the primary photo used for try-on; additional
  ids are alternate views (back, detail) for M7.

- wardrobeOutfits (Dexie v41): named compositions referencing
  garment ids. Encrypted: name/description/tags. Plaintext:
  garmentIds (FK array), occasion (closed enum — useful for
  undecrypted filtering), season, booleans, lastTryOn snapshot.

- picture.images gains `wardrobeOutfitId?: string | null` as a
  plaintext back-reference. Try-on results land in the Picture
  gallery like any other generation; the outfit detail view
  queries them via this id rather than maintaining a third table.

Space scope:

- `wardrobe` added to all five explicit allowlists in shared-types/
  spaces.ts (personal is wildcard, no edit needed). Each space type
  gets a one-line comment explaining the real-world use case.
- App registry: `wardrobe` entry in shared-branding/mana-apps.ts
  with a rose→fuchsia gradient icon (T-shirt on hanger silhouette),
  color #e11d48, tier 'beta', status 'beta'.
- Module registry: wardrobeModuleConfig imported + appended to
  MODULE_CONFIGS so SYNC_APP_MAP picks it up automatically.

Backend:

- MAX_REFERENCE_IMAGES bumped 4 → 8 in picture/generate-with-
  reference (plus the client-side default in ReferenceImagePicker).
  Justified with a comment: face + body + top + bottom + shoes +
  outerwear + 2 accessories = 8. Cost doesn't scale with ref count
  (OpenAI bills per output), so the bump is a pure capability
  expansion with no credit-side risk.
- New POST /api/v1/wardrobe/garments/upload wraps uploadImageToMedia
  with app='wardrobe'. Registered under /api/v1/wardrobe in index.ts.
  Pattern 1:1 with the profile/me-images/upload endpoint; tier-gating
  falls out of wardrobe NOT being in RESOURCE_MODULES (tier='guest'
  works — consistent with picture's plain CRUD).

Stores emit domain events (WardrobeGarmentAdded, WardrobeOutfitCreated,
WardrobeOutfitTryOn, etc.) so later mana-ai missions can observe
activity without polling.

No UI in this commit. M2 (Garments-Grundlayer) wires the route + grid
+ upload-zone; M3 the Outfit composer; M4 the Try-On integration.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-23 18:27:37 +02:00

99 lines
2.5 KiB
Svelte

<script lang="ts">
import type { BlockInspectorProps } from '../types';
import type { AnalyticsProps } from './schema';
let { block, onChange }: BlockInspectorProps<AnalyticsProps> = $props();
const provider = $derived(block.props.provider);
const helpText = $derived.by(() => {
if (provider === 'plausible') {
return 'Trage hier die Domain ein, die du bei Plausible registriert hast (z.B. "meineseite.de"). Keine Cookies, DSGVO-konform.';
}
return 'Umami Website-ID (UUID). Keine Cookies, DSGVO-konform.';
});
const keyLabel = $derived(provider === 'plausible' ? 'Domain' : 'Website-ID');
const keyPlaceholder = $derived(provider === 'plausible' ? 'meineseite.de' : 'abc12345-1234-…');
</script>
<div class="wb-inspector">
<label class="wb-field">
<span>Provider</span>
<select
value={block.props.provider}
onchange={(e) => onChange({ provider: e.currentTarget.value as AnalyticsProps['provider'] })}
>
<option value="plausible">Plausible</option>
<option value="umami">Umami</option>
</select>
</label>
<label class="wb-field">
<span>{keyLabel}</span>
<input
type="text"
value={block.props.siteKey}
oninput={(e) => onChange({ siteKey: e.currentTarget.value.trim() })}
placeholder={keyPlaceholder}
/>
<small>{helpText}</small>
</label>
<label class="wb-field">
<span>Script-URL (optional)</span>
<input
type="url"
value={block.props.scriptUrl}
oninput={(e) => onChange({ scriptUrl: e.currentTarget.value.trim() })}
placeholder="https://analytics.deineseite.de/script.js"
/>
<small>Für selbst-gehostete Instanzen. Leer lassen für Default-CDN.</small>
</label>
<p class="wb-hint">
Der Block ist im Editor unsichtbar — er fügt auf der veröffentlichten Website einen einzigen
&lt;script&gt;-Tag ein. Keine Cookies, keine PII.
</p>
</div>
<style>
.wb-inspector {
display: flex;
flex-direction: column;
gap: 1rem;
}
.wb-field {
display: flex;
flex-direction: column;
gap: 0.25rem;
}
.wb-field > span {
font-size: 0.75rem;
font-weight: 500;
opacity: 0.7;
}
.wb-field input,
.wb-field select {
padding: 0.5rem 0.625rem;
border-radius: 0.5rem;
border: 1px solid rgba(255, 255, 255, 0.12);
background: rgba(255, 255, 255, 0.04);
color: inherit;
font-size: 0.875rem;
}
.wb-field small {
font-size: 0.7rem;
opacity: 0.55;
line-height: 1.4;
}
.wb-hint {
margin: 0;
padding: 0.5rem 0.75rem;
background: rgba(255, 255, 255, 0.03);
border-radius: 0.375rem;
font-size: 0.75rem;
opacity: 0.6;
line-height: 1.4;
}
</style>