@cosmicdrift/kumiko-bundled-features 0.37.0 → 0.38.0

package/src/user-data-rights/README.md

@@ -90,15 +90,15 @@ weglassen wenn er Custom-Hooks registrieren will.
 
 | Datei | Pinst |
 |-------|-------|
-| `audit-log.integration.ts` | Cross-User-Isolation, Account-weite Sicht, eventType-Filter, Admin-only operator-query, download-attempt 90d-retention |
-| `cross-data-matrix.integration.ts` | 3-Provider-Pipeline (user + fileRef + custom-domain), Cross-Tenant Forget mit user-anonymize, Other-User-Isolation |
-| `download.integration.ts` | HTTP-e2e via `r.httpRoute`: Magic-Link, multi-use, expired, failed-job, storage-cleared, cross-tenant-same-user, malicious-filename |
-| `request-export.integration.ts` | Idempotency, active-job-constraint, cross-tenant-anyMember-userId-pattern |
-| `request-deletion-callback.integration.ts` + `request-cancel-deletion.integration.ts` | Grace + Cancel-Pfad + Email-Callback best-effort |
-| `restriction-flow.integration.ts` | Status-Flip + Auth-Middleware-Block + Lift |
-| `run-{export-jobs,forget-cleanup,user-export}.integration.ts` | Worker-Logic + Idempotency + Email-Callbacks |
+| `audit-log.integration.test.ts` | Cross-User-Isolation, Account-weite Sicht, eventType-Filter, Admin-only operator-query, download-attempt 90d-retention |
+| `cross-data-matrix.integration.test.ts` | 3-Provider-Pipeline (user + fileRef + custom-domain), Cross-Tenant Forget mit user-anonymize, Other-User-Isolation |
+| `download.integration.test.ts` | HTTP-e2e via `r.httpRoute`: Magic-Link, multi-use, expired, failed-job, storage-cleared, cross-tenant-same-user, malicious-filename |
+| `request-export.integration.test.ts` | Idempotency, active-job-constraint, cross-tenant-anyMember-userId-pattern |
+| `request-deletion-callback.integration.test.ts` + `request-cancel-deletion.integration.test.ts` | Grace + Cancel-Pfad + Email-Callback best-effort |
+| `restriction-flow.integration.test.ts` | Status-Flip + Auth-Middleware-Block + Lift |
+| `run-{export-jobs,forget-cleanup,user-export}.integration.test.ts` | Worker-Logic + Idempotency + Email-Callbacks |
 | `policy-to-strategy.test.ts` | Retention.strategy → UserDataDeleteStrategy mapping |
-| `user-data-rights.integration.ts` | Boot-Smoke + Feature-Meta |
+| `user-data-rights.integration.test.ts` | Boot-Smoke + Feature-Meta |
 | `token-helpers.test.ts` + `zip-path.test.ts` | Token-Hashing + Path-Traversal-Schutz |
 | `export-job-{idempotency,schema}.test.ts` | Active-job-uniqueness + Schema-Constraints |
 

package/src/template-resolver/handlers/archive.write.ts

@@ -1,39 +0,0 @@
-import { fetchOne } from "@cosmicdrift/kumiko-framework/bun-db";
-import { defineWriteHandler } from "@cosmicdrift/kumiko-framework/engine";
-import { NotFoundError, writeFailure } from "@cosmicdrift/kumiko-framework/errors";
-import { z } from "zod";
-import type { TemplateResourceRow } from "../table";
-import { templateResourcesTable } from "../table";
-import { executor } from "./shared";
-
-// Setzt einen Template-Eintrag auf status='archived'. Resolver liefert
-// archivierte Templates nicht zurück — sie bleiben aber als Audit-Trail
-// in der DB (kein physisches Delete). Reaktivierung via publish.
-export const archiveWrite = defineWriteHandler({
-  name: "archive",
-  schema: z.object({ id: z.string().min(1) }),
-  access: { roles: ["TenantAdmin", "SystemAdmin"] },
-  handler: async (event, ctx) => {
-    const existing = await fetchOne<TemplateResourceRow>(ctx.db, templateResourcesTable, {
-      id: event.payload.id,
-    });
-    // ctx.db ist via createTenantDb tenant-scoped — existing ist null wenn
-    // das Template einem fremden Tenant gehört (SystemAdmin-Cross-Tenant
-    // braucht tenantIdOverride im Schema, M2-Erweiterung).
-    if (!existing) {
-      return writeFailure(new NotFoundError("template-resource", event.payload.id));
-    }
-
-    const result = await executor.update(
-      {
-        id: existing.id,
-        version: existing.version,
-        changes: { status: "archived" as const },
-      },
-      event.user,
-      ctx.db,
-    );
-    if (!result.isSuccess) return result;
-    return { isSuccess: true as const, data: { id: String(existing.id), status: "archived" } };
-  },
-});

package/src/template-resolver/handlers/publish.write.ts

@@ -1,42 +0,0 @@
-import { fetchOne } from "@cosmicdrift/kumiko-framework/bun-db";
-import { defineWriteHandler } from "@cosmicdrift/kumiko-framework/engine";
-import { NotFoundError, writeFailure } from "@cosmicdrift/kumiko-framework/errors";
-import { z } from "zod";
-import type { TemplateResourceRow } from "../table";
-import { templateResourcesTable } from "../table";
-import { executor } from "./shared";
-
-// Setzt einen Template-Eintrag auf status='active'. Typischer Workflow:
-// User editiert ein Draft, ist zufrieden, drückt Publish.
-//
-// Tenant-Isolation: Template muss zum event.user.tenantId gehören
-// (oder zu SYSTEM_TENANT wenn SystemAdmin). Cross-Tenant-Publish-
-// Versuche → NotFound (Pattern aus row-level-security).
-export const publishWrite = defineWriteHandler({
-  name: "publish",
-  schema: z.object({ id: z.string().min(1) }),
-  access: { roles: ["TenantAdmin", "SystemAdmin"] },
-  handler: async (event, ctx) => {
-    const existing = await fetchOne<TemplateResourceRow>(ctx.db, templateResourcesTable, {
-      id: event.payload.id,
-    });
-    // ctx.db ist via createTenantDb tenant-scoped — existing ist null wenn
-    // das Template einem fremden Tenant gehört (SystemAdmin-Cross-Tenant
-    // braucht tenantIdOverride im Schema, M2-Erweiterung).
-    if (!existing) {
-      return writeFailure(new NotFoundError("template-resource", event.payload.id));
-    }
-
-    const result = await executor.update(
-      {
-        id: existing.id,
-        version: existing.version,
-        changes: { status: "active" as const },
-      },
-      event.user,
-      ctx.db,
-    );
-    if (!result.isSuccess) return result;
-    return { isSuccess: true as const, data: { id: String(existing.id), status: "active" } };
-  },
-});

package/src/tenant/handlers/disable.write.ts

@@ -1,18 +0,0 @@
-import { createEventStoreExecutor } from "@cosmicdrift/kumiko-framework/db";
-import { defineWriteHandler } from "@cosmicdrift/kumiko-framework/engine";
-import { z } from "zod";
-import { tenantEntity, tenantTable } from "../schema/tenant";
-
-const crud = createEventStoreExecutor(tenantTable, tenantEntity, { entityName: "tenant" });
-
-export const disableWrite = defineWriteHandler({
-  name: "disable",
-  schema: z.object({ id: z.uuid() }),
-  access: { roles: ["SystemAdmin"] },
-  // Admin flip: last-writer-wins is fine. SystemAdmin is the only caller and
-  // there's no meaningful concurrent-edit race on this single boolean.
-  handler: async (event, ctx) =>
-    crud.update({ id: event.payload.id, changes: { isEnabled: false } }, event.user, ctx.db, {
-      skipOptimisticLock: true,
-    }),
-});

package/src/tenant/handlers/enable.write.ts

@@ -1,20 +0,0 @@
-import { createEventStoreExecutor } from "@cosmicdrift/kumiko-framework/db";
-import { defineWriteHandler } from "@cosmicdrift/kumiko-framework/engine";
-import { z } from "zod";
-import { tenantEntity, tenantTable } from "../schema/tenant";
-
-const crud = createEventStoreExecutor(tenantTable, tenantEntity, { entityName: "tenant" });
-
-// Recovery-Gegenstück zu disable — ohne enable wäre ein Fehlklick des
-// Operators nur per Event-Hack reversibel.
-export const enableWrite = defineWriteHandler({
-  name: "enable",
-  schema: z.object({ id: z.uuid() }),
-  access: { roles: ["SystemAdmin"] },
-  // Admin flip: last-writer-wins is fine. SystemAdmin is the only caller and
-  // there's no meaningful concurrent-edit race on this single boolean.
-  handler: async (event, ctx) =>
-    crud.update({ id: event.payload.id, changes: { isEnabled: true } }, event.user, ctx.db, {
-      skipOptimisticLock: true,
-    }),
-});