mAi
390bd76287
Establishes the contract every per-question-type module must satisfy: - lib/questions/types.ts — QuestionTypeModule<T> interface (schema, defaultStub, isAnswerEmpty, emptyStats, ingest, finalise, sanitizeForPublic, csvColumns, csvCellFor, adminCellSummary, ParticipantInput, BuilderEditor, ResultsBlock). Plus the helper aliases QuestionForType<T> and StatsForType<T> (extract the discriminated-union variant for type T) and the shared Svelte component prop shapes. - lib/questions/registry.ts — QUESTION_MODULES (empty for now), getQuestion (throws on unknown), hasQuestion, listQuestionTypes. - lib/questions/registry.test.ts — locks the contract: getQuestion throws with a helpful error pointing at lib/questions/<type>.ts when a module is missing, hasQuestion returns false for nonsense, listQuestionTypes matches the modules array. Registry is intentionally empty in this commit — the legacy `q.type === '...'` strips in FormBuilder, participant page, Results.svelte, results.ts, submit, and export keep working. Per-type modules land in the next commits; the final commit flips callers to use getQuestion(q.type) and the legacy strips disappear. Svelte component slots accept broadly-typed props and narrow internally on question.type. The dispatch is sound at the call site (caller looked up by matching type) but TypeScript can't prove the cross-component relationship without significant generic gymnastics — runtime narrowing inside each component is cheaper and keeps the registry literal simple. 58 server tests + 2 component tests pass. svelte-check clean.
fdbck.msbls.de
Per-link feedback forms and live-chat masks. Anonymous, slug-gated, no auth required for participants.
Spun out from m/flexsiebels.de issue #63 — full design at docs/plans/feedback-feature.md.
Stack
SvelteKit 5 + Svelte 5 + bun + @sveltejs/adapter-node. Postgres + Supabase auth. Schema: fdbck.feedback_{instances,submissions,posts} on supa.flexsiebels.de (msupabase).
Run locally
cp .env.example .env # fill SUPABASE_*
bun install
bun run dev
Test + check
bun run test # rate-limit + public-scope unit tests
bun run check # svelte-check (type errors / a11y)
bun run build # adapter-node production build → ./build
Deploy
Dockerfile uses oven/bun:latest. Dokploy app: fdbck.msbls.de. DNS via Hostinger (handled out of band).
Structure
src/
hooks.server.ts — auth + public-scope policy gate
lib/server/
auth.ts — cookie JWT + Supabase refresh
fdb.ts — Postgres `fdbck` schema accessor
feedback.ts — slug generator + DB helpers + rate-limit constants
public-scope.ts — anonymous-DB-access fail-closed gate
rate-limit.ts — in-memory token bucket
schemas.ts — Zod request validation
supabase.ts — admin + anon client singletons
routes/
+page.svelte — landing
f/[slug]/ — public participant page (form + live chat)
admin/feedback/ — m's admin (list + detail + create)
api/
auth/ — sign-in / sign-out
public/feedback/ — anonymous slug-gated endpoints
admin/feedback/ — owner-scoped admin endpoints
Data model (canonical: design doc §5)
fdbck.feedback_instances— slug, title, description, owner_user_id, form_definition (jsonb), chat_enabled, status (open|closed), closed_atfdbck.feedback_submissions— instance_id, display_name (nullable = anonymous), client_session_id, answers (jsonb), client_ip, user_agentfdbck.feedback_posts— instance_id, display_name, client_session_id, body, hidden (m soft-moderate), client_ip, user_agent
Anti-abuse layers
- 32-char base62 slugs (~190 bits entropy)
- in-memory rate-limit (30 posts / 5 min, 10 submits / 5 min, per IP+slug)
- honeypot field on forms + chat (silently dropped)
- body length caps + closing kill-switch
- noindex meta +
robots.txtDisallow: /
Out of scope (v1)
Drag-drop form-builder · post reactions · realtime/SSE · CAPTCHA · trusted-tier owner sharing · branding/theming · auto-notifications. All have a clean upgrade path on the existing schema.
Issue origin
m/flexsiebels.de#63 — m PWA-voice 2026-05-05: "Im Wesentlichen quasi Microsoft Forms und Teams-Feedback in einem auf einer Webseite."