@lenne.tech/nest-server 11.35.0 → 11.36.0

package/src/core/modules/better-auth/core-better-auth.controller.ts

@@ -24,6 +24,7 @@ import {
   ApiProperty,
   ApiTags,
 } from '@nestjs/swagger';
+import { IsBoolean, IsEmail, IsNotEmpty, IsOptional, IsString } from 'class-validator';
 import { Request, Response } from 'express';
 
 import { Roles } from '../../common/decorators/roles.decorator';
@@ -122,10 +123,18 @@ export class CoreBetterAuthResponse {
  * Sign-in input DTO
  */
 export class CoreBetterAuthSignInInput {
+  // Validated, not merely documented. Without these the sign-in endpoint — the
+  // most-probed surface of any deployment — answered malformed input with a
+  // 500 from the first property read, which tells a client to retry something
+  // that can never work and buries real faults in the same bucket.
   @ApiProperty({ description: 'User email address', example: 'user@example.com' })
+  @IsNotEmpty()
+  @IsEmail()
   email: string;
 
   @ApiProperty({ description: 'User password' })
+  @IsNotEmpty()
+  @IsString()
   password: string;
 }
 
@@ -134,15 +143,30 @@ export class CoreBetterAuthSignInInput {
  */
 export class CoreBetterAuthSignUpInput {
   @ApiProperty({ description: 'User email address', example: 'user@example.com' })
+  @IsNotEmpty()
+  @IsEmail()
   email: string;
 
   @ApiProperty({ description: 'Display name', example: 'John Doe', required: false })
+  @IsOptional()
+  @IsString()
   name?: string;
 
   @ApiProperty({ description: 'User password (min 8 characters)' })
+  @IsNotEmpty()
+  @IsString()
   password: string;
 
+  // Deliberately left without a validator, unlike its three neighbours. Whether this field is
+  // REQUIRED is a policy question the framework cannot answer here — it depends on
+  // `betterAuth.signUpValidation`, which the handler consults through
+  // CoreBetterAuthSignUpValidatorService before anything else happens. A `@IsNotEmpty()` here would
+  // hard-code "consent is mandatory" into the DTO and reject a sign-up for a deployment that never
+  // asked for consent, with a message that names the wrong cause. The others carry validators
+  // because "an email must look like an email" needs no policy.
   @ApiProperty({ description: 'Whether user accepted terms and privacy policy', required: false })
+  @IsBoolean()
+  @IsOptional()
   termsAndPrivacyAccepted?: boolean;
 }
 
@@ -329,6 +353,15 @@ export class CoreBetterAuthController {
   ): Promise<CoreBetterAuthResponse> {
     this.ensureEnabled();
 
+    // A request with no body at all reaches here as `undefined`, and every line
+    // below reads `input.email`. Without this the caller gets a 500 for what is
+    // plainly their own malformed request — and a 500 tells a client to retry
+    // later, which will never help. The legacy sign-in answered this case with
+    // a 400 "Missing input"; keep that contract.
+    if (!input) {
+      throw new BadRequestException('Missing input');
+    }
+
     const api = this.betterAuthService.getApi();
     if (!api) {
       throw new BadRequestException(ErrorCode.BETTERAUTH_API_NOT_AVAILABLE);
@@ -494,6 +527,11 @@ export class CoreBetterAuthController {
     this.ensureEnabled();
     this.betterAuthService.ensureSignUpEnabled();
 
+    // Same reasoning as in signIn: a body-less request must not become a 500.
+    if (!input) {
+      throw new BadRequestException('Missing input');
+    }
+
     // Validate sign-up input (termsAndPrivacyAccepted is required by default)
     if (this.signUpValidator) {
       this.signUpValidator.validateSignUpInput({ termsAndPrivacyAccepted: input.termsAndPrivacyAccepted });

package/src/core/modules/file/README.md

@@ -346,6 +346,16 @@ override async getFileById(@Param('id') id: string, @Res() res: Response) {
 A class-level `@Roles()` on your subclass cannot relax an inherited member either: the inherited
 function carries its own handler-level roles, and the two are unioned rather than overridden.
 
+> **Boot reports this, since 11.35.1 — but it only reports.** `CoreFileAccessAuditInitializer` reads
+> the roles off the class you actually registered and warns when a member is open beyond platform
+> admins for a reason the configuration cannot explain. So a subclass whose `getFileById()` carries
+> `@Roles(RoleEnum.S_EVERYONE)` is now named at startup, with the member and the offending roles.
+>
+> It does **not** correct anything: your `@Roles()` still wins, because overwriting it would silently
+> relax a route you may have pinned on purpose. **If you re-declare a download member, its `@Roles()`
+> is your whole audience gate** — the warning tells you so, it does not close it for you. Inherit the
+> member instead if you want `file.downloadRoles` to govern it.
+
 ### If you override `getFileInfo()`: `GET /files/id/:id` no longer calls it (11.33.0)
 
 Up to 11.32.x, `GET /files/id/:id` called the public `CoreFileService.getFileInfo()` and then let

package/src/core/modules/file/core-file-access-audit.initializer.ts

@@ -0,0 +1,164 @@
+import { Injectable, Logger, OnApplicationBootstrap, Optional } from '@nestjs/common';
+import { DiscoveryService } from '@nestjs/core';
+
+import { ConfigService } from '../../common/services/config.service';
+import { CoreFileController } from './core-file.controller';
+import { CoreFileResolver } from './core-file.resolver';
+import { CoreFileService } from './core-file.service';
+import {
+  FILE_ROLE_MEMBERS,
+  FileEndpointClassName,
+  ObservedFileHandler,
+  warnOnUndecidedEffectiveFileAccess,
+} from './file-roles.config';
+
+/**
+ * Audits the file endpoints a project ACTUALLY registered, and warns when one of them is open beyond
+ * platform admins for a reason the configuration cannot show.
+ *
+ * WHY THIS CANNOT LIVE WHERE THE OTHER FILE WARNINGS LIVE
+ * -------------------------------------------------------
+ * `warnOnUndecidedFileAccess()` runs in the `CoreFileService` constructor and reads CONFIGURATION.
+ * For an inherited member that is exactly right: `applyFileRoles()` writes the configured roles onto
+ * the base-class function, the subclass picks them up through the prototype chain, and configuration
+ * and reality agree.
+ *
+ * They stop agreeing when a project RE-DECLARES a member. Decorator metadata lives on the function
+ * object, so an override is a different function carrying its own `@Roles()` — and that is the
+ * function Nest registers. Answering "is the gate open?" from configuration then answers a question
+ * about a route that is not the one being served. Two consumer projects shipped anonymously readable
+ * downloads that way, and nothing said a word.
+ *
+ * Seeing the real answer needs the registered class, and the registered class only exists once Nest
+ * has built its route table. Neither the service constructor nor `CoreModule.forRoot()` — which runs
+ * before any of that — can reach it. Hence a provider, and hence `onApplicationBootstrap`.
+ *
+ * WHY DISCOVERY RATHER THAN A CONFIG OPTION
+ * ------------------------------------------
+ * The file module ships abstract classes only: there is no `CoreFileModule.forRoot()` to hand a class
+ * to, and a class reference cannot travel through `config.env.ts` (it has to survive
+ * `NEST_SERVER_CONFIG` / `NSC__*`, i.e. JSON). Asking every consumer to register their controller in
+ * a second place would also make the audit opt-in — and an opt-in audit is missing precisely where
+ * nobody thought about access control, which is the population it exists for.
+ *
+ * WARNING ONLY. It never changes a role, and deliberately so: rewriting an override's metadata would
+ * silently relax a route the project pinned on purpose, which is the trap that rules out adopting the
+ * TUS module's approach here. The audit reports; the project decides.
+ *
+ * Registered as a `CoreModule` provider; consumers never interact with it.
+ */
+@Injectable()
+export class CoreFileAccessAuditInitializer implements OnApplicationBootstrap {
+  protected readonly logger = new Logger(CoreFileAccessAuditInitializer.name);
+
+  constructor(@Optional() protected readonly discoveryService?: DiscoveryService) {}
+
+  onApplicationBootstrap(): void {
+    if (!this.discoveryService) {
+      return;
+    }
+
+    const handlers = this.collectHandlers();
+    // No file endpoint registered — there is no route to be wrong about, and the configuration-side
+    // warning in the service constructor already covers a service-only integration.
+    if (!handlers.length) {
+      return;
+    }
+
+    const config = ConfigService.configFastButReadOnly;
+    warnOnUndecidedEffectiveFileAccess({
+      fileConfig: config?.file,
+      handlers,
+      hasPerFileRule: this.hasPerFileRule(),
+      multiTenancyEnabled: !!config?.multiTenancy && config.multiTenancy.enabled !== false,
+    });
+  }
+
+  /**
+   * The effective roles of every known member on every registered file endpoint class.
+   *
+   * `proto[method]` resolves through the prototype chain, so it yields the OVERRIDE when there is one
+   * and the inherited base function otherwise — which is exactly the function Nest registered.
+   */
+  protected collectHandlers(): ObservedFileHandler[] {
+    const handlers: ObservedFileHandler[] = [];
+
+    for (const [className, target] of this.registeredEndpointClasses()) {
+      for (const member of FILE_ROLE_MEMBERS) {
+        if (member.className !== className) {
+          continue;
+        }
+
+        const fn = (target.prototype as Record<string, unknown>)?.[member.method];
+        if (typeof fn !== 'function') {
+          continue;
+        }
+
+        handlers.push({
+          key: member.key,
+          member: `${target.name}.${member.method}`,
+          roles: this.effectiveRoles(fn, target),
+        });
+      }
+    }
+
+    return handlers;
+  }
+
+  /**
+   * The union the guards will compute for a member.
+   *
+   * Mirrors `mergeRolesMetadata([handlerRoles, classRoles])`: both halves count, so a class-level
+   * `@Roles()` on the subclass is seen too. `Reflect.getMetadata` walks the prototype chain for the
+   * class, which is what makes an undecorated subclass inherit the core `@Roles(ADMIN)` — the same
+   * resolution Nest's `Reflector` performs.
+   */
+  protected effectiveRoles(fn: unknown, target: Function): string[] {
+    const handlerRoles: string[] = Reflect.getMetadata('roles', fn as object) ?? [];
+    const classRoles: string[] = Reflect.getMetadata('roles', target) ?? [];
+    return [...handlerRoles, ...classRoles];
+  }
+
+  /** Whether the registered `CoreFileService` overrides `checkRights()` — the project wrote a rule. */
+  protected hasPerFileRule(): boolean {
+    const services = (this.discoveryService?.getProviders() ?? [])
+      .map((wrapper) => wrapper.instance)
+      .filter((instance): instance is CoreFileService => instance instanceof CoreFileService);
+
+    return services.some((service) => (service as any).checkRights !== (CoreFileService.prototype as any).checkRights);
+  }
+
+  /**
+   * Every registered class that IS one of the two file endpoint classes, deduplicated.
+   *
+   * Read off the instance rather than the wrapper's `metatype`, because that is the object whose
+   * prototype chain answers the `instanceof` question reliably for both controllers and providers.
+   */
+  protected registeredEndpointClasses(): [FileEndpointClassName, Function][] {
+    const found = new Map<Function, FileEndpointClassName>();
+
+    const consider = (instance: unknown): void => {
+      if (!instance || typeof instance !== 'object') {
+        return;
+      }
+      const target = (instance as object).constructor;
+      if (typeof target !== 'function' || found.has(target)) {
+        return;
+      }
+      if (instance instanceof CoreFileController) {
+        found.set(target, 'CoreFileController');
+      } else if (instance instanceof CoreFileResolver) {
+        found.set(target, 'CoreFileResolver');
+      }
+    };
+
+    for (const wrapper of this.discoveryService?.getControllers() ?? []) {
+      consider(wrapper.instance);
+    }
+    for (const wrapper of this.discoveryService?.getProviders() ?? []) {
+      consider(wrapper.instance);
+    }
+
+    return [...found].map(([target, className]) => [className, target]);
+  }
+}

package/src/core/modules/file/file-roles.config.ts

@@ -36,6 +36,31 @@ export const FILE_ROLE_DEFAULTS: Record<FileRoleKey, string[]> = {
   uploadRoles: [RoleEnum.ADMIN],
 };
 
+/**
+ * Which endpoint member each knob governs, by NAME only.
+ *
+ * Deliberately strings rather than function references: this file must stay a leaf that imports
+ * nothing but enums and interfaces (see the header), and both consumers need the same list —
+ * `applyFileRoles()` writes metadata onto these members, and the boot audit reads it back off
+ * whichever class the project actually registered. Two hand-maintained copies of that list is
+ * exactly how one of them ends up governing a member the other forgot.
+ *
+ * `getFileInfo` rides with `downloadRoles` rather than getting its own knob: it answers filename,
+ * size and content type for a blob, which is the metadata half of a download. Splitting it would let
+ * a project accidentally publish the bucket's contents list while believing downloads were closed.
+ */
+export const FILE_ROLE_MEMBERS: { className: FileEndpointClassName; key: FileRoleKey; method: string }[] = [
+  { className: 'CoreFileController', key: 'downloadRoles', method: 'getFileById' },
+  { className: 'CoreFileController', key: 'downloadRoles', method: 'getFile' },
+  { className: 'CoreFileResolver', key: 'downloadRoles', method: 'getFileInfo' },
+  { className: 'CoreFileResolver', key: 'uploadRoles', method: 'uploadFile' },
+  { className: 'CoreFileResolver', key: 'uploadRoles', method: 'uploadFiles' },
+  { className: 'CoreFileResolver', key: 'deleteRoles', method: 'deleteFile' },
+];
+
+/** The two core endpoint classes the role knobs govern. */
+export type FileEndpointClassName = 'CoreFileController' | 'CoreFileResolver';
+
 /**
  * Resolve one knob to the role list that will actually be applied.
  *
@@ -62,6 +87,21 @@ export function resolveRoles(key: FileRoleKey, config?: IFileConfig): string[] {
   return configured;
 }
 
+/**
+ * Did somebody DECLARE the per-file policy?
+ *
+ * Shared by both file-access warnings on purpose. They must silence on exactly the same conditions,
+ * and two copies of that rule is how a third silencer gets added to one and forgotten in the other —
+ * at which point the boot audit starts firing on a project that did decide, gets muted, and protects
+ * nobody. Keeping it in one place makes that particular drift impossible rather than merely unlikely.
+ *
+ * `'custom'` does not count: it is the escape hatch that says "I will answer this in code", so the
+ * only evidence that somebody actually did is an overridden `checkRights()`.
+ */
+export function hasDeclaredFilePolicy(options: { fileConfig?: IFileConfig; hasPerFileRule: boolean }): boolean {
+  return options.hasPerFileRule || !!(options.fileConfig?.access && options.fileConfig.access !== 'custom');
+}
+
 /**
  * Warn when presigned S3 downloads are combined with a restricted `downloadRoles`.
  *
@@ -152,6 +192,15 @@ export function warnOnPresignedDownloadsWithRestrictedRoles(
  * public logos, and refusing to start on a configuration that is correct for the second would be
  * wrong. What it can do is refuse to be silent.
  *
+ * SCOPE — this function reads CONFIGURATION, which is the right source for a member the project
+ * INHERITS: `applyFileRoles()` writes the configured roles onto the base-class function, the subclass
+ * picks them up through the prototype chain, and config and reality agree. It says nothing about a
+ * member the project RE-DECLARES, because an override is a different function carrying its own
+ * `@Roles()` and the configuration never reaches that route. That half is covered by
+ * {@link warnOnUndecidedEffectiveFileAccess}, driven from `CoreFileAccessAuditInitializer` at
+ * bootstrap — the earliest point at which the registered class exists. The two do not overlap: the
+ * audit reports only roles this function's source cannot account for.
+ *
  * @param hasPerFileRule whether `CoreFileService.checkRights()` is overridden — the caller knows,
  *   because it has the instance; this helper stays a pure function so it can be unit-tested.
  * @returns the message, or `undefined` when there is nothing to warn about. Returned as well as
@@ -166,7 +215,7 @@ export function warnOnUndecidedFileAccess(options: {
   const { fileConfig, hasPerFileRule, multiTenancyEnabled } = options;
 
   // (1) and (2): somebody decided.
-  if (hasPerFileRule || (fileConfig?.access && fileConfig.access !== 'custom')) {
+  if (hasDeclaredFilePolicy({ fileConfig, hasPerFileRule })) {
     return undefined;
   }
 
@@ -200,3 +249,109 @@ export function warnOnUndecidedFileAccess(options: {
   logger.warn(message);
   return message;
 }
+
+/**
+ * One registered endpoint member, as the GUARDS will see it.
+ *
+ * `roles` is the union of handler-level and class-level metadata, because that is what
+ * `mergeRolesMetadata` computes — not the handler alone. A subclass that carries a class-level
+ * `@Roles(S_EVERYONE)` widens every member it declares, and reading only the handler would miss it.
+ */
+export interface ObservedFileHandler {
+  /** which knob governs this member */
+  key: FileRoleKey;
+  /** `'FileController.getFileById'` — named as REGISTERED, so the operator can go straight to it */
+  member: string;
+  /** the effective role union the guards will evaluate */
+  roles: string[];
+}
+
+/**
+ * Warn when a REGISTERED file endpoint is open beyond platform admins for a reason the configuration
+ * does not explain — i.e. a `@Roles()` written in the project's own subclass.
+ *
+ * WHY THIS EXISTS SEPARATELY FROM {@link warnOnUndecidedFileAccess}. That one reads CONFIGURATION,
+ * which is the right source for the inherited case: `applyFileRoles()` writes the configured roles
+ * onto the base-class member, an inheriting subclass picks them up through the prototype chain, and
+ * config and reality agree. They stop agreeing the moment a project RE-DECLARES a member. Decorator
+ * metadata lives on the function object, so an override is a different function carrying its own
+ * roles — and that is the function Nest registers. The configuration never reaches the route.
+ *
+ * The consequence was a silence exactly where the noise was wanted: a subclassed `getFileById()` with
+ * `@Roles(RoleEnum.S_EVERYONE)` serves anonymous downloads while `resolveRoles('downloadRoles', …)`
+ * still answers `[ADMIN]`. Two independent consumer projects shipped that, and in both the actually
+ * open routes were the ones nothing reported. A warning that is quiet in the dangerous case and loud
+ * in the safe one is worse than no warning, because it reads as a clean bill of health.
+ *
+ * WHAT IT REPORTS — only roles the configuration does not account for:
+ *
+ *   effective = union(handler roles, class roles)      // what mergeRolesMetadata gives the guard
+ *   unexplained = effective − {ADMIN} − configured(key)
+ *
+ * That subtraction is what keeps this from double-warning. When the widening came from
+ * `file.downloadRoles`, {@link warnOnUndecidedFileAccess} has already said so and `unexplained` is
+ * empty. When an override widens FURTHER than the configuration does, only the extra roles are
+ * named — the part that is genuinely invisible elsewhere.
+ *
+ * ADMIN is subtracted because both endpoint classes carry a class-level `@Roles(ADMIN)` that the
+ * guards union in unconditionally. It is present on every member and never widens anything.
+ *
+ * The silencers are deliberately identical to {@link warnOnUndecidedFileAccess} — an overridden
+ * `checkRights()` or a declared `file.access` means somebody decided, and how they decided is beyond
+ * what a boot check can grade. A warning that fires on a correct setup gets muted, and a muted
+ * warning protects nobody.
+ *
+ * @returns the message, or `undefined` when there is nothing to report. Returned as well as logged
+ *   for the same reason as the other two warnings: the message IS the contract, and a module-private
+ *   Logger cannot be asserted against from a unit test.
+ */
+export function warnOnUndecidedEffectiveFileAccess(options: {
+  fileConfig?: IFileConfig;
+  handlers: ObservedFileHandler[];
+  hasPerFileRule: boolean;
+  multiTenancyEnabled: boolean;
+}): string | undefined {
+  const { fileConfig, handlers, hasPerFileRule, multiTenancyEnabled } = options;
+
+  // Somebody decided. The SAME predicate the configuration-side warning uses — see
+  // hasDeclaredFilePolicy() for why this must not be a second copy of the rule.
+  if (hasDeclaredFilePolicy({ fileConfig, hasPerFileRule })) {
+    return undefined;
+  }
+
+  const findings: string[] = [];
+  for (const handler of handlers) {
+    const configured = resolveRoles(handler.key, fileConfig);
+    const unexplained = handler.roles.filter((role) => role !== RoleEnum.ADMIN && !configured.includes(role));
+    if (unexplained.length) {
+      findings.push(`${handler.member} → ${JSON.stringify([...new Set(unexplained)])}`);
+    }
+  }
+
+  if (!findings.length) {
+    return undefined;
+  }
+
+  const tenantNote = multiTenancyEnabled
+    ? ' multiTenancy is active, and the leak crosses tenants too: the file stores are reached outside ' +
+      'Mongoose, so mongooseTenantPlugin never scopes them and these role names resolve against ' +
+      'user.roles — a GLOBAL attribute — never against membership.role.'
+    : '';
+
+  const message =
+    `A registered file endpoint is open beyond platform admins through roles declared in your own ` +
+    `class, not through configuration (${findings.join(', ')}), and no per-file policy is declared: ` +
+    `file.access is unset and CoreFileService.checkRights() is not overridden. Because the member is ` +
+    `RE-DECLARED, file.downloadRoles/uploadRoles/deleteRoles do NOT apply to it — decorator metadata ` +
+    `lives on the function object, so your override keeps its own @Roles() and the configuration ` +
+    `never reaches the route. Every holder of such a role can therefore read, overwrite or delete ` +
+    `EVERY file — and file ids are not secret, they are ENUMERABLE (an ObjectId shares a per-process ` +
+    `random part and an incrementing counter, so one own upload reveals the neighbourhood), with no ` +
+    `rate limit on the file routes.${tenantNote} Either inherit the member instead of re-declaring ` +
+    `it, so the knobs apply, or declare the per-file policy with file.access ` +
+    `('public' | 'authenticated' | 'owner' | 'tenant') or an overridden checkRights() — see ` +
+    `src/core/modules/file/README.md § Access control.`;
+
+  logger.warn(message);
+  return message;
+}

package/src/core/modules/file/file-roles.helper.ts

@@ -3,7 +3,7 @@ import { Logger } from '@nestjs/common';
 import { IFileConfig } from '../../common/interfaces/server-options.interface';
 import { CoreFileController } from './core-file.controller';
 import { CoreFileResolver } from './core-file.resolver';
-import { FileRoleKey, resolveRoles } from './file-roles.config';
+import { FILE_ROLE_MEMBERS, FileEndpointClassName, FileRoleKey, resolveRoles } from './file-roles.config';
 
 const logger = new Logger('CoreFileRoles');
 
@@ -12,32 +12,25 @@ const logger = new Logger('CoreFileRoles');
 // imports the endpoint classes, which inject CoreFileService — see file-roles.config.ts.
 export {
   FILE_ROLE_DEFAULTS,
+  FILE_ROLE_MEMBERS,
   resolveRoles,
   warnOnPresignedDownloadsWithRestrictedRoles,
+  warnOnUndecidedEffectiveFileAccess,
   warnOnUndecidedFileAccess,
 } from './file-roles.config';
-export type { FileRoleKey } from './file-roles.config';
+export type { FileEndpointClassName, FileRoleKey, ObservedFileHandler } from './file-roles.config';
 
 /**
- * Which member is governed by which knob.
+ * The prototypes the member names in {@link FILE_ROLE_MEMBERS} resolve against.
  *
- * `getFileInfo` rides with `downloadRoles` rather than getting its own knob:
- * it answers filename, size and content type for a blob, which is the metadata
- * half of a download. Splitting it would let a project accidentally publish the
- * bucket's contents list while believing downloads were still closed.
+ * The NAMES live in `file-roles.config.ts` so the boot audit can share them without importing these
+ * classes (that import is what makes this file a non-leaf — see the header of `file-roles.config.ts`
+ * for the temporal-dead-zone crash it caused). Only the class lookup lives here.
  */
-const ROLE_TARGETS: { key: FileRoleKey; member: string; owner: () => unknown }[] = [
-  {
-    key: 'downloadRoles',
-    member: 'CoreFileController.getFileById',
-    owner: () => CoreFileController.prototype.getFileById,
-  },
-  { key: 'downloadRoles', member: 'CoreFileController.getFile', owner: () => CoreFileController.prototype.getFile },
-  { key: 'downloadRoles', member: 'CoreFileResolver.getFileInfo', owner: () => CoreFileResolver.prototype.getFileInfo },
-  { key: 'uploadRoles', member: 'CoreFileResolver.uploadFile', owner: () => CoreFileResolver.prototype.uploadFile },
-  { key: 'uploadRoles', member: 'CoreFileResolver.uploadFiles', owner: () => CoreFileResolver.prototype.uploadFiles },
-  { key: 'deleteRoles', member: 'CoreFileResolver.deleteFile', owner: () => CoreFileResolver.prototype.deleteFile },
-];
+const ENDPOINT_PROTOTYPES: Record<FileEndpointClassName, unknown> = {
+  CoreFileController: CoreFileController.prototype,
+  CoreFileResolver: CoreFileResolver.prototype,
+};
 
 /**
  * Apply the configured file roles to the core file endpoints.
@@ -65,14 +58,14 @@ const ROLE_TARGETS: { key: FileRoleKey; member: string; owner: () => unknown }[]
 export function applyFileRoles(config?: IFileConfig): void {
   const resolved = new Map<FileRoleKey, string[]>();
 
-  for (const { key, member, owner } of ROLE_TARGETS) {
+  for (const { className, key, method } of FILE_ROLE_MEMBERS) {
     if (!resolved.has(key)) {
       resolved.set(key, resolveRoles(key, config));
     }
 
-    const target = owner();
+    const target = (ENDPOINT_PROTOTYPES[className] as Record<string, unknown>)[method];
     if (typeof target !== 'function') {
-      logger.warn(`Cannot apply file.${key}: ${member} is not a function — skipping.`);
+      logger.warn(`Cannot apply file.${key}: ${className}.${method} is not a function — skipping.`);
       continue;
     }
 

package/src/core.module.ts

@@ -1,6 +1,6 @@
 import { ApolloDriver, ApolloDriverConfig } from '@nestjs/apollo';
 import { DynamicModule, Global, MiddlewareConsumer, Module, NestModule, UnauthorizedException } from '@nestjs/common';
-import { APP_INTERCEPTOR, APP_PIPE } from '@nestjs/core';
+import { APP_INTERCEPTOR, APP_PIPE, DiscoveryModule } from '@nestjs/core';
 import { GraphQLModule } from '@nestjs/graphql';
 import { MongooseModule } from '@nestjs/mongoose';
 import type { Context } from 'graphql-ws';
@@ -51,6 +51,7 @@ import { CoreBetterAuthUserMapper } from './core/modules/better-auth/core-better
 import { CoreBetterAuthModule } from './core/modules/better-auth/core-better-auth.module';
 import { CoreBetterAuthService } from './core/modules/better-auth/core-better-auth.service';
 import { ErrorCodeModule } from './core/modules/error-code/error-code.module';
+import { CoreFileAccessAuditInitializer } from './core/modules/file/core-file-access-audit.initializer';
 import { applyFileRoles, warnOnPresignedDownloadsWithRestrictedRoles } from './core/modules/file/file-roles.helper';
 import { CoreHealthCheckModule } from './core/modules/health-check/core-health-check.module';
 import { CoreHubModule } from './core/modules/hub/core-hub.module';
@@ -305,6 +306,11 @@ export class CoreModule implements NestModule {
 
       // Core Services
       CoreCronJobsInitializer,
+      // Audits the file endpoints the project actually REGISTERED. applyFileRoles() above can only
+      // reach the base-class members; a subclass that re-declares one keeps its own @Roles() and the
+      // configuration never reaches that route. Only a bootstrap-time look at the registered class
+      // can tell those apart — see the initializer.
+      CoreFileAccessAuditInitializer,
       CoreRedisService,
       CoreS3Service,
       CoreTrustProxyInitializer,
@@ -381,7 +387,9 @@ export class CoreModule implements NestModule {
       }
     }
 
-    const imports: any[] = [MongooseModule.forRoot(config.mongoose.uri, config.mongoose.options)];
+    // DiscoveryModule: CoreFileAccessAuditInitializer needs the registered controller/resolver
+    // classes, which only exist once Nest has built its route table.
+    const imports: any[] = [DiscoveryModule, MongooseModule.forRoot(config.mongoose.uri, config.mongoose.options)];
 
     if (isGraphQlEnabled && config.graphQl) {
       imports.push(

package/src/index.ts

@@ -36,9 +36,11 @@ export * from './core/common/helpers/cookies.helper';
 export * from './core/common/helpers/graceful-shutdown.helper';
 export * from './core/common/helpers/db.helper';
 export * from './core/common/helpers/decorator.helper';
+export * from './core/common/helpers/execution-context-request.helper';
 export * from './core/common/helpers/file.helper';
 export * from './core/common/helpers/filter.helper';
 export * from './core/common/helpers/graphql.helper';
+export * from './core/common/helpers/graphql-ws-context.helper';
 export * from './core/common/helpers/interceptor.helper';
 export * from './core/common/helpers/gridfs.helper';
 export * from './core/common/helpers/input.helper';
@@ -94,6 +96,7 @@ export * from './core/common/services/core-cron-jobs.service';
 export * from './core/common/services/core-redis.service';
 export * from './core/common/services/core-redis-pubsub';
 export * from './core/common/services/core-s3.service';
+export * from './core/common/services/core-tenant-context.registry';
 export * from './core/common/services/rate-limit-store';
 export * from './core/common/services/crud.service';
 export * from './core/common/services/email.service';
@@ -173,6 +176,7 @@ export * from './core/modules/error-code';
 // Core - Modules - File
 // =====================================================================================================================
 
+export * from './core/modules/file/core-file-access-audit.initializer';
 export * from './core/modules/file/core-file-info.model';
 export * from './core/modules/file/core-file.controller';
 export * from './core/modules/file/core-file.resolver';