@cosmicdrift/kumiko-framework 0.359.0 → 0.360.0

package/dist/files/record-read-check.d.ts

@@ -0,0 +1,9 @@
+import type { Registry, SessionUser } from "../engine/types/index.js";
+export type RecordReadCheck = (args: {
+    readonly entityType: string;
+    readonly entityId: string;
+    readonly user: SessionUser;
+}) => Promise<boolean>;
+type QueryAsUser = (type: string, payload: unknown, user: SessionUser) => Promise<unknown>;
+export declare function createRecordReadCheck(registry: Registry, query: QueryAsUser): RecordReadCheck;
+export {};

package/dist/files/record-read-check.js

@@ -0,0 +1,49 @@
+import { toKebab } from "../engine/qualified-name.js";
+import { isKumikoError } from "../errors/index.js";
+import { createFallbackLogger } from "../logging/index.js";
+const log = createFallbackLogger("files");
+// Only the "<entity>:detail" handler counts: other "<entity>:...:detail"
+// queries map to the same entity but may return a different shape or scope.
+// Entity names are globally unique and only the owning feature maps handlers
+// to its entity, so at most one QN matches per entity.
+function isEntityDetailQuery(qn, entityName) {
+    return qn.endsWith(`:query:${toKebab(entityName)}:detail`);
+}
+function buildDetailQueryIndex(registry) {
+    const detailQueryByEntity = new Map();
+    for (const qn of registry.getAllQueryHandlers().keys()) {
+        const entityName = registry.getHandlerEntity(qn);
+        if (entityName !== undefined && isEntityDetailQuery(qn, entityName)) {
+            detailQueryByEntity.set(entityName, qn);
+        }
+    }
+    return detailQueryByEntity;
+}
+// "May this user read the record?" is answered by the entity's own detail
+// query run as that user: handler access, row ownership and parent visibility
+// all apply, exactly as when the record is opened. null (not found or not
+// visible) and access errors mean no. Entities without a detail query never
+// grant access this way.
+export function createRecordReadCheck(registry, query) {
+    let detailQueryByEntity;
+    return async ({ entityType, entityId, user }) => {
+        detailQueryByEntity ??= buildDetailQueryIndex(registry);
+        const detailQuery = detailQueryByEntity.get(entityType);
+        if (detailQuery === undefined)
+            return false;
+        try {
+            const record = await query(detailQuery, { id: entityId }, user);
+            return record !== null && record !== undefined;
+        }
+        catch (error) {
+            if (!isKumikoError(error) || error.httpStatus >= 500) {
+                log.error("record read check failed; file access denied", {
+                    entityType,
+                    detailQuery,
+                    error: error instanceof Error ? error.message : String(error),
+                });
+            }
+            return false;
+        }
+    };
+}

package/dist/jobs/cron-repeat-options.d.ts

@@ -0,0 +1,9 @@
+export type CronTrigger = {
+    readonly cron: string;
+    readonly tz?: string | undefined;
+};
+export type CronRepeatOptions = {
+    readonly pattern: string;
+    readonly tz?: string;
+};
+export declare function cronRepeatOptions(trigger: CronTrigger): CronRepeatOptions;

package/dist/jobs/cron-repeat-options.js

@@ -0,0 +1,5 @@
+export function cronRepeatOptions(trigger) {
+    return trigger.tz === undefined
+        ? { pattern: trigger.cron }
+        : { pattern: trigger.cron, tz: trigger.tz };
+}

package/dist/jobs/job-runner.js

@@ -17,6 +17,7 @@ import { RedisKeys } from "../pipeline/redis-keys.js";
 import { createGatedIdentitySwitch } from "../pipeline/system-identity-switch.js";
 import { buildPersonalDataGate, isPersonalDataGated, parseWriteOrigin, } from "../pipeline/write-origin.js";
 import { bridgeStub } from "../testing/handler-context.js";
+import { cronRepeatOptions } from "./cron-repeat-options.js";
 // Shape-checked after the BullMQ/Redis JSON round-trip. Unlike `_writeOrigin`
 // (a security-relevant escape hatch that must fail the run closed), a
 // malformed `_triggerEvent` only costs an idempotency-key convenience — the
@@ -1154,7 +1155,7 @@ export function createJobRunner(options) {
                 if ("cron" in jobDef.trigger) {
                     const schedulerId = schedulerIdForJobName(name);
                     expectedSchedulerIds.add(schedulerId);
-                    await consumerQueue.upsertJobScheduler(schedulerId, { pattern: jobDef.trigger.cron }, {
+                    await consumerQueue.upsertJobScheduler(schedulerId, cronRepeatOptions(jobDef.trigger), {
                         name: jobDef.perTenant ? `_perTenant:${name}` : name,
                         data: {},
                         // Queue-level defaultJobOptions (jobRetentionOpts) covers

package/dist/pipeline/dispatch-write.js

@@ -8,6 +8,7 @@ import { checkWriteFieldOwnership, maskWriteOnlyFields } from "../engine/field-a
 import { defineTransitions, guardTransition } from "../engine/state-machine.js";
 import { HookPhases } from "../engine/types/index.js";
 import { AccessDeniedError, FrameworkReasons, InternalError, memberResolutionReadOnlyDenied, NotFoundError, ValidationError, writeFailure, } from "../errors/index.js";
+import { bindPendingFileRefs } from "../files/bind-pending-file-refs.js";
 import { CACHE_SYNC_TOPICS } from "../redis/cache-sync-topics.js";
 import { assertNoSecretLeak } from "../secrets/index.js";
 import { buildHandlerContext, CONFIG_WRITE_RESET_TYPE, CONFIG_WRITE_SET_TYPE, isMemberResolutionPrincipal, resolveDbSource, runHandlerInstrumented, TENANT_TIMEZONE_CONFIG_KEY, } from "./dispatch-shared.js";
@@ -111,6 +112,12 @@ async function runLifecycle(ctx, type, data, handlerContext, user, origin, after
     // keeps projection state consistent with what the hooks observe.
     await runProjections(result, handlerContext.registry, runner);
     if (result.kind === "save") {
+        await bindPendingFileRefs({
+            registry: handlerContext.registry,
+            result,
+            user,
+            db: handlerContext.db,
+        });
         await lifecycle.runPostSave(type, result, handlerContext, HookPhases.inTransaction);
         afterCommitHooks.push(async () => {
             const afterCommitContext = await buildHandlerContext(ctx, type, user, origin, undefined, undefined, undefined, true);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cosmicdrift/kumiko-framework",
-  "version": "0.359.0",
+  "version": "0.360.0",
   "description": "Framework core — engine, pipeline, API, DB, and every other bit that makes Kumiko go.",
   "license": "BUSL-1.1",
   "author": "Marc Frost <marc@cosmicdriftgamestudio.com>",
@@ -210,8 +210,8 @@
     "./package.json": "./package.json"
   },
   "dependencies": {
-    "@cosmicdrift/kumiko-http": "0.359.0",
-    "@cosmicdrift/kumiko-types": "0.359.0",
+    "@cosmicdrift/kumiko-http": "0.360.0",
+    "@cosmicdrift/kumiko-types": "0.360.0",
     "bullmq": "^5.76.7",
     "bun-types": "^1.3.13",
     "hono": "^4.13.1",
@@ -227,7 +227,7 @@
     "zod": "^4.4.3"
   },
   "devDependencies": {
-    "@cosmicdrift/kumiko-dispatcher-live": "0.359.0",
+    "@cosmicdrift/kumiko-dispatcher-live": "0.360.0",
     "bun-types": "^1.3.13",
     "pino-pretty": "^13.1.3"
   },

package/src/changes.json

@@ -1,4 +1,49 @@
 [
+  {
+    "version": "0.360.0",
+    "type": "breaking",
+    "title": "Secure host-only session cookies use the __Host- prefix",
+    "detail": "Auth, csrf and tenant cookies are named __Host-kumiko_auth, __Host-kumiko_csrf and __Host-kumiko_tenant when they are written Secure and without a Domain (the tenant cookie is always host-only). With auth.cookieDomain or without Secure the auth and csrf names stay kumiko_auth and kumiko_csrf. New auth option secureCookies forces Secure (default NODE_ENV === \"production\"). Login deletes the legacy unprefixed host-only cookies, logout and deleteTenantCookie delete the prefixed and the legacy names. The server reads only the resolved names, so a request that carries only the legacy kumiko_auth is anonymous. AUTH_COOKIE_NAME, CSRF_COOKIE_NAME and TENANT_COOKIE_NAME are removed from the framework and dispatcher-live; the base names and sessionCookieName() are exported from @cosmicdrift/kumiko-types/session-cookies and @cosmicdrift/kumiko-framework/api, getSessionCookies(c) returns the resolved names of a request. The testing package's CSRF_COOKIE_NAME stays and resolves to the unprefixed name (e2e servers run without Secure).",
+    "migration": "Every user logs in once after the deploy, because the old kumiko_auth cookie is no longer read. Custom clients, proxies or scripts that read or forward the cookies by literal name break: read the names through sessionCookieName() / resolveSessionCookieNames() (types package) or getSessionCookies(c) on the server, and handle both the prefixed and the plain name in browser code (readCsrfToken() already does). Replace imports of AUTH_COOKIE_NAME, CSRF_COOKIE_NAME and TENANT_COOKIE_NAME with AUTH_COOKIE_BASE, CSRF_COOKIE_BASE and TENANT_COOKIE_BASE plus sessionCookieName(); e2e helpers that imported CSRF_COOKIE_NAME from @cosmicdrift/kumiko-dispatcher-live import it from @cosmicdrift/kumiko-testing/e2e instead (known: solon e2e/_helpers/api.ts and e2e/session-ended.spec.ts, kumiko-enterprise ai-agent-live-transcription.integration.test.ts uses AUTH_COOKIE_NAME). A reverse proxy that strips or rewrites cookie names must pass the __Host- names unchanged. Staging or preview deployments over plain http need no change (Secure is off there); set auth.secureCookies (also accepted by runProdApp) explicitly when TLS terminates before the app and NODE_ENV is not \"production\". A standalone createAuthRoutes mount outside buildServer must also mount sessionCookiesMiddleware with the same resolved names, otherwise the readers fall back to the domain-less default."
+  },
+  {
+    "version": "0.360.0",
+    "type": "improvement",
+    "title": "Duplicate session cookie names end the cookie session",
+    "detail": "When the Cookie header carries the resolved auth or csrf cookie name more than once, authMiddleware ignores the cookie transport and expires every variant (prefixed host-only, legacy host-only, the cookieDomain variant and retired domains). With anonymousAccess the request continues as anonymous, otherwise it gets 401 missing_token; a Bearer token on the same request still authenticates. A prefixed and a legacy name side by side are not a duplicate. The cookie clearing moved from the auth routes into clearSessionCookies in session-cookies.ts; ResolvedSessionCookies carries domain and retiredDomains."
+  },
+  {
+    "version": "0.360.0",
+    "type": "breaking",
+    "title": "Origin guard defaults on when the public app URL is known",
+    "detail": "New auth option publicOrigin. Without allowedOrigins, cookieDomain and unsafeSkipOriginCheck, buildServer mounts the Origin guard for cookie-authenticated state-changing /api requests and admits publicOrigin plus the request's own host (Host header). runProdApp sets publicOrigin from auth.publicOrigin, then auth.mail.baseUrl, then the APP_BASE_URL env (origin only, path dropped); with none of them in production it logs a warning that the Origin guard is off and boots anyway. allowedOrigins keeps its strict meaning, and the WebSocket check and the anonymous downgrade still use only allowedOrigins.",
+    "migration": "Cookie-authenticated POST, PUT, PATCH or DELETE requests from a page on another origin than the public app URL and than the API host itself now get 403 origin_not_allowed in runProdApp deployments that set auth.mail.baseUrl or APP_BASE_URL. A web client served from a different host than the API (for example a sibling subdomain) must list its origin in auth.allowedOrigins. Same-host setups, custom domains served by the same server and Bearer clients need no change."
+  },
+  {
+    "version": "0.360.0",
+    "type": "improvement",
+    "title": "createFileRefFromBytes creates FileRefs from handler- or job-produced bytes",
+    "detail": "createFileRefFromBytes({ db, files, registry, user }, { fileName, mimeType, data, attachTo? }) shares one pipeline with POST /api/files, so identifier checks, field-level maxSize/accept, content sniffing, MIME resolution, the tenant-prefixed storage key and the fileRef.created event are identical. The tenant always comes from ctx.user. A rejected file returns a 422 write failure with reason file_rejected and the upload error string in details.error. The FileRef's insertedById is the passed user, so the default access guard lets only that user and privileged roles read files attached to an entity."
+  },
+  {
+    "version": "0.360.0",
+    "type": "improvement",
+    "title": "Cron jobs with an IANA time zone, images fields with capture",
+    "detail": "A cron trigger accepts tz (IANA name; without it the server process zone applies) and is scheduled in that zone, DST included. r.job() throws at boot for an invalid zone. createImagesField accepts capture (\"environment\" | \"user\") like createImageField, and the edit view model carries it for images fields."
+  },
+  {
+    "version": "0.360.0",
+    "type": "breaking",
+    "title": "Uploads from an update form are attached to the record",
+    "detail": "computeEditViewModel accepts entityId (the record being edited, update mode only) and sets it on the hints of file, image, files and images fields; RenderEdit passes the id it was mounted with and the file input sends it as the entityId multipart part of POST /api/files. Create forms send no entityId; after a successful create the write pipeline binds the caller's own pending uploads named in the record's file fields (same entityType and fieldName, entityId null, insertedById = caller) to the new record via a fileRef.updated event in the same transaction, for single and plural file fields alike, when the files feature (fileRef entity) is mounted. Behaviour change: such files are now attached to the record. The default file access guard allows read on an attached file to the uploader, privilegedRoles (default Admin/SystemAdmin) and everyone whose run of the entity's <entity>:detail query returns the record; delete stays uploader and privilegedRoles only. A qr-overlay variant of an image field no longer throws for a file uploaded from an update or create form. Write-form sections send no entityId. EmbeddedListInput has a new required actionsLabel prop.",
+    "migration": "Files attached through forms now follow the record's read access instead of being tenant-wide: anyone who cannot read the record no longer reads the file, anyone who can read it does. Check image, images, file and files fields whose files must be visible beyond the record's readers (for example an avatar shown in lists to users without detail access) and add those roles to privilegedRoles or set accessGuard in the files feature options. An entity without a detail query falls back to uploader plus privilegedRoles. Files uploaded before the update keep their old attachment. Custom primitive sets that implement EmbeddedListInput accept the new actionsLabel prop and render it as the actions column header; custom file/image Input primitives forward entityId into the upload and offer a remove control that calls onChange(null)."
+  },
+  {
+    "version": "0.360.0",
+    "type": "improvement",
+    "title": "images and files fields get an edit widget; required is allowed",
+    "detail": "NO_WIDGET_FIELD_TYPES now holds only jsonb and embedded. required true on an images or files field passes boot validation and the client-side check treats an empty array as missing. The edit view model carries maxCount for files and images fields."
+  },
   {
     "version": "0.359.0",
     "type": "improvement",