@bleedingdev/modern-js-bff-core 3.5.0-ultramodern.3 → 3.5.0-ultramodern.31

package/dist/types/adapter-kit/parity-scenarios/schema.d.ts

@@ -0,0 +1,2 @@
+import type { AdapterParityScenario } from './shared';
+export declare const createSchemaParityScenarios: () => AdapterParityScenario[];

package/dist/types/adapter-kit/parity-scenarios/shared.d.ts

@@ -0,0 +1,32 @@
+import type { CrossProjectOperationContract, CrossProjectPolicyViolationReason } from '../../security/crossProjectPolicy';
+export declare const PARITY_REQUEST_ID = "crm";
+export declare const PARITY_PRODUCER_REQUEST_ID = "crm.producer-a";
+export type ParityExpectation = {
+    kind: 'payload';
+    status: number;
+    payload: unknown;
+} | {
+    kind: 'denied';
+    status: number;
+    reason: CrossProjectPolicyViolationReason;
+};
+export type AdapterParityScenario = {
+    name: string;
+    /** Run against policy-enabled server instead of the open one. */
+    policy: boolean;
+    request: {
+        method: 'get' | 'post' | 'patch';
+        path: string;
+        headers?: Record<string, string>;
+        body?: unknown;
+    };
+    expected: ParityExpectation;
+};
+export type AdapterParityScenarioContext = {
+    helloContract: CrossProjectOperationContract;
+    validEnvelope: string;
+    validOperationId: string;
+};
+export declare const envelopeHeader: (requestId: unknown) => string;
+export declare const detailHeader: (details: Record<string, unknown>) => string;
+export declare const deniedScenario: (name: string, reason: CrossProjectPolicyViolationReason, headers: Record<string, string>) => AdapterParityScenario;

package/dist/types/adapter-kit/parity.d.ts

@@ -1,45 +1,14 @@
 import type { APIHandlerInfo } from '../router';
-import type { CrossProjectPolicyViolationReason } from '../security/crossProjectPolicy';
-/**
- * Adapter parity (conformance) kit.
- *
- * One shared table of scenarios executed against every BFF server adapter
- * in its own test harness. Each scenario asserts the adapters produce
- * identical observable results: HTTP status, payload value and
- * policy-rejection reason.
- *
- * The express/koa adapters were removed from the fork, and this is internal
- * test support rather than a package subpath. Their expectations are retained
- * in the per-adapter drift pins as documentation of the historical behavior.
- * The live executable consumer of this table is the hono lane test
- * (`@modern-js/plugin-bff` runs it against `createHonoRoutes` plus the
- * cross-project policy middleware), while bff-core tests validate the table
- * shape and assertion helpers.
- *
- * Transport details intentionally NOT asserted: express serialized scalar
- * bodies as JSON while koa sent `text/plain`; {@link toParityResult}
- * normalizes both to the decoded payload value before comparison.
- *
- * Intentionally OUT OF SCOPE (known, accepted adapter drift — do not add
- * scenarios without deciding the drift first):
- * - operator route-middlewares: express applied them, koa ignored them;
- * - multipart/form-data: payload shapes differ per body parser;
- * - undefined-returning plain handlers are pinned via a per-adapter
- *   scenario below: express ended the response 200/empty, koa served its
- *   stock 404 ("Not Found"), hono serves its stock "404 Not Found";
- * - farrow schema-mode handlers are pinned per-adapter below: express/koa
- *   unwrapped the result envelope (200/400/500), the hono lane has no
- *   schema-mode unwrapping and passes the raw envelope through.
- */
-export declare const PARITY_REQUEST_ID = "crm";
-export declare const PARITY_PRODUCER_REQUEST_ID = "crm.producer-a";
+import type { AdapterParityScenario } from './parity-scenarios/shared';
+export type { AdapterParityScenario, ParityExpectation, } from './parity-scenarios/shared';
+export { PARITY_PRODUCER_REQUEST_ID, PARITY_REQUEST_ID, } from './parity-scenarios/shared';
 /**
  * Handler fixtures registered in both adapters before running the table.
  */
 export declare const createParityApiHandlerInfos: () => APIHandlerInfo[];
 /**
- * `bff` config slice for the policy-enabled parity server. All `require*`
- * switches stay at their strict defaults.
+ * `bff` config slice for policy-enabled parity server. All `require*`
+ * switches stay at strict defaults.
  */
 export declare const createParityBffConfig: () => {
     requestId: string;
@@ -48,37 +17,8 @@ export declare const createParityBffConfig: () => {
         allowedNamespaces: string[];
     };
 };
-export type ParityAdapterId = 'express' | 'koa' | 'hono';
-export type ParityExpectation = {
-    kind: 'payload';
-    status: number;
-    payload: unknown;
-} | {
-    kind: 'denied';
-    status: number;
-    reason: CrossProjectPolicyViolationReason;
-} | {
-    /** Pinned, intentional adapter drift: each adapter has its own expectation. */
-    kind: 'perAdapter';
-    expectations: Record<ParityAdapterId, {
-        status: number;
-        payload: unknown;
-    }>;
-};
-export type AdapterParityScenario = {
-    name: string;
-    /** Run against the policy-enabled server instead of the open one. */
-    policy: boolean;
-    request: {
-        method: 'get' | 'post' | 'patch';
-        path: string;
-        headers?: Record<string, string>;
-        body?: unknown;
-    };
-    expected: ParityExpectation;
-};
 export declare const createAdapterParityScenarios: () => AdapterParityScenario[];
-/** Structural slice of a supertest response used for normalization. */
+/** Structural slice of supertest response used for normalization. */
 export type ParityHttpResponse = {
     status: number;
     /** Content-type mime, e.g. `application/json`. */
@@ -91,12 +31,12 @@ export type AdapterParityResult = {
     payload: unknown;
 };
 /**
- * Normalizes a raw HTTP response to the observable payload value so JSON
- * (express) and text (koa) encodings of the same scalar compare equal.
+ * Normalizes raw HTTP response into an observable payload value so JSON and
+ * text encodings of the same scalar compare equal.
  */
 export declare const toParityResult: (res: ParityHttpResponse) => AdapterParityResult;
 /**
- * Framework-agnostic assertion: throws a descriptive error when the adapter
+ * Framework-agnostic assertion: throws a descriptive error when adapter
  * response deviates from the scenario expectation.
  */
-export declare const assertParityResult: (scenario: AdapterParityScenario, res: ParityHttpResponse, adapter?: ParityAdapterId) => void;
+export declare const assertParityResult: (scenario: AdapterParityScenario, res: ParityHttpResponse) => void;

package/dist/types/security/crossProjectPolicy.d.ts

@@ -10,14 +10,16 @@
  * authorization boundary: any caller can echo an allowed `requestId` and a
  * matching operation context.
  *
- * To turn `allowedNamespaces` into a real control, supply
+ * To use `allowedNamespaces` in production, supply
  * {@link CrossProjectPolicyConfig.verifyProducerIdentity}: a server-side
  * hook that derives the producer namespace from a VERIFIED channel (mTLS
  * peer identity, gateway-authenticated JWT claims, service-mesh headers
- * stripped at the edge, ...). When the hook is present, the client-asserted
- * namespace must match the verified namespace and the allowlist is checked
- * against the verified value — the envelope is no longer trusted for the
- * authorization decision.
+ * stripped at the edge, ...). Production requests fail closed when a
+ * namespace allowlist is configured without this hook. In non-production,
+ * the evaluator logs a one-time warning and keeps the legacy advisory
+ * behavior: the client-asserted namespace must match the allowlist. When the
+ * hook is present, the client-asserted namespace must match the verified
+ * namespace and the allowlist is checked against the verified value.
  *
  * Client-side counterparts in `@modern-js/create-request` (identity binding,
  * operation contract validation) are developer-experience aids that fail
@@ -53,7 +55,7 @@ export interface CrossProjectPolicyConfig {
     allowUnknownOperations?: boolean;
     denyStatus?: number;
     /**
-     * Server-side hook binding the producer namespace to a VERIFIED identity
+     * Server-side hook binding producer namespace to VERIFIED identity
      * channel (mTLS peer, gateway-authenticated JWT, mesh identity headers).
      *
      * When provided, the namespace asserted by the client envelope must match
@@ -61,8 +63,9 @@ export interface CrossProjectPolicyConfig {
      * against the verified value instead of the client-asserted one. Returning
      * `undefined` (identity could not be verified) denies the request.
      *
-     * Without this hook the namespace checks are advisory only — see the
-     * module-level threat model.
+     * In production, `allowedNamespaces` requires this hook and fails closed
+     * without it. In non-production, namespace checks without this hook remain
+     * advisory only — see the module-level threat model.
      */
     verifyProducerIdentity?: (headers: Record<string, unknown>) => string | undefined;
 }

package/package.json

@@ -17,7 +17,7 @@
     "modern",
     "modern.js"
   ],
-  "version": "3.5.0-ultramodern.3",
+  "version": "3.5.0-ultramodern.31",
   "types": "./dist/types/index.d.ts",
   "main": "./dist/cjs/index.js",
   "exports": {
@@ -36,7 +36,7 @@
     "koa-compose": "^4.1.0",
     "reflect-metadata": "^0.2.2",
     "type-fest": "5.7.0",
-    "@modern-js/utils": "npm:@bleedingdev/modern-js-utils@3.5.0-ultramodern.3"
+    "@modern-js/utils": "npm:@bleedingdev/modern-js-utils@3.5.0-ultramodern.31"
   },
   "devDependencies": {
     "@rslib/core": "0.23.1",
@@ -45,8 +45,8 @@
     "@typescript/native-preview": "7.0.0-dev.20260628.1",
     "tsconfig-paths": "^4.2.0",
     "zod": "^4.4.3",
-    "@modern-js/bff-runtime": "npm:@bleedingdev/modern-js-bff-runtime@3.5.0-ultramodern.3",
-    "@modern-js/types": "npm:@bleedingdev/modern-js-types@3.5.0-ultramodern.3",
+    "@modern-js/types": "npm:@bleedingdev/modern-js-types@3.5.0-ultramodern.31",
+    "@modern-js/bff-runtime": "npm:@bleedingdev/modern-js-bff-runtime@3.5.0-ultramodern.31",
     "@scripts/rstest-config": "2.66.0"
   },
   "peerDependencies": {